Purpose
You can reorganize posting runs using the report, that is, delete thedata records of the posting runs.
You have to decide between simulation posting runs and productiveposting runs:

• Simulation runs:

Simulation posting runs can be reorganized with this report. This meansthat the task is not restricted to certain statuses. If these postingruns still have the status "deleted" prior to reorganization, thisis set during a successful reorganization.

• Productive posting runs:

Productive posting runs can only be deleted using the actualadministrative transaction for these posting runs. The administrativetransaction does not delete the data with the delete action, but justhighlights the posting run as deleted instead. Revision istherefore possible for deleted productive runs and deleted productiveruns can still be compared with newly created productive runs in termsof content.
If you actually want to delete the data with productive runs, you mustinitially delete these productive runs in the administrativetransaction and then remove this data permanently using this report.This means that the report only processes productive runs with thestatus "deleted".
After deleting, only a few control records exist for the posting runin the system. Using this information, the status history and theoverview of the attributes of the run are accepted. This data onlyrequires a very limited space.

Selection


• Run type: Specify for which run type you want to execute the
reorganization (ID 'PP).

• Run number: Here you can specify the runs, which are to be reorganized.


• Simulation runs: Choose this option, if you want to reorganize the
simulation runs. If this option is not selected, simulation runs thatare included in the group of selected runs, are not included.

• Productive deleted posting runs: Choose this option if you want to
reorganize productive (already deleted) posting runs. If this option isnot selected, these are not included.

• Ignore reorganized runs: If a posting run is successfully reorganized,
an appropriate attribute is set for the posting run. The report can thenrecognize that the run has already been reorganized. If the option isset, the posting runs that have already been reorganized are excludedfrom another reorganization (makes sense if the "run number" criteriais not regularly adjusted and therefore older runs are always selected.)

• Confirmation, Ask before deleting: If this option is selected, a log is
displayed after starting the report, where you have to confirm that youwant to delete the runs. The runs are then reorganized.
If this option is not set, reorganization of the runs occurs directlyafter starting the report. A log appears after the reorganization.

Example
The report is constantly set for the regular reorganization ofsimulation runs. This significantly reduces the burden on the tables ofHR posting transfer.
We recommend that the selection criteria are regularly adjusted withthe regular deployment of the report. This affects the selection ofthe runs. If the lower limit of this value set is not raised, old runsare consistently included. This impairs the performance of the reportconsiderably. If in such cases the "Ignore reorganized runs" option isnot set, eventually an overflow of the run status history can result forold posting runs.