Compliance Value Calculation on BOM is Incorrect on Some BOM Parts Where Deviation is released on the latest ECO
(Doc ID 2253886.1)
Last updated on APRIL 25, 2019
Applies to:
Oracle Agile Product Governance and Compliance - Version 9.3.3.0 to 9.3.6.0 [Release 9.3]Information in this document applies to any platform.
Symptoms
Actual Behavior
Rollup in PG&C module is not Working for few Parts.
In the problem BOM structure where rollup shows incorrect result, Deviation is released on the latest ECO, and the released Date < the released Date of some leaf BOM children
Expected Behavior
Rollup in PG&C module to work correctly.
Steps to Reproduce
- Create below structure:
P001(rev A)
L P002 (compliant) - Create new rev for P002 as below:
P001(rev B)
L P002 (compliant)
L P003 (no compliance data) - Create deviation on A for P001 and do rollup.
Now you will get missing info, which is correct since p003 has no compliance data. - Now release p003 with a new revision and add a compliant BOM.
P001(rev B)
L P002 (compliant)
L P003 (no compliance data)
L P004 (compliant) - Now do rollup for P001 again should get compliant.
- However, still get missing info.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |