Unreleased Discrete Job Requirement Was NOT Changed With ECO Implementation (Doc ID 1902504.1)

Last updated on DECEMBER 15, 2015

Applies to:

Oracle Engineering - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.1 version, ECO

ACTUAL BEHAVIOR
---------------
Unreleased job requirement was NOT changed with ECO implementation

EXPECTED BEHAVIOR
-----------------------
Unreleased job requirement should be changed with ECO implementation

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Set profile ENG: Update Unreleased WIP Jobs to Yes
1.Create BOM A1 in master ORG “ORG1”, the BOM only has one component like C1
2.Create common BOM for sub ORG say “ORG2”
3.Create Routing in sub ORG “ORG2”
4.Create WO like 0001 in sub ORG2, start date is like 26-Jun, status with Unreleased
5.Create WO 0002 in sub ORG2, start date is 16-Jun. and change status to Released
6.Create ECO in master ORG1 to replace C1 with C2. The effective date is 10-Jun. Implement the ECO.
7.Check the ECO implementation output.
1 out of 1 jobs were successfully updated
8.Go back to WO, and check the requirements. Nothing changed, still shows component C1, instead of C2



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms