Previous | Next | Contents | Index | Navigation | Glossary | Library |
You can define ECOs for all types of items and bills, including:
Depending on the ECO type, an ECO can update manufacturing bills only or both manufacturing and engineering bills. If the ECO type can only update manufacturing bills, you cannot revise engineering items.
You can add either engineering or manufacturing items as components on engineering bills. However, you can only add manufacturing items as components on manufacturing bills.
Assign an effective date for each revised item on an ECO. Engineering uses this date to implement the ECO and to identify past due ECOs. Each time you change a revised item's effective date, Engineering adds an entry to list effective date changes. You can also specify an early effective date that determines the earliest date that you can manually implement a change. If you do not enter an early effective date, you can manually implement the change at any time. You can reschedule an ECO by entering a new effective date.
Note: There are two conditions under which revised items are not implemented: if the early effective date is greater than the current date, and if the user does not have access to the item type of the revised item. For example, if the revised item is a model item and the user does not have access to model items, the revised item is not implemented. The same is true for option class, planning, and standard items.
You can control whether Oracle Master Scheduling/MRP plans your proposed changes before implementation. If you have engineering changes that are firm, but whose effective date is in the future, you may want planning to consider those changes. You can choose to plan changes on any pending ECO regardless of the ECO status. Changes to the ECO status or the revised item status will automatically update the MRP active attribute. However, you can always manually set the MRP active attribute as desired.
For each revised item, you can also specify whether Engineering should update work in process material requirements. When you implement such an ECO revised item, Engineering automatically re-explodes and updates the bill of material for all unreleased jobs and repetitive schedules for that item.
Engineering also updates repetitive schedules with statuses of Released, Complete, or On hold accordingly.
Engineering uses the ENG: Require Revised Item New Revision to control new item revisions for each engineering change. If engineering changes always correspond to new item revisions, set this profile option to Yes. Doing so will force a new item revision for all revised items on an ECO. When you require new item revisions, you can track all engineering changes to an item by revision. For example, you can group related design changes on an ECO and roll revisions for each item to reflect the latest design.
If you define related ECOs at different times, set this profile option to No so you increment the revision only once. You can then define one ECO to change the revised item revision and other ECOs that do not change the item revision. Minor changes that do not affect form, fit, or function of an item may not require new revisions.
Bill / Component Validation Rules
Previous | Next | Contents | Index | Navigation | Glossary | Library |