Stepwise Guide to EDI Setup in SAP

Step 1: Define EDI Partner Profile (WE20)

1. Go to Transaction Code: WE20
2. Select Partner Type: LI (Vendor) or KU (Customer), depending on your business partner.
3. Click Create and enter the partner number (Customer/Vendor).
4. Under the Inbound Parameters, add:
   • Message Type: ORDERS
   • Process Code: ORDE
   • Inbound Function Module: IDOC_INPUT_ORDERS
   • Processing Mode: Background (or Foreground for testing)
5. Save the partner profile.

Step 2: Define Message Type (WE81)

1. Go to Transaction Code: WE81
2. Ensure ORDERS (Sales Order) message type exists.
3. If not available, create and assign a description.

Step 3: Assign Message Type to IDoc Type (WE82)

1. Go to Transaction Code: WE82
2. Check if the Message Type “ORDERS” is assigned to an IDoc Basic Type (e.g., ORDERS05).
3. If missing, create a new entry.

Step 4: Configure Process Code (BD51 & WE42)

1. Go to Transaction Code: BD51
   • Check if process code ORDE exists.
   • If missing, create and assign the function module IDOC_INPUT_ORDERS.
2. Go to Transaction Code: WE42
   • Link Process Code ORDE with Function Module IDOC_INPUT_ORDERS.

Step 5: Configure EDI Subsystem (SALE & WE21)

1. Logical System Setup
   • Go to Transaction Code: SALE → Define Logical System
   • Assign the Logical System to the Business Partner.
2. Port Definition (WE21)
   • Go to Transaction Code: WE21
   • Define a port for the EDI system.
   • Choose RFC, File, or ALE port type based on requirements.

Step 6: Configure Inbound Processing (WE57 & BD79)

1. Assign Function Module (WE57)
   • Go to Transaction Code: WE57
   • Ensure that IDOC_INPUT_ORDERS is assigned to Message Type ORDERS.
2. Define Field Mapping (BD79 – Optional for Custom Mapping)
   • If field conversions are required, use BD79 to create mapping rules.

Step 7: Define Partner Agreement (Transaction VOE2 – SD Specific)

1. Go to Transaction Code: VOE2
2. Maintain the partner number (Customer), Message Type ORDERS, and Agreement.

Step 8: Test & Process the Inbound IDoc

1. Send a Test IDoc
   • Use WE19 (Test Tool) to generate a test IDoc for ORDERS.
2. Monitor IDoc Processing
   • Use WE02 / WE05 to check IDOC status.
   • Common statuses:
     • 64 (Ready for Processing)
     • 53 (Successfully Posted)
     • 51 (Error – Needs troubleshooting)
3. Process the IDoc manually (if required)
   • Use BD87 to reprocess an IDoc.

Step 9: Automate the Inbound Process

• Schedule background jobs for inbound IDoc processing using RBDAPP01.
• Use WE20 settings to process IDocs immediately.

Step 10: Troubleshooting

• Check error logs in Transaction: WE02 / WE09.
• Verify Customizing in WE20, WE57, WE82.
• If sales order fails, check VA03 (Sales Order Display) for details.

Step 11: Important IDoc Related SAP Programs

• RSEOUT00 – Process outbound IDocs
• RBDAPP01 – Process inbound IDocs
• RBDMANIN – Reprocess IDocs with errors
• RBDAGAIN – Reprocess failed outbound IDocs
• RBDMIDOC – Process IDocs for message types
• RBDMOIND– Process IDocs with status 69 (IDoc not fully processed).
• RC1_IDOC_SET_STATUS – Program used to convert or change IDOC status; alternatively, Transaction WE47 is used to maintain and define valid status codes for IDocs.
• RBDSYNER – Process IDocs with syntax errors
• RSEIDOC1 – Display IDoc segments
• RSETESTD – IDoc test tool
• WE14 – Reprocess outbound IDocs
• WE15 – Reprocess inbound IDocs
• BD87 – Manually process IDocs

This completes the EDI Setup for Sales Order Creation in SAP.

The post Step-by-Step EDI Setup for Sales Order Creation in SAP – IDoc Configuration Guide appeared first on HowtolearnSAP.