SAP IDoc Transactions – Overview

How to use IDoc processing correctly

IDoc transaction overview – in an SAP system, numerous transactions exist by default for IDoc processing and development. In the following table, we have collected and structured the most important SAP IDoc transactions. Below is a brief description of the transaction.

The most important IDoc transactions

IDoc Ads / Monitoring / Admin

WLF_IDOC – IDoc processing – explained in great detail here
WE02 – View IDoc
WE05 – IDoc Lists
BD87 – Status Monitor for ALE Messages

IDoc Administration

WE20 – Partner Agreements
WE21 Port Description
SM59 – RFC Destinations
SM58 – Asynchr. Rfc

IDoc Selection

WE06 – Active IDoc Monitoring
WE07 – IDoc Statistics
WE09 – Find IDocs through Content
WE10 – Search IDocs via Content
WE11 – Deleting IDocs

IDoc Test Tools

WE19 Test Tool
WE15 – Test output processing from NAST
WE14 – Test Output Processing
WE18 – Create a status file
WE17 Test Status File
WE12 – Test Modified Input File
WE16 – Test Input File

IDoc Documentation

WE60 Documentation for IDoc Types
WE64 Documentation Message Types

IDoc Development Tools

WE31 – Development IDoc Segment
WE30 – Development IDoc Type
WE81 Logical Message Types
WE82 – Assignment Messages to IDoc Type
WE41 – Operation Codes Output
BD51 – Maintaining input function blocks
WE57 – Assignment Messages to Anw. Object
WE42 – Process Codes Incoming

IDoc Conversion Rules

BD62 – Define Segment Implementation Rule
BD79 – Maintenance IDoc Implementation Rules
BD55 – Maintain intermediate document implementation

IDoc Reclassification Rules

WE70 Reclassification: Base Types
WE71 Reclassification: Extensions
WE72 – Reclassification: IDoc Types
WE73 – Reclassification: log. Messages

IDoc Other

BDM2 – Monitoring: IDOCs at the receiver
BDM7 – ALE Audit: Statistical Evaluations
SARA Archive Administration
IDOC – IDoc: Repair and Testing Programs

Descriptions

SoonALE DevelopmentArea menu for the development of ALE processes. This summarizes transactions that are important for the development of ALE processes.
BaleArea menu for the administration ofArea menu for monitoring the ALE processes. Here are summarized transctions, which are important for the administration of ALE processes.
BD87Status monitor for ALE messagesThis is the most important transaction for processing IDocs. Here, the IDoc direction is distinguished first by status and then by base type. IDocs can also be edited from this transaction, but transactions WE02 or WE05 are much clearer for analysis. When processing an IDoc, further options can be selected here, such as the bright playing of IDocs, if it is posted via a folder processing. The traffic jams can also be set to “no further processing”.
SaleView ALE-CustomizingArea menu for setting ALE scenarios. Here you will find all important settings for logical systems, business process modeling, master data distribution, distribution models and many more.
SM59RCF DestinationsOverview and maintenance for RFC destinations. Here you can see which systems are addressed from the corresponding port of the partner agreement at IDoc Source Processing. Other system connections can also be set up here.
WE02View IDocDisplay of IDocs: This transaction can be used to display all inbound and outbound IDocs. The IDocs are grouped by direction, base type and status and can be monitored here. By double-clicking on an IDoc, this IDoc can be displayed in detail. You can view the individual status sets and segments with content. Depending on the authorization, the IDocs can be changed in terms of their values. The original IDoc is stored under a new IDoc number and the status of the edited IDoc changes to unedited. An IDoc with the status of a green traffic light can no longer be edited.
WE05IDoc ListsLike transaction WE02. No significant differences in content.
WE09Search IDocs via contentDisplay of IDocs: This transaction can be used to display all inbound and outbound IDocs. Here you can also select the contents of IDocs. To do this, you have to specify the corresponding segment with field and content.
WE19Test toolThis transaction is very important in the development and testing of IDoc scenarios. Here IDocs can be easily copied and then edited. After completion, these can then be fed according to the input or output processing. This function may also be used in production mode for re-recording of IDocs, which cannot be edited according to the requirements in the WE02.
WE20Partner agreementsIn this transaction, you define the partner agreement for each IDoc process. Each partner agreement has a scope for inbound and outbound processes. This determines which processing routines are used.
WE21Port descriptionFor all outgoing IDocs, a port must be defined in the partner agreement. The port determines which system the message is sent to. You can also place the outgoing messages on a file system and have them picked up by a partner system.
WE60Documentation for IDoc typesThis transaction provides detailed content and technical documentation for all basic types, extensions and segments. These can also be saved in HTML format.
WE64Documentation Message TypesDefined operation codes for incoming and outgoing messages. The task codes are used in the partner agreements. The corresponding message types are assigned to the operation codes and the function module is used for processing.
WediEDI baseArea menu for the administration and development of IDoc processes. Here are transactions that are important for IDoc processing.
WLF_IDOCIDoc ProcessingThis is the latest and most comprehensive transaction in the IDoc environment. Here are the functions from transactions WE02, BD87 and WE09. This transaction is available with the EHP 5 SP 10 in ECC 6.0. There are also innovations built in, such as optimized search for content, mass content replacement, IDoc comparison and much more.