DYNPRO_SEND_IN_BACKGROUND Dump

Hello, SAP Experts

Dump DYNPRO_SEND_IN_BACKGROUND' is triggered in the backend while using some SAP MM Purchasing Fiori Applications.

This dump can be regenerated by following steps:

• First login into your SAP Fiori launchpad.
• Then choose any App for example 'Approve Purchase Orders' 
• 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 the DYNPRO_SEND_IN_BACKGROUND short dump when a dialog screen (DYNPRO) is accidentally triggered during background processing. This problem may arise if the system attempts to send a screen to the front end unauthorized while operating in background mode.

Steps to Resolve the DYNPRO_SEND_IN_BACKGROUND Dump:

1. Check for Recent Updates or Changes:

   • Check to see if the backend ABAP system or the SAP Fiori apps have received any recent updates or modifications (such as the application of support packages, OSS Notes, or the implementation of custom enhancements).

2. Debug the Dump:

   • To analyze the dump details, use t-code ST22 (ABAP Dump Analysis). The "Call Stack" section should be closely examined as it can provide insight into the precise code segment where the dump was initiated.

   Review Application Configuration:

   • Check the configuration of the affected Fiori application. Verify that the application is configured correctly and that neither the OData services nor the authorization settings are problematic.
   • Verify in the SAP Fiori Launchpad Designer that the backend services (like OData services) and SAP Gateway services are linked correctly and are operational.

3. Check Custom Code or User Exits:

   • Examine any user exits, custom code, or updated or changed BAdI implementations for the impacted Fiori application.
   • Search for any custom code that might be causing a screen output while the processing is happening in the background, and adjust it so that processing is handled correctly without bringing up a dialog box.

   Apply Relevant SAP Notes:

   • Look for OSS Notes about the DYNPRO_SEND_IN_BACKGROUND dump on the SAP Support Portal. See if there are any notes relevant to the SAP version and components you are utilizing.
   • Implement any suggested SAP Notes that deal with issues that have been identified with the impacted Fiori apps.

   Check the Fiori Application Log:

   • Use t-code SLG1 (Application Log) to review any application-specific logs for additional clues or errors.
   • Check the SAP Gateway Error Log (/IWFND/ERROR_LOG) for any related errors in the communication between the frontend and backend.

4. Adjust the User's Role and Authorization:

   • Check that the Fiori applications' user roles and authorizations are correctly assigned. Moreover, improper or missing authorizations could result in dumps.

5. Test in a Different Environment:

   • Try to reproduce the problem in a different SAP environment (such as Development or Quality) if at all possible. This can assist in identifying whether the issue is environment-specific.

6. SAP Support Contact:

   • If the issue still exists after attempting the previously mentioned fixes, consider opening a SAP Support ticket. Provide them with the replication instructions, the dump details, and any relevant system information.

You ought to be able to pinpoint the primary cause of the DYNPRO_SEND_IN_BACKGROUND problem and apply the required remedies by closely examining the dump's specifics and going over any recent modifications.