ECO Implementation By Status
Oracle Engineering automatically implements engineering change orders (ECOs) with Release, Schedule, and Implement statuses for jobs with statuses of Unreleased and schedules with statuses of Unreleased, Released, and On Hold. You can optionally choose to implement Open status ECOs using the WIP:Exclude Open ECOs profile option. See: Work in Process Profile Options and ECO Statuses.
Oracle Engineering does not implement ECOs on non-standard discrete jobs.
Unreleased Standard Discrete Jobs and Repetitive Schedules
When an ECO is implemented in Oracle Engineering, the system automatically regenerates the bills of material for unreleased jobs and schedules to reflect the impact of the ECO.
Released, Complete, or On Hold Repetitive Schedules
The impact of an ECO implementation on Released, Complete, or On Hold repetitive schedules depends on whether repetitive assemblies have been moved beyond the Queue intraoperation step of the first routing operation.
See Also
Overview of Engineering Change Orders
Defining Engineering Change OrdersDefining Engineering Change Orders, Oracle Engineering User's Guide
