Atlas Diagnostic

SAP inbound processing diagnostics

A first-pass structure for finding why an inbound message was not received, not posted, or created wrong data.

Reviewed

Core idea

Inbound processing is the path from an external system into SAP. When an inbound IDoc or message is missing, stuck in status, or posts wrong data, the support goal is to trace the path from receipt through syntax check, partner profile validation, and application posting to identify where it failed and why.

Common symptoms

  • Partner reports a message was sent but no IDoc exists in SAP.
  • Inbound IDoc exists but is stuck in status 64 or 51.
  • IDoc posted successfully but the business document has wrong data.
  • Inbound IDoc creates duplicate business documents.
  • Inbound processing is slow and messages accumulate in the queue.

Likely causes

  • Receipt failure: the IDoc never arrived due to network, RFC, or gateway issues.
  • Syntax error: the IDoc structure does not match the expected segment definition.
  • Partner profile mismatch: the sender partner or message type is not configured in the inbound partner profile.
  • Application error: the IDoc passed syntax and profile checks but failed during posting due to master data or business rules.
  • Queue bottleneck: inbound qRFC queues are not processing fast enough.

Where to check in SAP

  • WE02 / WE05 — IDoc list filtered by direction 1 (inbound) and partner.
  • SM58 — tRFC error log for inbound RFC failures.
  • SMQ2 — inbound qRFC queue status.
  • SM21 — system log for gateway or connection errors.
  • SLG1 — application log for posting errors.

Key tables / transactions / objects

  • EDIDC / EDIDS — IDoc control and status.
  • TRFCQIN — inbound qRFC queue.
  • ARFCSSTATE — tRFC status.

Diagnostic workflow

  1. Confirm the partner sent the message and capture the message ID or timestamp.
  2. Check WE02 for the IDoc with direction 1 (inbound) and the sender partner.
  3. If the IDoc does not exist, check SM21 for gateway errors and SM58 for RFC failures.
  4. If the IDoc exists, check its status and status history for the failure layer.
  5. For status 51, check SLG1 for the application error details.
  6. For queue delays, check SMQ2 for queue depth and processing status.

Typical fixes or next actions

  • Request a resend from the partner if the IDoc never arrived.
  • Fix syntax errors by correcting the segment data or updating the partner's mapping.
  • Update the inbound partner profile to accept the message type and sender.
  • Fix master data or business rule issues before reprocessing status 51 IDocs.
  • Increase queue processing capacity or tune the queue scheduler if messages accumulate.

Support takeaway

Inbound issues are usually receipt, syntax, or application posting problems. A useful ticket should include: sender partner, message type, IDoc number if it exists, expected business document, actual result, and any error text from WE02, SM58, or SLG1.

Boundaries and non-goals

This page is a diagnostic frame, not an inbound processing configuration guide. It does not cover IDoc segment design, partner profile setup, or gateway configuration. It does not replace SAP's IDoc documentation.

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

Related Atlas Pages