DYNPRO_SEND_IN_BACKGROUND

[Former Member]

Hi,

We are creating PIR(Purchase Info Records) via a BAPI call from Informatica to ECC. This is a custom BAPI(RFC enabled), which does a call transaction to ME11. Now when informatica calls this BAPI to post PIRs, we have huge failure....the program is going on a dump (DYNPRO_SEND_IN_BACKGROUND:Screen output without connection to user), each time it shows a different screen number where a dump occurs. Now if informatica re-pushes the same set of data it gets successfully posted in ECC. We tried to debug the code by inserting an infinte loop and through SM50, but we are unable to see the call transaction even if the mode is A.Can u please help.

Thanks

[Sandra_Rossi]

Do you execute CALL TRANSACTION in E mode? If yes, and an error occurs, SAP tries to display the screen where the error happens and it dumps as it is called in RFC without SAPGUI dialog (as we can imagine as you get a DYNPRO_SEND_IN_BACKGROUND).

So, you'd better call it with N mode, and collect error messages to later analyze the issue (or convert the call transaction into batch input session to be able to replay the CALL TRANSACTION).

> We tried to debug the code by inserting an infinte loop and through SM50, but we are unable to see the call transaction even if the mode is A.

In mode A (or E), I don't understand how you could display the screen?

No, you must run in N mode, and get the error messages returned by the CALL TRANSACTION.