Message flow/Common Services/Message flow definition/Bdoc flow customization

Message flow

• §A central flow processing engine handles incoming BDoc messages by calling various services or adapters according to message type.
• §Various flow control services are called during the processing of a bdoc message. These services are function modules which process the data in the bdoc.
• §The different flow services can be-

1. -R/3 adapter service-upload data to connected R/3 system
2. -CRM service-data exchange with CRM online
3. -Replication and realignment service
4. -Outbound adapter service
5. -CDB service
6. -Rejection service- called in case of error during processing

• §Customer specific services can also be triggered during the bdoc flow 

 

Common Services

 

Common  services within the CRM Middleware:

•   The R/3 Adapter uploads business objects to the connected OLTP R/3 system.
•   The CRM service exchanges business objects with the CRM online components.
•   The CDB service saves the fields of a BDoc message in the corresponding CDB tables.
•   The Replication and Realignment service determines whether a realignment is necessary or not. If a realignment has to be performed for a BDoc message, this message is copied into a separate realignment queue for further processing. If realignment is not required, the sites are determined, where a BDoc message has to be replicated to.
•   The Outbound Adapter receives the list of sites computed by the Replication and Realignment service and appends the BDoc message to the outbound queues for all sites on that list.
• R/3 Adapter is used for data upload and download to and from a single OLTP R/3 system.
• On  the OLTP R/3 system, a plug-in is installed that acts as the counterpart of the R/3 Adapter on the CRM Middleware. The installation of the plug-in requires a specific hot package level on the OLTP R/3 system. Modifications on the OLTP R/3 system may not be supported and require further evaluation and possibly conflict resolution.
•   On the CRM Middleware, the release version of the OLTP R/3 system is kept as a parameter (in table SMOFPARSFA). With this parameter it is possible to map the business object data to the correct BAPI structures during upload and download.
•  CRM Adapter exchanges business objects with the CRM online components.
•  CRM Adapter receives data from the Flow and sends this data to the CRM online components. It receives the data contained in BDocs from the Flow Control and writes the content of the BDoc data segments into the corresponding tables of the CRM online database. This database is also accessed by the CRM online components.
•   If a business object is modified by an online component, the CRM online database is updated accordingly. At the same time the CRM online component also generates a new BDocs, which contains the modified tables, and initiates a new Flow by placing these BDocs into the queue of the Inbound Adapter.
• Each  business object that is uploaded to the online components has an individual CRM service, which is implemented in separate function module. The names of these functions modules can be obtained from the corresponding flow definition.  

Message flow definition

Flow definition for a bdoc can be checked from transaction-SMO8FD

 

Bdoc flow customization

 §

 

Message flow example 

-

§

§