Agile PLM Does Not Retain A Released Configuration If A Child Of An Assembly Is Revised
(Doc ID 2688450.1)
Last updated on JULY 07, 2020
Applies to:
Oracle Agile Product Collaboration - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Agile PLM does not retain a released configuration if a child of an assembly is revised. After an assembly is released, the release configuration is not retained if a child sub-assembly or part is subsequently revised. Agile shows the latest configuration versus the released configuration. How can a user retain the released configuration? Are there admin settings that can be adjusted to enable this?
Steps to Reproduce
The issue can be reproduced at will with the following steps:
- Release an assembly and all of its parts at Rev A.
- View the BOM structure. All Revs are A
- Revise one of the parts to Rev B.
- View the BOM structure, and the assembly will show the revised part at Rev B.
This is the "Latest" configuration. The admin needs to know how to have Agile reveal the "Released" configuration that shows all Revs at A.
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 |
Cause |
Solution |