topic Re: Using Idocs in Application Development and Automation Discussions

Using Idocs

Former Member — Wed, 13 Sep 2006 07:12:08 GMT

Hi,

Can you plz explain me the steps in creating an IDOC and using it?

Srinivas.

Re: Using Idocs

gopi_narendra — Wed, 13 Sep 2006 07:16:06 GMT

Go thru these links

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

ALE/ IDOC/ XML

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

http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp

http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm

IDOC Convertion

/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment

Re: Using Idocs

Former Member — Wed, 13 Sep 2006 07:18:08 GMT

Hi,

Send me your mail id. Will send you some good docus on IDocs.

Regarsd,

Senthil

Re: Using Idocs

Former Member — Wed, 13 Sep 2006 09:52:21 GMT

hi,

my mailid is srinureddy11@gmail.com

Re: Using Idocs

Former Member — Wed, 13 Sep 2006 10:10:21 GMT

Hi Srinivas,

Check you mail. I have sent you one document.

Raveendra.

Re: Using Idocs

Former Member — Wed, 13 Sep 2006 10:22:37 GMT

There are basically two types of IDOCs.

Basic IDOCs

Extended IDOCs

Idoc Components

Basic Idoc

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extension Idoc

Extending the functionality by adding more segments to existing Basic IDOCs.

Creation of IDoc

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.

Create IDOC Type

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

u can also check all these links related to idocs

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

http://www.allsaplinks.com/

http://www.sap-img.com/

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

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

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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html

http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358

http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm

regards

Re: Using Idocs

Former Member — Thu, 14 Sep 2006 06:02:07 GMT

Hi Ravi,

Your Reply is good. But, How Can I use the Idoc Type that was created using the steps you have provided? Can anyone please explain?

I know the creation of Segment type, Basic Idoc Type, assigning a message type and releasing. But, how can I use that in the applications?

Thanks in advance.

Srinu.

Re: Using Idocs

Former Member — Fri, 15 Sep 2006 08:43:16 GMT

Here is a sample program to Distribute IDOC.

This May Help You

DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',

C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',

C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',

Z1INVRV LIKE Z1INVRV,

C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',

IDOC_CONTROL LIKE EDIDC,

T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,

IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.

*--- Move the document header into a structure

LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.

ENDLOOP.

*--- Move the document item data into a structure

LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).

ENDLOOP.

*--- Populate the IDoc segment’s field with the required data

CLEAR Z1INVRV.

Z1INVRV-LIFNR = DOC_ITEM-LIFNR. “Store vendor number for filter

Z1INVRV-XBLNR = DOC_HEAD-XBLNR. “Billing number

IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. “Segment name

IDOC_DATA-SDATA = Z1INVRV. “Segment data

APPEND IDOC_DATA. “Populate IDoc internal table

*--- Move the control data info required for the distribution

IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.

IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.

*--- Call the distribute function with the required parameters

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK

EXPORTING

MASTER_IDOC_CONTROL = IDOC_CONTROL

TABLES

COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL

MASTER_IDOC_DATA = IDOC_DATA

EXCEPTIONS

ERROR_IN_IDOC_CONTROL = 1

ERROR_WRITING_IDOC_STATUS = 2

ERROR_IN_IDOC_DATA = 3

SENDING_LOGICAL_SYSTEM_UNKNOWN = 4

OTHERS = 5.

If you are using standard transactions then you can use user_exit to place this code.

Message was edited by: Raveendra Holla

Re: Using Idocs

Former Member — Fri, 15 Sep 2006 08:56:24 GMT

Here is the Example code to receive IDOC.

FUNCTION Z_IDOC_RECEIVE.

*"----

""Local interface:

*" IMPORTING

*" REFERENCE(INPUT_METHOD) TYPE BDWFAP_PAR-INPUTMETHD

*" REFERENCE(MASS_PROCESSING) TYPE BDWFAP_PAR-MASS_PROC

*" EXPORTING

*" REFERENCE(WORKFLOW_RESULT) TYPE BDWFAP_PAR-RESULT

*" REFERENCE(APPLICATION_VARIABLE) TYPE BDWFAP_PAR-APPL_VAR

*" REFERENCE(IN_UPDATE_TASK) TYPE BDWFAP_PAR-UPDATETASK

*" REFERENCE(CALL_TRANSACTION_DONE) TYPE BDWFAP_PAR-CALLTRANS

*" TABLES

*" IDOC_CONTRL STRUCTURE EDIDC

*" IDOC_DATA STRUCTURE EDIDD

*" IDOC_STATUS STRUCTURE BDIDOCSTAT

*" RETURN_VARIABLES STRUCTURE BDWFRETVAR

*" SERIALIZATION_INFO STRUCTURE BDI_SER

*" EXCEPTIONS

*" WRONG_FUNCTION_CALLED

*"----

*--- Declaration of local variables

DATA: C_SEGNAM(10) TYPE C VALUE 'Z1B_SEG'.

Data: T_Z1B_SEG like Z1B_SEG.

data: begin of t_zravtest OCCURS 0.

include structure zravtest.

data: end of t_zravtest.

*-Loop through the IDOCs

LOOP AT IDOC_CONTRL.

*---Loop through the data for the IDOC

LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.

CASE IDOC_DATA-SEGNAM.

WHEN C_SEGNAM.

* Here we get the info from the idoc table

T_Z1B_SEG = IDOC_DATA-SDATA.

ENDCASE.

t_zravtest-val1 = t_Z1B_SEG-value1.

t_zravtest-val2 = t_Z1B_SEG-value2.

append T_ZRAVTEST.

ENDLOOP.

WORKFLOW_RESULT = '0'.

IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.

IDOC_STATUS-STATUS = '53'.

IDOC_STATUS-UNAME = SY-UNAME.

IDOC_STATUS-REPID = SY-REPID.

IDOC_STATUS-MSGTY = SY-MSGTY.

IDOC_STATUS-MSGID = SY-MSGID.

IDOC_STATUS-MSGNO = SY-MSGNO.

IDOC_STATUS-MSGV1 = SY-MSGV1.

IDOC_STATUS-MSGV2 = SY-MSGV2.

IDOC_STATUS-MSGV3 = SY-MSGV3.

IDOC_STATUS-MSGV4 = SY-MSGV4.

RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.

RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.

APPEND RETURN_VARIABLES.

append IDOC_STATUS.

CLEAR IDOC_STATUS.

ENDLOOP.

t_zravtest contains the Data from IDOC.

ENDFUNCTION.

Then do the following steps

The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.

Link Message Type to Function Module (WE57) Client independent

To link a message <MESSAGE> type to a function module <FUNCTION MODULE> follow these steps:

• Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)

• Select an entry (EG. IDOC_INPUT_ORDERS) and copy

• Type in module name <FUNCTION Module NAME>

• Type in basic IDoc type as <IDOC TYPE>

• Type in message type as <MESSAGE TYPE>

• Type object type

• Direction should be set to 2 for inbound

• Enter and save

Define FM settings (BD51) Client independent

• Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)

• Click on New entries

• Type in the name of the new function module <FUNCTION MODULE>

• Enter 0 for mass processing in the output column

• Save and Exit

Maintain process codes (WE42) Client dependent

A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.

To maintain the process code follow these steps:

• Log on to the appropriate receiving system client

• Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)

• Choose Inbound with ALE service

• Choose Processing with function module

• Click on Processing with function module and choose create icon

• Click on New Entries

• Type in process code name EX: ZINR and give it a description and save

• Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.

• Enter your process code EX: ZINR

• Enter your function module <FUNCTION MODULE>

Create inbound partner profile

For each message type you need to maintain the inbound partner profiles.

Maintain receiving system partner profile (WE20) Client dependent

To maintain inbound partner profiles read the document ALE configuration procedure:

• Add the message type <MESSAGE TYPE> with process code EX: ZINR.

• Enter the output mode (background, immediately) for inbound processing and NO message code.

• Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.