Data Insight User Guides
DDR – Selected Data Deletion
Selected Data DeletionThe DDR Selected Data Deletion feature enables controlled and targeted removal of data within SAP systems. It supports both time-based and object-based deletion approaches, allowing users to define precise data scopes using date ranges, business objects, and filters. The DDR Selected Data Deletion feature enables controlled and targeted removal of data within SAP systems. It supports both time-based and object-based deletion approaches, allowing users to define precise data scopes using date ranges, business objects, and filters. With built-in controls such as loopback RFC restriction, business object dependency handling, and optional backup functionality, DDR ensures that data deletion is executed securely and accurately. This functionality is commonly used for system preparation, data cleanup, and maintaining optimised SAP environments while minimising risk.
The Selected Data Deletion function within Dynamic Data Replicator (DDR) enables controlled and targeted removal of data from a selected SAP system.
Selected Data Deletion is a destructive operation.
From the DDR Central Console, select Shell. In the Shell Board Dashboard, click New. In the pop-up window, select Data Deletion. Select Selected Deletion. Choose either Time-Based Deletion or Object-Based Deletion.
After selecting Time-Based Deletion, DDR prompts you to choose a template option.
Enter a meaningful Template Name, for example FI_Transaction_Deletion_Jan2024.
Define the deletion window.
Select the required data category:
DDR displays the available business object list. You can select one business object, select multiple business objects, use the description search to find a specific object, and review the related tables on the right-hand panel.
DDR allows customer-specific tables to be included in the deletion scope. This includes Z tables and Y tables.
You can refine the deletion scope by applying additional filters, such as company code, plant, document number, material, customer, vendor, or other key fields.
Click the field selection icon to add detailed conditions. This allows you to add additional selection criteria, restrict deletion to specific records, exclude specific tables or data, and prevent certain records from being deleted.
Exclusion rules allow you to protect specific records from deletion. They can be used to protect sensitive records, prevent deletion of business-critical data, exclude specific tables, exclude selected field values, and reduce the risk of unintended deletion.
Before executing deletion, you can enable Backup. A backup is strongly recommended when the deletion scope is large, the data may need to be restored, the deletion is part of testing or validation, or the impact is not fully confirmed.
Once all configuration, filters, exclusions, and backup options have been validated, click Data Deletion. The deletion process runs in the background, data is deleted from the selected target system, the template is locked for execution tracking, and the deletion run can be reviewed for audit and control purposes.
✔ Correct system and client
Selected Data Deletion – Time-Based and Object-Based Deletion
1. Overview
It supports two deletion approaches:
Time-Based Deletion: Deletes data within a defined date range, such as document creation date or change date.
Object-Based Deletion: Deletes data based on selected business objects, tables, fields, and filters without using a date range.
This guide explains how to execute Time-Based Selected Data Deletion.
2. Important Warning and Disclaimer
Once data is deleted, it cannot be recovered unless a valid backup has been taken before execution.
Before proceeding, ensure that the correct target system and client have been selected, the RFC connection is correctly configured, the selected business objects, tables, and filters have been validated, a backup has been taken where required, and the activity has been approved through the correct change control process.
This function must only be used by authorised DDR users who understand SAP data relationships, dependencies, and deletion impact.
3. Step-by-Step Guide – Selected Data Deletion
4. Template Selection
Standard Template: A pre-delivered EDI template or a template reused from a previous run.
Custom Template: Used when designing a new deletion configuration.
Blank Template: Used to build a deletion template from scratch.
Copy and Customise: Used to copy an existing template, modify the selection, and run it under a new execution ID.
For this guide, select Custom Template followed by Blank Template.
5. Define Template and Connection
Select RFC Connection as the transfer type.
Select the loopback RFC connection for the SAP system where the deletion will be executed.
Once completed, click Next.
6. Define Date Range
From Date: The start date from which data should be deleted.
To Date: The end date up to which data should be deleted.
Example: From 01.01.2023 to 31.12.2023.
7. Select Business Object Group
Master Data: Allows deletion of full master data or selected master data using date filters and granular field-level filters.
Process-Based Data: Deletes data across full business processes.
Transaction Data: Provides comprehensive deletion of transactional records, including dependent and associated records.
Customising: Used for configuration-level data where applicable.
Users: Used for user-related records where applicable.
For this demo, select Transaction Data. You can also review which tables will be included by checking the table list next to the object description.
8. Select Business Objects
After selecting the required business objects, click Include.
9. Include Custom Tables
Important: Custom tables may contain critical business data. Always validate custom table selection before including them in a deletion run.
10. Apply Granular Filters
11. Add Advanced Field Conditions
12. Exclusion Rules
13. Backup Option
14. Execute Data Deletion
Final Validation Checklist
✔ Correct RFC connection
✔ Correct deletion type
✔ Date range is accurate
✔ Business object group is correct
✔ Business objects are validated
✔ Related tables have been reviewed
✔ Z and Y tables have been checked
✔ Filters have been applied correctly
✔ Exclusions have been defined
✔ Backup has been taken, if required
✔ Business approval has been received
✔ Change control approval has been completed