Data Insight User Guides
DDR – Delete Complete Master and Transaction Data
This guide outlines how to perform Master and Transaction Data deletion using the DDR Data Deletion application. It provides a structured step-by-step approach, along with critical warnings and security controls such as loopback RFC usage, ensuring data is removed safely and effectively within non-production SAP environments while preventing any risk to production systems.
The Master and Transaction Data deletion option in Dynamic Data Replicator (DDR) allows authorised users to remove both master data and transactional data from a target SAP system in a controlled manner.
Master and transaction data deletion is a high-impact and destructive activity. It must only be executed in approved non-production or controlled environments. Before execution, confirm that the correct target system has been selected, the deletion scope has been approved, and a valid backup or recovery option is available.
Select Master and Transaction data, then choose the approved loopback RFC connection to the target system.
From the DDR Central Console, click Shell from the left-hand navigation menu.
When the Shell Build popup appears, select Data Deletion to open the deletion options.
Choose the Master and Transaction data radio button. This option is used when both master records and transactional records must be deleted.
Select the approved loopback RFC connection pointing back to the target system. This prevents accidental deletion against production or external source systems.
Confirm that the selected option is Master and Transaction data and that the correct target system and connection have been selected.
Click Create to start the deletion job and monitor the execution logs from DDR.
DDR is designed to protect production systems from accidental deletion. For Data Deletion, users should not be allowed to select an RFC connection back to production or any external source system.
Deletes transactional data only while retaining master data and configuration.
Deletes both master data and transactional data from the selected target system.
Allows controlled deletion based on selected objects, tables, or approved deletion scope.
Confirm the target system is non-production, the selected RFC is the loopback RFC, backups are available, the deletion scope has been approved, key business users have been informed, no critical testing is active, and post-deletion validation steps are agreed.
Delete Complete Master and Transaction Data
This option is used when the target environment needs a deeper cleanup than transaction-only deletion. It is typically used for non-production systems, training clients, development systems, sandbox systems, or post-refresh cleanup scenarios where the business wants to retain the system structure and configuration while removing operational business data.
Warning and Disclaimer
This option can remove customer, vendor, material, transactional, and other operational business data depending on the configured scope. Once deleted, recovery may require system restore, reload, or re-replication. The user is responsible for validating the selected RFC connection, deletion option, and system before execution.
Step-by-Step Process
Security Control: Loopback RFC Only
The only permitted RFC for deletion should be the loopback RFC going back to the target system. This ensures the delete operation remains contained within the intended target environment.
Deletion Options Explained
Transaction Data
Master and Transaction Data
Selected Deletion
Pre-Execution Checklist