You can use the report RPCIPQ00 to reorganize posting runs, that is, delete their data records.
You have to decide between simulation posting runs and productive posting runs:
- Simulation runs:
- Simulation posting runs can be reorganized with this report. This means that the action is not restricted to certain statuses. If these posting runs still do not have the status “Deleted” prior to reorganization, this is set upon successful reorganization.
- Productive posting runs:
- Productive posting runs can only be deleted using the actual administrative transaction for these posting runs. The administrative transaction does not delete the data for the delete action, it just highlights the posting run as deleted instead. A type of revision is therefore possible for deleted productive runs, and deleted productive runs can still be compared with newly created productive runs in terms of content.
- If you want to actually delete the data for productive runs, you must first delete these productive runs in the administrative transaction and then remove the data permanently using this report. This means that the report only processes productive runs with the status “Deleted”.
- Note: Productive posted posting runs (status 40 or 50) and reversed posting runs (status 63 or 64) cannot be deleted.
Following deletion, only a few control records exist for the posting run in the system. With this information, you can view the status history and the overview of the attributes of the run. This data takes up very little space.
Each run that was deleted with this report receives the attribute ‘DELBYREORG: Deleted by Reorganization’.
Selection
- Run type:
- Specify for which run type you want to execute the reorganization (usually ‘PP’).
- Run number:
- Here you can specify the runs that are to be reorganized.
- Simulation runs:
- Choose this option if you want to reorganize simulation runs. If this option is not selected, simulation runs that are included in the quantity of selected runs are not considered.
- Productive deleted posting runs:
- Choose this option if you want to reorganize productive (already deleted) posting runs. If this option is not selected, they are not included.
- Delete: Run history:
- Select this option if you want to delete the run history of the deleted posting run. For each posting, the first status ‘NEW’ and the last status ‘DELETED’ are retained. This ensures a gap-free revision of the runs in the administration transaction. All other statuses are deleted (for example: “Document creation is running”, “Incorrect documents”…).
- Delete: Run attributes:
- Select this option if you want to delete the run attributes of the deleted posting run. For each posting run, the attributes program, payroll period, and release are retained so that the display is still possible in the management transaction.
- Ask before deleting:
- If this option is selected, once the report has started, a log is initially output where you have to confirm that you want to delete the runs. It is not until after this that the runs are actually reorganized.
- If this option is not set, the runs are reorganized as soon as the report starts. A log appears after the reorganization.
- If the report is started or scheduled in the background, the selected runs are deleted immediately, meaning that this option has no effect.
- Display rejected runs:
- Choose this option if you want to display runs in the log that were rejected for the reorganization (for example, because the status is not permitted, or because the run has already been reorganized).
- If the option is not selected, the log displays only the runs to be deleted and statistics.
Example
The report is often used for regular reorganization of simulation posting runs. This significantly reduces the burden on the tables of HR posting transfer.
With SAP Note 3508150, the report was extensively revised.
The option “Ignore Reorganized Runs” has been removed. As of now, the reorganized runs are ignored in general. This ensures that the run status table does not contain unnecessary status entries from regular reorganization.
We recommend that you delete the status history and the run attributes with the reorganization. This prevents the tables from growing too much, especially in systems with a posting history going very far back in time.
