Block Customer and Vendor Master Data

You can use the Block and Unblock Customer and Vendor Master Data report (transaction CVP_PRE_EOP) to block data related to customers and vendors. The report checks with the dependent applications if business is complete and the residence period is over and then blocks the customer and vendor master data.

You can no longer display, edit, create business objects or conduct follow-up activities with the blocked data. The blocked data can be displayed only by users having the appropriate permissions.

You can request unblocking of data that you might have blocked inadvertently using the Request Unblocking report (transaction BUP_REQ_UNBLK). For more information about the report, see Request Unblocking.

Prerequisites

You have maintained the residence period and retention period rules in the SAP Information Lifecycle Management (ILM) portal (transaction IRMPOL).
You are authorized to block customer and vendor master data. You can use this report if the authorization object B_BUP_PCPT is set with ACTVT 05 .

You have made the settings in Customizing required for blocking customer and vendor master data in Customizing under Logistics - General Business Partner Deletion of Customer and Vendor Master Data .

Features

Data to be Processed

You select whether you want to process customer master data or vendor master data.

You can further narrow down the data for which you want to trigger the end of purpose check using the following options:

Check on all data levels: EoP check is started on general level, so all the selected customers or vendors are checked and can be blocked.
Check only at company code level: EoP check is started on company code level, so only company code specific data of customers or vendors is checked and can be blocked.
Check only contact persons: EoP check is started for contact persons assigned to the selected customers or vendors. Only contact persons are checked and can be blocked.

End of Purpose Check Execution Mode

Interim Check (Local) w/o Setting Compl. Flag

You can run the report for the end of purpose check from the dependent systems as well. The Interim Check (Local) w/o Setting Compl. Flag enables you to conduct the EoP check for the data in the dependent systems. The completion flag, which denotes that the EoP check has been done for the data, is not set when you run the report with this option.

You can run the report from the master system also to trigger an interim check in the dependent systems. The completion flag is not set.

Overall Check (Remote) w/ Setting Compl. Flag

The overall EoP check for data can be triggered only from the main system after which the completion flag is set for the checked data.

Options

Skip Subsequent EoP Checks if Ongoing Business Found

If ongoing business is found for a master data in an application, the master data cannot be blocked. The report provides an option to optimize the EoP check; you can choose to skip subsequent EoP checks for the data from being conducted in the other applications.

Example Example

Three applications, APPL_1, APPL_2, and APPL_3 are registered for EoP check for master data A, B, and C. If APPL_1 has open business activities for master data A and B, then APPL_2 is called for master data C only. Again, if APPL_2 has open business activities for master data C, then APLL_3 is not called at all.

End of the example.

Consider Next Check Date

For data that has ongoing business activities, applications return a date when the next EoP check can be conducted. You can also set the default next check date period for a data by configuring the activity Define Next Check Date Period under Customizing for Deletion of Customer and Vendor Master Data. The report considers the default value if the application has not returned any next check date or if the next check date returned by the application is too far in the future.

If you select the Consider Next Check Date option, the report considers the next check date before triggering an EoP check for the data.

Processing Parameters

Number of Objects per Process

Specify the minimum number of objects per process. All dependent objects are handled in the same process. There is no strict upper limit, since the system ensures that all objects are always processed together.

However, processing runs in packages and the packages are formed internally, using SAP blocking logic. It is therefore a possibility that more objects will need to be processed in a package. When defining the package size, you should start with a value like 25, then measure the runtime and moderately increase or decrease the values as appropriate. Then measure the runtime again. The optimum package size needs to be predetermined for each system.

Parallel Processing

The report enables you to trigger parallel processing, that significantly improves runtime. Similar to synchronous processing, parallel processing also runs in packages. When you select this option, the default values for parallel processing made in Define Parallel Processing Settings under Customizing for Deletion of Customer and Vendor Master Data are used. You can also change these settings as per your requirement when you run this report.

Maximum Number of Parallel Processes and Maximum Utilization of Server Group
Specify the maximum number of parallel processes you want to run and the maximum utilization of the server group in percent.

The percentage of maximum utilization of the server group that you specify determines or restricts the maximum number of parallel processes, in relation to the work processes of the server group that are available at runtime. Therefore, ensure that you specify at least one of the two values when selecting parallel processing. If you specify one parameter, the number of parallel processes is defined using only this parameter. If you specify both parameters, the number of parallel processes is determined using the parameter that applies first.

Example
If you define 10 parallel processes as maximum and 50% maximum utilization, but after seven parallel processes you already reach 50% utilization of the server group, the report will not start another parallel process. Similarly, if you would have only 25% utilization with 10 parallel processes reached, the report will not start more than these 10 parallel processes to get the maximum utilization of 50%.

End of the example.

Server Group

In parallel processing several dialog work processes on one or more application servers are used for the processing, regardless of whether they are called from a dialog program or a background job. The server group specifies which application servers can be used to what extent for parallel processing. You must specify a server group to use parallel processing.

Processing Options

You can run the report in test mode to view the data that meets the end of purpose check criteria and can be blocked. In this mode data is not blocked.

Detail Log

Without Success Message

With this option, the log lists summary messages or error messages.

Complete

With this option, the log lists all successful EoP checks for each registered application.

Log Output

The options Application Log and List and Application Log enable you to save the logs so that they can be analyzed using the report Display Stored Application Logs for Customer and Vendor (transaction CVP_DISPLAY_LOG).

For more information about the report, see Display Stored Application Logs for Customer and Vendor.

Activities

To access this report from the SAP Easy Access screen, choose Cross-Application Components Data Protection Deletion of Customer and Vendor Master Data Block Customer and Vendor Master Data .

Based on the data you choose, and the execution criteria you specify, the report triggers an EoP check and blocks data. It stores the Start of Retention Time (SoRT) in the table SoRT Details of Customer/Vendor/Contact for Each Application (CVP_SORT) and blocks the customer and vendor master data by setting the blocking indicators in the master database tables.

More Information

Unblock Customer and Vendor Master Data