PURPOSE and ADVANTAGES
- Provides seamless back-end integration
- Provides Groupware Integration
- Synchronizes Mobile Client
- Is an integral part of the CRM Server
Requires:
- No Extra Software
- No Extra Installation
- No Extra Server
CRM Server contains the CRM Middleware which handles the data exchange with internal applications and external major components like SAP R/3, SAP BI, Non-SAP Systems etc
CRM Middleware can exchange messages with non SAP ERP Systems via standard interfaces like XML, SOAP etc
The data exchange between CRM Middleware and external systems is performed via adaptors. The adapters map and convert data between various formats
Load Objects ( BP Master data, Orders, Product Master data etc) can be exchanged between source ( eg. SAP R/3) and target systems (eg. CRM).
Load objects are stored in the SMOFOBJECT Table. Load Objects are grouped as follows:
- Business Objects
- Customizing Objects
- Condition Objects
BDOC’s
BDOC’s (Business Documents) are data containers that are used for processing business objects that logically belong together ( Eg. All data about one order, one partner etc)
BDOC Terminologies:
- BDoc Type – This the structure of the BDoc that defines the business object ( Sales Order, BP, Contact Person etc). BDoc Types are defined and managed in the BDoc repository with the BDoc Modeler
- BDoc Message – This contains the Modified fields only. These include new and deleted fields.
- BDoc Classes
- Messaging BDoc’s
- Synchronization BDoc’s ( for Mobile only)
ADAPTERS
Adapters are special services that provide connectivity to external systems in order to exchange BDoc messages between Middleware and SAP R/3, Mobile Clients or other systems
DATA CONSISTENCY BETWEEN SYSTEMS:
Following Tools can be used to maintain Data Consistency
Solution Manager
- Customizing Scout and Distribution
Data Integrity Manager
- Synchronization of Transactional Data
- With the Data Integrity Manager, you can detect and repair inconsistencies between Objects across components within the SAP CRM system landscape
- TCODE – SDIMA
Requests:
- If you are aware of the inconsistencies, then you can use Requests. Requests loads the required data from SAP R/3 to CRM or vice versa. ( Request for some Objects may not be supported from CRM to SAP R/3)
TCODE –
R3AR2 ( To define a Request)
R3AR4 ( To Start a Request)
ADMINISTRATION
Replication
The replication takes place in a star-like fashion from the CRM Server to the Mobile Clients, SAP R/3. Non-SAP systems
Data is replicated to Sites (local databases) and not to individual persons.
This Replication model is created and administered in the Administration Console (TCODE – SMOEAC)
Site
Every receiver is represented by an Site. (TCODE – SMOEAC)
Publication
Grouping of BDoc types to be distributed by distribution type are categorized under Publication. (TCODE – SMOEAC)
Subscription
Assignments of Sites to Publications are Subscriptions. (TCODE – SMOEAC)
DATA LOAD and MONITORING
Initial load:
You can load Customizing and Business Objects from SAP R/3 to SAP CRM
Usually a Customizing Load is started before the Business Objects are loaded.
Due to dependency of Objects, a specific sequence during data load is necessary like –
- Customizing
- Business Objects
- Parent/Child relationship between different objects
To start the initial load goto – SAP Menu – Architecture and Technology – Middleware – Data Exchange – Start Initial Load
LOAD FILTERING
The objects to be exchanged between CRM & R/3 can be filtered using Filter Criteria
Filetr settings are stored in the table – SMOFFILTAB
Filters for Business Objects are pre defined ( Table – SMOFFILFLD)
Filters for Customizing and Conditions objects can be set on existing fields
Filter options allow the filtering at the Source, at the Target.
Business Objects – Can be filtered at Source, at Target, At Source & Target
Business Data – Usually filtered at Source
Customizing Objects – Can be filtered at Source only
Conditions Objects – Can be filtered at Source only
Filter Criteria settings – SAP Menu – Architecture and Technology – Middleware – Data Exchange – Object Management – Business Objects / Customizing Objects / Consition Objects
MONITORING TOOLS
· Monitoring Initial Load: R3AM1
· qRFC Monitoring:
o Outbound Queue Scheduler: SMQS
o Outbound Queue: SMQ1
o Inbound Queue Scheduler: SMQR
o Inbound Queue:SMQ2
· Middleware Trace: SMWT
· Middleware Portal: SMWP
TROUBLESHOOTING – CRM and ECC
In ECC:
- 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
