1

Ø Best Version Tables.Ø Source Data and History Tables.Ø Survivorship Tables.Ø Cross Reference Tables.Cross Reference Tables.Ø System Registration Tables.Ø Merge /Unmerge Tables.Ø Data Quality Tables.

2

Ø Base tables store the golden record for the customer.

Ø These table schemas are the exact replica of the CRM customer schema.

Ø Cross referencing data is stored as child Ø Cross referencing data is stored as child records to the records in base tables.

Ø Entities mastered in base tables can undergo merge and unmerge process.

Ø Records undergo DQ Process such as cleansing, matching and Survivorship engine.

3

S_PARTY

S_ORG_EXT S_CONTACT

4

Ø Provides a mechanism to trace life-cycle properties of records.

Ø Helps maintain the version of the base table records.records.

Ø Provides a staging area for data quality processes before records move into the base tables.

Ø External systems must integrate with these SDH tables.

5

S_UCM_ORG_EXT

Source Data History Tables (SDH)

S_UCM_CONTACT

Source Data History Tables (SDH)

S_UCM_ORG_CHILD S_UCM_CON_CHILD

6

Ø Customer Data originates in multiple systems.Ø Different sources have conflicting data for the same attribute.Ø For example two systems have 2 different addresses for the samecustomer.

Ø UCM resolves these conflicts which ensures that the best versionrecord survives.

Ø Survivorship rules are an automated mechanism for consolidatingcustomer data to produce a best-version record.Survivorship rules are an automated mechanism for consolidatingcustomer data to produce a best-version record.

Ø Evaluates updates from each registered system.Ø Applies rules to decide which value is best for each attribute.Ø Can be built by a system integrator or data steward.Ø UCM allows two thresholds to be set depending on the matchscore from the matching process.§ Records with high match score can be auto-merged with survivorship rules.§ Records with match score in middle will be brought to the attention of DataSteward for manual review and resolution.

§ Records with low match score will be left as separate record.

7

S_UCM_ORG_ATGP S_UCM_ATGP_RULE

S_UCM_RULE_SET

Survivorship Tables

S_UCM_ORG

S_UCM_ATGP

S_UCM_ATGP_FLD

S_FIELD

S_UCM_CONF_LVL

8

Ø Every operational application that connects to UCM must register with UCM.

Ø After registration, a system’s privileges and accessibility can be defined:accessibility can be defined:Ø QueryØ InsertØ UpdateØ Delete

Ø Define grant access to Siebel UCMØ Privileges are granted at the BO layer.

9

S_CIF_EXT_SYST

System Registration Tables

S_CIF_SYS_DTL

10

Ø Cross referencing provides consistency by maintainingan external unique identifier from different systems toensure universal uniqueness of records in theenterprise.

Ø UCM stores identification information about externalsystems that have been registered.systems that have been registered.

Ø A single UCM record maps to one or many records inany registered application.

Ø UCM support cross referencing for the followingobjects:Ø ContactsØ AccountsØ HouseholdsØ Financial Account

11

Ø Cross-reference entries are created automatically with the creation of every new account, contact or household record.

Ø External system sends requests to insert a record.Ø If there is existing cross reference entry, the entry Ø If there is existing cross reference entry, the entry is updated.

Ø If there is no existing cross reference entry, a new record is inserted.

Ø The system id is the value assigned when system was registered and the system name is the associated name.

12

Cross Reference Tables

S_ORG_EXT S_CONTACT

S_CIF_ORG_MAP S_CIF_CON_MAP

13

Ø These tables are populated during the merge process and the information stored in them is used for the unmerge process.

Ø They store the relationship information about the child entities of the victim record during a merge.

14

Merge Unmerge Tables

S_UCM_ORG_EXT S_UCM_CONTACT

S_UCM_ORG_MERGE S_UCM_CON_MERGE

15

Ø Data Quality consists of data cleansing and datamatching.

Ø Cleansing standardizes data. Typical functions are:Ø Address validation and standardization.CapitalizationØ Capitalization

Ø Abbreviations

Ø Data matching identifies possible duplicate recordsfor account, contact and prospect records.Ø Deduplication is sometimes used to describe matching inuser properties and system parameters.

16

Data Quality Tables

S_ORG_EXT

S_UCM_DEDUP S_DEDUP_RESULT

17

Thank YouThank You

18