122 Engug
122 Engug
122 Engug
User's Guide
Release 12.2
Part No. E48939-09
November 2022
Oracle Engineering User's Guide, Release 12.2
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No
other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface
1 Setting Up
Setup Overview......................................................................................................................... 1-1
Setup Flowchart and Checklist................................................................................................. 1-2
Setup Prerequisites ................................................................................................................... 1-3
Setup Steps ............................................................................................................................... 1-3
Defining ECO Types ................................................................................................................ 1-6
Defining ECO Autonumbering ................................................................................................ 1-8
Defining ECO Priorities ......................................................................................................... 1-10
Defining ECO Reasons ........................................................................................................... 1-11
Defining ECO Approval Lists ................................................................................................ 1-12
Defining Material Dispositions ............................................................................................. 1-13
Starting the AutoImplement Manager....................................................................................1-14
Engineering Profile Options and Security Functions............................................................ 1-15
Profile Option Settings........................................................................................................... 1-16
Profile Options........................................................................................................................ 1-18
iii
ECO Approvals.......................................................................................................................... 2-9
Customizing the Standard Approval Process......................................................................... 2-11
The ECO Approval Item Type................................................................................................ 2-13
Summary of the ECO Approval Process................................................................................. 2-15
ECO Approval Process Activities............................................................................................2-16
Defining Engineering Change Orders.................................................................................... 2-20
Creating an ECO ..................................................................................................................... 2-22
Viewing ECO Approval Status .............................................................................................. 2-25
Rescheduling an ECO or Revised Items................................................................................. 2-27
Changing the ECO Status ....................................................................................................... 2-27
Defining Implementation Costs ............................................................................................ 2-28
Defining an ECO Revision ..................................................................................................... 2-29
Defining ECO Revised Items ................................................................................................. 2-29
Viewing ECO Schedule History ............................................................................................ 2-33
Viewing Item Revisions ......................................................................................................... 2-34
Viewing Routing Revisions.................................................................................................... 2-34
Defining Revised Operations ................................................................................................ 2-35
Defining Revised Resources .................................................................................................. 2-37
Defining Revised Components .............................................................................................. 2-39
Assigning or Deleting Substitute Components .....................................................................2-42
Assigning Reference Designators .......................................................................................... 2-43
Attaching Files to ECOs.......................................................................................................... 2-43
Transfer to Manufacturing from an ECO .............................................................................. 2-44
Copy to Manufacturing from an ECO .................................................................................... 2-46
Mass Changing ECOs.............................................................................................................. 2-49
Implementing ECOs................................................................................................................ 2-49
Automatic Implementation..................................................................................................... 2-50
Cancelling ECOs and Revised Items ..................................................................................... 2-52
Viewing ECO Schedules ........................................................................................................ 2-53
Use Up ECOs........................................................................................................................... 2-54
MRP Planning for ECOs .........................................................................................................2-55
Unreleased Item Revisions in Oracle Work in Process.......................................................... 2-56
Implementation of ECOs on Jobs and Schedules.................................................................. 2-56
Purging ECOs.......................................................................................................................... 2-60
Engineering Change Orders Field Reference......................................................................... 2-61
Change Orders Dashboard...................................................................................................... 2-64
3 Engineering Prototypes
Overview of Engineering Prototype Environment................................................................... 3-1
ECOs on Engineering Items and Bills...................................................................................... 3-4
iv
Transferring or Copying Engineering Items, Bills, and Routings........................................... 3-5
4 Reports
Engineering Change Order Approval Lists Report ................................................................. 4-1
Engineering Change Order Detail Report ............................................................................... 4-1
Engineering Change Order Open Interface Report..................................................................4-3
Engineering Change Order Priorities Report .......................................................................... 4-4
Engineering Change Order Reasons Report ............................................................................ 4-4
Engineering Change Order Schedule Report .......................................................................... 4-4
Engineering Change Order Types Report ............................................................................... 4-7
B Engineering Alerts
Engineering Alerts.................................................................................................................... B-1
Index
v
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle Engineering User's Guide.
• Engineers
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Structure
1 Setting Up
2 Engineering Change Orders
3 Engineering Prototypes
4 Reports
A Engineering Windows and Navigator Paths
B Engineering Alerts
ix
C Engineering Tools Menu
D 21 CFR Part 11 Compliance
x
• Oracle Warehouse Management User's Guide
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As
your instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
xi
1
Setting Up
Setup Overview
This section contains an overview of each task you need to complete to set up Oracle
Engineering.
Before you set up Oracle Engineering, you should:
• Setting Up Oracle Applications System Administrator. See: System Administration
Setup Tasks, Oracle E-Business Suite Setup Guide.
Setting Up 1-1
Setup Flowchart and Checklist
Some of the steps outlined in this flowchart and setup checklist are Required and some
are Optional. Required Step With Defaults refers to setup functionality that comes with
pre-seeded, default values in the database; however, you should review those defaults
and decide whether to change them to suit your business needs. If you want or need to
change them, you should perform that setup step. You need to perform Optional steps
only if you plan to use the related feature or complete certain business functions.
The diagram below is described in detail in the Setup Checklist table, and Setup Steps
section that follow.
The following table lists setup steps. After you log on to Oracle Applications, complete
these steps to implement Oracle Engineering:
Setup Prerequisites
Before you set up Oracle Engineering, you must complete the setup for the following:
In Oracle Inventory:
• Define items. See: Defining Items, Oracle Inventory User's Guide
Setup Steps
Setup Steps:
1. Set Profile Options (Required)
Profile options specify how Oracle Engineering controls access to and processes
data. In general, profile options can be set at one or more of the following levels:
site, application, responsibility, and user.
Oracle Engineering users use the Update Personal Profile Options form to set
profile options only at the user level. System administrators use the Update System
Profile Options form to set profile options at the site, application, responsibility,
and user levels.
Context: Perform this step once for each entity, that is, site, application,
responsibility, or user.
Setting Up 1-3
2. Enter Employee (Required)
Define employees for your organization. ECO requestors and approvers must be
defined as employees.
If you do not install Oracle Human Resource Management Systems with Oracle
Engineering, you use the Enter Employee form to define and maintain employees in
Oracle Engineering.
If you install Oracle Human Resource Management Systems, you use the forms in
Oracle Human Resource Management Systems instead to enter and maintain
employees.
Context: Perform this step once for each entity organization.
If you automatically implement ECOs, you must specify the frequency that you
want the AutoImplement manager to run. Once an ECO has been released to the
autoimplement manager, you can automatically implement all scheduled ECO
revised items whose effective date is less than or equal to the current date.
Related Topics
Starting the AutoImplement Manager, page 1-14
Defining ECO Priorities, page 1-10
Defining ECO Reasons, page 1-11
Defining Material Dispositions, page 1-13
Defining ECO Approval Lists, page 1-12
Defining ECO Autonumbering, page 1-8
Defining ECO Types, page 1-6
Oracle Engineering Profile Options and Security Functions, page 1-15
Setting Up 1-5
Defining ECO Types
Engineering change order (ECO) types help classify engineering and mass change
orders to items and bills of material, and determine whether such orders apply to
engineering in addition to manufacturing.
An ECO type can be associated with an Oracle Workflow process. If so, a priority can
optionally be associated with the ECO type.
If you define an ECO using a type and priority combination (even if the priority is
blank) that is associated with a workflow process, Workflow will control the ECO
approval process. If the type and priority combination is not associated with a workflow
process, the ECO approval status defaults to Approved.
Use this form to define and update change order types that determine the types of items
and bills of material you can modify on mass change orders.
Note: You can now create an engineering change order type in the
Change Types window with a name of up to 80 characters in length in
the Type field. Previously, the name of an engineering change order
type was limited to 10 characters.
You can now set up engineering change order types in the Change
Types window in multiple languages.
3. Indicate whether the change order type can revise both engineering and
manufacturing items and bills.
ECOs with an engineering change type can include both engineering and
manufacturing items. ECOs with a manufacturing change type cannot include
engineering items.
If an ECO with a status of Open, Hold, Release, or Schedule is using this ECO type,
this value cannot be updated.
You must choose the Manufacturing option in this field for Oracle Engineering.
5. Enter a date to inactivate the change order type. As of this date, you can no longer
assign this change order type to a change order.
6. To associate this ECO type with a Workflow process, choose the Processes button.
If you do not associate this ECO type with a Workflow process, any ECO using this
type will default to Approved.
2.
Setting Up 1-7
Optionally, select an ECO priority.
Related Topics
Overview of Engineering Change Orders, page 2-2
Engineering Change Order Types Report, page 4-7
Workflow for ECO Approvals, page 2-9
Defining ECO Priorities, page 1-10
For example, if a prefix is set up for you and the current organization, it supersedes a
prefix defined for you across all organizations.
When defining an ECO, you can either accept a default ECO number or manually enter
one. Engineering displays the prefix along with the next available number. If
Engineering does not find an autonumbering prefix, you must assign an ECO number
manually.
Setting Up 1-9
Important: The information you provide in the Organizations
region is associated with the specific user or the All Other Users
record in the Users region.
4. Enter a prefix to use as the first characters for each defaulted ECO identifier for the
specific user or All Other Users, whichever is currently selected.
You can define only one prefix per user per organization. You can define only one
prefix per user across all other organizations.
5. Enter a Next Number to use as the of the base of the numeric portion of ECO
autonumbering.
The combined prefix and next number-the autonumber-is incremented when each
ECO is created. For example, if you enter 100 and your prefix is ABC, the first ECO
number is ABC100. The next will then be ABC101.
Each new ECO number is defaulted to one integer plus the last used ECO number.
When defining a new ECO, you can override this with a higher value. The next
ECO number will then be one integer greater. For example, assuming ABC as the
prefix and no ECOs defined using ABC, ABC1 is the default. If you have defined an
ECO called ABC234, ABC235 is the default.
You cannot enter a prefix and next number that, when used together, exceeds ten
alphanumeric characters.
Related Topics
Engineering Change Orders, page 2-2
Creating an ECO, page 2-22
Note: ECO priorities can be specified when associating ECO types with
Oracle Workflow processes, which are used for ECO approvals.
3. Enter a priority sequence. This is a number between 0 and 9. For example, you can
use 0 to denote the highest priority and 9 the lowest.
5. Optionally, enter a date on which the priority becomes inactive. As of this date, you
can no longer assign the priority to an ECO.
Related Topics
Defining ECO Types, page 1-6
Engineering Change Order Priorities Report, page 4-4
Setting Up 1-11
2. Enter alphanumeric text to describe a unique reason for initiating an engineering
change. For example, you could define a reason obsolete to indicate an obsolete part,
or waiver to indicate a component change on a bill of material.
4. Enter a date on which the reason becomes inactive. As of this date, you can no
longer assign the reason to an ECO.
Related Topics
Engineering Change Order Reasons, page 4-4
3. Enter a sequence for the approver. This number indicates the sequence of the
approver for the ECO. Engineering uses this for information purposes only.
5. Enter a date for this approver on the approval list. As of this date, the approver is
no longer notified when an ECO requires their approval.
Related Topics
ECO Approval Statuses, page 2-61
Workflow for ECO Approvals, page 2-9
Viewing ECO Approval Status, page 2-25
Engineering Change Order Approval Lists Report, page 4-1
Setting Up 1-13
To define a material disposition:
1. Navigate to the Material Dispositions Lookups form and define your material
disposition.
4. Navigate to the Revised Items window and assign your material disposition to
revised items.
Related Topics
Defining ECO Revised Items, page 2-29
3. Enter the dates and times when to run the ECO auto implement process.
Related Topics
Changing the ECO Status, page 2-27
Setting Up 1-15
Engineering Items: Revisions (ENG_INVIDITM_REVISIONS)
Determines whether revisions for engineering items can be updated.
ENG: - Y Y Y Y Required No
Change
Order
Autonum
bering -
System
Administ
rator
Access
ENG: - Y Y Y Y Optional No
ECO
Departm
ent
ENG: - 0 0 0 Y Optional No
ECO
Revision
Warning
ENG: - 0 0 0 Y Optional No
Mandator
y ECO
Departm
ents
ENG: - Y Y Y Y Optional No
Planning
Item
Change
Order
Access
ENG: - 0 0 Y Y Optional No
Require
Revised
Item
New
Revision
Setting Up 1-17
Profile User User Resp App Site Required Default
Option ? Value
Profile Options
You can set or view profile options in Oracle Engineering. The profile options
mentioned in the preceding table are described here.
Setting Up 1-19
ENG: Require Revised Item New Revision
Indicates whether it is mandatory to assign a new revision to revised items on ECOs. A
blank (or "null") value is equivalent to No.
Related Topics
Overview of Function Security, Oracle E-Business Suite Security Guide
Implementing Function Security, Oracle E-Business Suite Security Guide
Defining Preferences with User Profile Options, Oracle E-Business Suite User's Guide
Profile Options in Oracle Application Object Library, Oracle E-Business Suite Setup Guide
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.
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.
Engineering changes can be defined by date and or model/unit number effectivity. You
should assign an effective date and model / unit number for each revised item on an
ECO. Engineering uses this information 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. A date effective revised item
can only have date effective revised components.
A unit effective revised item can have both unit and/or date effective components. All
unit effective revised items must have a from end item unit number specified, if the
effectivity profile is set to Unit effectivity. The from end item unit number will be null
and non-updatable for date effective revised items. The to end item unit number field
will also be null and non-updatable for revised components of date effective revised
items If you are implementing a ECO for a unit effective component, the from unit
number needs to be specified in the revised item block and the to unit number needs to
be specified in the revised components block.
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.
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.
Revised Operations
You can define an ECO for Operations. You can add, disable, and change Department
information, Effective dates, Minimum Transfer quantities, and many other attributes.
Revised Resources
You can define an ECO for Resources. You can add, change, and disable resource
information.
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.
ECO Types
For each ECO type, you specify if it can update engineering items. Only users whose
profile option indicates they can update engineering items can choose ECO types that
update engineering items.
Related Topics
Implementation of ECOs on Jobs and Schedules, page 2-56
ECO Revised Item Statuses, page 2-61
Copy Engineering Items to Manufacturing, page 2-46
Transfer Engineering Items to Manufacturing page , page 2-44
Bill / Component Validation Rules, Oracle Bills of Material User's Guide
• ENG: Model Item Change Order Access (model and option class items)
Engineering enforces security for engineering items by letting only the users who are
allowed to update engineering items choose ECO types that update engineering items.
In addition, to update engineering bills of material for manufacturing items, you must
choose ECO types that update engineering items.
Each time you try to add a revised item to an ECO, Engineering checks to see if you can
In the example, Joe can create ECOs that update standard items. Mary can create ECOs
that update manufacturing standard items and model / option class items. But Mary is
not allowed to update engineering items.
ECO Departments
You can assign users to departments and secure each ECO to a department so that only
those users can access the ECO. If you do not specify a department for an ECO, any user
can access it. If you do not assign a user to a department, they can access all ECOs.
Setting the ENG: Mandatory ECO Departments to Yes requires you to specify a
responsible department on every ECO.
You can update the responsible department as you release an ECO from the current
ECO department. For example, if Product Engineering releases an ECO to
Manufacturing Engineering, they can reassign the responsible department so it becomes
visible and updatable to users assigned to the Manufacturing Engineering ECO
department.
Related Topics
Engineering Profile Options and Security Functions, page 1-15
Oracle Bills of Material Profile Options, Oracle Bills of Material User's Guide
Defining ECO Types, page 1-6
Access Control by Item Type, Oracle Bills of Material User's Guide
Related Topics
Transfer Items to Manufacturing from an ECO, page 2-44.
Copy Items to Manufacturing from an ECO: page, page 2-46.
Transferring or Copying Engineering Items, Bills, and Routings, page 3-5.
Copying Bill and Routing Information, Oracle Bills of Material User's Guide.
ECO Approvals
ECOs can be approved in three ways, two of which require an approval process. The
third requires no approval process.
First, the ECO, based on the ECO type in combination with the ECO priority, can be
associated with an Oracle Workflow process. Once approval is granted, Workflow
automatically updates the approval status.
Second, a simple approval list can be used, which sends an Oracle Alert to all those
listed requesting their approval. Once approved, you must manually update the
approval status. This approval option does not require an Oracle Workflow process.
The third method is to use neither of the above; the ECO needs no formal approval
process and is given the status of Approved.
If the ECO is associated with an Oracle Workflow process, only Workflow may set the
status to Approved. If the ECO has an approval list, you must set the status to
Approved manually after the ECO has been approved by the appropriate member(s) on
the approval list.
If neither is used, the ECO is set to Approved but can be manually rejected.
The following table describes the conditions under which the different approval
statuses can be used:
ECO Approval
The only user intervention required for a workflow approval process is for individual
approvers to respond to an ECO approval notification. Once the process is complete,
Workflow automatically updates the ECO approval status.
Related Topics
Workflow for ECO Approvals, page 2-9
ECO Approval Statuses, page 2-61
3. Expand the data source, then the ECO Approval item type branch within that data
source.
4. Expand the Processes branch within ECO Approval then double-click on the
Standard Approval Process activity to display the diagram of the process in a
Process window.
Required Modifications:
You must make the following modifications to the Standard Approval Process before
you can use it to initiate a workflow:
1. Specify an Approval for the ECO Approval Process
• Choose Load Roles From the Database from the File menu. Select the role you
wish to use for an approval.
• Enter Constant as the Performer Type. Select a Performer from the adjacent list
of values.
Optional Modifications:
Although you can use the Standard Approval Process as is, you may want to customize
the process further to accommodate your organization's specific needs.
Related Topics
ECO Approval Process Activities, page 2-16
Defining ECO Types, page 1-6
Defining ECO Approval Lists, page 1-12
Creating an ECO, page 2-22
Viewing ECO Approval Status, page 2-25
• Required - Yes
• Required - Yes
• ECO_STATUS
• INITIATION_DATE
• PRIORITY_CODE
• REASON_CODE
• ESTIMATED_ENG_COST
• ESTIMATED_MFG_COST
• ATTRIBUTE_CATEGORY
• ATTRIBUTE1
• ATTRIBUTE2
• ATTRIBUTE3
• ATTRIBUTE4
• ATTRIBUTE5
• ATTRIBUTE6
• ATTRIBUTE7
• ATTRIBUTE8
• ATTRIBUTE9
• ATTRIBUTE10
• ATTRIBUTE12
• ATTRIBUTE13
• ATTRIBUTE14
• ATTRIBUTE15
• APPROVAL_STATUS
• ORGANIZATION_CODE
• ORGANIZATION_NAME
• FULL_NAME
• CHANGE_TYPE
• ECO_DEPT_NAME
• ECO_DEPT_CODE
• Required - Yes
• Expand Roles - No
• Required - Yes
• Required - No
• Required - No
• Required - Yes
• Required - No
• Required - No
3. Assign an ECO approval list and status. See: Viewing ECO Approval Status, page 2-
25.
6. Define revised items. See: Defining ECO Revised Items, page 2-29.
7. Review ECO scheduling. See: Viewing ECO Schedule History, page 2-33.
11. Optionally, attach files to ECOs. See: Attaching Files to ECOs, page 2-43.
12. Submit the ECO for approval or set approval status to Ready to Approve.
13. Transfer or Copy the ECO to manufacturing See: Transfer to Manufacturing from
an ECO page , page 2-44 and Copy to Manufacturing from an ECO page , page 2-
46.
Related Topics
Rescheduling an ECO or Revised Items, page 2-27
Changing the ECO Status, page 2-27
Implementing ECOs, page 2-49
Engineering Change Order Detail Report, page 4-1
Transferring or Copying Engineering Items, Bills, and Routings, page 3-5
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.
You can create, update and delete ECOs for the current organization, or for the current
organization and all subordinate organizations in a given organization hierarchy.
You can use ECO propagate function to implement ECO in all eligibles across
organization.
To create an ECO:
1. Navigate to the Engineering Change Orders window.
4. Indicate whether to process the ECO across all organizations within the given
organization hierarchy, or for the current organization.
Note: If the checkbox is clear, then the ECO applies to the current
organization. If the checkbox is selected and a value is provided in
the Organization Hierarchy field, then the ECO propagate function
allows ECO to be applied to the current organization and all
subordinate organizations under the given organization hierarchy
structure.
• 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.
Note: If the ECO type and the priority combination are associated
with an Oracle Workflow process, you cannot use an approval list.
9. 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.
11. Choose the ECO Revisions button to define ECO revisions. See: Defining an ECO
Revision, page 2-29.
12. Choose the Revised Items button to define revised items. See: Defining ECO
Revised Items, page 2-29.
13. Select the ECO status from the Tools menu. See ECO Statuses, page 2-61.
If the ECO status is Implement or Cancelled, the date of either status change is
displayed.
Related Topics
Defining ECO Types, page 1-6
Viewing ECO Approval Status, page 2-25
Changing the ECO Status, page 2-27
Implementing ECOs, page 2-49
Defining ECO Autonumbering, page 1-8
MRP Planning for ECOs, page 2-55
Unreleased Item Revisions in Oracle Work in Process, page 2-56
Implementation of ECOs on Discrete Jobs and Repetitive Schedules, page 2-56
Engineering Profile Options and Security Functions, page 1-15
Creating Organization Hierarchies, Using Oracle HRMS-The Fundamentals
2. Highlight the desired Approval Process, and select the Status button.
Related Topics
Creating an ECO, page 2-22
ECO Approval Statuses, page 2-61
Workflow for ECO Approvals, page 2-9
Related Topics
Overview of Function Security, Oracle E-Business Suite Security Guide
Implementing Function Security, Oracle E-Business Suite Security Guide
Scheduled Yes No No No
2. From the Tools menu, choose the status (Open, Hold, Release, Schedule,
Implement, or Cancel). See: ECO Statuses, page 2-61.
3. If you are cancelling the ECO, select the Cancel Comments pop list to enter
comments.
Related Topics
Implementing ECOs, page 2-49
Starting the AutoImplement Manager, page 1-14
Engineering Profile Options and Security Functions, page 1-15
Note: You can create a bill for the item (if one does not exist) by
choosing the Components button and adding components in the
Revised Components window.
3. Optionally, enter an alternate for the item. You can create or update alternate bills
using an ECO.
Note: You cannot enter a future effective date for revised item
associated with editable common bill.
8. Choose a status for the ECO revised item from the Tools menu. See: ECO Revised
Item Statuses, page 2-61.
Note: You can set the revised item status to Hold, Released,
Implemented, or Cancelled only if the ECO status is Open.
Otherwise, the revised item status defaults from the ECO status.
If the ECO has a Workflow process and the item or its components are changed, the
revised item's status is changed from Scheduled to Open and the approval status is
changed to Not Submitted for Approval.
9. Indicate whether the revised item is MRP Active, that included in the planning
process. The default is No if the Status is Hold; Yes if the Status is Open, Release, or
Schedule.
If the ECO lists engineering changes and has an effective date in the future, you
may want the planning process to consider those changes.
10. Open the Item Details tabbed region and view the description and the user-defined
item type for that item.
11. Optionally, open the Dates tabbed region and enter the Early Effective date. This is
the earliest date you can manually implement the revised item.
If applicable, the Cancelled date for the changes of the revised item and its
components, or the Implemented date for the revised item is displayed.
The Implemented field indicates the date the revised item was implemented and
the Implemented By field indicates either that the revised item was implemented
manually from the Tools menu or implemented automatically.
12. Open the Use Up Details tabbed region and do the following:
• If not already selected, enter the item whose use-up date is tied to the revised
• View the use-up item associated with the use-up date selected as the effective
date.
• View the name of the MRP plan to use for determining item use-up dates.
13. Open the Routing Details tabbed region and do the following:
• Indicate whether CTP is enabled. This attribute is derived from the routing
header information if the revised item has existing routing information. If
routing information does not exist, routing header information is created
automatically when you enable this attribute.
• Enter Locator information. If the completion subinventory does not have a valid
location, or the revised item's Locator Control attribute is set to No Control,
then this field is disabled. If the revised item's Locator Control attribute is set to
Dynamic Entry, then this field is enabled.
14. Open the Work in Process tabbed region and indicate whether to update WIP
requirements for unreleased jobs or schedules when the revised item is
implemented.
15. Select a disposition for inventory and work in process inventory affected by the
ECO. See: Disposition, page 2-61.
16. Open the Cancel Details tabbed region to view the cancellation date and cancel
comments.
17. Choose the History button to view revised item effective date history and track
schedule changes to the revised item. Choose the Revisions button to view item
revisions. Choose the Components button to add, change, or disable components.
Related Topics
Viewing ECO Schedule History, page 2-33
Defining Revised Components, page 2-39
Viewing Item Revisions, page 2-34
Use Up ECOs, page 2-54
Defining Material Dispositions, page 1-13
A history of all previous effective dates and their entry date is listed for the revised
item.
2. View the employee who initiated the change to the effective date and any
comments describing the change to the effective date.
Related Topics
Engineering Change Order Detail Report, page 4-1
Related Topics
Defining ECO Revised Items, page 2-29
Related Topics
Defining Revised Components, page 2-39
Defining Revised Resources, page 2-37
Defining Revised Operations, page 2-35
Defining ECO Revised Items, page 2-29
3. Enter the Operation Sequence Number of the target operation. If you selected the
Add action, enter a new operation sequence number. If you selected the Change or
Disable actions, enter an existing operation sequence number.
4. Indicate whether this operation will be referenced if you selected the Add action. If
you selected a standard operation, then this flag is turned on automatically. If you
selected the Change action, then this flag is disabled.
5. Enter the Department Code. If you selected the Add action, or the Change action
and a standard operation, enter an existing department code.
6. Enter the date the operation is to be disabled in the Disable Date field. If you
selected the Disable action, the system date is entered automatically.
7. Indicate whether this operation is option dependent if you selected the Add action,
or the Change action and did not select the reference flag.
9. Open the WIP tabbed region and enter the following attributes:
• If you selected the Add action, or the Change action and did not select the
reference flag, you can update the Count Point flag.
• If you selected the Add action, you can update the Autocharge flag.
• If you selected the Add action, or the Change action and did not select the
reference flag, you can update the Backflush flag.
• If you selected the Add action, or the Change action and did not select the
reference flag, you can enter the Minimum Transfer Quantity.
10. Open the Operation Yield tabbed region and do the following:
• Enter the Yield if you selected the Add or Change actions. Operation Yield is
applicable to lot-based jobs, and is used to track variances between estimated
and actual scrap absorption. See: Defining a Department, Oracle Bills of Material
User's Guide
• Enter the Cumulative Yield if you selected the Add or Change actions. See:
Yield, Oracle Bills of Material User's Guide.
Related Topics
Defining Revised Components, page 2-39
Defining Revised Resources, page 2-37
Item and Operation Sequence, Oracle Bills of Material User's Guide
Effective Date Fields, Oracle Bills of Material User's Guide
3. Enter the Resource Sequence Number. If you selected the Add action, enter a new
resource sequence number. If you selected the Disable action, enter an existing
resource sequence number.
4. Enter the Resource Code. If you selected the Add action, select a resource belonging
to the selected department in the Revised Operations window.
Note: The UOM field is derived from the Resource attribute and is
read-only.
5. Enter the Basis Type. If you selected the Add or Change actions, select Item or Lot.
See: Basis, Oracle Bills of Material User's Guide.
7. Enter the Inverse Rate or Amount if you selected the Add or Change actions. Once
you enter or change this value, the Usage will be calculated automatically.
• If you selected the Add or Change actions, enter a Schedule Sequence Number.
• Select the Schedule option. Available options are Yes, No, Prior, and Next.
• If you selected the Add or Change actions, enter the Offset percentage. This
number should be greater than or equal to zero, and less than or equal to 100.
• Indicate whether this is the principle resource in the operation, if you selected
the Add or Change actions.
• Select a Charge Type if you selected the Add action. If you selected the Change
action, you can change the Charge Type but cannot enter an autocharge type of
PO Move or PO Receipt for a resource without Outside Processing enabled.
You can select Manual or WIP Move.
Related Topics
Defining Revised Components, page 2-39
Defining Revised Operations, Oracle Engineering User's Guide
Item and Operation Sequence, Oracle Bills of Material User's Guide
4. Do the following:
• If you are changing component information, enter the old operation sequence
where the component is currently assigned.
• If you are changing the component's operation sequence, enter a new operation
sequence (from the routing) for the component of the revised item. The default
is 1 for components being added where no routing exists.
• Enter the item sequence of the item on the bill of material. The default is the
next highest item sequence.
• For components you are adding or changing, enter an inactive date for the
revised component.
5. Review the item's description, revision, and whether it is an engineering item in the
Item Details tabbed region.
• Enter a component yield factor. You cannot enter component yield for an
option class item or for any components of a planning bill. The default is 1,
indicating 100% yield. See: Yield, Oracle Bills of Material User's Guide.
• Indicate whether to include the cost of this component in the cost of its parent
item for the cost rollup.
7. Open the Material Control tabbed region and select a supply type, a subinventory,
and a locator. See: Supply Type, Oracle Work in Process User's Guide and
Subinventory and Locator, Oracle Bills of Material User's Guide.
• For optional components, enter the minimum and maximum sales order
quantities. See: Minimum and Maximum Quantities, Oracle Bills of Material
User's Guide.
10. If the component is cancelled, open the Cancel Details tabbed region. Once the
component is cancelled, you can no longer update any information about the
revised component on this ECO.
11. Choose the Substitutes button to open the Substitute Components window. Choose
the Designators button to open the Reference Designators window.
Related Topics
Assigning Reference Designators, page 2-43
Assigning or Deleting Substitute Components, page 2-42
Item and Operation Sequence, Oracle Bills of Material User's Guide
Effective Date Fields, Oracle Bills of Material User's Guide
2. Enter an action: add a substitute item to, or delete a substitute item from the revised
component.
3. Enter or select a substitute item for the revised component. This must be a
manufacturing item.
4. Enter the quantity of the substitute item needed to replace the full component
quantity.
This can differ from the bill usage quantity of the component. The default is the
usage quantity of the component.
3. Select an action: add to or delete a range of reference designators from the revised
component.
Engineering enables you to view a prefix, suffix, and number range to assign to a
sequence of reference designators.
Related Topics
Creating Reference Designators, Oracle Bills of Material User's Guide
2. Select the Transfer Button from the Engineering Change Orders window.
8. Select the Selection Option from the list. The available selections are:
All: All past, current or future components and or operation steps associated with
the assembly.
Current: All current components and or operation steps associated with the
assembly that are effective on the Selection Date.
Future and Current: All current and future components and or operation steps
associated with the assembly.
Related Topics
Transferring or Copying Engineering Items, Bills, and Routings, page 3-5
Transfer or Copy from an ECO, page 2-7
Copy to Manufacturing from an ECO, page 2-46
Copying Bill and Routing Information, Oracle Bills of Material User's Guide
2. Select the Copy Button from the Engineering Change Orders window.
6. Select the Revisions tabbed region. For information on the Revisions tabbed region
and the Alternates tabbed, See:Transferring or Copying Engineering Items, Bills,
and Routings, page 3-5
8. Select the Selection Option from the list. The available selections are:
All: All past, current or future components and or operation steps associated with
the assembly.
Current: All current components and or operation steps associated with the
assembly that are effective on the Selection Date.
Future and Current: All current and future components and or operation steps
associated with the assembly.
Related Topics
Transferring or Copying Engineering Items, Bills, and Routings, page 3-5
Transfer or Copy from an ECO, page 2-7
Transfer to Manufacturing from an ECO, page 2-44
Copying Bill and Routing Information, Oracle Bills of Material User's Guide
Related Topics
Engineering Profile Options and Security Functions, page 1-15
Mass Changing Bills of Material, Oracle Bills of Material User's Guide
Implementing ECOs
When you implement an ECO, each revised item's status is marked as "implemented";
you can no longer reschedule it. You can implement all revised items on an ECO, or
implement each revised item on a different date. Engineering only lets you implement
ECOs that do not have an approval status of Rejected, or do not have an ECO status of
Hold or Cancelled. Once you implement an ECO or revised item, you can no longer
make any revised item changes.
Manual Implementation
For an ECO, you can specify whether to implement all or specific revised items. An
ECO can be implemented today, but will not make the changes to the revised items
effective until the date specified on the change order.
Automatic Implementation
To AutoImplement a revised item on an ECO, you mark the revised item status as
'scheduled' and specify an effective date. You can schedule all revised items on an ECO
for auto-implementation, or schedule each revised item individually. Engineering
automatically implements scheduled changes on their effective dates.
You can automatically implement scheduled ECOs in the current organization, or the
current organization including all subordinate organizations. You have the ability to
specify the organization hierarchy name, since the current organization can be accessed
from more than one organization hierarchy. You can also automatically implement
scheduled ECOs in all organizations having the same item master organization as the
current organization, and if they are accessible by the user responsibility.
Start the AutoImplement Manager process so Engineering implements scheduled
changes daily.
3. Choose Implement from the Tools menu. Doing so automatically changes the status
of all revised items.
3. Set the ECOs status and/or the status of revised items to Scheduled.
• Organization Hierarchy
Related Topics
Engineering Profile Options and Security Functions, page 1-15
Starting the AutoImplement Manager, page 1-14
Implementation of ECOs on Discrete Jobs and Repetitive Schedules, page 2-56
Creating Organization Hierarchies, Using Oracle HRMS-The Fundamentals
• Cancel a revised item by choosing the Revised Items button on the Engineering
Change Orders window, and choosing Cancel from the Tools menu.
Related Topics
Engineering Profile Options and Security Functions, page 1-15
Creating an ECO, page 2-22
See: Material Requirements Planning, Oracle MRP User's Guide.
3. Select how to sort ECOs-by ECO identifier then effective date, or by effective date
then ECO identifier.
• A revised item
• A revised component
• Whether to query for revised item status, and if so, any combination of revised
item statuses.
5. Choose the Find button to find ECOs based on your search criteria.
This opens the View ECOs folder window which has three tabbed regions, each
containing specific ECO information: Revised Items, ECO Details, and Use Up.
6. Choose the New and Open buttons to navigate to the Engineering Change Orders
window. Using the New button enables you to create a new ECO; using the Open
button enables you to view an existing ECO.
Related Topics
Using Query Find, Oracle E-Business Suite User's Guide
Using Query Operators, Oracle E-Business Suite User's Guide
Searching For Information, Oracle E-Business Suite User's Guide
Performing Query-by-Example and Query Count, Oracle E-Business Suite User's Guide
Defining Engineering Change Orders, page 2-20
Customizing the Presentation of Data in a Folder, Oracle E-Business Suite User's Guide
Use Up ECOs
Oracle Master Scheduling/MRP automatically computes and stores the use-up date for
each item it plans on each MRP plan. The use-up date is the date when on-hand
quantity is exhausted based on projected gross requirements. It calculates the use-up
date by applying any on-hand quantity in inventory (supply) against any gross
Use-Up Alerts
Engineering uses Oracle Alert to automatically notify planners whenever the MRP
planning process computes a new use-up date for an item if it is a use-up item for an
ECO revised item. For example, if revised item A specifies item B as its use-up item (so
the revised item effective date for A equals B's use-up date), then if the MRP planning
process computes a different use-up date for B, Oracle Alert notifies the planner for A
that B's use-up date no longer equals the revised item effective date for A.
Related Topics
Creating an ECO, page 2-22
Overview of Planning Logic, Oracle Master Scheduling/MRP User's Guide
Reviewing the Horizontal Plan, Oracle Master Scheduling/MRP User's Guide
Related Topics
Material Requirements Planning, Oracle Master Scheduling/MRP User's Guide
Related Topics
Overview of Discrete Manufacturing, Oracle Work in Process User's Guide
Overview of Repetitive Manufacturing, Oracle Work in Process User's Guide
Example
Released Schedule:
• Production rate = 50 per day
• Throughput = 1 day
Since the daily quantity is 50, this means that production is in its second day. Therefore,
if you implement the ECO now, the schedule splits after the second day's work is
completed.
If you implement a change order for the item on Day 3 (Today), the shop floor
distribution of assemblies following the implementation of the ECO are:
New Schedule 1 = 100 total units
• 20 units in queue of the first operation
• 80 units spread in the routing beyond queue of the first operation. These 80 units
New Schedule 2:
• First unit start date = Day 3
Related Topics
Overview of Discrete Manufacturing, Oracle Work in Process User's Guide
Overview of Repetitive Manufacturing, Oracle Work in Process User's Guide
Purging ECOs
You can purge fully implemented engineering change information from the database.
You can choose a range of ECOs and a date. Engineering purges all fully implemented
or cancelled ECOs on or before that date.
When you purge ECOs, Engineering removes all implemented and cancelled ECOs as
of that date from the database, along with all related information (except for the
revision history of the bill itself). You cannot view or report ECO information once you
purge it.
To purge an ECO:
1. Navigate to the Purge Engineering Change Order window. See: Submitting a
Request, Oracle E-Business Suite User's Guide.
5. Enter a date on or before which all implemented and/or cancelled ECOs are purged.
ECO Statuses
Whenever this status is updated, the status of all revised items is also updated.
Note: If the organization hierarchy is selected when creating an ECO, the ECOs having
approval process will be propagated with an 'Open' status.
Not Submitted for Approval The ECO has not been submitted to the
Workflow approval process.
Disposition Field
These values describe the disposition of inventory and work in process inventory
affected by an engineering change order (ECO).
No change required The ECO does not affect the revised item in
WIP and inventory. This is the default.
Scrap WIP and inventory Scrap the revised item in WIP and inventory
when you implement the revised item.
Scrap only inventory Scrap the revised item only in inventory when
you implement the revised item.
Scrap only WIP Scrap the revised item only in WIP when you
implement the revised item.
Rework inventory and WIP Rework the revised item in WIP and
inventory when you implement the revised
item.
Rework only WIP Rework the revised item only in WIP when
you implement the revised item.
Exhaust WIP and inventory Use the revised item until you exhaust WIP
and inventory for the item.
Exhaust only WIP Use the revised item until you exhaust WIP
for the item.
Note: This does not apply to Product Families. See: Creating a Product
Family, Oracle Bills of Material User's Guide
• Track inventory
• Rollup costs
ECO Types
Engineering controls the access to ECOs and the changes you can specify on an ECO.
For each ECO type, you can specify if ECOs of this type can update engineering items.
Only users whose profile option indicates they can update engineering items can choose
ECO types that update engineering item information. If you define a new bill of
material using an ECO with an ECO type that updates engineering items, Engineering
creates the bill as an engineering bill when you implement the ECO.
Profile Options
Engineering uses the following four profile options to control the types of items you can
change on an ECO:
• ENG: Model Item Change Order Access (model and option class items)
Related Topics
Creating an ECO, page 2-22
Defining ECO Types, page 1-6
Engineering Profile Options and Security Functions, page 1-15
Transferring and copying engineering data is organization specific. That is, you can
only transfer or copy an engineering item, bill, or routing to manufacturing within the
same organization.
Engineering Items
All information associated with the engineering item is transferred or copied.
If you copy an engineering item, you must provide a new name and description. The
original item information is retained in engineering.
When you transfer an engineering item assigned to a category set different from the
inventory category set, Engineering automatically assigns the new manufacturing item
to the inventory category set. Engineering also enables you to assign a new item
revision and lets you reference an ECO when you transfer an engineering item.
Note: This is applicable for ECOs in the tabbed region and for
Transfer/Copy specific to Engineering Prototypes.
Engineering Routings
When you transfer a bill of material without transferring the engineering routing, all
components on the manufacturing bill report to the operation sequence 1, regardless of
the operations on the engineering routing. If components of the bill of material overlap
(the same component item appears twice) at operation sequence one, Engineering does
not transfer the engineering bill of material until you also transfer the engineering
routing. If you transfer the engineering bill of material and routing simultaneously,
components on the manufacturing bill report to the appropriate operation on the
manufacturing routing.
When you transfer a routing, you can also specify a new routing revision and reference
an ECO. Engineering transfers all operations, current effective operations, or future
effective operations depending on your transfer criteria. For routings that reference a
common engineering routing, you must transfer the common routing to manufacturing
before you transfer any engineering routings that reference the common routing.
Note: This is applicable for ECOs in the tabbed region and for
Transfer/Copy specific to Engineering Prototypes.
4. Optionally, open the Alternates tabbed region and for Selection, select Specific to
transfer (or copy) a specific alternate, select Primary to transfer the primary
alternate, or select All to transfer all alternates.
Leaving this blank will transfer (or copy) the primary and all alternates (if any).
To transfer (or copy) a specific alternate, you must enter its name.
5. Open the ECO, Description tabbed region and enter an ECO. This is for
informational purposes only.
8. If you are transferring (or copying) bills, indicate if only implemented components
should be transferred.
9. Select whether to transfer (or copy) All past, Current (effective on the specified
revision date), or Future components and/or operation steps associated with the
assembly. The default is Current. If you select Current or Future and Current, enter
an effective date.
Related Topics
Transfer or Copy from an ECO, page 2-7
Transfer items to manufacturing from an ECO, page 2-44
Copying Bill and Routing Information, Oracle Bills of Material User's Guide
Report Submission
In the Submit Requests window, select Engineering Change Order Approval Lists
Report in the Name field.
Related Topics
Submitting a Request, Oracle E-Business Suite User's Guide
Report Submission
In the Submit Requests window, select Engineering Change Order Detail Report in the
Name field.
Reports 4-1
All Organizations
Choose one of the following options:
Organization Hierarchy
Enter a valid organization hierarchy name from the list of values. If the value for the All
Organizations parameter is set to No, and you have provided a value for the
Organization Hierarchy parameter, then the report will provide ECO information for
the current organization and all organizations below the current organization in the
specified organization hierarchy. If this parameter is left blank, and the All
Organizations parameter is set to No, then the report will provide ECO information for
the current organization. You can enter a value in this field only if you have entered No
in the All Organizations field.
Dates From/To
To restrict the report to a range of dates, select the beginning and ending dates.
Status
Enter Open, Hold, Scheduled, Cancelled, Implemented, or Released to indicate the
status of the ECO to print. See: ECO Statuses, page 2-61.
Related Topics
Creating Organization Hierarchies, Oracle Bills of Material User's Guide
Submitting a Request, Oracle E-Business Suite User's Guide
Reports 4-3
Engineering Change Order Priorities Report
This report lists engineering change order (ECO) priorities that you defined for Oracle
Engineering. ECO priorities enable you to specify the urgency of your ECO.
Engineering uses ECO priorities for reference only.
Report Submission
In the Submit Requests window, select Engineering Change Order Priorities Report in
the Name field.
Related Topics
Submitting a Request, Oracle E-Business Suite User's Guide
Report Submission
In the Submit Requests window, select Engineering Change Order Reasons Report in
the Name field.
Related Topics
Submitting a Request, Oracle E-Business Suite User's Guide
Report Submission
In the Submit Requests window, select Engineering Change Order Schedule Report in
the Name field.
Print Components
Enter either Yes or No to indicate whether you want to print revised components
associated with the revised item.
Display Option
Choose one of the following options:
Revised Item
Enter a revised item to print.
Revised Component
Enter a revised component to print.
Reports 4-5
Sort Criteria 1
Choose one of the following options. The report sorts ECOs first in this order, then in
the specified order for Sort Criteria 2 and Sort Criteria 3.
Sort Criteria 2
Choose one of the following options. Engineering sorts the ECOs by the first sort type
and then by this sort type within the first type.
Sort Criteria 3
Choose one of the following options. Engineering sorts the ECOs by the first sort type,
then by the second sort type within the first type, and finally by this sort type within the
second type.
Report Submission
In the Submit Requests window, select Engineering Change Order Types Report in the
Name field.
Related Topics
Submitting a Request, Oracle E-Business Suite User's Guide
Reports 4-7
A
Engineering Windows and Navigator Paths
Engineering Responsibility
Assign Cross Reference Types (See INV) Prototypes > Items > Cross References >
[Assign]
Bill Components Comparison (See BOM) Prototypes > Bills > Comparison
Bill Details (See BOM) Prototypes > Bills > Bills > [Bill Details
Calculate Lead Times (See BOM) Prototypes > Routings > Lead Times
Change Type Processes, page 1-6 Setup > Change Types > [Processes]
Component Changes, page 2-49 ECOs > Mass Changes > [Changes]
Component Changes (See BOM) Prototypes > Bills > Mass Changes > [Changes]
Copy to Manufacturing: from within an ECO ECOs > ECOs > [Copy]
page , page 2-46
Cross Reference Types (See INV) Prototypes > Items > Cross References
Descriptive Elements (See BOM) Prototypes > Bills > Bills > [Elements]
Engineering Change Orders, page 2-20 ECOs > ECOs ECOs > Schedules
Engineering Master Item (See INV) Prototypes > Items > Master Items
Engineering Organization Item (See INV) Prototypes > Items > Organization Items
History, page 2-33 ECOs > ECOs > [Revised Items] > [History]
Import Bills and Routings (See BOM) Prototypes > Bills > Import
Indented Bill of Material (See BOM) Prototypes > Bills > Indented Bills
Item Attributes (See INV) Prototypes > Items > View Item Details >
[Attributes]
Item Catalog Groups (See INV) Prototypes > Items > Catalog Groups
Item Relationships (See INV) Prototypes > Items > Related Items > [Find]
Item Revisions, page 2-34 ECOs > ECOs > [Revised Items] > [Revisions]
Item Revisions (See BOM Prototypes > Bills > Bills > [Revision]
Item Search (See INV) Prototypes > Items > Item Search > [Find]
Item Template (See INV) Prototypes > Items > Item Template > [Find] >
Item Templates Summary > [Open]
Item WhereUsed (See BOM) Prototypes > Bills > Item WhereUsed
Operation Resources (See BOM) Prototypes > Routings > Routings > [Operation
Resources]
Reference Designators, page 2-43 ECOs > ECOs > [Revised Items] >
[Components] > [Designators]
Reference Designators (See BOM) Prototypes > Bills > Bills > [Designators]
Resource WhereUsed (See BOM) Prototypes > Routings > Resource WhereUsed
Revised Components, page 2-39 ECOs > ECOs > [Revised Items] >
[Components]
Revised Items, page 2-29 ECOs > ECOs > [Revised Items]
Routing Details (See BOM) Prototypes > Routings > Routings > [Routing
Details]
Routing Revisions (See BOM) Prototypes > Routings > Routings > [Routing
Revisions]
Standard Operations (See BOM) Prototypes > Routings > Standard Operations
Substitute Components, page 2-42 ECOs > ECOs > [Revised Items] >
[Components] > [Substitutes]
Substitute Components (See BOM) Prototypes > Bills > Bills > [Substitutes]
Character Mode Form and Menu Path GUI Window or Process, and Navigation
Path
\Navigate Setup Flexfields Key Security Navigator: Setup > Flexfields > Key > Security
Assign > Assign
\Navigate Setup Flexfields Validation Navigator: Setup > Flexfields >Validation >
Security Assign Security > Assign
\Navigate Report Bill Compare Navigator: Prototypes > Bills > Comparison
\Navigate Setup Flexfields Key Rules Navigator: Setup > Flexfields > Key > Rules
\Navigate Setup Flexfields Descriptive Navigator: Setup > Flexfields > Descriptive >
Segments Segments
\Navigate Setup Flexfields Descriptive Navigator: Setup > Flexfield > Descriptive >
Security Define Security > Define
\Navigate Setup Flexfields Descriptive Values Navigator: Setup > Flexfields > Descriptive >
Values
\Navigate Prototype Define Bill Navigator: Prototypes > Bills > Bills
or
Approval History
or
Approval Dates
or
ECO Revisions
or
or
\Navigate Prototype Define Item Item Navigator: Prototypes > Items > Master Items
or
\Navigate Prototype Define Item Revision Navigator: Prototypes > Bills > Bills >
[Revision]
\Navigate Prototype Define Routing Navigator: Prototypes > Routings > Routings
or
Routing Details
\Navigate Prototype Inventory Catalog Navigator: Prototypes > Items > Catalog
Define Groups
\Navigate Prototype Inventory Cross- Navigator: Prototypes > Items > Cross
Reference References > [Assign]
\Navigate Prototype Inventory RelatedItems Navigator: Prototypes > Items > Related Items
> [Find]
\Navigate prototype Inventory Template Navigator: Prototypes > Items > Templates >
[Find] > Item Templates Summary > [Open]
\Navigate Setup Flexfields Key Security Navigator: Setup > Flexfields > Key > Security
Define > Define
\Navigate Setup Flexfields Key Segments Navigator: Setup > Flexfields > Key >
Segments
\Navigate Setup Flexfields Key Values Navigator: Setup > Flexfields > Key > Values
\Navigate Setup Flexfields Key Groups Navigator: Setup > Flexfields > Key > Groups
\Navigate Setup Flexfields Validation Navigator: Setup > Flexfields >Validation >
Security Define Security > Define
\Navigate Setup Flexfields Validation Values Navigator: Setup > Flexfields >Validation >
Values
\Navigate Setup Flexfields Key Aliases Navigator: Setup > Flexfields > Key > Aliases
\Navigate Setup Flexfields Validation Set Navigator: Setup > Flexfields > Validation >
Sets
\Navigate Prototype Inventory Catalog Navigator: Prototypes > Items > Item Search >
Search [Find]
or
Transfer to Manufacturing
\Navigate Prototype Define Item Update Navigator: Prototypes > Items > View Item
Details > [Attributes]
\Navigate Inquiry Bill Compare Navigator: Prototypes > Bills > Comparison
Navigate Inquiry Bill Detail Navigator: Prototypes > Bills > Bills > [Bill
Details]
Choose:
\Navigate Inquiry Bill Indented Navigator: Prototypes > Bills > Indented Bills
\Navigate Inquiry Item Attributes Navigator: Prototypes > Items > View Item
Details > [Attributes]
Navigate Inquiry Item Revision Navigator: Prototypes > Bills > Bills >
[Revision]
or
\Navigate Inquiry WhereUsed Item Navigator: Prototypes > Bills > Item
WhereUsed
Engineering Alerts
Engineering includes these pre-coded alerts that you can use with or without
customizing.
Inputs Organization
Example:
Inputs Organization
Example:
Enter Costs Opens the ECO Costs window so that you can
enter engineering or manufacturing
implementation costs.
Copy Bill from Opens the Copy Bill window so that you can
copy a bill into an ECO.
Check for Loops Verifies that a bill does not contain items are
not listed as components of the same item.
Opens the Approval Dates window which
shows the date the ECO approval list was
requested, the date it was approved, or the
days remaining for approval to take place.
Related Topics
Changing the ECO Status, page 2-27
ECO Statuses, page 2-61
ECO Revised Item Statuses, page 2-61
Rescheduling an ECO or Revised Items, page 2-27
Defining Implementation Costs, page 2-28
Assigning an ECO Approval List and Status, page 2-25
Engineering Profile Options and Security Functions, page 1-15
Copying Bill and Routing Information, Oracle Bills of Material User's Guide
Checking for Bill Loops, Oracle Bills of Material User's Guide
Related Topics
E-Records and E-Signatures for Oracle Engineering, page D-2
See Viewing Oracle E-Records and E-Signatures
* By default, the online e-signatures marked with an asterisk (*) are disabled. To enable
e-signatures for these events, change the ESIG_REQUIRED configuration variable
default value to Y. See: Setting Up the Configuration Variables, Oracle E-Records
Implementation Guide.
ECO Approval
When a completed ECO is submitted for approval, the required e-signatures must be
captured to complete the approval process. You can enter your signature online, while
the event is happening in the window or in deferred mode. All users in the ECO
approval list receive workflow notifications requesting that they provide their e-
signature before the ECO is approved.
The ECO Approval process requires an additional setup step in Oracle Engineering
because this process is not defined in Oracle Approvals Management. You must
associate the Change Type and Priority used by the ECO with the ERES Approval
Process in Oracle Workflow. See: Defining ECO Types.
When creating the ECO, you must enter a Change Type and Priority that is associated
with the ERES Approval Process. You must also select a valid approval list in the
Approval List field.
ECO Implementation
You can create an e-record upon either manual or automatic implementation of an ECO.
When you implement an ECO, a concurrent program executes your command, captures
an e-record, and invokes the necessary event to make the change. The necessary event
could be a bill, routing, or item update or a transfer or copy to manufacturing. See:
Implementing ECOs..
• Engineering > Prototypes > Items > Master/Organization Items (M) Tools >
Engineering Transfer
• Engineering > Prototypes > Bills (M) Tools > Transfer Bill
• Engineering > Prototypes > Routings (M) Tools > Transfer Routing
Related Topics
Viewing Oracle E-Records and E-Signatures, page D-4
Also see: 21 CFR Part 11 Overview in the Oracle Engineering User's Guide.
• Selecting the eRecord Details option from the Tools menu of a transaction or event
initiating form. This option is available from many, but not all, of the transaction or
event initiating forms.
Related Topics
21 CFR Part 11 Overview
E-Records and E-Signatures for Oracle Engineering
Bill of material
Symbols defining, 3-4
21 CFR Part 11
Bills of Material Command Center
Oracle Engineering, D-2
Change Orders dashboard, 2-64
overview, D-1
viewing e-records and e-signatures, D-4
C
A Change Orders Dashboard, 2-64
Change order type, 1-4
Access Control
Change Types
ECO, 2-5
Defining ECO Types, 1-6
Action
Check ATP, 2-41
reference designators, 2-43
Components
Alert
Cancelling, 2-53
use up, 2-55
mutually exclusive, 2-41
Alerts
optional, 2-41
engineering, B-1
Revised, 2-4
Alternate
substitute, 2-42
in ECO revised items, 2-30
viewing
Approval list, 1-4, 1-12
on ECO, 2-54
Assign
Copy, 3-5
reference designators, 2-43
ECO, 2-44, 2-46
substitute components, 2-42
Costing
Attaching Files to ECOs, 2-43
items, 3-2
AutoImplement Manager
Cost Rollup, 2-41
setup, 1-5
starting, 1-14
D
Autonumbering ECOs
Autonumbering ECO's Defining
ECO, 1-8 bills of material, 3-4
ECO, 2-2
B Department
ECO
Basis, 2-41
ECO, department, 2-7
Index-1
Discrete job, 2-56, 3-3 repetitive schedule
Disposition, 2-32, 2- Pages, 2-56
requester, 2-24
E rescheduling, 2-27
revised components, 2-4
ECO, 2-24
revised item
approval, 2-9
status, 2-61
activities, 2-16
revised items, 2-3
creating a new process, 2-13
revised operations, 2-4, 2-35
customizing, 2-11, 2-12, 2-13
revised resources, 2-4, 2-37
item type, 2-13
revisions, 2-4
process, 2-15
defining, 2-29
status, 2-24, 2-25, 2-61
status
status conditions, 2-9
changing, 2-27
approval list report, 4-1
transfer, 2-4, 2-21
approval sequence, 1-13
Transfer, 2-7
attaching files, 2-43
type, 2-23
autonumbering, 1-8
types, 2-5
Defining, 1-9
setup, 2-11
building unreleased item revisions, 2-56
use up alert, 2-55
cancelling, 2-52
view
change order detail report, 4-1
schedule history, 2-33
change order priorities report, 4-4
Viewing ECO Schedules, 2-54
change order reasons report, 4-4
ECODisposition
controlling access, 2-5
status, 2-61
copy, 2-4, 2-7, 2-21
Effective Date
defining, 2-2, 2-20, 2-22
linking to use up date, 2-55
reasons, 1-11
revised item, 2-3
department, 2-7, 2-24
Employee
description, 3-7
ECO approver, 1-13
discrete job, 2-56
Engineering
engineering bills, 3-4
e-records and e-signatures, D-2
engineering change order schedule report, 4-4
Engineering alerts, B-1
engineering items, 3-4
Engineering bill of material
Implement, 2-50
defining, 3-4
implementing, 2-49
ECO, 3-4
life cycle, 2-8
releasing, 3-5
MRP planning, 2-55
transferring, 3-5
number, 2-23
types, 3-3
Oracle Work in Process, 2-56
Engineering change order
order types report, 4-7
use up, 2-54
personal profile options, 2-5, 3-4
Engineering item
priorities, 1-10
ECO, 3-4
priority
releasing, 3-5
setup, 2-11
transferring, 3-5
purging, 2-60
Engineering routing
reason, 2-24
releasing, 3-6
Index-2
transferring, 3-5
E-records N
Oracle Engineering, D-2
New operation sequence, 2-40
overview, D-1
viewing, D-4
O
E-signatures
Oracle Engineering, D-2 Old operation sequence, 2-40
overview, D-1 Operations
viewing, D-4 revised, 2-4
Organization
F ECO
defining autonumbering, 1-9
Forms
Define Change Order Types, 1-6
P
I Personal profile options
ECO, 3-4
Implementation
Planning
costs
items, 3-3
defining, 2-28
unimplemented revised items, 2-55
ECO, 2-49
Use-up ECO, 2-56
automatic, 2-50
Planning percent, 2-41
manual, 2-50
Prefix, 1-10
Implemented
Priority, 1-10, 1-11
Components to transfer
setup, 1-5
components to transfer, 3-8
use with workflow process, 1-7
Item
Priority sequence, 1-11
catalog, 3-2
Profile Options, 1-3
revised, 2-3, 2-34
ECO, 2-56
defining, 2-29
personal
rescheduling, 2-27
ECO, 2-5
status, 3-2
settings, 2-6
to change with ECO, 2-30
Purging
to transfer to manufacturing, 3-7
ECO, 2-60
types, 3-3
Use-up date, 2-31
Q
L Quantity, 2-41
substitute component, 2-42
List, 1-13
R
M
Reason, 1-5
Mass Changing
Reference Designators
ECOs, 2-49
assigning, 2-43
Material Dispositions, 1-5
Releasing
defining, 1-13
engineering bill, 3-5
Maximum sales order quantity, 2-41
engineering item, 3-5
Minimum sales order quantity, 2-41
engineering routing, 3-6
Index-3
Repetitive schedule Status
Pages, 2-56 ECO
Reports revised item, 2-31
ECO Approval List, 4-1 Substitute Components
Engineering Change Order Detail, 4-1 Assigning or Deleting Substitute Components,
Engineering Change Order Priorities, 4-4 2-42
Engineering Change Order Reasons, 4-4
Engineering Change Order Schedule, 4-4 T
Engineering Change Order Types, 4-7
Transfer, 3-5
Revised
bill, 3-7
components
ECO, 2-44
defining, 2-39
item, 3-7
item
routing, 3-7
implement ECO, 2-51
Transferring Engineering Items, Bills, and
items
Routings, 3-6
cancelling, 2-53
Types
rescheduling ECO, 2-27
ECO, 2-5, 3-4
viewing on ECO, 2-54
of bills of material, 3-3
operations, 2-35
resources, 2-4, 2-37
U
routing, 2-34
Revision User profile options
ECO, 2-4, 2-29 ECO, 3-4
User Profile Options
S ECO, 2-5
Use up
Selection
ECO's, 2-54
of alternates to transfer
Use-up date, 2-27
of alternate to transfer, 3-7
Sequence
V
ECO approval, 1-13
Setup View
approval lists, 1-4 item revisions, 2-34
AutoImplement manager, 1-5 routing revisions, 2-34
autonumbering, 1-4
change order type, 1-4 W
checklist, 1-2 Workflow
employees, 1-4 abort approval process, C-2
flowchart, 1-2 approval status, 2-22
material dispositions, 1-5 ECO
overview, 1-1 approval status, 2-25
prerequisites, 1-3 ECO approval, 2-22
priority, 1-5 ECO approval list, 1-12
reason, 1-5 ECO definition, 2-22
steps, 1-3 ECO priorities, 1-10
Shipping details, 2-42 ECO status, 2-27
Special menu, C-1 ECO types, 1-6
Index-4
process
Workflow process, 1-8
revised item effectivity, 2-51
revised item status, 2-31
Y
Yield, 2-41
Index-5