You are browsing the archive for ECO.

3.1 Engineering Change Order

Engineering Change Orders are created to modify items, BOMs and Routings. ECOs will support to capture the changes, approve and implement new revisions at a specified date.

Navigation: Engineering -> ECOs -> ECOs

1) ECO: Name or Number of the ECO. If ECO auto numbering is setup then this is defaulted automatically.

2) Type: ECO type. This field along with ECO priority controls the approval workflow process.

3) Status: Shows the status of ECO – Open, Approved, Cancelled, Scheduled, Implemented.

4) Requestor: Name of the Requestor.

5) ECO Department: Name of the ECO department

6) Reason: ECO Reason code

7) Priority: ECO Priority code. This field along with ECO type controls the approval workflow process.

8) Approval List: Predefined approvers list

9) Approval Status: Approval status of ECO

Engineering Change Order

Engineering Change Order

Click on ‘Revised Items’ to enter revised item, BOM & routing information.

ECO Revised Items

ECO Revised Items

11. ECO Departments

ECO or Engineering departments are organization entities to which ECOs are assigned. ECO departments are not tied to any inventory org structure but it gives flexibility based on business need to setup engineering entities.

ECO Departments are setup using the same screen as Inventory Organizations or Operating Units.

Navigation: Engineering -> Setups -> ECO Departments

Click “New” to enter new department

1) Name: Name of the ECO Department

2) Type: Usually it should be “department” for ECO department

3) From: Effective start date

4) To: Effective end date

5) Location: Pre-defined physical locations that represent the physical address of the department

6) Organization Classification Name: It should be ‘ECO Department’

7) Enabled Flag: Check the flag to enable.

Save the changes.

ECO Departments

ECO Departments

10. ECO Deletion Constraints

Deletion Constraints are additional rules that system validates before deleting any master objects like ITEMs, BOMs, ROUTINGs and ECOs.

Some deletion constraints are seeded (comes out of box), each business can add/impose additional constraints.

Navigation: Engineering -> Setups -> Deletion Constraints

1) Constraint: Name of the deletion constraint

2) Description: Meaningful description of the deletion constraint

3) Delete Entity: Select the object to be deleted, Eg. Items, Boms, Routings, ECOs

4) SQL Statement: Validation logic that system should execute before deletion

5) Delete if: You can select either “No Rows found” or “Rows found”, this is based on SQL statement written above.

6) Failure Message: If deletion constraint met and can’t be deleted, then what should be the message to be displayed.

Deletion Constarints

Deletion Constarints