Data Insight User Guides
DDR Error Log – Runtime Error Analysis & Troubleshooting Guide
This guide explains how to access and use the DDR Error Log from the DDR Dashboard when an export fails, does not complete successfully, or requires technical investigation. The Error Log helps users analyse source and target runtime dumps, review ABAP runtime errors, identify the system where the issue occurred, and support faster technical resolution.
Purpose of the DDR Error Log
The DDR Error Log is used when a replication export fails, stops unexpectedly, shows an error status, or does not complete as expected. It provides a guided way to check whether the issue occurred on the source system, target system, or during runtime processing.
The Error Log is especially useful for analysing ABAP runtime dumps, memory dumps, MESSAGE_TYPE_X errors, RFC-related failures, cancelled programs, and workprocess issues. It gives users a structured view of technical errors without immediately needing to manually navigate through every SAP system.
Key point: The DDR Error Log does not replace standard SAP troubleshooting. It provides a central DDR entry point to quickly identify the issue. Users can also validate the same problem directly in SAP using SM37, ST22, SM21, SM50, and SM66.
Access the Dashboard and Select the Failed Export
From the DDR Central Console, select Dashboard from the left-hand navigation menu. The Dashboard displays the available exports, export status, template name, export ID, run ID, source logical system, target logical system, active status, created by, changed by, and message information.
If an export fails, does not complete, or shows an error indicator, select the failed export row by clicking the radio button before the export. This ensures the Error Log analysis is performed against the correct replication run.
Open the Error Log from the Dashboard Toolbar
After selecting the failed or error export, click the Error Log button from the Dashboard toolbar. DDR opens the Error Log popup and allows the user to select the relevant RFC connection.
The selected RFC connection determines which SAP system is checked for runtime dumps. This is important because a replication issue can occur on the source side during extraction, or on the target side during loading and processing.
Choose Source Dump or Target Dump
DDR provides two analysis options within the Error Log popup:
- Source Dump: Use this option when the issue is suspected during source data extraction, source table reading, selection logic, package generation, or source-side processing.
- Target Dump: Use this option when the issue is suspected during target insertion, target update, deletion before load, database commit, target workprocess execution, or target-side processing.
Selecting the correct dump location helps the support team quickly understand where the runtime failure occurred.
Review ABAP Runtime Errors
Once Source Dump or Target Dump is selected, DDR displays the ABAP runtime error records found for the selected SAP system. This may include the runtime date, time, application server, user, client, runtime error, cancelled program, and workprocess index.
In the example below, the target system shows repeated MESSAGE_TYPE_X runtime errors. This type of error normally requires technical investigation by the SAP BASIS, ABAP, or EDI support team.
How to Investigate the Error
DDR Error Log gives the first-level view of the issue from the Dashboard. For deeper investigation, the same issue should also be validated directly in SAP using standard transactions.
| Check Area | Recommended Transaction | Purpose |
|---|---|---|
| Background job status | SM37 | Check whether the job completed, cancelled, failed, or is still running. Review job logs and runtime steps. |
| ABAP runtime dump | ST22 | Review the full ABAP dump details, exception text, call stack, source code position, and memory/runtime information. |
| System log | SM21 | Check SAP system level messages, RFC communication issues, update failures, and application server events. |
| Active workprocesses | SM50 / SM66 | Review active or cancelled workprocesses and identify runtime bottlenecks or long-running processing. |
| DDR monitoring | DDR Monitoring | Use the DDR Monitoring guide to identify which stage, table, package, source, or target area experienced the issue. |
Important: If the error is memory related, review the package size, batch size, source workprocess allocation, target workprocess allocation, SAP memory configuration, and available system resources before restarting the replication.
Common Error Types and What They Usually Indicate
| Error Type | Possible Meaning | Recommended Action |
|---|---|---|
| MESSAGE_TYPE_X | Critical ABAP runtime termination. The program deliberately stopped due to an unexpected runtime condition. | Check ST22, review the dump call stack, validate the program/include, and escalate to EDI support if required. |
| Memory dump | The package size, batch size, or workprocess allocation may be too high for the available SAP memory. | Reduce package size and batch size, then rerun or resume using controlled runtime parameters. |
| RFC failure | Communication issue between DDR central, source, or target system. | Validate RFC destination, authorisation, network availability, and target system availability. |
| Database update or insert error | The target system may have database locks, missing structures, authorisation issues, or data consistency problems. | Check target dump, target job log, ST22, SM21, and table level details. |
| Cancelled background job | The background process was cancelled due to runtime error, manual cancellation, system restart, or workprocess termination. | Check SM37 and DDR Monitoring to identify where the process stopped. |
Benefits of the DDR Error Log
The Error Log provides a faster and more structured way to identify runtime issues during DDR replication. It helps technical and operational teams reduce investigation time and improve support response.