SAP TCodes · LessonReviewed by Ravi M, SAP Trainer, 10 yrs · Updated · Published · SAP S/4HANA 2023 · all levels
SAP WE02
WE02 is the SAP transaction code for Display IDocs (Integration). It displays IDocs and their statuses, the tool for monitoring inbound/outbound document exchange and diagnosing integration issues.
Quick answer
WE02 displays IDocs and their statuses, the tool for monitoring inbound/outbound document exchange and diagnosing integration issues.
Key takeaways
- Watch out: status 53 means a document was created, not that it is correct.
Purpose
It displays IDocs and their statuses, the tool for monitoring inbound/outbound document exchange and diagnosing integration issues.
Key fields and screen
- Selection: date, direction, message/IDoc type, status.
- IDoc list with status (e.g. 51 error, 53 posted, 03 sent).
- Control, data and status records of each IDoc.
- Navigation to the application document.
Tips
- Filter by status 51 to find errored inbound IDocs.
- Read the status records for the error detail.
- Use BD87 to reprocess, WE19 to test/edit.
Common errors
- Status 51 (application error on inbound posting).
- Status 29/02 (outbound dispatch errors).
- No IDocs found (wrong selection or partner profile issue).
Common pitfalls
- Reading the status number and not the status record. The number says it failed; the record says why, and the two are one click apart.
- Treating status 53 as success. It means an application document was created, not that the document is correct.
- Selecting a narrow date range. An IDoc stuck in an earlier window is exactly the one you are looking for.
- Reprocessing from here. BD87 is the tool for that, and doing it the other way tends to produce duplicates.
- Not checking the partner profile when nothing appears. No IDocs found often means none were ever created, which is a configuration problem rather than a missing message.