How to set up ORDERS, ORDRSP, DESADV, INVOIC IDOCs interchange in the same system

In order to prepare IDOCs interaction between two systems, it's better to check them in the same (SAP) system. Here I'll show, which steps you should pass to.

At the beginning I will describe system & document environment.
I'm going to use two organization units Distributor and Manufacturer and four IDOC message types: ORDERS, ORDRSP, DESADV, INVOIC.
Every active step bellow will be highlighted by dark arrow, which also point a direction of IDOC from OUT to IN:

General view:

 

Steps 1-2 (A): IDOC ORDERS ORDERS Purchase order / order
I use Basic type ORDERS05, because only this can transfer material's configuration, which is important for Automotive.



Pre-requisites for Outbound part:

• XK01 – Create vendor (90500) and attach with SO customer (C40AF00323 – correspondence view, field EIKTO)

• WE20 – Create Vendor 90500 (Partner type – LI)
• WE20 – Create Outbound parmtrs. For Vendor 90500 (Partner type – LI) , (othewise error message VN032 Maintain outgoing EDI-connection data for partner 90500)
• MN04 – Create output type NEU for Vendor (90500)

Pre-requisites for Inbound part:

• WE20 – Create Inbound parmtrs. For Logical system T90CLNT090 (Partner type – LS)
• VOE2 - create EDSDC Entry (othewise error message VG204 - VKORG, VTWEG, SPART cannot be determined for customer C40AF00323 , vendor 0000090500)
• VOE4 - create EDPAR Entry (othewise error message VG140 - Partner number 9000 for customer C40AF00323 , partner function WE does not exist) LVEDAF2J (FM IDOC_INPUT_ORDERS) – for debug message VG140

• VD51 - Maintain Customer-Material Inforecord (othewise error message VG203 - The material number for item 000010 could not be identified)
• VD51 - fill text (not only material code for customer-material inforecord) othewise error message no. 00347 Field VBAP-ARKTX (1) is not an input field

Steps 3-4 (B): IDOC ORDRSP Purchase order / order confirmation

Pre-requisites for Outbound part:

• WE20 – Create Outbound parmtrs. For Customer C40AF00323 (Partner type – KU & SP)
• VV11 - Create Output Type BA01

Pre-requisites for Inbound part:

• WE20 – Create Inbound parmtrs. For Logical System T90CLNT090 (Partner type – LS)
• ME12 – Set up confirmation control key for Purchase Inforecord

Steps 5-6 (C): IDOC DESADV Delivery: Shipping notification

Pre-requisites for Outbound part:

• WE20 – Create Outbound parmtrs. For Customer C40AF00323 (Partner type – KU & SH)
• VV21 - Create Output Type LALE
• WE42 – change for DELS FM to IDOC_INPUT_DESADV1 (othewise error message B1252 - Function module not allowed: BORES_IDOC_INPUT_DESADV1)

Pre-requisites for Inbound part:

• WE20 – Create Inbound parmtrs. For Logical System T90CLNT090 (Partner type – LS)

Steps 7-8 (D): IDOC INVOIC Invoice/Billing Document

Pre-requisites for Outbound part:

• WE20 – WE20 – Create Outbound parmtrs. For Bill-To C40AF00323 (Partner type – BP)
• VV31 - Create Output Type RD00

Pre-requisites for Inbound part:

• WE20 – Create Inbound parmtrs. For Logical System T90CLNT090 (Partner type – LS)
• OBCA – Maintain Table T076B, create two records in case you use the same system (othewise error message FD006 - A company code cannot be determined for LS 0000090500)
• OBCE – Maintain Table T076S (othewise error message FD145 - Program parameters for LS T90CLNT090 9000 have not been set)
• OBCD - Maintain Table T076M (othewise error message in application log FD008 - Assigning a new tax key for B2 and VAT 18.000 not possible)