CRM Server / Middleware
The CRM Server is scalable just like any standard R/3 system. It is built on top of an R/3 Basis system but instead of the R/3 core applications, it contains the CRM online components, the CRM Middleware and the Consolidated Database.
The R/3 Basis system provides SAP basis technology and the ABAP workbench as a development environment known to many application developers.
The functionality of the CRM Middleware is described in more detail in the following units. An important part of it is the replication and realignment service, which ensures that every Mobile Sales/Service user obtains the data he or she requires.
The Consolidated Database (CDB) has several advantages:
- Data lost on a laptop can be reloaded from the CDB.
- Special CRM data, e.g. territory data, is only kept in the CDB and not in the database of the OLTP R/3 system.
- The performance, especially of the realignment service, depends heavily on the availability of the data on the CRM server
OLTP R/3 System
A Plug-in on the OLTP R/3 system enables the communication between SAP R/3 systems and mySAP.com components, such as the Business Information Warehouse (BW), Customer Relationship Management (CRM) or Advanced Planner and Optimizer (APO).
B/W and Other System
Integration through ASCII adapter takes place through configuration in transaction ASCI and SMAP .
Bdoc messages within the CRM Middleware are the largest unit of data that can be handled. They represent the standard format for data exchange between mobile clients and the CRM server. Definitions of all BDoc types are contained in the BDoc repository .
Food for thought : CRM MW and BW integration .
Replication and Realignment
The replication model consists of publications and subscriptions for certain replication objects. To be more specific, the replication model also contains Replication Objects and the flow definitions. However Replication Objects are not covered here. Please consult the course CR540 CRM Middleware for Mobile Scenarios for further information about Replication Objects.
Sites (mobile clients) subscribe to publications via subscription rules, e.g. number ranges for replication relevant fields.
Data Consolidation on CRM System
Although the mobile scenario is a network of distributed databases, a copy of each object in the entire system is kept in the Consolidated Database (CDB). This ensures data consistency and the possibility to restore a client database from scratch.
The consolidated database is neither a subset nor a superset of a standard R/3 database, which is necessary to enable the system running as a standalone system. Only a part of the R/3 data is copied, for example, data needed for Mobile Sales Scenario. Likewise, some Mobile Sales data is not or only partially contained in OLTP R/3, e.g. activities and/or opportunities.
Administrating and Monitoring
No comments:
Post a Comment