Movement of Declarations to next Rev (ECO & MCO)

The PCG documentation specifies that a Declaration for a part is specific to the Number and Revsion and the Rev must be ECO or MCO supported.  For a Part Group only the part number is associated with the Declaration.  The system I’m working on is not OOTB and I’m trying to understand what changes have been made.  When I create an ECO or MCO and add an affected item the behavior is that under the Compliance tab the Specification and Declarations are copied from the prior revision whether the part is individually associated with the Delaration or is in a Part Group.  While this seems to disagree with the documentation I’m trying to find out what the OOTB behavior actually is.  I don’t have access to a plain vanilla system at the moment.

Add Comment
2 Answer(s)

The declarations and compositions that you see in the Compliance tab of the part is meant to be the composition of the part provided by the supplier irrespective of the revision. It shows the active declaration/composition from each supplier that provided the data. When the same supplier provides updated declaration for the same part, the previous declaration is inactivated. This is the default behavior.

Agile Angel Answered on May 4, 2018.
Add Comment

Thanks, that explains the behavior we are seeing.  The 9.3.2 documentation does not describe it that way.

Agile User Answered on May 4, 2018.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.