Enterprise Resource Planning Portal ERPGenie.COM Enterprise Resource Planning Portal

   Advertise | BLOG

Web ERPGenie.COM

Home | Vote for us |

ERPGenie.COM -> mySAP.com -> mySAP CRM -> mySAP CRM IDoc handling

CRM does not make use of conventional IDoc processing as known in the 4.6C system. It does, however, still support IDoc processing through an adaptor provided by SAP for CRM. The adaptor converts IDocs to and from CRM middleware BDocs.

Scenario

  • Convert inbound Purchase Order (ORDERS) or Purchase Order Change (ORDCHG), with an R/3 ORDERS IDoc message format, into a CRM IDoc message format. CRM needs to create a sales order (business transaction of type Sales) when receiving the ORDERS IDoc. It needs to perform an update on the applicable sales order when receiving an ORDCHG.
  • Convert outbound Purchase Order Confirmation message, in a Complex Data Type for Business Transaction message format, into an R/3 ORDRSP IDoc message. Both an order create and an order update activity will generate an ORDRSP IDoc.

Process Flow

Inbound and Outbound Scenario for Purchase Order IDoc Mappings
This graphic is explained in the accompanying text

Inbound Message - Purchase Order or Purchase Order Change

  • The Buyer sends a purchase order to the Seller.
  • The Application Link Enabling (ALE) layer receives the inbound R/3 ORDERS IDoc with message types ORDERS or ORDCHG and stores the message in the database.
  • The R/3 ORDERS IDoc Mapping receives the inbound R/3 ORDERS IDoc message via the ALE and transforms it into a CRM IDoc message in sequential steps.

    During transformation, the R/3 ORDERS IDoc Mapping maps the:

    1. R/3 ORDERS IDoc structure to the Complex Data Type of the SAP CRM System.
    2. Complex Data Type to the Messaging BDoc (mBDoc) 
    3. R/3 ORDERS IDoc Mapping then passes the mBDoc to the CRM Middleware for validation. The successful processing of an mBDoc triggers the creation of a sales order in the Vendor system.

Outbound Message - Purchase Order Confirmation

  • The Seller sends a sales order confirmation to the Buyer.
  • The CRM Middleware replicates the sales order confirmation to the external receivers based on the site types of the recipients, for further processing. When the recipient site type is the External Interface for IDocs, it transfers the mBDoc to the External Interface Adapter.
  • R/3 ORDERS IDoc Mapping maps the outbound Complex Data Type for Business Transactions message into a R/3 ORDERS IDoc message in sequential steps. 
    • This mapping occurs in the XIF (External Interface Adaptor) located on the CRM server and is delivered with mySAP CRM. i.e. the XIF converts the IDoc to a mBDoc

During transformation, the R/3 ORDERS IDoc Mapping maps the: 

  1. mBDoc to the Complex Data Type of the SAP CRM System
  2. Complex Data Type to the R/3 ORDERS IDoc message of type ORDERSP
  3. R/3 ORDERS IDoc Mapping sends the transformed outbound message to the Buyer system.
 

Contact Us | Polls | Add URL | Contribute | About | Privacy | Terms | Feedback | Help!

Message Board | Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job