## 13.13.3.2.5.2  Deletion of Personal Data
SAP Waste and Recycling 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. SAP Waste and Recycling uses SAP ILM to support the deletion of personal data as described in the following sections.
SAP provides a check for the end of the usage and WUC (Where use Check) for SAP Waste and Recycling. The business partner assignments at the waste disposal facility (transaction EWAEL04 ) are checked (debtor, vendor and cBP for the owner of the waste disposal facility) due to the fact that waste disposal facilities are not part of the ILM implementation. If the assignment of the business partner data to the waste disposal facility is no longer valid, this data has to be removed from the waste disposal facility. After the removal of the business partner data from the waste disposal facility, this data is not further considered at the WUC.
All applications register either an end of purpose check (EoP) in the Customizing settings for the blocking and deletion of the customer, vendor and central business partner.
## 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.
## Integration with Other Solutions
In the majority of cases, different installed applications run interdependently as shown in following graphic.
## Relevant Application Objects and Available Deletion Functionality
SAP Utilities uses SAP ILM to support the deletion of personal data. For more information, see the documentation for Information Lifecycle Management at https:/ /help.sap.com.
Deletion Functionality
| Application         | Description                                             | Deletion Functionality   |
|---------------------|---------------------------------------------------------|--------------------------|
| TransactionEWAORDER | Standard application for changing waste disposal orders | ILM object ISU_EORDER    |
| Application             | Description                                                             | Deletion Functionality   |
|-------------------------|-------------------------------------------------------------------------|--------------------------|
| Transaction EWAWA01     | Standard application for maintaining single position weighing processes | ILM object ISU_WPROC     |
| Transaction EWAWA_MULTI | Standard application for maintaining multi position weighing processes  | ILM object ISU_MWPROC    |
| Transaction ELOC        | Maintaining service time slices for con- tainers                        | ILM Object ISU_SERVFQ    |
## Relevant Application Objects and Available EoP/WUC Functionality
The following end of purpose checks exist:
- Check for customer and vendor assignments for waste disposal facilities
- Check for partner assignment of bulky orders
The checks for the SAP Waste and Recycling object types can be enhanced in the enhancement spot EEWA\_BF\_DPP . For more information, see the documentation for the Business Add-Ins in the system.
## Process Flow
1. Before archiving data, you must define residence time and retention periods in SAP Information Lifecycle Management (ILM).
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. You do the following:
- Run transaction IRMPOL and maintain the required residence and retention policies for the central business partner (ILM object: CA\_BUPA).
- Run transaction BUPA\_PRE\_EOP to enable the end of purpose check function for the central business partner.
- Run transaction IRMPOL and maintain the required residence and retention policies for the customer master and vendor master in SAP ERP (ILM objects: ISU\_ROUTE, ISU\_SERVFQ, ISU\_WPROC).
- Run transaction CVP\_PRE\_EOP to enable the end of purpose check function for the customer master and vendor master in SAP ERP.
4. Business users can request unblocking of blocked data by using the transaction BUP\_REQ\_UNBLK .
5. If you have the needed authorizations, you can unblock data by running the transaction BUPA\_PRE\_EOP and CVP\_UNBLOCK\_MD .
6. You delete data by using the transaction ILM\_DESTRUCTION for the ILM objects of &lt;application, component, scenario&gt;.
For information about how to configure blocking and deletion for &lt;application, component, scenario&gt;, see Configuration: Simplified Blocking and Deletion.
## 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 in under Data Protection  Authorization Management. For more information, see the Customizing documentation.
- Define the settings for blocking in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking Business Partner .