1 / 7

TCA and DQM Overview

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.

issac
Download Presentation

TCA and DQM Overview

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. TCA and DQM Overview Anil Passi Please click to proceed through presentation http://oracle.anipassi.com

  2. 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 Staging Transformation rules applied DQM Screen Displays Highest score records on top Applies Filter criteria Applies weightings Applies Scoring DQM Registry HZ_STAGED_PARTIES Student System Student Number **Same as Party Number Last Name **Referenced from TCA First Name **Referenced from TCA Date Of Birth **Referenced from TCAParty Id Payables PO_VENDORS Vendor NumberVendor Name Employee Id HRMS PER_ALL_PEOPLE_F EMPLOYEE_NUMBER[CID] LAST_NAME FIRST_NAME DATE_OF_BIRTH PERSON_ID Reference to Party Id TCA HZ_PARTIES Party Number Last Name First Name Date Of Birth Gender Reference to Person Id PARTY_ID Kept in Synch-In Different physical schemas http://oracle.anipassi.com

  3. ->Exact and Cleanse are common transformations given by Oracle [Pre-Seeded] Last Name Passi’an ->You can define as many custom transformation rules, like replacing Z with S Exact Cleanse ->Multiple transformation rules can be applied to each column. For each transformation applied, a independent column value is stored in staging table Exact Cleanse ANIL ANL PASSIAN PSN 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 Match Found Transformation can be applied again to values that user is searching. Lets say user searches on Aneeal Passion ANEEAL ANL PASSION PSN ->These transformations can differ from those used for staging. But most likely we use same transformations when searching as that for staging. Exact Cleanse Exact Cleanse While doing DQM config, we will give Higher Scoring to Last Name, and lower Scoring for First Name match Aneeal First Name Passion Last Name 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? Staging First Name Anil http://oracle.anipassi.com

  4. 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. • To setup DQM for Staging:- • Decide the columns that you would like to search & score/rank upon. For example Last Name, First Name, DOB, NI Number etc • Define custom attributes for those columns that are not held within TCA table like HZ_PARTIES. For example NI Number is not in TCA tables, hence we can define Custom Attributes for NI Number, and then define Custom Procedure that returns NI number from HR tables [for a given party_id] • Define the transformations for each column. Multiple transformations can be defined http://oracle.anipassi.com

  5. 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 http://oracle.anipassi.com

  6. 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. http://oracle.anipassi.com

  7. Records with Highest score are displayed on the Top of DQM Screen End of presentation - Thanks http://oracle.anipassi.com

More Related