This dump is because of Batch input sessions in SM35 for both these transactions. Which is trying to get some input through a screen, but since running in background it is not able to send the screen. Refer to the ST22 dumps pasted at the top. Error analysis During background processing...
Just read the doc on call trans and found out by default that NOBINPT = 'X'. The main reason this dump occurs, I think, is that the mode was set to 'E' instead of 'N'. Setting it to 'E' would result in an error screen popping up if the message control was set that way. R...
but changed to immediate, after the change, the background billing document process triggered the output process and then the dump took place. After we rollback the "without immediate output"action, the issue solved.
When press approves, you will notice a DUMP 'DYNPRO_SEND_IN_BACKGROUND'in the backend on your system. Please help me to resolve this issue Cause of the Error Typically, SAP generates theDYNPRO_SEND_IN_BACKGROUNDshort dump when a dialog screen (DYNPRO) is accidentally triggered during backgro...
Solved: Hello, I sometimes get a shortdump in my workflow and the background process is not triggered then. DYNPRO_SEND_IN_BACKGROUND Can anybody tell me what kind of