Previous	Next		Contents	Index	Navigation	Glossary	Library

Note: If the approval status is Approval Requested, you cannot modify the ECO. If the approval status is Approved and the ECO is modified, the approval status will be set back to Not Submitted for Approval.

When ECO types are defined, they can optionally be associated with a priority as they are being associated with an Oracle Workflow process. When creating the ECO, if the selected ECO type / priority combination matches a defined ECO type/priority combination, the associated workflow process defaults. The approval status is set to Not Submitted for Approval until the Submit button is chosen. If there is no match between entered values and existing ECO type / priority combinations, the approval status is set to Approved and you can enter an approval list.

Prerequisites

   Define at least one ECO type.

   To create an ECO:

1. Navigate to the Engineering Change Orders window.

2. Enter an alphanumeric ECO identifier. If you use ECO autonumbering, the next identifier is defaulted.

3. Enter or select an ECO type.

You can only select ECO types that can revise engineering items and bills if the ENG: Engineering Item Change Order Access profile option is set to Yes. If the selected ECO type updates engineering and manufacturing items and bills, any new bills defined on the ECO are engineering bills.

4. Optionally, enter the requestor of the ECO.

5. Optionally, enter the ECO department responsible for the ECO.

This can be used to transition the ECO from one department to another, for example, from manufacturing engineering to operations. For new ECOs, the default is derived from the ENG: ECO Department profile option.

If you specify that each ECO must have an ECO department, that is, the ENG: Mandatory ECO Departments profile option is set to Yes, then you must specify a responsible department.

Access to ECOs by ECO department is as follows:

• You can only view and update ECOs with the same ECO department as your ENG: ECO Department profile option.

• If you do not have a value for the profile option ENG: ECO Department, you can query and update any ECO.

• Any user can query and update ECOs with no department reference.

6. Optionally, enter a reason for the engineering change.

7. Optionally, enter or select a priority for the ECO.

Note: If the ECO type and the priority combination are associated with an Oracle Workflow process, you cannot use an approval list.

8. If a workflow process is not associated with the ECO, you can enter an approval list. If you do not enter an approval list, the ECO approval status defaults to Approved without any kind of approval process.

9. Choose the ECO Revisions button to define ECO revisions. See: Defining an ECO Revision.

10. Choose the Revised Items button to define revised items. See: Defining ECO Revised Items.

11. Select the ECO status from the Special menu. See: ECO Statuses.

If the ECO status is Implement or Cancelled, the date of either status change is displayed.

12. If a workflow process is associated with the ECO, choose the Submit button to start the process.

If you are using an approval list, change the approval status to Ready to Approve. Doing so sends the Alert.

See Also

Viewing ECO Approval Status

Changing the ECO Status

Implementing ECOs

Defining ECO Autonumbering

MRP Planning for ECOs

Unreleased Item Revisions in Oracle Work in Process

Implementation of ECOs on Discrete Jobs and Repetitive Schedules

Engineering Profile Options and Security Functions