I-Doc's

[Former Member]

Hi all,

What are i-doc's and how are they uesed in SAP?

What is the link between i-doc and EDI ?

Regards,

Tatvam

[former_member204513]

Dear Srinivas,

Go through this link you can know what is IDOc and What is EDI

http://help.sap.com/saphelp_47x200/helpdata/en/af/1210377eff2e7ae10000009b38f889/frameset.htm

I hope it will help you

Regards,

Murali.

[Former Member]

Hi

IDocs (Intermediate Documents) are the crux of ALE. These are the documents with the help of which data is exchanged between SAP R/3 and non-R/3 systems. As the name suggests, these documents act as intermediate storage of information, which can be sent bi-directionally. Message types are responsible for creation of Idocs.

IDocs Components

Data on Internet is exchanged using data formats like IPV6 – and SAP uses a similar approach. Idocs are a well-structured medium through which data transfer takes place.

An IDoc is made up of the following parts:

Control Record: This section contains control information regarding the Idoc. Its constituents are Sender’s name, Receiver name, Message type and Idoc type. The format of the control record is similar for all IDoc types.

Data Segment: It consists of a header that contains the identity of the Idoc. Its constituents include, a sequential segment number, a segment type description and field containing the actual data of the segment.

Status records: The status record shows the information regarding the already processed stages and remaining processing stages of the Idoc. It has an identical format for each IDoc type.

If you need more information post your mail ID. I shall send you the document.

Regards

[Former Member]

HI,

Idoc are nothing but intermediate documents. They are transferred from nonsap/sap system to sap system. EDI is the technology which helps in converting flat file sent by customer into EDI format .

The std examples and 850 PO, 855 Order confirmation.

Thanks,

Pramod

[Former Member]

Hi srinivas

 An IDoc is not a process. The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.

 IDocs are stored in the database. In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."

 Every IDoc has a unique number. When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.

 IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.

 IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.

 IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.

Hope the above information is helpful to u

Regards

kishore