October 2007


For IDOC in WM it will have some different configuration as in WM no output type are required for the transaction.

If you required IDOC in WM you have to configure extra setting in OMKY.

1) In OMKY under R/3 ->Ext System choose Interface Control. Select your warehose number, source type, destination type, movement type and under Receiver fill in the partner number name.

2) The IDOC generation is based on those field that mention in step 1. Only those field that fullfill the requirement will generate IDOC.

In WM not all the message type have Inbound and Outbound functions. Please refer to the link http://help.sap.com/saphelp_nw04/helpdata/en/52/16ac57543311d1891c0000e8322f96/frameset.htm

As I received some comments that requested to have a step by step how-to create IDOC, I will try to explain the step here…

In IDOC the main configuration will be in Partner Profile (WE20)

1) Create a Logical system to use in the logical system as Partner No in WE20

Tcode: SALE -> Sending and Receiving Systems -> Logical System -> Define Logical System

2) In WE20 create new partner number and put in the logical system name that you created in the 1st step and partner type = LS.

3) In Outbound/ Inbound Parameter fill in the relevant message type.

4) For Outbound you will require to fill in Receiver port. Before this you have to create a port using WE21 by filling in your RFC destination name.

Notes: If your destination are using RFC create the port under Transaction RFC. File are used if the data are send using file format and same as XML File.

5) Fill in the basic type or Extension if necessary under Outbound Options.

6) Fill in also data under message control tab for application, message type, process code and other relevant info.

7) For Inbound parameters it has less info to fill in. You need to fill in the process code. This process code will tie to the Function module. Just double click on the process code to check on the function module.

WE41 – Outbound process code

WE42 – Inbound process code

8) After you have completed these steps create the relevant document eg: Sales order (VA01) and make sure you put in the output type in the Sales order. Check your IDOC created under WE02. If no IDOC is created check your partner profile and make sure all the partner function, message type in your SO output type fullfill the requirement in partner profile.

These are the basic steps you are required to setup IDOC. Hope these steps are clear for you to start your own IDOC

  1. Try Goto RSA1 -> PSA, find the PSA, then delete the error request from there
  2. Goto RSRV, drag in the ‘foreign key ..’ and ‘check status…’ tests to the right, then put in the ODS name, and run
  3. ST22, see if there is any relevant error
  4. SM37, job name you put “BI_DEL*” basically try to find the deletion job that failed see if u can find it
  5. Solution: a) Goto table RSODSACTREQ

b) Put the request number in the request ID

Eg: “REQU_ALZLI4CPDLXMINAQ7397WLNWC”

c) Delete that record, check the record, then ‘table entry’ -> ‘delete’

d) Goto table RSODSACTUPDTYPE, deletes all the entries which have the same request number

e) After deleted go to SE37,

RSDRO_SETSTATUS_FOR_REQUEST_20

I_ODSOBJECT put your ODS name

I_ACTREQUEST put your ODS request name

Eg:“ODSR_0V86SZU38DNXULICERI5A6CJ7”

  1. If Reconstruct DO NOT DELETE any of the Request in the ODS. It will cause the following request wont activate and roll up.

Solution: Goto the request QM status and manually set to RED although it is already in red.