Data Insight User Guides
DDR Housekeeping Module: Log Maintenance and Deletion Guide
This guide explains how to use the DDR Housekeeping module to identify, review, and delete old log entries from SAP source and target systems. The module helps keep DDR operational tables clean, reduces unnecessary log growth, protects system performance, and gives administrators a controlled process for clearing historical execution logs linked to a selected connection, export ID, and run ID.
Purpose of the Housekeeping Module
The DDR Housekeeping module is designed to manage and delete old log entries from both source and target SAP systems. Over time, DDR execution logs can grow significantly because every data refresh, object refresh, system refresh, validation activity, and technical execution step can generate operational records.
If historical logs are not maintained, the log tables can increase in size and affect performance during dashboard loading, monitoring, reporting, technical troubleshooting, and database housekeeping. This module gives authorised users a structured way to select the relevant job context and safely remove old records through the configured DDR connection framework.
Key point: Housekeeping should be used for completed or obsolete runs only. Before deletion, users should confirm that the selected export ID and run ID are no longer required for audit review, customer evidence, or active issue investigation.
Access DDR from the Main Console
The DDR main console provides access to all core Dynamic Data Replicator functions, including Home, Connection, Template, Shell, Utilities, Data Refresh, Object Refresh, System Refresh, Dashboard, Monitoring, Admin, User Guide, Installation Check, Data Validation, and Support.
Housekeeping is available from the template related navigation area where users can work with selected execution information and review log records linked to historical DDR jobs.
Open the Housekeeping Tab
From the relevant DDR template screen, select the Housekeeping tab. This tab contains the input fields used to select the exact log deletion scope. The screen is intentionally simple so the user can focus on the three key values required for safe housekeeping.
Selects the target DDR connection where the housekeeping activity will be executed.
Displays export IDs available for the selected connection.
Displays run IDs linked to the selected export ID.
Select the Connection
Select the required Connection from the dropdown. The connection determines the SAP source and target landscape that DDR will use for housekeeping. Once the connection is selected, DDR retrieves the available export IDs linked to that connection.
| Field | Purpose | Technical Behaviour |
|---|---|---|
| Connection | Identifies the configured DDR source and target relationship. | DDR uses the connection configuration and RFC destinations to read available housekeeping values. |
| Export ID | Restricts housekeeping to a specific DDR export execution set. | DDR filters the available run IDs based on the selected export ID. |
| Run ID | Restricts housekeeping to the selected run under the export ID. | DDR fetches source and target log counts linked to the selected run. |
Technical note: The connection value is important because housekeeping is not a local only activity. DDR must communicate with the relevant SAP systems using the configured RFC route so that source and target log records can be counted and deleted consistently.
Select the Export ID and Run ID
After selecting the connection, choose the required Export ID. DDR then displays the available Run ID values related to that export ID. Select the run that needs to be reviewed for housekeeping.
This three level selection prevents accidental deletion across unrelated refresh jobs. It ensures that the user first chooses the connection, then the export context, and finally the exact run context before any deletion action is performed.
- User selects the connection and DDR fetches the available export IDs.
- User selects the export ID and DDR fetches the linked run IDs.
- User selects the run ID and DDR prepares the log review scope.
- User reviews the displayed source and target records before deletion.
Fetch and Review Log Records
Once the connection, export ID, and run ID are selected, DDR retrieves the number of log records from the source and target systems. The output table displays the export and run identifier, table name, source records, source database size, target records, and target database size.
This review step is critical because it gives the administrator visibility of what will be affected before deletion is executed. It also helps identify whether log records exist on the source, target, or both systems.
Delete Old Log Entries
After the log records have been fetched and reviewed, the user can proceed with the deletion action. DDR deletes the selected log records from the relevant source and target systems using the configured RFC connections.
The deletion should only be performed when the selected run is no longer needed for operational monitoring, customer reporting, audit support, or issue diagnosis. For production support scenarios, it is recommended to retain logs until the refresh cycle has been fully signed off.
Confirm the connection, export ID, run ID, table records, and database size values are correct.
Refresh the screen or fetch the records again to confirm that obsolete logs have been removed.
Housekeeping Process Flow
| Step | User Action | DDR System Action | Outcome |
|---|---|---|---|
| 1 | Select connection | DDR reads the configured connection and fetches export IDs. | Export ID dropdown is populated. |
| 2 | Select export ID | DDR filters run IDs linked to the selected export. | Run ID dropdown is populated. |
| 3 | Select run ID | DDR calculates source and target log records for the selected run. | Record counts and database size values are displayed. |
| 4 | Review records | DDR presents affected log tables and record counts. | User confirms the deletion scope. |
| 5 | Delete logs | DDR deletes the selected source and target log entries using RFC. | Old housekeeping records are removed safely. |
Technical Behaviour
The Housekeeping module works by using the selected DDR connection to identify the relevant source and target system route. Based on the selected export ID and run ID, DDR reads the associated technical log tables and presents the volume of records available for housekeeping.
DDR checks log entries held in the source side logging tables for the selected run.
DDR checks log entries held in the target side logging tables for the selected run.
DDR uses the configured RFC paths to perform the housekeeping activity without manual table deletion.
The output shows affected technical log tables so the administrator can review what has been identified.
Source and target database size values help users understand how much log data is involved.
The deletion is driven by connection, export ID, and run ID to avoid broad unstructured clean up.
Advantages and Benefits
Regular housekeeping reduces unnecessary log volume, which can improve screen loading, monitoring response, and technical reporting performance.
Old execution logs can consume database space over time. Controlled deletion helps keep DDR operational tables lean.
Administrators can remove obsolete runs and keep monitoring screens focused on current and relevant activity.
The selection process reduces risk by forcing users to choose the exact connection, export ID, and run ID before deletion.
Housekeeping is not limited to one side of the landscape. It can manage relevant logs across both systems through DDR connectivity.
Users do not need to manually identify and delete log records table by table. DDR provides a guided operational process.
Recommended Operating Practice
- Use housekeeping only for completed or historical runs that are no longer under investigation.
- Keep logs for active refreshes, failed jobs being analysed, customer evidence packs, and support tickets until sign off is complete.
- Confirm the connection, export ID, and run ID before deleting any record set.
- Review source and target record counts before deletion so the housekeeping impact is understood.
- Run housekeeping periodically as part of DDR administration, especially in active test data management landscapes with frequent refresh cycles.
- Restrict housekeeping access to authorised administrators only.