# SAP IDoc and ALE Transaction Codes, Tables and Programs > Source: https://netray.co/tools/sap-idoc-transactions-tables-and-programs-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer One searchable list of the transactions, tables and standard programs an SAP integration developer uses to build, monitor and repair IDoc and ALE interfaces. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP integration developer - SAP Basis administrator - SAP functional consultant ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Item **Key:** item **Type:** text #### Type **Key:** kind **Type:** text #### Purpose **Key:** purpose **Type:** text #### Typical use **Key:** phase **Type:** text **Rows:** #### Monitoring **Item:** WE02 **Kind:** Transaction **Purpose:** Display IDoc, read control record, data records and status history #### Monitoring **Item:** WE05 **Kind:** Transaction **Purpose:** IDoc lists with selection by date, status, message type and partner #### Monitoring **Item:** WE09 **Kind:** Transaction **Purpose:** Search for IDocs by content of a segment field #### Testing **Item:** WE19 **Kind:** Transaction **Purpose:** Test tool: create or copy an IDoc and process it inbound or outbound #### Configuration **Item:** WE20 **Kind:** Transaction **Purpose:** Partner profiles with inbound and outbound parameters #### Configuration **Item:** WE21 **Kind:** Transaction **Purpose:** Port definition for tRFC, file, XML HTTP and other transports #### Development **Item:** WE30 **Kind:** Transaction **Purpose:** IDoc type development: create and change basic types and extensions #### Development **Item:** WE31 **Kind:** Transaction **Purpose:** Segment editor: create and change IDoc segments #### Configuration **Item:** WE41 **Kind:** Transaction **Purpose:** Process codes for outbound processing #### Configuration **Item:** WE42 **Kind:** Transaction **Purpose:** Process codes for inbound processing #### Configuration **Item:** WE46 **Kind:** Transaction **Purpose:** IDoc administration: general settings, status and process codes #### Configuration **Item:** WE47 **Kind:** Transaction **Purpose:** Maintain IDoc status values and their texts #### Configuration **Item:** WE57 **Kind:** Transaction **Purpose:** Assign function module to logical message and IDoc type #### Development **Item:** WE60 **Kind:** Transaction **Purpose:** IDoc type documentation: structure and field descriptions #### Configuration **Item:** WE81 **Kind:** Transaction **Purpose:** Display and maintain logical message types #### Configuration **Item:** WE82 **Kind:** Transaction **Purpose:** Assign message type to IDoc type and release #### Configuration **Item:** BD54 **Kind:** Transaction **Purpose:** Maintain logical systems #### Configuration **Item:** BD64 **Kind:** Transaction **Purpose:** Maintain the ALE distribution model #### Configuration **Item:** BD82 **Kind:** Transaction **Purpose:** Generate partner profiles from the distribution model #### Monitoring **Item:** BD87 **Kind:** Transaction **Purpose:** Status monitor for ALE messages: select, process and delete IDocs #### Master data **Item:** BD10 **Kind:** Transaction **Purpose:** Send material master data via ALE #### Master data **Item:** BD11 **Kind:** Transaction **Purpose:** Request material master data from another system #### Master data **Item:** BD12 **Kind:** Transaction **Purpose:** Send customer master data via ALE #### Master data **Item:** BD14 **Kind:** Transaction **Purpose:** Send vendor master data via ALE #### Change pointers **Item:** BD21 **Kind:** Transaction **Purpose:** Select change pointers and create IDocs from them #### Change pointers **Item:** BD50 **Kind:** Transaction **Purpose:** Activate change pointers per message type #### Change pointers **Item:** BD52 **Kind:** Transaction **Purpose:** Activate change pointers per changed field #### Change pointers **Item:** BD61 **Kind:** Transaction **Purpose:** Activate change pointers generally #### Configuration **Item:** SALE **Kind:** Transaction **Purpose:** ALE IMG: central entry for ALE and IDoc configuration #### Navigation **Item:** WEDI **Kind:** Transaction **Purpose:** Area menu for IDoc and EDI basis #### Configuration **Item:** SM59 **Kind:** Transaction **Purpose:** RFC destinations, connection tests and logon settings #### Monitoring **Item:** SM58 **Kind:** Transaction **Purpose:** Transactional RFC: list and resend failed tRFC calls #### Monitoring **Item:** SMQ1 **Kind:** Transaction **Purpose:** qRFC monitor for the outbound queue #### Monitoring **Item:** SMQ2 **Kind:** Transaction **Purpose:** qRFC monitor for the inbound queue #### Development **Item:** SE37 **Kind:** Transaction **Purpose:** Function Builder: inspect and test IDoc function modules #### Development **Item:** SE38 **Kind:** Transaction **Purpose:** ABAP editor: run IDoc reports directly #### Batch job **Item:** RSEOUT00 **Kind:** Program **Purpose:** Process outbound IDocs that are waiting in status 30 #### Batch job **Item:** RBDAPP01 **Kind:** Program **Purpose:** Process inbound IDocs that are waiting in status 64 #### Repair **Item:** RBDMANI2 **Kind:** Program **Purpose:** Manually process IDocs that ended with an application error #### Change pointers **Item:** RBDMIDOC **Kind:** Program **Purpose:** Create IDocs from change pointers for a message type #### File interface **Item:** RSEIDOCR **Kind:** Program **Purpose:** Process IDocs from external files placed in a directory #### Analysis **Item:** EDIDC **Kind:** Table **Purpose:** IDoc control records (header) with current status #### Analysis **Item:** EDID4 **Kind:** Table **Purpose:** IDoc data records (segments) from release 4.0 onward #### Analysis **Item:** EDIDS **Kind:** Table **Purpose:** IDoc status records, one row per status change #### Analysis **Item:** EDP13 **Kind:** Table **Purpose:** Partner profile: outbound parameters #### Analysis **Item:** EDP21 **Kind:** Table **Purpose:** Partner profile: inbound parameters #### Analysis **Item:** EDPP1 **Kind:** Table **Purpose:** Partner profile: general data #### Change pointers **Item:** BDCP2 **Kind:** Table **Purpose:** Change pointers for ALE master data distribution #### Change pointers **Item:** BDCPS **Kind:** Table **Purpose:** Change pointer status **Notes:** Transaction codes are as found in standard SAP ECC and S/4HANA. Availability depends on release and authorization, and some functions are also available in Fiori or in SAP Integration Suite monitoring. ## Content **Intro:** IDoc and ALE work spreads across a few dozen transactions, three core tables and a handful of batch programs. This list puts them in one searchable table so you do not have to remember which transaction does what. **Sections:** #### How to use this list **Body:** Search by transaction code, by keyword such as port or status, or by phase such as Monitoring. The Typical use column groups items into configuration, development, testing and monitoring so you can walk through a build in order. Export to Excel to hand a new team member a ready cheat sheet. #### A normal outbound to inbound flow **Body:** An application creates an IDoc through output control or a function module. It lands in EDIDC with status 01, moves to 30 when ready for dispatch, and RSEOUT00 or immediate processing sends it through the port from WE21 to the receiver. On the receiving system the IDoc arrives at status 50, goes to 64 when waiting to be processed, and RBDAPP01 posts it to the application, ending at status 53 on success. **Bullets:** - Check partner profile first when nothing is created (WE20) - Check port and RFC destination when status 02 appears (WE21, SM59) - Check process code and function module when inbound fails (WE42, WE57) #### Where to look when something breaks **Body:** Start in WE05 with the status filter. A stuck outbound IDoc at 30 usually means the dispatch job is missing. An IDoc at 02 means the transfer failed, so look in SM58 for the tRFC call and SM59 for the destination. For inbound at 51, open the status record in WE02 to read the application message and use BD87 or WE19 to reprocess after the master data or configuration is fixed. #### Common mistakes **Body:** Teams often schedule RBDAPP01 but not the program that picks up status 51 errors, so failures sit unnoticed. Others reprocess in production without checking whether the cause was data or configuration, which just recreates the error. **Cta:** Netray builds private assistants and dashboards on top of SAP data. If monitoring IDocs across several systems takes up your team, ask for a review of what could be automated. **Faq:** #### Which transaction shows all IDocs for a message type? **Answer:** Use WE05 and enter the message type and a date range, or WE02 for the same selection. Both read table EDIDC. Add a status filter to find only errors, and use direction to separate inbound from outbound. BD87 gives the same data grouped for processing. #### What is the difference between WE02 and WE05? **Answer:** They use the same selection and show the same IDocs. WE02 opens with an overview tree, while WE05 opens with a list view. Both let you drill into the control record, data records and status history, so the choice is mostly habit. #### How do I send a test IDoc without the application? **Answer:** Use WE19. You can copy an existing IDoc, edit its segment values, then choose inbound processing or outbound processing. It is the fastest way to reproduce an inbound posting error, but treat it with care in production because it really posts data. #### Do these transactions work in S/4HANA? **Answer:** Yes, the core IDoc and ALE transactions remain available in S/4HANA. Some master data distribution scenarios are replaced by newer mechanisms, so check SAP notes for your release before relying on a specific message type. ## Search terms sap idoc transaction codes, we02 we05 we19 we20 we21, sap ale transaction codes list, bd87 idoc reprocess, rbdapp01 program, sap idoc tables list, sap idoc monitoring tcodes, sm58 tRFC idoc --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json