My Oracle Support Banner

Items On Pending Change Are Incorrectly Rebased When A Change Is Released (Doc ID 2902520.1)

Last updated on OCTOBER 18, 2022

Applies to:

Oracle Agile Product Collaboration - Version and later
Information in this document applies to any platform.


Items on Pending Change are incorrectly rebased when a Change is released

Parts and Documents on one Pending Change are incorrectly rebased when a Change is released, even when Parts and Documents are not on the released Change

If multiple pending  Change Orders (COs) are against an item, when one of the Changes is released it “rebases” the Pending Change redlines against the released Change.

This seems to occur only for Multi List attributes and only when there is no redline conflicts between Pending Changes.

Parts/Documents that are not on both Changes should not be affected when separate Change is released

The issue can be reproduced at will with the following steps:
1. Engineering Change Order (ECO) 1 is pending and has the following affected items:
Document A: Attribute redline is Not Applicable
Document B: Attribute redline is Not Applicable
2. ECO 2 is pending and has Document A as an affected item:
Document A: Attribute redline is Not Applicable
Document B is NOT on ECO 2
3. Release ECO 2
Document A on ECO 1 is rebased against the released values for Document A from ECO 2
Document A: Attribute redline is rebased from Not Applicable to “Not Applicable” No issue here. The redline is updated to reflect the latest released revision.
Document B: Attribute is blank/null (redline was removed). Document B was not on ECO 2 and should not be impacted at all by ECO2s release.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.