SAP Knowledge Base Article - Public

3459221 - Status of the package is invalid MDR

Symptom

Error raised in failed Mass Data run - Status of the package is invalid - example: Package 6: Status of the package is invalid"

Environment

SAP Cloud for Customer

SAP Business ByDesign

SAP Cloud Application Studio

Reproducing the Issue

Error is raised in a failed mass data run

Cause

1. What does this error message mean? Is there any reason for this to happen?

The error "Package 6: Status of the package is invalid" 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.

Solution: Optimize the number of instances processed within a package so that it gets finished within 10 hours. This will improve the performance of MDRO overall.

 2. Is there any impact in the backend?

There could be two reasons why the work package sub process didn't come back to the main process within 10 hrs.

  1. The work package dumped in the backend. In this case, the processing of the instances part of this package would have failed.
  2. The work package running for more than 10 hrs. In this case, the customer would notice that the business document would still be locked by the MDRO but the main process would show the package is invalid.

 Solution: optimize the number of instances processed within a package so that it gets finished within 10 hours. This will improve the performance of MDRO overall.

 3. Customer schedule 30 jobs in parallel - is there any restriction for the max amount of parallel processing?

There is no restriction as such. But this is very error prone and the chances of work package failing with lock error (based on the use case) are very high. Also to trigger work package we use RFC calls. If you consider a minimum of 6 work packages per job. Then it will be almost 180 RFC calls happening in the system parallelly which could result in failures based on the system performance and load. So it's not recommended to schedule these many MDRO jobs parallelly.

Resolution

optimize the number of instances processed within a package so that it gets finished within 10 hours. This will improve the performance of MDRO overall.

Keywords

Parallel processing, MDR, MDRO, Locking, locks , KBA , AP-RC-BDS-BO , ByDesign Studio BO definition/generation , Problem

Product

SAP Business ByDesign 2402