topic Re: extending an idoc in Application Development and Automation Discussions

extending an idoc

Former Member — Wed, 26 Dec 2007 20:34:10 GMT

hi gurus,

there is standard idoc type orders05

but how do i make a customized idoc out of it.

i need to create an idoc with type orders05 with added functionality, how do i do this.

thank you.

Re: extending an idoc

Former Member — Wed, 26 Dec 2007 20:53:45 GMT

Sanjana,

What are you trying to do? Do you want to extend an IDOC or Create a brand new IDOC based on an existing one and add new fields to it.

You have to take different routes for both.

Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process.

In brief IDoc extension takes place when extra fields are required for the business process.

If you are creating a new IDOC.....

1) Create segment (WE31)

Of course it will have naming convention for different company. Here are some tips:

If you copy from existing or std segment eg: Z1E1EDP01_01.

If not you can just put Z1….but this is only the example.

2) Create IDOC Types (WE30)

3) Create message type (WE81)

4) Link message type with basic type (WE82)

5) Create FM

In the FM all the attributes should be the same for Inbound or Outbound. Basically you can get an example from the std FM eg: Inbound - IDOC_INPUT_DELVRY

Outbound - IDOC_OUTPUT_SHPMNT.

6) Create Process Code (Inbound - WE41/ Outbound - WE42)

IMPORTANT: Before you key in the FM, you are required to add the FM in this table V_TBD51.

7) Link FM with Basic Type

......

le'me know if you need more information.

Award points if useful.

Vinodh Balakrishnan

Re: extending an idoc

Former Member — Thu, 27 Dec 2007 00:23:12 GMT

Hi Sanjana,

Here is the link:

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm

Regards,

Ravi Kanth Talagana

Re: extending an idoc

Former Member — Thu, 27 Dec 2007 04:20:04 GMT

Hi ,

plz check these links ..

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

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)

- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.

- Click on Create new and enter a description and press enter.

- Click on ZIDOCTYPE01 and then on the Create icon.

- Enter ZIDOCTYPE as the segment type, click on Segment Editor.

- Enter a description for your segment type and create.

- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.

- Save and generate, press back

- To release the segment choose Goto, Release from the menu.

- Check the box on the line of your segment.

- Save, back and enter.

- Your Idoc type structure should be displayed with your new segment.

- Save and back.

- To release the Idoc type choose Extras, Release type from the menu and Yes.

Regards,

Sana.

reward points for helpful answers..

Re: extending an idoc

Former Member — Thu, 27 Dec 2007 04:23:55 GMT

Hi,

we can extende the idoc by using the segments. in these segemnt we add the data fields. go to the tcode WE31.

here we can extend the idoc.

we can crete the custom idoc like this

Aim: Transfer the data from one system to another using user customized IDOC.

Sender System:

Server: 172.25.8.185

Client: 200

Data from Z table: zsach1

ReceiverSystem:

Server: 172.25.9.198

Client: 800

Data from Z table: zsach1

Data is fetched from Z table on the sender system and inserted it in the Z table of Receiver system using ALE/IDOC.

Settings on the Sender End

Table Creation T – Code SE11. The table contains data that is to be sent to Receiver.

ALE Configuration

T-Code – SALE

Defining Logical System

200 is our sender

800 is our receiver

Assigning Client to Logical System

200 is our sender

800 is our receiver

Defining Target System for RFC Calls (Tcode – SM59)

Click on R/3 Connections and then Create TAB

Step 1

Step 2

Save and test the connection.

Defining Port

The sender system is connected to the receiver system through this Port.

Defining Partner Profiles

The partner for client 200(Sender) is the client 800 (Receiver)

Since this is a sender we have to define only Outbound Parameters in this case.

Here you can see the Message type is Z message type.

2. Maintaining Distribution Model (TCode BD64 )

Create new Distribution Model

Add Message Type

Now Distribute this Model View

Distribute it from Edit à Model View à Distribute

Defining the Z Segment type

Tcode – WE31

Defining the Basic Type

T Code WE30

Click on New

This will take you to next screen as follows

Here you have connected the basic type to the segment type.

Enter again and this will take you to screen as follows

This shows the relation between the basic and the segment types.

Next you need to make the entry of the segment in the system table.

Tcode : WE81

Next is the following entry which is required.

Here you are specifying the message type and the basic type and the release version.

This is all about the configuration you need to do on the sender side.

Now on the sender side you also need a program that will fetch the required data, couple it in the IDOC format and post it.

Here is a small piece of code that could be useful.

*&----

*& Report ZSACH_CUST_IDOC *

*& *

*&----

*& *

*&----

report zsach_cust_idoc .

parameters : p_logsys like tbdlst-logsys.

data : gen_segment like edidd-segnam value 'ZSACH'.

data : control_dat like edidc,

gen_data like z1hdr .

tables :zsach1.

data: begin of inttab occurs 0,

lname type z1hdr-lname,

fname type z1hdr-fname,

end of inttab.

data :

int_edidd like edidd occurs 0 with header line,

int_edidc like edidc occurs 0 with header line.

select * from zsach1 into corresponding fields of table inttab.

if sy-subrc ne 0.

message 'no data' type 'I'.

exit.

endif.

control_dat-mestyp = 'ZSACH'.

control_dat-idoctp = 'ZSACH'.

control_dat-rcvprt = 'LS'.

control_dat-rcvprn = p_logsys.

loop at inttab.

gen_data-lname = inttab-lname.

gen_data-fname = inttab-fname.

GEN_DATA-SSN = INTTAB-SSN.
GEN_DATA-DOB = INTTAB-DOB.

int_edidd-segnam = gen_segment.

int_edidd-sdata = gen_data.

append int_edidd.

endloop.

call function 'MASTER_IDOC_DISTRIBUTE'

exporting

master_idoc_control = control_dat

OBJ_TYPE = ''
CHNUM = ''

tables

communication_idoc_control = int_edidc

master_idoc_data = int_edidd

exceptions

error_in_idoc_control = 1

error_writing_idoc_status = 2

error_in_idoc_data = 3

sending_logical_system_unknown = 4

others = 5

if sy-subrc <> 0.

message id sy-msgid type sy-msgty number sy-msgno.

else.

loop at int_edidc.

write 😕 'IDOC GENERATED',int_edidc-docnum.

endloop.

commit work.

endif.

Settings on the receiver side.

The ALE configuration is same as we did it on the sender side. Please refer to earlier pages.

The receiver specific differences are mentioned below.

T-Code – SALE

200 is our sender

800 is our receiver

Steps

Defining Logical System (Same as sender)

Assigning Client to Logical System (Same as sender)

Defining Target System for RFC Calls (Tcode – SM59) (Same as sender)

Defining Port(Same as sender)

Defining Partner Profiles – Here we are accepting the data from Sender system. Hence we need to configure it as Inbound.

Click on the sign above to go to next screen.

Here the message type is to be created again as it was created on the sender side.

The following steps are repeated, as done on the sender side, on the receiver end

Tcode WE30

Tcode WE31

Tcode WE82

Tcode WE81

Here on the receiver end, we need to specify a process code at the time of defining the partner profile.

Process code is something that has the logic defined about what to be done after receiving the IDOC.

In our case, on receipt of the IDOC, we are updating the Z Table. i.e Inserting the data from the IDOC into the Z Table.

Creating a Process Code

Tcode – WE42

The logic associated is coded in the Function Module which is specified in the Identification Field above.

Also the processing type is selected as Processing by Function Module as above.

The function Module is specified in the following screen.

To have your function Module in the above drop down list, the entry is to be made using the following transaction

TCode – BD51

Once the entry is done here, the function module appears in the drop down list in the previous stage.

Also it is important to make the following entry

Tcode WE57

Function Module will look something as below:

Source Code

function z_idoc_input_sach .

*"----

""Local interface:

*" IMPORTING

*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD

*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC

*" VALUE(NO_APPLICATION_LOG) LIKE SY-DATAR OPTIONAL

*" VALUE(MASSSAVEINFOS) LIKE MASSSAVINF STRUCTURE MASSSAVINF

*" OPTIONAL

*" EXPORTING

*" VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT

*" VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR

*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK

*" VALUE(CALL_TRANSACTION_DONE) LIKE 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

*"----

include mbdconwf.

data : it_emp_data like zsach1 occurs 0 with header line.

data : gen_data like zsach1 .

workflow_result = c_wf_result_ok.

data : counter type int4.

select count( * ) from zsach1 into counter.

counter = counter + 1.

loop at idoc_contrl.

if idoc_contrl-mestyp ne 'ZSACH'.

raise wrong_function_called.

endif.

clear gen_data.

refresh it_emp_data.

loop at idoc_data where docnum eq idoc_contrl-docnum.

if idoc_data-segnam = 'ZSACH'.

gen_data = idoc_data-sdata.

it_emp_data-mandt = counter.

it_emp_data-lname = gen_data-lname.

it_emp_data-fname = gen_data-fname.

counter = counter + 1.

append it_emp_data.

else.

message 'ERROR' type 'I'.

endif.

endloop.

insert zsach1 from table it_emp_data.

*****

call function 'EDI_DOCUMENT_OPEN_FOR_EDIT'

exporting

document_number = idoc_data-docnum

importing

idoc_control = idoc_contrl

tables

idoc_data = idoc_data

exceptions

document_foreign_lock = 1

document_not_exist = 2

document_not_open = 3

status_is_unable_for_changing = 4

others = 5.

call function 'EDI_CHANGE_DATA_SEGMENTS'

tables

idoc_changed_data_range = idoc_data

exceptions

idoc_not_open = 1

data_record_not_exist = 2

others = 3.

data t_itab_edids40 like edi_ds40 occurs 0 with header line.

clear t_itab_edids40.

t_itab_edids40-docnum = idoc_data-docnum.

t_itab_edids40-status = '51'.

t_itab_edids40-repid = sy-repid.

t_itab_edids40-tabnam = 'EDI_DS'.

t_itab_edids40-mandt = sy-mandt.

t_itab_edids40-stamqu = 'SAP'.

t_itab_edids40-stamid = 'B1'.

t_itab_edids40-stamno = '999'.

t_itab_edids40-stapa1 = 'Sold to changed to '.

*t_itab_edids40-stapa2 = t_new_kunnr.

t_itab_edids40-logdat = sy-datum.

t_itab_edids40-logtim = sy-uzeit.

append t_itab_edids40.

call function 'EDI_DOCUMENT_CLOSE_EDIT'

exporting

document_number = idoc_data-docnum

do_commit = 'X'

do_update = 'X'

write_all_status = 'X'

tables

status_records = t_itab_edids40

exceptions

idoc_not_open = 1

db_error = 2

others = 3.

endfunction.

Running the Application

Sender system

Execute the program we created earlier

Checking the IDOC

T Code WE02

Checking the data on the Receiver end

Tcode: WE02

The IDOC has arrived here

Checking the Data

Double click on the IDOC

Checking the Database

This way, the data has come to the receiver end successfully.

please reward points,

regards,

satish.

Re: extending an idoc

Former Member — Thu, 27 Dec 2007 04:41:34 GMT

Hi,

for this u need to extend ur idoc type Orders 05.

-->cretae ur zsegment in we31 with ur custom fiedls.

--> go to we30 , enter ZIDOC and selcet Extension , it will ask for Basic Idoc type , here u eneter ORDERS05.

And then add ur Zsegmant to Zidoc type.

--> Cretae ur Zmessage in We81

--> Assign ur Zmessage to ZIDOC type in WE82.

--> As this ZIDOC type is extension of ORDERS05, this idoc will be populated by message control.

So ME10 (idoc_output_orders)

and Me11(idoc_output_ordchg) is the Prcocess Code which will points to Function Module.

--> Now add ur own functionality to fill th eZSEGMENT in the cUstome exit of th eFunction Modules..

Thses are the things which u need to do ....

Revert back if any issues,

Regards,

Naveen