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.

• The change pointers technique automatically initiates the outbound process when we create or change master data.
• When we want to reflect changes made to master data (i.e. customer master, vendor master, material master) visible to other clients listed in the customer distribution model, we follow the change pointer technique.
• The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master, vendor master & sales orders.
• Changes made to a document are recorded in the change document Header table CDHDR and Item table CDPOS.
• Additional change pointers are written in the BDCP and BDCPS tables.
• BDCPS table stores the status of changed documents processed or not.
• The SMD (Shared Master Data) tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document.
• The contents of the document are passed to the SMD tool. The tool writes change pointers, reads the application data, and creates the Master IDoc.
• In simple words, if we change anything in SAP, like a material master, vendor information, etc. It will create an entry in the change pointers table (BDCP, BDCPS).
• After that, we run the RBDMIDOC program to pick up these change pointers and send the IDOC to other systems to reflect the changes appropriately.

Change Pointers – Configuration

Step 1: Enable Change Pointers Globally

• Go to transaction BD61.
• Check the flag, go to Activation Status, and click on save.

• We will get the below message.

Step 2: Enable Change Pointers for a Message Type

• Go to transaction BD50.
• Click on New Entries and enter Message Type and check the Active flag and click on Save.

Step 3: Specify the Fields for which Change Pointers are to be written

• For standard master data objects such as the material, customer, and vendor objects, SAP already provides a list of fields for which change pointers are written.
• If we want to add new fields, we must add entries for the required fields.
• If we are not interested in IDocs being generated for changes to a particular field, we can remove it from the list.
• For example, if we do not want to distribute the material master for changes made to the Catalog Profile (RBNRM) field, we can delete this entry from the table.
• Go to transaction BD52.
  In the pop-up, enter the Message Type and click on Continue.

• Click on New Entries, add the Table Name and Field, and click on Save.

Step 4: Changing a Field in the Master Data

• Change a field in the master data object for which the change pointer is enabled.
• For example, if we change the net weight of a material in the material master data, a change pointer is written.

Step 5: Executing program RBDMIDOC to process Change Pointers

• Execute program RBDMIDOC to initiate the process of generating an IDoc.
• On the selection screen, specify the message type and click on Execute. For example, if we specify MATMAS. After we execute the process, it displays the number of entries processed.

• The below information messages will be displayed.

The post Change Pointers & related Configurations in SAP appeared first on HowtolearnSAP.

• IDoc is an acronym for Intermediate Document.
• IDoc is an SAP object that carries business transaction data from one system to another in the form of an electronic message.
• An IDoc is a container for exchanging data between R/3, R/2, and non-SAP systems.
• The purpose of an IDoc is to transfer data or information from SAP to other systems and vice versa.
• The transfer from SAP to the non-SAP system is done via EDI (Electronic Data Interchange) subsystems, whereas ALE (Application Link and Enabling) is used for transfer between two SAP systems.

IDoc Types

• IDoc can be triggered in the SAP system or in EDI (Electronic Data Interchange) subsystem.
• This depends on the direction in which IDoc is sent and is called Inbound IDoc and Outbound IDoc accordingly.
• Inbound IDoc: IDocs that are received into the system are termed Inbound IDocs.
• Outbound IDoc: IDocs that are sent outside the system are termed Outbound IDocs.

IDoc Structure

• IDoc structure is divided into Control Records, Data Records, and Status records.
• These records are stored in transparent tables in SAP. These are EDIDC, EDID4 or EDID_OLD, and EDIDS respectively.

Control Record (EDIDC)

• All control record data is stored in the EDIDC table.
• The key to this table is the IDoc Number
• It contains information like IDoc number, the direction (inbound/outbound), sender, and recipient information, the channel it is using, which port it is using, etc.
• Direction ‘1’ indicates outbound, and ‘2’ indicates inbound.

Data Record (EDID4 / EDID_OLD)

• All data record data is stored in EDID2 to EDID4 tables and EDIDD is a structure where you can see its components.
• It contains data like the IDoc number, name and number of the segment in the IDoc, the hierarchy, and the data
• The actual data is stored as a string in a field called SDATA, which is a 1000-char-long field.
• It contains the details of the IDoc Segments.
• IDoc Segment has fields that contain the data necessary for posting the documents.

Status Record (EDIDS)

• IDoc Status defines the processing status of the IDoc.
• IDoc status is used to track the IDoc and its various processing states.
• Status Numbers represent IDoc status.
• The current status of the IDoc is present in the Control record.

• We can identify the process with the number of status records.

01 – 49 for Outbound Process

50 – 75 for Inbound Process

• Table TEDS1 contains the list of all status codes.

Master IDoc & Communication IDoc

Master IDoc

• Stored in temporary storage areas.
• Only 1 Master IDoc is generated for any number of receivers for the same data.

Communication IDoc

• Stored in the database.
• The number depends on the number of receivers for the same data.

Important Tcodes:-

• SALE / BD54 – Define Logical Systems
• SALE / SCC4 – Assign Logical Systems to Clients
• SM59 – Create RFC Destination
• WE21 – Define Port Definition
• WE20 – Generate Partner Profile
• BD82 – Generate Partner Profiles
• BD64 – Maintain Distribution Model
• BD71 – Distribute customer distribution model
• WE31 – Create Segments
• WE30 – IDoc Type
• WE81 – Create Message Type
• WE82 – Assign IDoc Type to Message Type
• WE41 – Create Outbound Process Code
• WE42 – Create Inbound Process Code
• BD51 – Define the Function Module characteristics
• BD61 – Activate Change Pointers – Globally
• BD50 – Activate Change Pointer for Msg Type
• BD52 – Activate change pointer per change.doc object
• BD59 – Allocation object type -> IDOC type
• BD56 – Maintain IDOC Segment Filters
• BD53 – Reduction of Message Types
• BD21 – Select Change Pointer
• BD87 – Status Monitor for ALE Messages
• WE60 – IDoc documentation
• WE05 – IDoc overview
• BD87 – Inbound IDoc reprocessing
• BD88 – Outbound IDoc reprocessing
• BD21 – Create IDocs from change pointers
• SM58 – Schedule RFC Failures

Check out other related IDoc Posts from the Author.

The post What is IDOC & its Structure? appeared first on HowtolearnSAP.