Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC

Former Member
0 Kudos
124

what is idoc? how to create idoc?what is the use of this idoc?

1 ACCEPTED SOLUTION

Former Member
0 Kudos
88

Hi Srujana,

IDOC is an intermediate document which is used to transfer data between different systems. One of sender or receiver systems may not be SAP system.

Check these links for IDOCs

http://www.sappro.com/downloads/OneClientDistribution.pdf

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

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

Thanks,

Vinay

4 REPLIES 4

Former Member
0 Kudos
89

Hi Srujana,

IDOC is an intermediate document which is used to transfer data between different systems. One of sender or receiver systems may not be SAP system.

Check these links for IDOCs

http://www.sappro.com/downloads/OneClientDistribution.pdf

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

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

Thanks,

Vinay

Former Member
0 Kudos
88

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

Regards

Former Member
0 Kudos
88

Hi,

go thru the below information.

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.

SALE - ALE (Application Linking and Enabling) settings

Go through the link for basics related to IDOCs:

http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm

Check these links.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

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

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

Please check this PDF documents for ALE and IDoc.

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

Check below link. It will give the step by step procedure for IDOC creation.

http://www.supinfo-projects.com/cn/2005/idocs_en/2/

Check these out..

Check below link. It will give the step by step procedure for IDOC creation.

http://www.supinfo-projects.com/cn/2005/idocs_en/2/

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

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

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

go trough these links.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

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

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

Reward Points if it is Useful.

Thanks,

Manjunath MS

Former Member
0 Kudos
88

Hi Srujana,

IDOC - Intermediate Document - is used to transfer the data from SAP to SAP or

SAP to non-SAP or Non-SAP to SAP

You need to do the following setting to create idoc

1. Create logical system - tcode SALE

2. Assign logical system to client - SCC4

3. Message Type - we81

4. IDOC TYPE - WE30 and We31

5. Assign IDOC type to message type - we82

6. Port - WE21

7. Partner Profile - we20

8. Customer distribution model - BD64

9. Process code - WE41 or WE42

Regards

Arun