Issue in RRI

[Former Member]

Hi All,

I have been facing an issue with RRI which is working fine in Development system. But when i moved it to UAT, it is not working.

I have created the RRI between the report and the R/3 transaction. When i try to navigate from the report to the transaction in dev, it is working. But when it is moved into UAT, I'm not able to do the same function.

The system is not throwing any dump or error message. But when i clicked on the goto option, the control remains in the report itself. It is not even asking for the logon credentials for the source system. I tried to debug the code, but not able to find out the reason for the issue.

This is the first time, i'm trying the RRI functionality in UAT. I have included RRI object in the transport.

I am using BW3.5.

Is there anything needed to be additionally included while transporting or any configuration needs to be done in the system to acheive the functionality of RRI between report to R/3?

Please help me to overcome this issue...

Regards,

Yokesh Kumar.

[Former Member]

RFC Connections need to be configured for enabling the 'Logon screen' option for the dialog user.

[emjay]

Hello

Did you check the RSBBS T-Code in UAT to see if the Src. System has been correctly mapped to the UAT (R3) system, If not then recheck teh conversion of source system name one more time and re-transport.

Thanks

[Former Member]

Hi,

I have checked the mapping in RSBBS. Everything is correct over there. And aslo, I found that the system is throwing a dump in the R3 with the error message,

"DYNPRO_SEND_IN_BACKGROUND"

"Screen output without connection to user"

But I could not figure out why the dump has thrown.

Is any one aware of this issue?

Regards,

Yokesh Kumar.

[Former Member]

same issue here...anyone have a solution?

[Former Member]

Hi All,

The issue is resolved now. We have made changes in the RFC settings for the dialog user where the Logon screen option needs to be enabled.

Now it is working fine.

Regards,

Yokesh Kumar.