SAP IDoc Transactions – Overview

This is how you use IDoc processing correctly

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

The most important IDoc transactions

IDoc Display / Monitoring / Admin

WLF_IDOC – IDoc processing – explained in great detail here
WE20 – Partner Agreements
WE05 – IDoc Lists
BD87 – Status Monitor for ALE Messagess

IDoc Administration

WE20 – Partner Agreements
WE21 – Port Description
SM59 – RFC Destinations (Display & Maintenance)
SM58 – Error Log Async. RFC

IDoc selection

WE06 – Active IDoc Monitoring (Monitoring)
WE07 – IDoc Statistics
WE09 – IDocs search content
WE10 – IDocs search via content
WE11 – Delete IDocs

IDoc test tools

WE19 – test tool
WE15 – test output processing from NASt
WE14 – test Outbound Processing
Create WE18 – 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 of Messages to IDoc type
WE41 – Process Codes Output
BD51 – Maintaining Inbound Function Modules
WE57 – assignment messages to application object
WE42 – Process Codes Inbox

IDoc conversion rules

BD62 – Define Segment Conversion Rule
BD79 – Maintenance IDoc Implementation Rules
BD55 – Maintain Interim Document Implementation

IDoc conversion rules

WE70 – Reclassification: Base types
WE71 – Encryption: Extensions
WE72 – Reclassification: IDoc types
WE73 – Reclassification: log. News

IDOC: Repair and test Programs

IDoc Other

BDM2 – Monitoring: IDOCs at the Receiver
BDM7 – ALE Audit: Statistical Evaluations
SARA – Archive Administration

descriptions

BALDALE DevelopmentArea menu for the development of ALE processes. Here are summarized 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 transactions that are important for the administration of ALE processes.
BD87Status Monitor for ALE Messagesthis is the most important transaction for processing IDocs. Here, according to the IDoc direction, a distinction is made first according to status and then according to basic types. 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 clear play of IDocs, if it is posted via a session processing. Likewise, the jam can be set to “no further processing” here.
SALEDisplay ALE CustomizingArea menu for setting ALE scenarios. Here you will find all important settings options for logical systems, business process modeling, master data distribution, distribution models, etc.
SM59RCF DestinationsOverview and Maintenance for RFC Destinations. Here you can see which systems from the corresponding port of the partner profile are addressed in IDoc outbound processing. Here also further system connections can be established.
WE02Display IDocDisplay of IDocs: With this transaction, all incoming and outgoing IDocs can be displayed. the IDocs are grouped by direction, base type and status and can be monitored here. Double-click on an IDoc to display this IDoc in detail. the individual status records and segments with contents can be displayed. Depending on the authorization, the IDocs can be changed with regard to their values. the original IDoc is saved under a new IDoc number and the status of the edited IDoc changes to unprocessed. An IDoc with the status of a green traffic light can no longer be edited.
WE05IDoc ListsLike transaction WE02. No significant content differences.
WE09IDocs look for contentDisplay of IDocs: With this transaction, all incoming and outgoing IDocs can be displayed. Here you can additionally select according to the contents of IDocs. to do this, you must specify the appropriate segment with field and content.
WE19test toolthis transaction is very important in the development and testing of IDoc scenarios. Here, IDocs can simply be copied and then edited. After completion, these can then be supplied according to the input or output processing. Under certain circumstances, this function can also be used in productive operation to re-import IDocs that can not be edited according to the requirements in WE02.
WE20partnerIn this transaction you define the partner profile for each IDoc process. Each partner agreement has a scope for inbound and outbound processes. this determines which corresponding processing routines are used.
WE21Port DescriptionFor all outbound IDocs, a port must be defined in the partner profile. the port determines to which system the message will be sent. You can also store the outgoing messages on a file system and have them picked up there by a partner system.
WE60Documentation for IDoc typesthis transaction provides a detailed content and technical documentation for all basic types, enhancements and segments. these can also be saved in HtML format.
WE64Documentation message typesHere process codes are defined for incoming and outgoing messages. the process codes are used in the partner agreements. the process codes are assigned the corresponding message types and the function module for processing.
WEDIBase EDIArea menu for administration and development of IDoc processes. Here are summarized transactions that are important for the IDoc processing.
WLF_IDOCIDoc processingthis is the latest and most comprehensive transaction in the IDoc environment. Here the functions from the transactions WE02, BD87 and WE09 are summarized. this transaction is available with the EHP 5 SP 10 in ECC 6.0. there are also new features built in, such as optimized content search, mass content replacement, IDoc comparison and more.