• For Inbound Message Flow: Only one service available – Validation Service
• Associated Validation Function Module of each BDoc: Transaction SMW3FDIF
  • For BUPA_MAIN the validation FM is CRM_BUPA_MAIN_VAL
• After successful validation and posting to the CRM application, the middleware starts the corresponding outbound message flow with flow context MO1 or MO2 in case of mass processing
• Usually the Flow Context MO1 contains the following services:
  • Simple Replication Service – looking for valid receivers interested in the data
  • Call outbound adapters

View flow contexts

• Each Flow Context specifies or exists of a sequence of Services (Function Modules)
• MI0 Validate (MI – Messaging flow Inbound): Synchronization Inbound Flow, XML Adapter and R/3 adapter pass data to CRM
• MO1 Notification (MO – Message flow Outbound): Delta Distribution of one instance to subscribed sites and additional consumers such as the BW adapter
• MO2 Notification Multiple: Delta distribution of more than one instance (multiple case) to subscribed sites and additional consumers such as the BW adapter
• MO3 Initial Load: Method PROCESS_INITIAL_LOAD transfers gross data only from the CRM DB to the CDB. The initial load from external systems to the CRM DB uses first the context Validate followed by the context Notification, but not the initial load
• MO4 Direct Send: Data x=extract starting at Admin Console (From CRM to external sites R/3, XIF)
• Table SMW3FDSTD: contains the SAP standard flow definitions in the form of flow contexts
• Table SMW3FDBDOC: contains flow definitions that are BDoc specific but not customer specific
• Table SMW3FDCUST: contains the customer specific and BDoc specific flow definitions in the form of flow contexts. These entries override the BDoc Type-specific flow and standard flow.
• Table SMW3BDOCIF: additional definitions i.e. the validation service…