IDoc and integration T-codes: the working list
SAP integration connects an SAP system to other systems through IDocs, ALE, RFC calls and web services. This page lists the transaction codes integration consultants use most, from monitoring IDocs to setting up partners and ports.
Each line gives the code as you type it and what it does. For a failed IDoc, WE02 shows the status and BD87 reprocesses it.
IDoc monitoring and reprocessing
- WE02
- Display IDocs
- WE05
- IDoc lists
- WE09
- Search IDocs by content
- BD87
- Status monitor to reprocess IDocs
- WE14
- Send outbound IDocs waiting for dispatch
- BD20
- Pass inbound IDocs to the application
- WE19
- IDoc test tool
Partners, ports and distribution
- WE20
- Partner profiles
- WE21
- Ports in IDoc processing
- SALE
- ALE customizing
- BD54
- Maintain logical systems
- BD64
- Maintain the distribution model
IDoc development
- WE30
- Develop IDoc types
- WE31
- Segment editor
- WE81
- Logical message types
- WE60
- IDoc documentation
RFC, queues and web services
- SM59
- RFC destinations
- SM58
- Transactional RFC monitor
- SMQ1
- qRFC monitor for the outbound queue
- SMQ2
- qRFC monitor for the inbound queue
- SOAMANAGER
- Configure web services
- SRT_UTIL
- Web service utilities and error log
- SXMB_MONI
- Integration Engine message monitor (SAP PI/PO)
What changes in SAP S/4HANA?
IDoc, ALE and RFC tools work the same way in S/4HANA on-premise. SAP points new integrations toward APIs and SAP Integration Suite rather than new IDoc interfaces, but existing IDoc flows keep running. SXMB_MONI monitors the Integration Engine of SAP PI/PO. Public cloud uses communication arrangements in Fiori apps instead of these codes.
23 codes. Any code's title can be checked in the system itself with SE93.
The area itself: The SAP integration consultant.