Overview of Engineering Change Orders

Engineering Change Orders (ECOs) enable you to control new item revisions and bill
of material changes. With one ECO, you can group several bill of material changes
that affect one or more bills.

You can define ECOs for all types of items and bills, including:

o manufacturing and engineering items

o bills and their components

o planning, model, option class, and standard items

o primary and alternate bills of material

An ECO specifies changes to one or more items that are logically related to each
other, such as a new product introduction. Each ECO specifies changes for one or
more revised items and each revised item can have one or more revised components.

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.

Revised Items

Revised items can be either items or bills. If a revised item is a bill, you can change
the item revision and component information (revised components). If a revised item
defines a new bill, you can create revised components by copying an existing bill.

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.

Revised Components

You can add, change, or delete bill of material components and their attributes. The
components and their attributes have the same restrictions as when you define a bill
using Oracle Bills of Material. For example, you can only add components that are
standard, model, or option class items for revised items that are model items.

Revisions

When you enter a revised item on an ECO, Engineering displays the current and latest
revision of the item. The latest revision could be higher than the current revision if the
latest revision is on a pending ECO.

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.

See Also

Implementation of ECOs on Jobs and Schedules

Bill / Component Validation Rules

Item and Routing Revisions

ECO Revised Item Statuses

ECO Revised Item Statuses

These statuses are updated by changes to the ECO status.
Open Changes to the revised item are still in process or not complete. The MRP active
attribute will be updated to Yes. This is the default.
Hold Changes to the revised item are on hold; you cannot implement them.
Release Changes to the revised item have been released and can be implemented manually.
The revised item has not been scheduled for auto-implementation.
Schedule The revised item is scheduled for auto-implementation. You can only set the revised
item to Schedule if the ECO status is Approved. The MRP active attribute is
updated to on.
Implement The revised item has been implemented manually or automatically. You cannot list
additional changes for implemented revised items.
Cancel The revised item has been cancelled.

Engineering Profile Options and Security Functions

During implementation, the system administrator sets up and maintains security
functions and profile options.

Security Functions
Engineering Change Orders: Approvals (ENG_ENGFDECN_APPROVAL)
Determines whether an Engineering Change Order (ECO) approval Workflow process
can be submitted or aborted.
Engineering Change Orders: Cancel (ENG_ENGFDECN_CANCEL)
Determines whether ECOs can be cancelled.
Engineering Change Orders: Implement (ENG_ENGFDECN_IMPLEMENT)
Determines whether ECOs can be implemented.
Engineering Change Orders: Release (ENG_ENGFDECN_RELEASE)
Determines whether ECOs can be released.
Engineering Change Orders: Reschedule (ENG_ENGFDECN_RESCHEDULE)
Determines whether ECOs can be rescheduled.
Engineering Change Orders: Schedule (ENG_ENGFDECN_SCHEDULE)
Determines whether ECOs can be scheduled.
Engineering Change Orders: Update (ENG_ENGFDECN_UPDATE)
Determines whether ECOs can be updated.
Engineering Items: Delete (ENG_INVIDITM_DELETE)
Determines whether engineering items can be deleted from the Bills of Material or
Routings windows.
Engineering Items: Revisions (ENG_INVIDITM_REVISIONS)
Determines whether revisions for engineering items can be updated.
Engineering Items: Transfer (ENG_INVIDITM_TRANSFER)
Determines whether engineering items can be transferred to manufacturing.

Profile Option Settings

You can set or view the following profile options in Oracle Order Entry/Shipping. The
table also includes some profile options from other applications that are used by
Engineering.

Key

You can update the profile option.

- You can view the profile option value but you cannot change it.
 User System Administrator Requirements
Profile Option
Default
User User Resp App Site Required?
Value

ENG: Change Order Autonumbering - System - Required No

Administrator Access

ENG: ECO Department - Optional No?

ENG: ECO Revision Warning -       Optional No

ENG: Engineering Item Change Order Access - Optional Yes

ENG: Mandatory ECO Departments -       Optional No

ENG: Model Item Change Order Access - Optional Yes

ENG: Planning Item Change Order Access - Optional No

ENG: Require Revised Item New Revision -     Optional No

ENG: Standard Item Change Order Access - Optional Yes

Profile Options

ENG: Change Order Autonumbering - System Administrator Access

Indicate whether you can define ECO autonumbering for all users or for yourself
only.
ENG: ECO Department
Indicate the default department Engineering uses when you define an ECO. An ECO
department is the department currently responsible for an ECO. It restricts
departments from updating ECOs for which they are not responsible.
ENG: ECO Revision Warning
Indicate whether to raise a warning but still implement ECO revisions with pending
lower level revisions (Yes), or to raise an error and not perform the implementation
(No or blank). A blank (or "null") value is equivalent to No.
ENG: Engineering Item Change Order Access
Indicate whether you can revise engineering items on ECOs.
ENG: Mandatory ECO Departments
Indicate whether it is mandatory to assign a department to each ECO so you can
enforce a security policy.
ENG: Model Item Change Order Access
Indicate whether you can revise model and option class items on ECOs.
ENG: Planning Item Change Order Access
Indicate whether you can revise planning items on ECOs.
ENG: Require Revised Item New Revision
Indicate whether it is mandatory to assign a new revision to revised items on ECOs. A
blank (or "null") value is equivalent to No.
ENG:Standard Item Change Order Access
Indicate whether you can revise standard items on ECOs.