IDOC Step by step

[Former Member]

Hi All,

I am an ABAPer but new to IDOC.

Can anyone send me the detailed step-by-step procedure for sending data from one sytem to another thru IDOC.

Better if some example be given.

Thanks.

Vinod.

[Former Member]

Hi All,

I am an ABAPer but new to IDOC.

Can anyone send me the detailed step-by-step procedure for sending data from one sytem to another thru IDOC.

Better if some example be given.

Thanks.

Vinod.

[Former Member]

http://help.sap.com

[Former Member]

Hi,

CHeck this link for a IDOC ...The steps are mentioned in details about creating custom idoc..

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

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

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

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30 )

Create Message Type ( WE81 )

Assign Idoc Type to Message Type ( WE82 )

Creating a Segment

Go to transaction code WE31

Enter the name for your segment type and click on the Create icon

Type the short text

Enter the variable names and data elements

Save it and go back

Go to Edit -> Set Release

Follow steps to create more number of segments

Create IDOC Type

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

Create Message Type

Go to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message ?The table is cross-client (see Help for further info)?. Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc Type

Go to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message ?The table is cross-client (see Help for further info)?. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

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://www.sapgenie.com/sapedi/index.htm

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

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

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

Pls reward if helpfull.

Regards,

Sharath

[Former Member]

Hi,

Go to SAPTECHNICAL.com..it is really good to do the idoc...

Thank u,

Manjula Devi.D

[Former Member]

Hi,

Follow the steps below.

Creating Custom IDoc type and Message type

All the objects created should be present on both source as well as target system(s).

1. Create segments u2013 Transaction WE31

u2022Create a segment

u2022Add all fields of table zkstd to it

u2022Save the segment

u2022Release it using the menu path Edit -> Set Release

2. Create Basic IDoc type u2013 Transaction WE30

u2022Create a Basic type zkkuidoc

u2022Add the created segments in the hierarchy shown

u2022Maintain attributes for each of the segments

u2022Save the object and go back

u2022Release the object using the menu path Edit -> Set Release

3. Create/Assign Message type u2013 Transactions WE81/WE82

u2022Go to WE81

u2022Create a new Message type

u2022Save the object

u2022Go to WE82 and create new entry

u2022Assign the message type to the basic type

u2022Also specify the Release Version as 620.

u2022Save the object

Outbound Settings

1) Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE

u2022Go to Define Logical System

u2022Define a new logical system to identify the local system and save it

u2022Now, go to Assign Client to Logical System

u2022Add a new entry

u2022Specify the client, previously created logical system and other attributes

u2022Save the entry

u2022Define a new logical system to identify the partner system and save it

2) Maintain RFC Destinations u2013 Transaction SM59

u2022Create a new RFC destination for R/3 type connection

u2022Specify the target host on Technical settings tab

u2022Provide the Logon credentials on the Logon/Security tab

u2022Save the settings

u2022To verify the settings, Click on Test connection or Remote logon

3) Define Ports u2013 Transaction WE21

u2022We need to define a tRFC port for the partner system

u2022Click on Transactional RFC node

u2022Create a new port

u2022Provide a description

u2022Specify the name of the target RFC destination

u2022Save the object

4) Maintain Distribution Model u2013 Transaction BD64

u2022Click on Change

u2022Create a new model view k

u2022Provide a Short text and Technical name to the model view

u2022Add message type

u2022Specify sender and receiver systems

u2022Also, specify the message type that we created previously

u2022Save the Distribution model

5) Generate/Create Partner Profile u2013 Transactions BD82/WE20

u2022To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles

oOtherwise, you may use transaction WE20 to create a partner profile

u2022On selection screen, specify the model view, target system and execute

u2022The result log will be displayed on the next screen

u2022To verify the partner profile go to WE20

u2022Check the partner profile for the target system

6) Distribute Model View u2013 Transaction BD64

u2022Select the Model View

u2022Go to menu path Edit -> Model View -> Distribute

u2022Result log will be displayed on the next screEN.

NOW, WRITE THE IDOC GENERATION PROGRAM.

Inbound IDoc Posting Function Module

In the receiving system, create a function module using SE37.

Inbound Settings

u2022Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed)

u2022Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed)

u2022Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed)

u2022Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed)

u2022Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed)

u2022Assign Function Module to Logical message u2013 Transaction WE57

oCreate a new entry

oSpecify name of the Function Module

oAlso, specify Type as F, Basic IDoc type as zkkuidoc, Message type as zkkumsg and Direction as 2 (Inbound)

oSave the entry

u2022 Define Input method for Inbound Function Module u2013 Transaction BD51

oCreate a new entry

oProvide Function Module name

opecify the Input method as 2

oSave the entry

u2022Create a Process Code u2013 Transaction WE42

oCreate a new Process Code zkkuproc

oSelect Processing with ALE Service

oChoose Processing type as Processing by function module

oSave the entry

oOn the next screen, select your function module from the list

oSave the changes

oNow you will be taken to the next screen

oDouble-click on Logical message

oIn the Assignment to logical message, specify the message type zkkumsg

oSave the changes

Send and receive data

On the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02

Check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.

Reward points if useful.

Regards..

kiran

[Former Member]

Thanks to everyone.