R/3 ORDERS IDoc
Mapping 
Purpose
This mapping enables the communication between the SAP CRM System of a Vendor and the:
· SAP R/3 System of a Buyer
· EDI Subsystem
The SAP R/3 System and the EDI Subsystem send and receive messages in an SAP R/3 ORDERS IDoc format. The messages sent or received by the SAP CRM System however, are in a CRM IDoc format, represented by the Complex Data Type for Business Transaction. The R/3 ORDERS IDoc Mapping maps the Complex Data Type structure with the R/3 ORDERS IDoc structure. The mapping thus, helps avoid enhancement of an EDI Subsystem to support CRM IDoc messages.
The Complex Data Type structure of the Business Transaction is more hierarchical when compared to the SAP R/3 IDoc structure. During the mapping, R/3 ORDERS IDoc Mapping maps the segments and data fields of the Complex Data Type structure with the segments and data fields of the R/3 IDoc structure.
When the R/3 ORDERS IDoc Mapping receives an inbound message from the Buyer system, in an R/3 ORDERS IDoc message through Application Link Enabling (ALE), it transforms the message into a CRM IDoc message. Similarly, when R/3 ORDERS IDoc Mapping receives an outbound message, in a CRM IDoc message format, it transforms the message into a R/3 ORDERS IDoc message.
The R/3 ORDERS IDoc Mapping transforms messages belonging to the following types of Business Transactions:
· Purchase Order – Sales Order
· You can also call the R/3 ORDERS IDoc Mapping as a Sales Order Mapping.
· R/3 ORDERS IDoc Mapping supports mappings for the Standard CRM Customizing.
· R/3 ORDERS IDoc Mapping supports customer specific enhancements through Business Add-Ins (Add-Ins). For more information, see Enhancements for R/3 ORDERS IDoc Mapping.
· R/3 ORDERS IDoc Mapping uses the External Interface adapter framework.
Constraints
The R/3 ORDERS IDoc Mapping supports various business processes of an ORDERS IDoc. There are however, some limitations.
Limitations in the R/3 ORDERS IDoc Mappings
· Partner Identification
The SAP CRM System supports the IL (International Location) number and EIAJ (Electronic Industries Association of Japan) number to identify partners. These are however, not a part of the standard customizing. The R/3 ORDERS IDoc Mapping relies on standard customizing.
· Partner Functions
The solution supports the Partner Functions that you have defined as a part of standard customization. R/3 ORDERS IDoc Mapping only supports the following partner functions:
¡ Payer
· Product Configuration
The R/3 ORDERS IDoc Mapping does not support configurable material.
Limitations in the SAP CRM System
· Product identification – Manufacturer part number, batch number, serial numbers and revision levels as identifiers for a product
· Route determination for delivery of items ordered
· Handling units for shipping