3772763 - Custom Mass Data Run fails with "rfc exception system_failure" or "work package status not valid"

• Custom Mass Data Run fails in the UI
• Error: "RFC exception SYSTEM_FAILURE raised; The application running deliberately caused an abort with short dump."
• Error: "Work package 1: Work package status not valid."
• In WorkCentre, the run shows finished status with error.

• SAP Cloud for Customer 
• SAP Business ByDesign

1. Go to Custom Mass Data Run Work Center.
2. Start the run and review the application log.
3. The Job ends in finished status with an error.

The Error: "RFC exception SYSTEM_FAILURE raised; The application running deliberately caused an abort with short dump." Can produce a Backend short dump “Failure deleting records of node AccessControlList.ENTRY in BO SERVICE_REQUEST” due to very large data volumes causing memory exhaustion or a work process exceeding the allowed memory.

“Work package 1: Work package status not valid” occurs when a work package subprocess does not return a result within 10 hours; the main process records this status and proceeds.

The dump with error happens whenever there is a huge amount of data to be processed which cannot be fit into the backend memory allocated/ if a work process exceeds the maximum memory that is allowed. This application cannot be controlled. 

 

Error Work package 1: Work package status not valid"

This Comes up when the work package sub process didn't come back to the main process with the result within 10 hours. After that the main process writes the above error into application log and will go on to trigger the next package execution.

1. Reduce the number of instances processed per MDRO work package so that each package completes well within 10 hours.
2. Implement smaller data packages/chunks and ensure memory is released between packages to avoid exceeding backend memory limits.
3. Optimize the custom PDI/ABSL implementation to fetch and process only the necessary data (minimize selects, avoid large in-memory collections, and remove unnecessary loops).
4. Re-run the MDRO after tuning to verify that no package exceeds the 10-hour limit and that no memory-related short dumps occur.
5. If required, iteratively adjust package size and data retrieval to stabilize run time to prior baseline.

• Refer to: Cloud Application Studio: Performance Check
• Refer to: Performance Improvements with ABSL
• Refer to: Performance ABSL Trace – New functionality
• Refer to: Cloud Application Studio Performance Best Practices

mdr, mass data run, rfc exception system_failure, short dump, work package status not valid, c4c batch job, service_request bo, accesscontrollist.entry, memory limit, package size, pdi, absl, performance tuning, application log, day band calculation , KBA , AP-RC-BDS-LM , ByDesign Studio Lifecycle Management , Problem

SAP Business ByDesign all versions ; SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions