Correspondence of OLTP R/3 and CDB Tables
§
Tables named as “XYZ” in the R/3 system are followed by a prefix “SMO” in the CDB. Hence they are called as “SMOXYZ”.
§
Hence development class for CDB Service is “SMO”.
•
Some important development classes are:
•
SMOF (R/3 Adapter Service)
•
SMOG (CRM Middleware Repository Services)
•
SMOH (Replication and Realignment service)
§
However, CDB tables do not have a 1:1 mapping with the R/3 tables. CDB tables are partly alike to the R/3 tables.
§
CDB Tables house the relevant R/3 data and might have some extra fields as well depending on the requirement.
§
Data requirements for CDB can be industry specific (Consumer goods, pharmaceuticals etc. )
Examples of Data mapping
§
One typical example is OLTP R/3 table KNA1 + OLTP R/3 table KNVK == table SMOKNA1 on the CDB.
§
Merging the two tables is necessary to be able, for example, to subdivide Business Partners in the pharmaceutical industry into institutions and persons.
§
Other examples of SMO tables are:
§
SMOADRC (has all addresses of all Business Partners)
§
SMOBNKA (Master data bank)
How is the data mapped from OLTP R/3 to CRM?
§
CRM uses the concept of GUID (Globally Unique Identifiers) to map the data from OLTP R/3 system to CRM Middleware system and CRM Mobile components.
§
Using GUIDs is typically advantageous in Mobile scenarios, though the difficulty faced is by the OLTP R/3 system which does not understand or records CRM keys (GUIDs). So lets understand what are GUIDs.
What is a GUID?
§
GUIDs (Globally Unique Identifiers) are system-generated technical keys. This serves as the primary keys for all tables in the CDB.
§
A GUID is generated by a special hashing algorithm using as input data certain OS (Operating system) information, the host computer information, the current system time and a randomly generated number.
§
GUIDs are technical key and are content free, which means that a GUID can be represented in various formats (in CRM, we use CHAR32 or RAW16).
§
It is globally unique in the sense that two GUIDs produced on any two computers (or even on the same one) at any time can never be the same. It remains active for a record for lifetime and is deleted only when the particular record is deleted.
§
Primary keys of all tables are called SFA<table name without the SMO prefix>, such as SFAKNA1, SFAMARA.
Advantages of own key system (GUID) in Mobile Scenarios
§
Global Unique Identifiers (GUID) are unique in the world due to generation method
§
No number range intervals of R/3 keys are needed
§
GUID is a technical key and content free
§
Can be used to model relations between objects
§
This ensures consistency of data on a CDB even when the actual GUID is generated on the various distributed mobile databases (laptops, PDAs etc. ) and later synchronized with CDB.
Table Correspondence: CRM Online – CDB – OLTP R/3
•
The main customer table on the OLTP R/3 system is the KNA1 table with the customer number (KUNNR) as the key field. The corresponding CDB table is the SMOKNA1 with the GUID (SFAKNA1) as the key. The field KUNNR is an ordinary table field. The main table for customers in CRM online is the BUT000 table with the key field PARTNER. The R/3 customer number is kept in the field CUSTOMER_NO in the table CRMM_BUT_CUSTNO. The link between this table BUT000 can be established via the field PARTNER_GUID.
No comments:
Post a Comment