SAP WE09 — IDoc Search for Business Content
WE02 and WE05 find IDocs by their metadata: when, who, what status. WE09 finds them by what is written inside them.
That is the difference between useful and useless in most real investigations. Nobody rings up quoting an IDoc number. They say "our purchase order 4500012345 never came through". WE09 is how you turn that sentence into a document.
You tell it which segment and which field to look in, and what value to look for. It searches the payload and returns the IDocs that contain it.
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 WE09
- A partner quotes their order or invoice number and you need to find the message.
- Checking whether a specific delivery was ever transmitted.
- Finding every IDoc that mentions a particular material or customer.
- Proving a message was never received, which requires having genuinely looked.
What the screen looks like
IDoc selection
Search in segment
| IDoc number | Status | Segment | Field | Value | Created |
|---|---|---|---|---|---|
| 0000000004471955 | 51 | E1EDK01 | BELNR | 4500012345 | 02.08.2026 |
The fields, in plain English
EDID4-SEGNAMWhich part of the IDoc to look in. Segments are named E1xxxxx — E1EDK01 is a document header, E1EDP01 a line item. WE60 documents the structure of any basic type.
Watch out: Guessing the segment wastes time. Open a known-good IDoc in WE02 first, find the field there, and note which segment it sits in.
The field within that segment. BELNR is a document number, MATNR a material, KUNNR a customer.
What you are looking for. Beware of leading zeros — SAP often stores 4500012345 internally as 0004500012345.
Watch out: If an exact search finds nothing, try wildcards or the zero-padded form before concluding the IDoc does not exist.
Still required, because this searches payload data across potentially enormous tables. A month is usually a sensible ceiling.
Step by step
- 1Open a similar IDoc in WE02 and find which segment and field carry the value you want.
- 2In WE09, set a date range wide enough to cover when the message would have arrived.
- 3Set direction and, if known, message type and basic type.
- 4Enter the segment, field and value.
- 5Execute. If nothing is found, retry with leading zeros or a wildcard before ruling it out.
- 6Open any hit to read its status records and see what happened.
Errors you will hit, and what they mean
No IDocs found although the partner insists they sent it
Why: Wrong segment or field, a leading-zero mismatch, a date range that misses it — or it genuinely never arrived.
Fix: Widen the date range and drop the segment restriction before concluding anything. Then check the port and middleware: it may never have reached SAP.
Search runs for a very long time
Why: No segment named, so every segment of every IDoc in range is scanned.
Fix: Always name the segment and field. That is the difference between seconds and a coffee break.
Finds the IDoc but the value looks different from what the partner quoted
Why: Internal versus external formatting — leading zeros, or a conversion exit applied on display.
Fix: Compare the raw segment value in WE02 rather than the formatted display.
Common questions
How do I know which segment to search?
Open a working IDoc of the same type in WE02 and look at the data records — the segment name is shown beside each field. WE60 gives the full documentation for a basic type.
Why does the search miss a value I can see?
Almost always leading zeros. Numeric SAP keys are stored padded, so 4500012345 may be held as 0004500012345. Try both.
Can I search several fields at once?
The standard screen searches one segment and field per run. For anything more complex, run it twice or take the IDoc numbers into a report.
Transactions that go with WE09
Reading about it only gets you so far
Practise SAP transactions in a safe simulated environment and keep what you learn.
Practise SAP transactions hands-on
Interactive modules, games, and an AI tutor — free to start.
Get started free →