How Can You Standardize Information Across Sites For Global Reporting
(Doc ID 2340174.1)
Last updated on DECEMBER 25, 2017
Applies to:Oracle Quality - Version 12.1.3 and later
Information in this document applies to any platform.
Customer needs to standardize information across sites for global reporting
The user has acquired several other companies over the last few years. They want to do global quality reporting for all units so things can be compared equally for all of the sites.
Through analysis of all collection plans they have found they have 3 distinct groups of collection plans, so rework is out of the question. Over 50 % of their char elements contain 2 or more distinct collection elements. They are discussing mapping options with our BI group. We are considering changing from mapping from char columns to using collection element names, since they are the common aspect across all NCR plans. There definition and content does not change. Also, since NCR data is tiny compared to most BI volume, BI pulls a complete refresh of all NCR data, daily, into BI. So a remapping also eliminates any redo of individual NCR's
However, what they are hearing from BI, is that it adds to the sql complexity, that pulling data through the element, as opposed to columns, is not the preferred method. BI team is looking at these two tables for trying to link the data.
select * from apps.QA_CHARS_V; Lists the collection element and any logic used to populate (lookup value sets etc.)
select * from apps.QA_PLAN_CHARS_V; Lists the collection element association the collection plan.
Any suggestions on how best to link collection element name to char columns in individual ncr's for extraction would be extremely helpful to our BI team
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document