Show TOC

 Blocking Personal Data in IS-M

 

As of SAP Enhancement Package 7 for SAP ERP 6.0, Industry Extension Media (IS-M 618), support package 08, the business function Media, Blocking of Business Partner Data (MED_BP_BLOCKING) is available. This business function adds SAP Information Lifecycle Management (ILM) functions to SAP for Media (IS-M) and supports media companies in processing personal data according to defined rules (regarding retention obligations). ILM provides functions for processing the entire lifecycle of business partner data (such as subscription or advertiser data).

Prerequisites

If you want to use this business function, you must also activate the following business functions:

  • Information Lifecycle Management (ILM)

  • ILM-Based Deletion of Business Partners (BUPA_ILM_BF)

  • ILM-Based Deletion of Customers/Vendor Master Data (ERP_CVP_ILM_1)

Technical Details

Technical Name of Business Function

MED_BP_BLOCKING

Available As Of

SAP Enhancement Package 7 (SP08) for SAP ECC 6.0

Country Dependency

Valid for all countries

Software Component Version

IS-M 617

Application Component

IS-M (Media)

Effects on Existing Data

These functions mean you can use the component SAP Information Lifecycle Management (ILM) to delete personal data and to control the deletion and blocking of master data for business partners. The personal data collected in the business partner master data can be blocked once the business activities, for which this data is required, have been completed and the residence duration for this data has expired. After this time, this data can only be accessed by users with additional authorizations. If the retention period for this data has expired, it can be deleted completely, meaning that it can no longer be accessed. Retention and residence periods must be defined in the customer system.

Check Whether Blocking Is Possible in IS-M

You can use the transaction JGDPP_EOP_DETERMINE in the SAP menu under Start of the navigation path Media Sales and Distribution Next navigation step Periodical Sales and Distribution Next navigation step Master Data Next navigation step Business Partner Next navigation step Environment Next navigation step Data Protection Next navigation step Define Residence End for Each Business Partner End of the navigation path or under Start of the navigation path Advertising Management Next navigation step Master Data Next navigation step Business Partner Next navigation step Environment Next navigation step Data Protection Next navigation step Define Residence End for Each Business Partnerr End of the navigation path to check which business partners have reached the end of purpose and define their retention start using application-specific objects. The system saves the result of the check.

Using the SAP Business Partner to Block Business Partner Master Data

You block business partner master data using the blocking program in the SAP business partner (transaction BUPA_PRE_EOP in the SAP menu under Start of the navigation path Cross-Application Components Next navigation step Data Protection Next navigation step Block Business Partner Data End of the navigation path). To ensure that the IS-M check results are observed, the function module ISM_BUPA_EOP_CHECK is registered to check whether the end of purpose has been fulfilled for the ISM application. The residence duration recorded in ILM specifically for the ISM application defines the end of the usage period, from which the business partner can be blocked. The blocking program observes all application components that use a business partner. If none of the application components used here reports an open business transaction for a business partner and the residence duration has been exceeded, the program blocks the business partner master data. You can unblock the data again if necessary.

Working With Blocked Business Partner Master Data in IS-M

Checking the end of purpose defines whether data is still relevant for business activities on the basis of the retention period defined for the data. The retention period for data comprises the following phases:

  • 1. Phase: Relevant data is used actively.

  • 2. Phase: Relevant data is available actively in the system.

  • 3. Phase: Relevant data must be retained for other reasons.

It is for example no longer necessary to process data for the primary business purpose, but the legal regulations for retaining data, mean it must still be available. Relevant data is blocked during the third phase. Users of SAP applications can then no longer display and use data that contains personal data and is no longer relevant for business activities.

Blocking data can have the following implications on system response:

  • Display: The system no longer displays the blocked data.

  • Change: It is not possible to change a business object for a blocked SAP business partner.

  • Create: It is not possible to create a business object for a blocked SAP business partner.

  • Copy/Subsequent Activities: It is not possible to copy a business object with blocked data or perform subsequent activities.

  • Search: It is not possible to search for blocked data or to search for a business object using blocked data in the search criteria.

A user with then relevant authorization can display blocked data, but they are also not able to create, change or copy a business object for a blocked SAP business partner or perform subsequent activities. Displaying data for a blocked SAP business partner is controlled using authorization for the activity “03” in the authorization object B_BUP_PCPT.

Customizing

SAP Information Lifecycle Management (ILM)

Proceed as follows to simplify the deletion of application.specific and personal data using SAP Information Lifecycle Management (ILM):

  • Activate the business function Information Lifecycle Management (ILM).

  • Make the Customizing settings required for SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver under the following path: Start of the navigation path Application Server Next navigation step Basis Services Next navigation step Information Lifecycle Management End of the navigation path.

  • Execute the transaction IRMPOL and maintain the retention policies for the ILM objects in the application for the object category SAP Business Suite.

Blocking and Deletion of Business Partner Master Data

Proceed as follows to use the new simplified functions for blocking and deleting the business partner master data:

  • Activate the following business functions:

    • Information Lifecycle Management (ILM)

    • ILM-Based Deletion of Business Partners (BUPA_ILM_BF)

    • ILM-Based Deletion of Customers/Vendor Master Data (ERP_CVP_ILM_1)

    • Media, Blocking of Business Partner Data (MED_BP_BLOCKING).

  • Make the settings required for blocking and deleting business partner data in Customizing for Cross-Application Components under Data Protection.

  • If you have defined application rule variants, maintain residence rules with rule groups for the ILM object CA_BUPA for the SAP Business Suite in the transaction IRMPOL.

Media-Specific Customizing Settings

You make the media-specific Customizing settings from the following path: Start of the navigation path SAP Media Next navigation step Tools Next navigation step Data Protection Next navigation step Maintain Application Objects End of the navigation path.

Additional Information