WE05Integration

SAP WE05 — IDoc Lists

WE05 answers the shape-of-the-day question: how did the interfaces do? Rather than a flat list, it groups IDocs into a tree by status, so you see at a glance that 480 posted and 12 failed.

It reads exactly the same data as WE02 with the same selection screen. The difference is entirely presentation. WE02 is better when you are chasing one message; WE05 is better when you are surveying a day.

Every IDoc carries a two-digit status. Inbound: 53 posted successfully, 51 application error, 64 waiting to be processed, 68 abandoned. Outbound: 03 passed to the port, 12 dispatched, 02 port error, 29 ALE service error. 56 means no partner profile was found.

When you would actually use WE05

What the screen looks like

IDoc Lists
WE05

Selection

Created on03.08.2026
Direction
Message type
Partner number
Client 100 | S/4HANA | Company Code 1000
Illustrative recreation.Leave direction blank to see inbound and outbound together — Drawn for training with invented data; not a capture of a real SAP system. Fields with a blue border are required. SAP is a trademark of SAP SE.
IDoc Lists: Status Overview
WE05
NodeStatusDescriptionCount
Inbound53Application document posted486
Inbound51Application document not posted12
Inbound64IDoc ready to be transferred3
Outbound12Dispatch OK311
Outbound02Error passing data to port2
14 IDocs need attention: 12 application errors, 2 port errors
Client 100 | S/4HANA | Company Code 1000
Illustrative recreation.The tree turns "did the interfaces work?" into a number in seconds — Drawn for training with invented data; not a capture of a real SAP system. Fields with a blue border are required. SAP is a trademark of SAP SE.

The fields, in plain English

Created onEDIDC-CREDAT

The date range to survey. For a morning check this is usually yesterday plus today.

Watch out: The only real protection against a very slow report. The IDoc tables grow without limit unless archived.

Status group nodes

The tree groups by status so you can expand only the branch that matters. Statuses in the 50s are inbound; the low numbers and 20s are outbound.

Direction

Leave blank for a full picture of the day. Set it when you already know which side is failing.

Step by step

  1. 1Enter the date range.
  2. 2Execute to get the status tree.
  3. 3Read the error branches: 51 and 68 inbound, 02 and 29 outbound.
  4. 4Expand an error branch to list the individual IDocs.
  5. 5Double-click one to open it and read its status records.
  6. 6Move to BD87 to reprocess once the underlying cause is fixed.

Errors you will hit, and what they mean

A large number in status 64

Why: IDocs arrived but were never passed to the application — usually the partner profile is set to collect them for a background job that has not run.

Fix: Check whether the processing job is scheduled and running. BD87 can process them immediately in the meantime.

Report is extremely slow

Why: Date range too wide against unarchived IDoc tables.

Fix: Narrow to a day or two. Long-term, IDoc archiving is a housekeeping task worth having.

Common questions

Should I use WE05 or WE02?

WE05 to survey, WE02 to investigate. Same data, and neither can do anything WE02 cannot — the choice is purely about which view helps.

What does status 64 mean?

The IDoc is sitting in SAP waiting to be passed to the application. Common when the partner profile is set to background processing rather than immediate.

Transactions that go with WE05

WE02Investigate an individual IDocBD87Reprocess the errors this surfacesWE09Search by business content instead

Reading about it only gets you so far

Practise SAP transactions in a safe simulated environment and keep what you learn.

See the SAP games →Study the full module

Practise SAP transactions hands-on

Interactive modules, games, and an AI tutor — free to start.

Get started free →