Scribd
Upload
164 views4 pages

Idoc Notes

This document provides information about SAP IDocs including: 1. It defines IDocs and lists T-Codes related to IDoc definition, processing, utilities, and more. 2. It describes the three parts of an IDoc - the administration part (control record), application data (data record), and status information (status record). 3. It explains inbound and outbound IDocs, how they are used to transfer data into and out of SAP systems, and the configuration steps for outbound IDoc processing.

Uploaded by

Nikhil Malpe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
164 views4 pages

Idoc Notes

This document provides information about SAP IDocs including: 1. It defines IDocs and lists T-Codes related to IDoc definition, processing, utilities, and more. 2. It describes the three parts of an IDoc - the administration part (control record), application data (data record), and status information (status record). 3. It explains inbound and outbound IDocs, how they are used to transfer data into and out of SAP systems, and the configuration steps for outbound IDoc processing.

Uploaded by

Nikhil Malpe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

IDOC NOTES

T-code: we02

IDoc definition TCodes


IDoc define: WE31
IDoc type define: WE30
IDoc document: WE60

IDoc processing TCodes


IDoc process: BD87
IDoc testing: WE19
IDoc utilities: IDoc
IDoc workbench: WE02, WE05
Search IDoc by content: WE09, WE10
IDoc statictis WE07
Delete IDoc: WE11
Process all IDoc: WE14
Ports in IDoc processing: WE21
Display outbound process code: WE41
Display inbound process code: WE42
Display partner types: WE45
IDoc status maintenance : WE47
Display texts for process code: WE50

What is an SAP IDOC? – Intermediate Documents.


SAP IDOC is an object / Container that transports business transaction data in the form of an electronic
message from one system to another.

The I doc structure consists of 3 parts –

1. The administration part(Control Record)- which has the type of idoc, message type, the current
status, the sender, receiver etc. This is referred to as the Control record.
2. The application data (Data Record) – Which contains the data. These are called the data
records/segments.
3. The Status information (Status Record)- These give you information about the various stages the
idoc has passed through.

You can view an I-DOC using transaction WE02 or WE05

– Control Record

 All control record data is stored in EDIDC table. The key to this table is the IDOC Number
 It contains information like IDOC number, the direction(inbound/outbound), sender, recipient
information, channel it is using, which port it is using etc.
 Direction ‘1’ indicates outbound, ‘2’ indicates inbound.

Data Record

 Data record contains application data like employee header info, weekly details, client details etc
 All data record data is stored in EDID2 to EDID4 tables and EDIDD is a structure where you can see
its components.
 It contains data like the idoc number, name and number of the segment in the idoc, the hierarchy
and the data
 The actual data is stored as a string in a field called SDATA, which is a 1000 char long field.

Status Record

 Status record is attached to an I-DOC at every milestone or when it encounter errors.


 All status record data is stored in EDIDS table.
 Statuses 1-42 are for outbound while 50-75 for inbound

IDOCs can be classified into two . Inbound IDOCs and Outbound IDOCs.

Inbound IDOC   : These are IDOCs which get the data into SAP system from external source i.e PI system  or
any other external system. Inbox direction is represented by 2

Inbound data flow

Outbound IDOC: These are IDOCs which are sent out from SAP system to any other system. i.e PI system or
any other external system. Outbox direction is represented by 1.

Outbound data flow


Outbound IDoc configuration steps:

Config RFC destination, TCode: SM59

WHY DO WE NEED TO TRANSFER THE DATA ?

Clients having operations in various countries and wants a centralized location where all the data is stored
If the customer is using sap then we use it to transfer the data from his system to our system
Eg. Customer sends PO to us via idoc then we can use it to create a sales order.

 EDI (Electronic Data Interchange) subsystems are used to move data from SAP to non-SAP systems
and ALE (Application Link Enabling) is used to transfer data between SAP systems.
  An IDOC is used to move data or information from SAP to other systems and vice versa. 

EDI – Electronic Data Interchange: -

 SAP will support EDI through Intermediate documents (IDOCS).


 EDI is the electronic exchange of business documents between the computer systems of business
partners, using a standard format over a communication network.
 EDI is also called paperless exchange.

Advantages:

 Reduced Data entry errors


 Reduced processing time
 Availability of data in electronic form
 Reduced paperwork
 Reduced Cost
 Reduced inventories and better planning
 Standard means of communications
 Better business process

1. ALE – APPLICATION LINKING ENABLING.

 Application Link Enabling (ALE) is a technology to create and run distributed applications.
 ALE incorporates controlled exchange of data messages ensuring data consistency.
 ALE comprises of three layers.
 Application Services
 Distribution Services
 Communication Services
 Basic principle of ALE is to provide a distributed and fully integrated R/3 systeM

 ALE is a tool which helps in transferring the data from one sap system to another sap system
 ALE can also transfer data from sap system to another non sap system but for this it uses translators .
translators are ------- TIBCO/Xi

You might also like