SAP Note 19056 - SIS reorganization: Shorter runtimes by parallel processing

Symptom:

The documentation on reorganization in the Sales Information System states that reports RMCVNEUA, RMCVNEUL,and RMCVNEUF must run in sequence. This is necessary because the reports RMCVNEUL and RMCVNEUF require information for the redetermination of the update group which is written into buffer tables by previous reports. If no update group needs to be determined (and thus no document update) during the reorganization because the update group is already correctly set in all documents, you can execute the reports RMCVNEUA, RMCVNEUL, and RMCVNEUF in parallel. Set the parameters for the reports in such a way that they neither determine the update group again nor update the documents. On multi-processor computers, running the reports in parallel can help to reduce the runtimes considerably.
If, because of changes in update Customizing, you must redetermine the update group, you can follow the procedure below to determine the update group before the actual reorganization. Then you can take advantage of the option of running the reports in parallel as described above. In addition, the redetermination can take place at a time different to the reorganization.

• Make the settings for update Customizing according to your requirements.

• Start Report RMCVNEUA with the following parameters:

• Info structure: S999 (or another info structure that does not yet exist)

• Redetermine update group: X

• Update documents: X

• Start Report RMCVNEUL after the execution of RMCVNEUA with the following parameters (ignore the occurring errors):

• Info structure: S999 (or another info structure that does not yet exist)

• Redetermine update group: X

• Update documents: X

• Number of tolerated incorrect documents: 999999999

• Start Report RMCVNEUF after the execution of RMCVNEUL with the following parameters (ignore the occurring errors):

• Info structure: S999 (or another info structure that does not yet exist)

• Redetermine update group: X

• Update documents: X

These reports set the update group in all documents. They require considerably less time because they do not have to execute an update due to the non-existing info structures.

Irrespective of this, you can also execute the reports in parallel by starting several runs of the same reorganization report respectively. To do this, you must divide the documents to be updated in separate packages, for example by selecting certain document numbers.

Caution:
If the different reports which run at the same time attempt to access the same records of the statistics tables at the same time, DEADLOCKS may occur. To prevent this, you may not be able to run all reports at the same time but you have to plan them in such a way concerning their sequence that they do not write to the same data records at the same time. However, their is no general "recipe" for this. The suitable sequence to be selected depends on the key fields and the time of the update. In addition, make sure that all notes for avoiding deadlocks listed in Note 385372 are implemented.

Cause and prerequisites

*

Solution
*

Additional key words

Performance, RMCVNEUA, RMCVNEUL, RMCVNEUF, speed