Professional Documents
Culture Documents
This article provides a basic overview of the key features of the CRM
Middleware along with steps to help analyze and/or resolve some of
the most common middleware problems.
In the context of an SAP CRM landscape, Middleware refers to the R3
adapter, which is used to transfer data from the CRM to external
systems such as R3, mobile client, Groupware and vice versa. The
data are sent via qRFC (queued remote function calls).
This area enables the replication, synchronization and distribution of
data, for example between a networked branch office and its mobile
field sales representatives.
CRM middleware integrates various data producers both SAP and
Non-SAP systems with SAP CRM landscape.
Middleware is a tool which is inbuilt within SAP CRM that enables the
SAP CRM system to interact with various other SAP (R/3, BW, APO
etc.) and non SAP systems (3rd party web channel etc.)
Using middleware we can control what data should flow in and out of
the CRM system and also monitor the same.
The data exchange between the CRM Middleware and external
systems is performed via adapters. The adapters map and convert
data between various formats.
SAP CRM Architecture
SAP CRM system can be act as a logical box and connected to
different systems like interaction center, web channel, mobile clients,
handholds, SAP SCM, BI/BW, ERP and with other various systems.
CRM Server Architecture:
CRM architecture can be divided into 3 parts.
1. SAP CRM Middleware
2. Business Objects
3. CRM Server applications
Types of Data Transfer/Loads using Middleware:
Customizing Objects (Transaction R3AC3) The IMG is also used for CRM
customizing, but much of the customizing that governs how application
data are configured must be synchronized between the CRM and R3 using
customizing Adapter Objects.
SMQR Inbound Queue Scheduler - Queues in SMQ2 must be registered in SMQR to be processed automatically.
SMQS Outbound Queue Scheduler - Uses destination names rather than queue names. For outbound queues, automatic processing
requires that the corresponding destination be registered in SMQS.
BDoc Analysis
BDOCs are containers for transporting the business data.
Tr SMW01 can be used to check the status of all BDocs.
The different relevant BDOC types:
-BUPA_MAIN: contains the master data of a business partner (and is
triggered on creation and change of a business partner)
- BUPA_REL: used when you create a relationship between two
business partners
- PRODUCT_MAT: is used for data exchange of products/materials