Idoc interface

[radhushankar]

Hi all

can anyone tell me the <u><i><b>strucure of idoc interface</b></i></u> ie components ??

Thanks in advance

[Former Member]

Hi,

Which Message type/IDOC type you looking for. Check t-code WE31.

regards,

Atish

[Former Member]

Hi Radhu

Please check transaction SALE which will give a good idea about the config+components.

Regards,

Arun

[Former Member]

in idoc interface u need to know following components

IDOc Type

Message type

Process Code

Partner Profiles

for outbound idoc u need to do settings in NACE (for transactional data)

[Former Member]

IDOCs:

*- IDOC is an 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.

*

*-When an IDOC is created in the system , an unique number(16 Digits) is assigned to it. This number is unique with in the client. - IDOCs are independent of the sending and receiving systems.

*- IDOCs are independent of the direction of data exchange.

*- In the IDOCs, data is stored in text format.

*

*- IDOC will wait until the Remote System is Active.

*IDOC Definition Components

• --------------------------

*- Basic Idoc Type: Basic Idoc type defines the structure and format of the business document that is to be exchanged between

• two systems. Basic Idoc type can refer to an SAP provided basic IDOC type or a customer developed basic IDOC type.

*

*- A basic IDOC type has the following characteristics:

* Name : A basic Idoc type can be assigned upto a thirty character name.

• List of permitted segments: The segments make up the IDOC structure.

* Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.

* Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory.

* Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.

*- Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.

*

• IDOC Run time components:

• -------------------------

*- A unique IDOC number 16 digits is allocated.

*- One control record is attached to the IDOC.

*- Segments translate into data records.

*- Status records are attached.

*- Sytax rules are checked.

*

• IDOC Record Types:

• ------------------

• 1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.

*

*- there is only one control record per IDOC.

*- The stucture of the control record is the same for all the IDOCs and is defined by SAP.

*- The structure of the control record is defined by the data dictionary structure EDI_DC40.

*- The control record is stored in the EDIDC table.

• 2. Data Record : Data records contain the application data. A data record has two sections Administrative Section and a Data section.

*- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.

*- The Data section of a data record is a stram of 1000 bytes where the actual data resides.

*- The data record is defined by the data dictionary structure EDI_DD40.

*- Data records for IDOCs stored in the EDID4 table.

• 3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.

*- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.

*

• Message Type: Identifies what type of information transformed between logical systems or partners. Message type is not a local object type , it is transportable.

• Port : A Port defines the medium in which data is exchanged between the two systems in the ALE process, IDocs are transferred via memory.

*1. TRFC ports are used for ALE communicaion.

*2. File Ports used by EDI

*3. CPI-C ports used to communicate with R/2 systems.

*4. Internet ports used to connect with Internet Applications.

*5. ABAP-PI ports used to process data via the ABAP programming interface.

*6. XML ports used to process files in XML format.

*

• Partner Profiles:

*A partner profile has three views, which maintain different parameters for the partner.

*1. The General Parameters View : Values are stored in table EDPP1.

*2. The Outbound Parameters view : Values are stored in table EDP13, except for the Message control parameter , which are stored in table EDP12.

*3. The Inbound Parameters View: Values are stored in table EDP21.

*

*

*

• Transaction Codes :

• WE31- Segment Creation

• WE30 - IDOC structure

• WE81 - Message type creation

• WE82 - Link between Message type and IDOC type.

• WE21 - Creation of POrt

• WE20 - Partner Profile creation

• WE19 - Test tool for IDOC Processing.

[Former Member]

Hi Radhu Shankar G ,

These r the details regarding IDoc i/f.

IDOCS

IDocs are part of SAP's EDI solution known as ALE (Application Link Enabling). Their definitions are stored in SAP's BOR (Business Object Repository) and can be accessed globally within an SAP system.Using IDocs is the simplest, fastest and most effective way to set up interfaces between SAP R/3 systems.

Advantages

System can work even if target system not always online. The IDoc will be created and sending will just continue once you get connected to the other system.

No additional programming required. You just need to set up the configuration.

Disadvantages

Receipt/processing on the target system may not be immediate.

The sending system has no way to know whether the target system actually received what you sent (unless you use ALE).

If there is no SAP standard IDoc available for your requirement, it's harder to create a customized IDoc than a customized BAPI.

The following web-sites give u detailed description abt IDoc i/f :

http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm

http://www.erpgenie.com/abaptips/content/view/482/62/

http://help.sap.com/saphelp_nw04/helpdata/en/d5/edf163dcdc11d1890c0000e8216438/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c7639490-0201-0010-48b9-cfd... Converters)

http://www.erpgenie.com/sapedi/idoc_abap.htm

http://www.supinfo-projects.com/cn/2005/idocs%5Fen/1/(Details about an IDoc)

*******pls reward points if u find this useful

thanks & regards,

gyanaraj