cancel
Showing results for 
Search instead for 
Did you mean: 

DYNPRO_SEND_IN_BACKGROUND error when we change the userid

Former Member
0 Kudos

I have created a RFC which will run the program RPCEOYG0(GB year end report) by using BDC and we are calling the RFC by web dynpro application to get PDF form display. The input for this RFC is u2018USERIDu2019. Now the problem is that it is working fine for only one userid and for rest of the users it is not able to display PDF form in portal and in u2018ST22u2019 transaction Runtime Errors u2018DYNPRO_SEND_IN_BACKGROUNDu2019 are recorded. We have already checked the SU01 transaction for the authorization of other useridu2019s but everything is same for useridu2019d at SU01 transaction.

Can someone help on this?

Thanks,

Prashanth J R

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Prashanth,

This error occurs when you call an RFC that tries to get user input or run a report as if you we in the SAPGUI. There are also a number of other reasons you could receive this error, but if you do an external debugging on the RFC, it will narrow down your issue.

To External Debug,

Go to your RFC in transaction SE37

Click on Utilities --> Settings --> Debugging Tab

In the "External User" field, put the userid of the user you want to debug. This is who you will log in with on the portal or web side.

*Make sure the user you enter here has external debug permission

Go back to your RFC, find a line of code that is not a declaration, click on it, then click the external debugging button (It looks like a stop sign with a person in front of it).

Then run it from the web side and wait unitl the ABAP debug window pops up and step through the code to see where this ST@@ "DYNPRO ..." error is being generated.

Regards,

Tom

Former Member
0 Kudos

I tried this but this doesn't solve my problem

Former Member
0 Kudos

I was not able to find the reson for above dump but my actual problem is solved