TCA and DQM Overview. Anil Passi. Please click to proceed through presentation. Stored independently of TCA. Users ensure Vendor Number/name is same as in TCA. Unlike HRMS, OSS simply references these fields from TCA Table HZ_PARTIES. References. DQM Staging Process.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Please click to proceed through presentation
Stored independently of TCA. Users ensure Vendor Number/name is same as in TCA
Unlike HRMS, OSS simply references these fields from TCA Table HZ_PARTIES
DQM Staging Process
Staging Transformation rules applied
Displays Highest score records on top
Applies Filter criteria Applies weightings Applies Scoring
**Same as Party Number
Last Name **Referenced from TCA
First Name **Referenced from TCA
Date Of Birth
**Referenced from TCAParty Id
Vendor NumberVendor Name
Reference to Party Id
Date Of Birth
Reference to Person Id
Kept in Synch-In Different physical schemas
->Exact and Cleanse are common transformations given by Oracle [Pre-Seeded]
->You can define as many custom transformation rules, like replacing Z with S
->Multiple transformation rules can be applied to each column. For each transformation applied, a independent column value is stored in staging table
EXACT TRANSFORMATIONMake all characters UPPER caseRemove non-alphanumeric charactersReplace multiple white spaces by single white spaceCLEANSE – All above rules of EXACT plusRemove double letters
Remove all vowels, except leading vowels
Transformation can be applied again to values that user is searching. Lets say user searches on Aneeal Passion
->These transformations can differ from those used for staging. But most likely we use same transformations when searching as that for staging.
While doing DQM config, we will give Higher Scoring to Last Name, and lower Scoring for First Name match
For Last Name, we give 100% Weighting to EXACT Match, and say 65% weight to CLEANSE. Hence match based on Exact will have higher rank
User searches for Aneeal Passion….eeeks
Purpose of Transformation in DQM?
Make a transformation active to allow it being used for scoring or “data search”
If Acquisition Flag is checked, it means this transformed value will be used for searching initial set of matching records.
Multiple transformations can be applied to each column.
If Acquisition Flag is NOT checked, it means this transformed value will be used solely for the purpose of Scoring the records returned by acquisition phase.
Scoring happens after Filtration and Acquisition has been done. The resultant set of records are then run through scoring process, so that we can display highest ranked matches on the top of list
These are the transformations which will be used for performing search.
Only those Transformations that have their “Acquisition Checkbox Flag” checked [in previous slide], can be used in acquisition phase
A custom attribute can be defined to Filter out invalid Party Records. Filter is applicable if we can programmatically suppress duplicate/invalid Party records from appearing.
Define match rules
Assign score to each column. Match found on Party Number will have Score 100, whereas match on Last Name can be score of 90. Score for match on Title[Mr/Ms] will be still lower
Within each column, each transformation can be given different Weight. EXACT match can be given 100% weight, whereas CLEANSE [after removing vowels] will be give lower weight.
Scoring Phase [After Acquisition phase is completed]
Transformations used in Acquisition can be used for Scoring too.
End of presentation - Thanks