## 13.13.3.1.3.1  Deletion of Personal Data
The Remote Logistics Management (RLM) might process data that is subject to the data protection laws applicable in specific countries as described in SAP Note 1825544 .
The SAP Information Lifecycle Management (ILM) component supports the entire software lifecycle including the storage, retention, blocking, and deletion of data. The Remote Logistics Management uses SAP ILM to support the deletion of personal data as described in the following sections.
- SAP delivers an end of purpose check for the Remote Logistics Management
All applications register either an End of Purpose (EoP) check in the Customizing settings for the blocking and deletion of the customer and vendor master or a Where Used Check (WUC). For information about the Customizing of blocking and deletion for Remote Logistics Management application , see Configuration: Simplified Blocking and Deletion.
## End of Purpose Check (EoP)
An end of purpose check determines whether data is still relevant for business activities based on the retention period defined for the data. The retention period of data consists of the following phases.
- Phase one : The relevant data is actively used.
- Phase two : The relevant data is actively available in the system.
- Phase three : The relevant data needs to be retained for other reasons. For example, processing of data is no longer required for the primary business purpose, but to comply with legal rules for retention, the data must still be available. In phase three, the relevant data is blocked. Blocking of data prevents the business users of SAP applications from displaying and using data that may include personal data and is no longer relevant for business activities.
Blocking of data can impact system behavior in the following ways:
- Display : The system does not display blocked data.
- Change : It is not possible to change a business object that contains blocked data
- Create : It is not possible to create a business object that contains blocked data.
- Copy/Follow-Up : It is not possible to copy a business object or perform follow-up activities for a business object that contains blocked data.
- Search : It is not possible to search for blocked data or to search for a business object using blocked data in the search criteria.
It is possible to display blocked data if a user has special authorization; however, it is still not possible to create, change, copy, or perform follow-up activities on blocked data.
For information about the configuration settings required to enable this three-phase based end of purpose check, see Process Flow and Configuration: Simplified Blocking and Deletion.
## End of Purpose Check in RLM
The end-of-purpose check for RLM ensures data integrity in the event of potential blocking. It checks whether the Vendor or Customer passed is present in the RLM specific tables and returns the following status:
- If there is no data present in the RLM tables the system returns a status of '1' (No business made with Vendor or Customer) back to the blocking report.
- If there is data present in the RLM tables the system returns a status of '2' (Business is ongoing with Vendor or Customer) back to the blocking report.
## End of Purpose Check in ERP Customer or Vendor
| Application                               | Rule                                                                                                                                              | Check                                                           |
|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
| RLM-P Shipping and Container Man- agement | Do not block the customer or vendor if there are any open status containers which have the customer or vendor as a partner.                       | Checks table OIO_CNTNR for any open status containers.          |
| RLM-R Returns Management                  | Do not block the customer or vendor if there are any open material returns or container returns which have the cus- tomer or vendor as a partner. | Checks table OIO_RT_RTDOC for any open status return documents. |
## Relevant Application Objects and Available Deletion Functionality
Archived business data is destroyed after the retention time has expired. This applies to the following application objects:
| Application                               | Archive Objects                                                                                     | Requirement            |
|-------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------|
| RLM-P Shipping and Container Man- agement | OIO_CTHST: RLMContainer History Data OIO_CNTNR: RLMContainer Master Data OIO_VOYAGE: RLMVoyage Data | Need to be ILM enabled |
| Application              | Archive Objects                                                  | Requirement            |
|--------------------------|------------------------------------------------------------------|------------------------|
| RLM-R Returns Management | OIO_RTDOC: Returns Document OIO_OBJFLW: RLMDocument Flow In- dex | Need to be ILM enabled |
## Process Flow
1. Before archiving data, you must define residence time and retention periods in SAP Information Lifecycle Management ( ILM ).
- Run transaction IRMPOL and maintain the required residence and retention policies for the customer master and vendor master in SAP S/4HANA (ILM objects: FI\_ACCPAYB , FI\_ACCRECV , FI\_ACCKNVK ).
- Run transaction IRMPOL and maintain the required retention policies for the ILM objects of Remote Logistics Management , application.
2. You choose whether data deletion is required for data stored in archive files or data stored in the database, also depending on the type of deletion functionality available.
3. To determine which business partners have reached end of purpose and can be blocked, you do the following:
- Run transaction CVP\_PRE\_EOP to execute the end of purpose check function for the customer master and vendor master in SAP S/4HANA.
4. To unblock blocked business partner data, you do the following:
- Request unblocking of blocked data by using the transaction BUP\_REQ\_UNBLK .
- If you have the needed authorization for unblocking business partner data, you can unblock the requested data by running the transaction CVP\_UNBLOCK\_MD for customer master data and vendor master data in SAP S/4HANA.
5. You delete data by using the transaction ILM\_DESTRUCTION for the ILM objects of Remote Logistics Management .
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components under Data Protection .
- Define the settings for authorization management under Data Protection Authorization Management For more information, see the Customizing documentation.
- Define the settings for blocking under Data Protection Blocking and Unblocking Business Partner