Ansicht
Dokumentation
RJGDPP_EOP_DETERMINE - Define Residence End for Each Business Partner
PERFORM Short Reference Vendor Master (General Section)This documentation is copyright by SAP AG.
Purpose
This report calculates the residence end for each business partner and application object. Results are displayed in the table JYTDPP_SORT. This report should be scheduled at regular intervals, since the results it provides are the prerequisite for the report BUPA_PREPARE_EOP that is used to block business partners. You should therefore always execute this report immediately before executing the report BUPA_PREPARE_EOP.
Integration
Prerequisites
If you want to maintain various residence durations according to the application object (order, billing document, settlement), record suitable rule groups in the retention rules for the ILM objects affected and assign rule variants to these rule groups in the Customizing settings for the SAP Business Partner. The system determines the rule groups and rule variants that apply to the respective business partner for each application object from the assigned ILM object and determines the residence durations on the basis of the rule variants. You maintain the residence durations in the Information Lifecycle Manager for each BP category and rule variant.
You maintain rule groups in ILM using the transaction IRM_CUST_CSS. You maintain retention and residence rules using the transaction IRMPOL. You maintain retention rules in your own audit area for the respective ILM objects. You maintain residence rules in the audit area BUPA_DP for the ILM object CA_BUPA.
If you want to define residence durations independently of the respective business for a partner, it is sufficient to maintain one rule for the application ISM with a blank rule variant. The system then determines one residence duration for each business partner.
Features
The report performs dynamic parallel processing and distributes data processing between various work processes. You can enter a package size for the database selections and a package size for processing data in a task. The first defines the number of entries that are read from the database for each database selection. This data package is processed in one or more tasks, where the package size indicates how many entries are processed collectively in each task. This means that the DB selects package size is always the same or larger than the package size for each task. Depending on the mode, the package size either refers to the number of records from the table JYTDPP_INDEX (delta processing) or the number of records from the table BUT000 (restructure).
In the delta mode, triggers are read from the table JYTDPP_INDEX (restricted to the BPs and application objects selected) and then processed. Triggers with errors remain in the database and successfully processed triggers are deleted.
If you want to calculate the residence durations independently of the existing triggers, start the report in the restructure mode. This is for example necessary during the go-live for Data Protection and Privacy or if you have changed rules in the Information Lifecycle Manager.
You can restrict the number of work processes to be used or create your own server group for this report.
Selection
Standard Variants
Output
The report generates an application log that you can access at any time using transaction SLG1 when the log is saved. You can define the level according to your requirements here. Log level 1 means that only serious errors, such as missing Customizing settings or RFC errors are logged. Log level 4 means that the residence periods are listed for every business partner and application object. Information about open business transactions, such as billing indexes that have not been processed, is also recorded for business partners who have finite residence periods in log level 4.
Activities
Example
CPI1466 during Backup CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 4168 Date: 20240531 Time: 061744 sap01-206 ( 105 ms )
