SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP IDoc and ALE Transaction Codes, Tables and Programs

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.

Download:

Item	Type	Purpose	Typical use
WE02	Transaction	Display IDoc, read control record, data records and status history	Monitoring
WE05	Transaction	IDoc lists with selection by date, status, message type and partner	Monitoring
WE09	Transaction	Search for IDocs by content of a segment field	Monitoring
WE19	Transaction	Test tool: create or copy an IDoc and process it inbound or outbound	Testing
WE20	Transaction	Partner profiles with inbound and outbound parameters	Configuration
WE21	Transaction	Port definition for tRFC, file, XML HTTP and other transports	Configuration
WE30	Transaction	IDoc type development: create and change basic types and extensions	Development
WE31	Transaction	Segment editor: create and change IDoc segments	Development
WE41	Transaction	Process codes for outbound processing	Configuration
WE42	Transaction	Process codes for inbound processing	Configuration
WE46	Transaction	IDoc administration: general settings, status and process codes	Configuration
WE47	Transaction	Maintain IDoc status values and their texts	Configuration
WE57	Transaction	Assign function module to logical message and IDoc type	Configuration
WE60	Transaction	IDoc type documentation: structure and field descriptions	Development
WE81	Transaction	Display and maintain logical message types	Configuration
WE82	Transaction	Assign message type to IDoc type and release	Configuration
BD54	Transaction	Maintain logical systems	Configuration
BD64	Transaction	Maintain the ALE distribution model	Configuration
BD82	Transaction	Generate partner profiles from the distribution model	Configuration
BD87	Transaction	Status monitor for ALE messages: select, process and delete IDocs	Monitoring
BD10	Transaction	Send material master data via ALE	Master data
BD11	Transaction	Request material master data from another system	Master data
BD12	Transaction	Send customer master data via ALE	Master data
BD14	Transaction	Send vendor master data via ALE	Master data
BD21	Transaction	Select change pointers and create IDocs from them	Change pointers
BD50	Transaction	Activate change pointers per message type	Change pointers
BD52	Transaction	Activate change pointers per changed field	Change pointers
BD61	Transaction	Activate change pointers generally	Change pointers
SALE	Transaction	ALE IMG: central entry for ALE and IDoc configuration	Configuration
WEDI	Transaction	Area menu for IDoc and EDI basis	Navigation
SM59	Transaction	RFC destinations, connection tests and logon settings	Configuration
SM58	Transaction	Transactional RFC: list and resend failed tRFC calls	Monitoring
SMQ1	Transaction	qRFC monitor for the outbound queue	Monitoring
SMQ2	Transaction	qRFC monitor for the inbound queue	Monitoring
SE37	Transaction	Function Builder: inspect and test IDoc function modules	Development
SE38	Transaction	ABAP editor: run IDoc reports directly	Development
RSEOUT00	Program	Process outbound IDocs that are waiting in status 30	Batch job
RBDAPP01	Program	Process inbound IDocs that are waiting in status 64	Batch job
RBDMANI2	Program	Manually process IDocs that ended with an application error	Repair
RBDMIDOC	Program	Create IDocs from change pointers for a message type	Change pointers
RSEIDOCR	Program	Process IDocs from external files placed in a directory	File interface
EDIDC	Table	IDoc control records (header) with current status	Analysis
EDID4	Table	IDoc data records (segments) from release 4.0 onward	Analysis
EDIDS	Table	IDoc status records, one row per status change	Analysis
EDP13	Table	Partner profile: outbound parameters	Analysis
EDP21	Table	Partner profile: inbound parameters	Analysis
EDPP1	Table	Partner profile: general data	Analysis
BDCP2	Table	Change pointers for ALE master data distribution	Change pointers
BDCPS	Table	Change pointer status	Change pointers

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.

Need an IDoc monitoring view without custom reports?

Optional: talk through how a read-only assistant could answer IDoc status questions from your SAP data.

Optional. The tool and every export work without this. No spam.

How to use this list

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

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.

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

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

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.

Frequently Asked Questions

Which transaction shows all IDocs for a message type?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools