## 13.2.4.3.3.1  Deletion of Personal Data
## Use
Cash and Liquidity Management 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. Cash and Liquidity Management uses SAP ILM to support the deletion of personal data as described in the following sections.
## Relevant Application Objects and Available Deletion Functionality
<!-- image -->
| Application                  | Detailed Description                                                                                                                                                                                                                                                                                                                                                                                    | Provided Deletion Functionality   |
|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|
| Bank Account Master Data     | You can destroy the bank account contact person data, namely the gen- eral contacts and the bank relationship managers that are maintained in the bank account master data. For more information about this object, see the Data Management in Cash and Liquidity Management topic. You can find this topic in the Product Assistance under Finance Treasury Management Cash and Liquidity Management . | Destruction object BAM_AMD        |
| One Exposure from Operations | You can destroy personal data that are stored in the database table FQM_FLOW , including business partners, custom- ers, and suppliers. For more information about this object, see the Data Management in Cash and Liquidity Management topic. You can find this topic in the Product Assistance under Finance Treasury Management Cash and Liquidity Management .                                     | Destruction object FQM_FLOW       |
<!-- image -->
<!-- image -->
<!-- image -->
| Application                                   | Detailed Description                                                                                                                                                                                                                                                                                                                                             | Provided Deletion Functionality         |
|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
| One Exposure from Operations                  | As an alternative to the ILM destruc- tion object FQM_FLOW , you can use this transaction to delete flows with certainty level ACTUAL in One Exposure and substitute them with aggregation flows. It helps to reduce the data vol- ume in database table FQM_FLOW and delete personal data. For more information, see the corre- sponding program documentation. | Transaction FQM_AGGREGATE_FLOWS         |
| One Exposure from Operations                  | As an alternative to the ILM destruc- tion object FQM_FLOW , you can use this transaction to delete transactional data in One Exposure from Operations to en- sure data protection and privacy. The deleted data will no longer be displayed in cash management reports. For more information, see the corre- sponding program documentation.                    | Transaction FQM_DELETE                  |
| Powers of Attorney for Banking Trans- actions | You can use the data destruction object FCLM_POA_DESTRUCTION to destroy powers of attorney for banking transac- tions. For more information about this object, see the Data Management in Cash and Liquidity Management topic. You can find this topic in the                                                                                                    | Destruction object FCLM_POA_DESTRUCTION |
## Relevant Application Objects and Available EoP/WUC Functionality
| Application                  | Implemented Solution                              | Further Information                                                                                         |
|------------------------------|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
| One Exposure from Operations | EoP check with function module FQM_BUPA_WUC_CHECK | It checks if business partners are still relevant for One Exposure from Opera- tions in the FQM_FLOW table. |
| Application                                   | Implemented Solution                              | Further Information                                                                                                                                                                                                                                              |
|-----------------------------------------------|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Bank Account Master Data                      | EoP check with function module FCLM_BAM_EOP_CHECK | It checks if business partners are still relevant for bank account management in the following tables: • FCLM_BAM_AMD • FCLM_BAM_BNKABP2                                                                                                                         |
| Powers of Attorney for Banking Trans- actions | EoP check with function module FCLM_POA_EOP_CHECK | Cash and Liquidity Management pro- vides an end of purpose (EoP) check to determine whether a business part- ner is still relevant for business activi- ties in the Manage Powers of Attorney for Banking Transactions application or whether it can be blocked. |
For more information about the above checks, see the Data Management in Cash and Liquidity Management topic. Y ou can find this topic in the Product Assistance under Finance Treasury Management Cash and Liquidity Management .
## Process Flow for Destroying Business Partners in Bank Account Master Data
To destroy business partner data in the bank account master data, proceed as follows:
1. Before deleting 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. Run transaction IRMPOL and maintain the required residence and retention policies for the central business partner (ILM object: BAM\_AMD ).
4. You delete data by using the transaction ILM\_DESTRUCTION for the ILM object BAM\_AMD .
## Process Flow for Destroying Business Partners, Customers, and Suppliers in One Exposure from Operations
To destroy business partner, customer and supplier data in One Exposure from Operations, proceed as follows:
1. Before deleting 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. Run transaction IRMPOL and maintain the required residence and retention policies for the central business partner (ILM object: FQM\_FLOW ).
4. You delete data by using the transaction ILM\_DESTRUCTION for the ILM object FQM\_FLOW .
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business data in Customizing for CrossApplication Components under Data Protection .
- Define the settings for authorization management under Cross-Application Components Data Protection Authorization Management .
- Check the following settings for blocking in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking of Data Business Partner .
- In the Define Application Names for EoP Check Customizing activity (view V\_BUTEOPAPP ), you find the following applications in the view:
- One Exposure from Operations ( FQM )
- Bank Account Management ( FIN\_FSCM\_CLM\_BAM )
- In the Define Application Function Modules Registered for EoP Check Customizing activity (view V\_BUTEOPFM ), you find a list of application function modules. Each application that consumes business partners registered their function module in this view. These function modules are called by the blocking/unblocking report when performing the end-of-purpose checks.
- FQM : Function module FQM\_BUPA\_WUC\_CHECK
- FIN\_FSCM\_CLM\_BAM : Function module FCLM\_BAM\_EOP\_CHECK
For more information about configuration, see the Customizing documentation.