Professional Documents
Culture Documents
Oracle TCA
Ensure and Maintain Data Quality in TCA Registry
White Paper
June 2004
Ramakrishna Goud,
Accenture, IDC
ramakrishna.goud@accenture.com
Introduction
Trading Community Model
The below diagram depicts the relationship among the entities of
Trading Community. Refer to the Oracle Trading Community
Architecture Administration Guide for complete information.
Party
Person
Organization
Group
Classification
Code
Party Relationship
Party Site
Account
Code Assignment
Electronic
Contact Point
Sub Code
Party Account Role
Account Relationship
Phone
Physical Contact Point
/ Location
Contact Preferences
Relationship Type
Account Site
Relationship Type
Group
Internal Organization
URL
The Need
The party information inside TCA registry can be duplicated for many
reasons like incomplete data, typographical errors, conversion from
external systems or spelling mistakes. 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 TCA registry contains the party information, which could have
been duplicated. When you run the DQM staging program, it
transforms the attribute values like Party Name, Party Number etc into
a staging schema. Each attribute represents a table column in the TCA
repository. The staged schema also stores attributes and
transformation functions used with the attributes. The staged schema
is separate schema from original registry and contains attribute values
(Party Name = XYZ Corporation)
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.
Each step in the above diagram is briefly explained below. Refer to the
Oracle Trading Community Architecture Data Quality Management
Guide for complete information on the setup.
Run the DQM staging program to create the staged schema and
intermedia indexes
You have to run the DQM staging program to create/update staged
schema which consists of attribute values and transformation
functions. The intermedia index on the staged schema will help in fast
search for the duplicates.
Run the DQM index optimisation program, this should be scheduled
to run periodically
Run the DQM index optimisation program to improve the
performance of the intermedia indexing.
Run the DQM synchronization program, this should be scheduled to
run periodically
Run the DQM synchronization program to synchronize the data
between staged schema, intemedia index and TCA registry. Running
this program frequently will ensure that the changes/updations to
TCA registry are reflected in staged schema and intermedia index
Note: Oracle workflow listener can be used to synchronize the data
between staged schema and TCA registry. Run the Workflow Agent
Listener Concurrent Program periodically to automate the
synchronization between the staged schema and the TCA registry.
Define Custom attributes, and then rerun the DQM staging program
(Optional Setup)
Navigation: Trading Community Manager ! Data Quality
Management ! Setup ! Attributes and Transformation Functions
You can use the Attributes and Transformation Functions screen to
define the Custom Attributes. Custom Attributes are used when
business needs doesnt match with the seeded Attributes provided by
the Oracle.
Follow the below steps to create a custom attribute
1. Write a PL/SQL function with the signature. The p_record_id in
the function is the primary key of the table from which the attribute
value is picked. The values for the p_record_id could be
PARTY_ID, PARTY_SITE_ID etc.
FUNCTION <custom_attribute_proc> (
p_record_id IN NUMBER,
p_entity_name IN VARCHAR2,
p_attrib_name IN VARCHAR2)
RETURN VARCHAR2;
2. In the Attributes and Transformation Functions window, select one
CUSTOMATTRBUTE and enter the PL/SQL function name against
it in Custom Procedure field.
3. You have to run the DQM Staging Program again after the
custom attributes are defined
Conclusion
As the volume of parties and customer data increases inside the Oracle
TCA registry, it is prone to incomplete and duplicate information.
Hence Implementing DQM will help in successful run of the business
by ensuring that the quality of data is maintained, which is correct and
accurate.