CRM uses mBDocs (messaging Business Documents) to replicate data between mySAP suite components. i.e. ECC, SCM and SRM

Message Flow Overview

Inbound messages to CRM – all converted to BDocs:

• BAPI structures
• BDOC’s
• XML/SOAP
• IDOC’s

VALIDATION: The integrity of the incoming data is done by the respective application. When successful, it is passed to the application. If not, it will remain in the message flow in an error status

Outbound processing:

• The receiving system is determined
• Then the BDoc is passed on to the corresponding outbound adapter which converts the BDoc in the format required by the receiving system

Connecting CRM and ECC

In R/3:

• Check assigned logical system name – 3-digit system name – i.e. ECC
• Create RFC Destinations – SM59 or SALE
• Maintain table CRMCONSUM - to activate either R/3 or CRM as a consumer of the system you are maintaining the table in
• Maintain table CRMRFCPAR – Through this table the determination of the RFC destination for the data transfer is connected with the consumer, client, object name and transfer type

In CRM:

• Check assigned logical system name – CRM
• Create RFC Destinations – SM59 or SALE
• Maintain table CRMCONSUM
• Create a Site definition - SMOEAC - start the administration console in CRM

Data Consistency

• Solution Manager: Customizing Scout & Distribution
• Data Integrity Manager (transaction SDIMA): Synchronization of Transactional Data
• Requests: For data with no initial load capability

Monitoring Tools

• Monitoring Initial Load: R3AM1
• qRFC Monitoring:
  • Outbound Queue Scheduler: SMQS
  • Outbound Queue: SMQ1
  • Inbound Queue Scheduler: SMQR
  • Inbound Queue:SMQ2
• Middleware Trace: SMWT
• Middleware Portal: SMWP