-
In real time, when a new record(driving record) come to UCM, Siebel
calls EDQ web services to generate cluster keys for the new record
- EDQ generate the cluster keys and its send back to Siebel
- Siebel stores these new keys and then looks up all records that share any key with the driving record- Once Siebel find a matching key, it submits driving and candidate records to the matching service
- Driver record and all candidate records are send back to EDQ, to be ranked by Match score
- Siebel then pop-up the Matching record with the match score and user can select 'pick' or 'ignore' to commit the record.
Cluster keys are stored in S_DQ_xxx_KEY tables;
Accounts: S_DQ_ORG_KEY
Contact: S_DQ_CON_KEY
Prospects: S_DQ_PRSP_KEY
- EDQ generate the cluster keys and its send back to Siebel
- Siebel stores these new keys and then looks up all records that share any key with the driving record- Once Siebel find a matching key, it submits driving and candidate records to the matching service
- Driver record and all candidate records are send back to EDQ, to be ranked by Match score
- Siebel then pop-up the Matching record with the match score and user can select 'pick' or 'ignore' to commit the record.
Cluster keys are stored in S_DQ_xxx_KEY tables;
Accounts: S_DQ_ORG_KEY
Contact: S_DQ_CON_KEY
Prospects: S_DQ_PRSP_KEY
This comment has been removed by the author.
ReplyDelete