Classification Party. Person Organization Group. Classification Code. This duplicate party information may reduce performance and efficiency of the transaction processing and further lead to several business critical issues. The Solution To prevent, maintain and eliminate duplicate party information inside TCA registry, the Data Quality Management functionality need to be implemented. This DQM functionality is part of Oracle Trading Community Architecture which maintains party and customer information free of duplicates.
It would also help in performing powerful searches on the parties. After identifying the duplicates, it passes the information to merge program, which actually eliminates the duplicates from the TCA registry. The below diagram illustrates how the different features of DQM functionality work together.
The TCA registry contains the party information, which could have been duplicated. Each attribute represents a table column in the TCA repository. The staged schema also stores attributes and transformation functions used with the attributes. Then when you run the duplicate identification program or search for a party, the attribute values of the newly entered records will be converted to transformations using a match rule. The attribute values on the newly entered record will be compared against the attribute values in the staged schema.
Then the duplicates are identified based on the match rule, attribute match and score. DQM Setup Steps. The below diagram illustrates the setup steps to be performed while implementing the DQM functionality.
Each step in the above diagram is briefly explained below. Define attributes and transformation functions. Navigation: Trading Community Manager! Data Quality Management!
Attributes and Transformation Functions. Each attribute represents a table column from TCA repository. In this setup you can define the attributes which will be used in searching the duplicates. You can define custom attributes if seeded attributes fail to satisfy the business needs while searching for duplicate parties.
Define word replacements Optional Setup. Word Replacements. To reduce inconsistency within the party information, you can define word replacements and use in transformation functions. Primarily the word replacement will help in identifying the words, which act like synonyms. Oracle provided seeded word replacement lists as part of DQM which can be used in transformation functions. Define and compile match rules. Match Rules. In this setup, you can define Match Rule which determines whether a particular party is a duplicate or potential duplicate.
Duplicate Identification Program internally uses the match rule to identify the duplicates. Primarily match rule works in Score matching which is mainly divided into two parts. Acquisition Provides the initial criteria to filter the records 2. Score Assigns score to each attribute. While defining match rule, you have to identify the key attributes and assign the score accordingly.
A record is identified as a duplicate when the attribute score is greater than or equal to threshold value. After match rule is defined, it should be compiled. Run the DQM staging program to create the staged schema and intermedia indexes. Index Creation Tablespace: Enter the table space where the interMedia indexes are to be created in.
You should run this program once in a while, but frequent optimization is not mandatory. The DQM Synchronization program, however, synchronizes data between the TCA Registry and the staged schema, so you should run this program as often as possible to keep the search results accurate. Prerequisites Before you submit the DQM Staging program, you must define attributes and transformations.
Staging program that did not finish. Define your match rules. You can define as many match rules 6. In Match rules, you specify how the users search criteria[values being used by users] are transformed prior to acquisition. Run the staging process. Give me some examples where DQM is used? Lets say your organization has employees and a person named john smith gets recruited for a job. HRMS team must know whether this John Smith has had any kind of interaction with the organization in past.
Ideally if John Smith has had any kind of interaction with the company in past, then there must exist an entry for this record in TCA.
By doing so a degree view of the employee be maintained in your organization. So DQM is about being able to identify a duplicate entry in your system. Correct, and this I made possible by applying some transformations as you will see in the presentation. Isn't finding duplicates as simple as matching the social security number or national insurance number? Correct, but say if your payables department wants to pay expenses to a third party for their interview travel expenses, then payables team will not have access to SSN or "NI Number".
In this case, they rely upon other attributes of the person to find duplicates. Certainly not, in an efficient organization, any department that registers a party into oracle apps must have access to DQM functionality.
But what if Payables team wants to use DQM, but with different set of search and ranking criteria altogether? This is a very common requirement.
0コメント