## 13.13.5.2.2  Deletion of Personal Data
## Use
The student administration of the Student Lifecycle Management application might process data (personal 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 Student Lifecycle Management (SLCM) solution uses SAP ILM to support the blocking and deletion of personal data as described in the following sections. SAP delivers an end of purpose check (EoP) for the students registered in the SLCM application. SAP delivers an end-of-purpose check (EOP) for the blocking of business partner data if the SLCM application has a student linked to a business partner. All applications register either an end of purpose check (EoP) in the Customizing settings for the blocking and deletion of the business partner data or a where-used check (WUC). n.
You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ / help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Data Protection .
## 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. . This 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 the Process Flow and Configuration: Simplified Blocking and Deletion.
## End of Purpose Check (EoP) in SLCM
The end-of-purpose check for SLCM is a simple check to ensure data integrity in the event of potential blocking. It checks whether there is any dependent data for a business partner that is a student in the SLCM application and returns one of the following statuses:
- If the business partner is not a student the system returns status as '1' (No business with business partner).
- If the business partner exists as a student in the SLCM system, then the system checks for the SORT (Start of retention time), and depending on the date,returns the status '2' (business is ongoing ) or '3' (business is complete).
The system does not block the business partner related to the student if the status is '3', business is ongoing .
## Relevant Application Objects and Available Deletion Functionality
| Archiving Object   | Description                                         |
|--------------------|-----------------------------------------------------|
| HRIQ_ACADW         | IS-HER-CM: Academic work - Admissions registrations |
| HRIQ_AD            | IS-HER-CM: Admission decision framework             |
| HRIQ_EXTTR         | IS-HER-CM: Student external transcripts             |
| HRIQ_FEE           | IS-HER-CM: Fee calculation document                 |
| HRIQ_MODBK         | IS-HER-CM: Module booking                           |
| HRIQ_PROC          | IS-HER-CM: Activity document                        |
| HRIQ_STAT          | IS-HER-CM: Statistical reporting                    |
| HRIQ_STGRT         | IS-HER-CM: Student grants                           |
| HRIQ_STMD          | Archiving Object for Student master data            |
| Archiving Object   | Description                                                                |
|--------------------|----------------------------------------------------------------------------|
| HRIQ_STYDT         | IS-HER-CM: Study data                                                      |
| HRIQ_ATTDN         | Attendance data                                                            |
| GFD_ARCH1          | Archiving for Admission Portal (Form Runtime) and MyRe- quest applications |
## Relevant Application Objects and Available Deletion Functionality
| Application   | Detailed Description                                          | Provided Deletion Functionality                                  |
|---------------|---------------------------------------------------------------|------------------------------------------------------------------|
| PSCM          | Student Lifecycle Management: Public Sector Campus Management | HRIQ_ATTDN Data Destruction in Stu- dent Lifecycle Management    |
| PSCM          | Student Lifecycle Management: Public Sector Campus Management | HRIQ_SPCD : Data Destruction for Stu- dent Special Category data |
## Relevant Application Objects and Available EoP/WUC functionality
| Application   | Implemented Solution (EoP or WUC)   | Further Information                                                                               |
|---------------|-------------------------------------|---------------------------------------------------------------------------------------------------|
| PSCM          | EoP implemented                     | EoP checks if the business for the stu- dent and related business partner is complete or ongoing. |
## Process Flow
1. Before archiving data, you must first 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 enter the required 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 S/4HANA (ILM objects: HRIQ\_STMD ).
- Run transaction CVP\_PRE\_EOP to enable the end of purpose check function for the customer master and vendor master in SAP S/4HANA .
4. Business users can request unblocking of blocked data for customers, vendors and central business partners by using the transaction BUP\_REQ\_UNBLK .
5. 5.If you have the necessary authorizations, you can unblock data by running the transaction BUPA\_PRE\_EOP and CVP\_UNBLOCK\_MD .
6. 6.You delete data by using the transaction ILM\_DESTRUCTION for the ILM objects of SLCM.
## 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 in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking Business Partner