Atlas Diagnostic

SAP IDoc diagnostics

Trace IDoc failures from creation through partner profile to final posting status.

Reviewed

Core idea

IDocs fail at four points: creation, dispatch, receipt, and application posting. The status monitor shows the last failure, but the first error status in the history usually points to the real cause. The diagnostic job is to read the history from oldest to newest and trace the first error to partner profile, port, segment, or application validation.

Common symptoms

  • Expected business document was not created from an inbound IDoc.
  • Outbound IDoc was not sent to the partner system.
  • IDoc shows status 51, 56, or 62 in the status monitor.
  • IDoc was sent but the receiving system reports a format error.
  • Duplicate IDocs create duplicate business documents.

Likely causes

  • Partner profile missing: the logical system or partner is not configured for the message type.
  • Port issue: RFC or file port used by the IDoc is unavailable.
  • Segment error: mandatory segment is missing or a value violates the IDoc type definition.
  • Application posting error: the IDoc arrived correctly but the business document failed validation.
  • Queue issue: qRFC queue is stuck and prevents sequential processing.
  • Duplicate IDoc: same message was resent and processed twice.

Where to check in SAP

  • WE02 / WE05 — IDoc status monitor.
  • WE20 — partner profiles.
  • WE21 — port definitions.
  • BD87 — IDoc reprocessing.
  • SM58 — asynchronous RFC errors.
  • SMQ1 / SMQ2 — qRFC outbound and inbound queues.

Key tables / transactions / objects

  • EDIDC — IDoc control record.
  • EDIDD — IDoc data segments.
  • EDIDS — IDoc status records.
  • EDPP1 / EDP13 — partner profile message control.
  • TBDLS — logical systems.

Diagnostic workflow

  1. Find the IDoc number from the business document reference or message trace.
  2. Open WE02/WE05 and review the status history from creation to final status.
  3. Identify the first error status and its text.
  4. For outbound errors, check partner profile, port, and RFC destination.
  5. For inbound errors, check segment data, business document validation, and queue status.
  6. Fix the root cause before reprocessing.

Typical fixes or next actions

  • Maintain the missing partner profile or message type assignment.
  • Restore the RFC or file port used for transmission.
  • Correct segment values or mapping in the sending system.
  • Fix the underlying business document validation error and reprocess.
  • Clear the qRFC queue and reprocess in correct sequence.

What to capture first

Before routing the issue, capture: IDoc number, direction, message type, partner, first error status, and error text. Reprocessing without fixing the cause produces more failed IDocs and makes the original failure harder to read.

Boundaries and non-goals

This page is a diagnostic frame, not an IDoc configuration guide. It does not cover partner profile setup, port or RFC destination configuration, IDoc segment design, or AIF mapping. It does not replace SAP's IDoc and ALE documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.

Related diagnostics