Ansicht
Dokumentation

PPC_CONF_POST_PROC - Postprocessing Program for Archiving Object PPC_CONF

PPC_CONF_POST_PROC - Postprocessing Program for Archiving Object PPC_CONF

ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Postprocessing Program for Archiving Object PP_CONF

Purpose

The postprocessing program deletes data from the database tables for DI Backflush in the ERP system. In the case of this data, it cannot be determined definitely after the archiving whether it can be deleted. This data has a master data character. To determine whether this data can be deleted, it is necessary to perform extensive checks. The system performs these checks and any resulting deletions in the postprocessing program so that the archiving program and the actual deletion program are not slowed down.

Integration

The postprocessing program should run after the archiving program (PPC_CONF_ARCH_WRI) and the deletion program (PPC_CONF_ARCH_DEL) and you should schedule it regularly. It can run much less frequently than the archiving program and the deletion program.

Prerequisites

The postprocessing program can remove excess data with a master data character from the system only if the movement data for the backflush is archived and deleted regularly. You cannot therefore use the postprocessing program alone to reduce the amount of data in the system.

Features

Selection

Standard Variants

Output

Activities

The postprocessing program checks whether the data with movement data characteristics still exists for the data with master data characteristics. If this is not the case, the system deletes the data with master data characteristics. Locks must be set because these checks and the deletion work against the checking and writing of data for the backflush. This may mean that a backflush cannot be posted while the postprocessing program is running. The lock concept used keeps the lock times as short as possible. In addition, there can be competing accesses. It is recommended therefore that you run the postprocessing program at a time when no or significantly fewer backflushes than usual are posted.

The postprocessing program, among others, deletes data from the following tables:
PPC_ORD_INF (order information)
PPC_MAT (material information)
PPC_MAT_DET (material account assignment information)
PPC_ACT (activity information (resources))
PPC_RP_VERS (reporting point structure versions)

Example






ROGBILLS - Synchronize billing plans   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 2527 Date: 20240531 Time: 144330     sap01-206 ( 64 ms )