topic Idoc in Application Development and Automation Discussions

Idoc

Former Member — Mon, 26 May 2008 10:39:32 GMT

Hi all,

Can any one tell me how may I get a complete reference of IDOC?So that there will be no problem to working with IDOC objects.

Re: Idoc

Former Member — Mon, 26 May 2008 10:45:58 GMT

hi rajarshi,

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

i think this link will help u

to get the overview of an idoc how to create

and the transcations which are used regularly are se18,se19,we18,we19,we30,we02

regards,

sindhu.

Re: Idoc

Former Member — Mon, 26 May 2008 10:50:48 GMT

hi,

if u want an example to follow.....the sequence is as follows.....

Lets take an example to understand this:

u2022 Whenever a Purchase Order (PO) is created we want to send the IDOC to a vendor.

u2022 The PO is sent in the form of an IDOC to the vendor (partner). That partner has to be EDI enabled in that system.. SAP should realize that it could send doc to this vendor electronically. (Creating a vendor is not sufficient). Partner Profile should be EDI enabled i.e. A partner profile should exist in the sap system.

u2022 Quotation, RFQ, PO, SO, Invoice, delivery challan etc are some of the commonly exchanged documents through IDOCs

u2022 We create only one profile for both inbound and outbound IDOCs.

u2022 Partner profile should contain message typeu2026u2026to be able to exchange the IDOC.

u2022 We define partner type, partner function and message type (it distinguish if an IDOC is being sent to same person in same function for different reason e.g. SO)

Process Code

Creating Outbound Process Code (WE41)

u2022 What is Process Code?

Process of filling the IDOC with application data is done by Function Module. But, function module is not assigned to a Partner. It is encapsulated by a Process Code and this Process Code is assigned to a Partner in Partner Profile.

u2022 Assigning Function Module to Process Code

- Go to Transaction WE41.

- Switch to u201CChangeu201D Mode and click u201CNew Entriesu201D.

- Enter Process Code Name and assign the Function Module created.

Partner Profile

Creating Partner Profile (WE20)

u2022 What is Partner Profile?

We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles.

u2022 Steps to create Partner Profile

- Goto Transaction WE20.

- Click on Create Button.

- Enter the Number of Vendor Created in Partner No. and u2018LIu2019 in Partner Type fields.

- Save the Data.

- For Outbound Partner Profile we have to create Outbound Parameters

- Specify Partner Function, Message type created, Port (create a port in WE21),Basic Type and Output Mode.

- Goto u201CMessage Controlu201D Tab and link the Message Type and Process Code created.

- Save.

Change Application Data to be transmitted

u2022 Change Purchase Order Created using transaction ME22n for the Vendor to which partner profile has been created.

u2022 Go to u201CMessagesu201D , add the new u201CMessage Typeu201D to the list and Save the Purchase Order.

u2022 An IDOC will be created for the purchase order and will be dispatched to PORT mentioned.

Check the status of IDOC (WE02)

u2022 The IDOC status can be checked using transaction WE02

u2022 If the status is u201903u2019, it implies that IDOC is passed to Port.

Summary: IDOC Workflow

The sequence:

1. Checks whether Partner profile exists or not

2. Whether that PP has a outbound parameter

3. Whether NEU message type is there or not (message control)

4. Checks the process code (gives the name of Function module)

5. Checks immediate transfer or batch transfer

6. Based on that it checks the receiver port

7. Then it will trigger the RFC destination

8. Then it triggers the event on subsystem/customer system

9. Transfer the IDOC to a port and transfer the Idoc in terms of file and it triggers the customer system

10. Customer knows from where it should pick up the file u2026.it picks up the file.

Extending an Existing IDOC Type

u2022 Used in cases where some additional information is required in addition to that supplied by the Standard IDOC Type.

u2022 In Transaction WE30 we create the IDOC as an Extension and specify the basic type for which it is an extension.

u2022 We add the segments needed as children to existing ones.

u2022 None of the Reference Segments can be deleted or changed.

Extension Child Segs

Basic Type (ORDERS01)

Cannot be modified

IDOC Views

u2022 An IDOC type can be used for more than one message type, which results in IDOCs containing more fields than required for a particular message type.

u2022 IDOC views are used to improve performance in generating IDOCs to ensure only the relevant segments are filled with data.

u2022 IDOC Views are important only for Outbound Processing.

IDOC Type

Processing Logic

u2022 The processing logic associated with the IDOC is the function module that is written to handle the inbound/outbound IDOC.

u2022 Its written just like any function module but has to follow a standard interface (i.e. Import, Export, Changing & Tables) parameters and it is should be RFC enabled.

u2022 In this function module we are effectively building up a table of type EDID4 (IDOC Data table) and change the control record.

regards,

praveena.

Re: Idoc

Former Member — Mon, 26 May 2008 10:58:54 GMT

Hi Rajarshi,

This article gives you an overall view:

http://articles.techrepublic.com.com/5100-10878_11-1051228.html

What is IDOC

u2022 IDOC = Intermediate Document

u2022 IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.

u2022 When we execute an outbound ALE or EDI Process, an IDOC is created

u2022 In an inbound ALE or EDI process, an IDOC serves as input to create an application document.

u2022 In the SAP System, IDOCs are stored in database.

u2022 Every IDOC has an unique number(within a client).

u2022 IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP)

u2022 IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In case of any conflict in data size, it adopts one with greater length

u2022 IDOCs are independent of the direction of data exchange e.g. ORDERS01: Purchasing module : Inbound and Outbound

u2022 IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format.

IDOC Components

Basic IDOC Type (we30)

u2022 Basic IDOC Type defines the structure and format of the business document that is to be exchanged.

u2022 IDOC Type has a

u2013 specific name

u2013 list of permitted segments

u2013 hierarchy of segments

u2013 mandatory/optional segments

u2013 minimum/maximum range of each segment.

Segments

u2022 Segment defines the format and structure of a data record. Segments are reusable components.

u2022 For each segment SAP creates

u2013 Segment Type (version independent)

u2013 Segment Definition (version dependent)

u2013 Segment Documentation

u2022 The last 3 characters is the version of the segment

u2022 Definitions keep changing as per the version but the segment type remains the same

IDOC Run-Time Components

u2022 An IDOC is an instance of an IDOC Type

u2022 At run time the following events occur

u2013 A unique IDOC no. is allocated by SAP

u2013 One control record is attached to the IDOC

u2013 Segments translate into data records

u2013 Status records are attached

u2013 Syntax rules are checked.

u2022 Each IDOC has 3 parts

u2013 Control Record

u2013 Data Record

u2013 Status Record

u2022 We02 or We05

Control Record

u2022 All control record data is stored in EDIDC table. The key to this table is the IDOC Number

u2022 It contains information like IDOC number, sender, recipient information, channel it is using, which port it is using etc.

Data Record

u2022 Data record contains application data like employee header info, weekly details, client details etc

u2022 All data record data is stored in EDI_DD40 table and EDI_DD

Status Record

u2022 Status record are attached to an IDOC at every milestone or when it encounter errors.

u2022 All status record data is stored in EDID8 table.

Where and How IDOC is created

Where and How an IDOC is created?

u2022 Lets take an example to understand this:

u2022 Whenever a Purchase Order (PO) is created we want to send the IDOC to a vendor.

u2022 Quotation, RFQ, PO, SO, Invoice, delivery challan etc are some of the commonly exchanged documents through IDOCs

u2022 We create only one profile for both inbound and outbound IDOCs.

u2022 Partner profile should contain message typeu2026u2026to be able to exchange the IDOC.

u2022 We define partner type, partner function and message type (it distinguish if an IDOC is being sent to same person in same function for different reason e.g. SO)

Process Code

Creating Outbound Process Code (WE41)

u2022 What is Process Code?

u2022 Assigning Function Module to Process Code

- Go to Transaction WE41.

- Switch to u201CChangeu201D Mode and click u201CNew Entriesu201D.

- Enter Process Code Name and assign the Function Module created.

Partner Profile

Creating Partner Profile (WE20)

u2022 What is Partner Profile?

We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles.

u2022 Steps to create Partner Profile

- Goto Transaction WE20.

- Click on Create Button.

- Enter the Number of Vendor Created in Partner No. and u2018LIu2019 in Partner Type fields.

- Save the Data.

- For Outbound Partner Profile we have to create Outbound Parameters

- Specify Partner Function, Message type created, Port (create a port in WE21),Basic Type and Output Mode.

- Goto u201CMessage Controlu201D Tab and link the Message Type and Process Code created.

- Save.

Change Application Data to be transmitted

u2022 Change Purchase Order Created using transaction ME22n for the Vendor to which partner profile has been created.

u2022 Go to u201CMessagesu201D , add the new u201CMessage Typeu201D to the list and Save the Purchase Order.

u2022 An IDOC will be created for the purchase order and will be dispatched to PORT mentioned.

Check the status of IDOC (WE02)

u2022 The IDOC status can be checked using transaction WE02

u2022 If the status is u201903u2019, it implies that IDOC is passed to Port.

Summary: IDOC Workflow

The sequence:

1. Checks whether Partner profile exists or not

2. Whether that PP has a outbound parameter

3. Whether NEU message type is there or not (message control)

4. Checks the process code (gives the name of Function module)

5. Checks immediate transfer or batch transfer

6. Based on that it checks the receiver port

7. Then it will trigger the RFC destination

8. Then it triggers the event on subsystem/customer system

9. Transfer the IDOC to a port and transfer the Idoc in terms of file and it triggers the customer system

10. Customer knows from where it should pick up the file u2026.it picks up the file.

Extending an Existing IDOC Type

u2022 Used in cases where some additional information is required in addition to that supplied by the Standard IDOC Type.

u2022 In Transaction WE30 we create the IDOC as an Extension and specify the basic type for which it is an extension.

u2022 We add the segments needed as children to existing ones.

u2022 None of the Reference Segments can be deleted or changed.

Extension Child Segs

Basic Type (ORDERS01)

Cannot be modified

IDOC Views

u2022 An IDOC type can be used for more than one message type, which results in IDOCs containing more fields than required for a particular message type.

u2022 IDOC views are used to improve performance in generating IDOCs to ensure only the relevant segments are filled with data.

u2022 IDOC Views are important only for Outbound Processing.

IDOC Type

Processing Logic

u2022 The processing logic associated with the IDOC is the function module that is written to handle the inbound/outbound IDOC.

u2022 Its written just like any function module but has to follow a standard interface (i.e. Import, Export, Changing & Tables) parameters and it is should be RFC enabled.

u2022 In this function module we are effectively building up a table of type EDID4 (IDOC Data table) and change the control record.

(The above article can be found at http://sapsdforum.com/2007/12/02/idoc/)

Please go through the following link for code snippets:

http://www.erpgenie.com/sapedi/idoc_abap.htm#ALE%20Inbound%20Pre-Processing

Hope this helps you.

Please Reward if Helpful.

Regards,

Kalyan Chakravarthy

Edited by: Kalyan Chakravarthy Misra on May 26, 2008 1:00 PM

Re: Idoc

Former Member — Mon, 26 May 2008 11:06:37 GMT

Hi,

Please check below link...

http://www.soacity.org/www7/EDI/HTML/IDocBook.htm

Regards,

N M Poojari.