My Oracle Support Banner

How To Propagate An ECO Using An Organization Hierarchy ? (Doc ID 278533.1)

Last updated on FEBRUARY 22, 2023

Applies to:

Oracle Engineering - Version 11.5.9 and later
Information in this document applies to any platform.
FORM:ENGFDECN.FMB - Define engineering change order
FORM:PERWSDOH.FMB - Define Organization Hierarchy
EXECUTABLE:ENCACN - Engineering Change Order Implementation (AutoImplement Manager)
*This document includes all versions of Oracle E-Business Suite 11.5.9, 11i and Release 12*




Goal

Oracle Engineering provides a method to facilitate the creation of an Engineering Change Order (ECO) in multiple organizations by creating an ECO in
one organization and propagating it to other organizations. This can greatly reduce ECO creation and maintenance for large organizations.

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. ECOs will not be propagated to organizations in the hierarchy that are defined as "siblings" or "parents" but only to the
subordinate ("child") organizations.

Organization hierarchy creation is functionality provided by the Oracle Human Resources (HR) product and is available even when HR is installed in
shared mode. Refer to "Creating Organization Hierarchies, Using Oracle HRMS - The Fundamentals" in the Oracle HRMS User's Guide.

A hierarchy does not have to follow business lines and so can be defined in any manner required by your business. However, Engineering only
supports propagation to defined hierarchies where all associated organizations are in the same business group.

The following describes how to set up set up a hierarchy and perform the propagation of an ECO to subordinate organizations by way of example.

Note:  If using common bills, you are will not need to use an ECO to propagate adding / disabling components on common bills to the commoned organizations . The bill
can be updated only in the common org unless 'Enable attributes for update' is checked and you are updating the material control attributes alone on the component.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Step 1: Create the Hierarchy
 Step 2: Create the ECO and Propagate
 Step 3: Implement the ECOs
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.