Results for “change_order”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.ENG_CANCEL_ECO is the Oracle Engineering change management PL/SQL package responsible for cancelling an Engineering Change Order (ECO) and reversing its un-released engineering change activity in Oracle E-Business Suite 12.1.1 and 12.2.2. Within the ETRM (E-Business Suite Technical Reference Manual) it is classified as an OTHER API under the APPS schema, meaning it is an internal support package rather than a formally published public interface. Its central purpose is to unwind the effects of a change order by cancelling the revised items, components, and operations linked to the ECO, restoring engineering bills of material and routings to their prior state, and removing pending structures that were staged but never released. The package header comment dates to 2008 (ENGCNCLB.pls 120.4.12010000.2), and the code contains bug fixes such as Bug 3668603 relating to routing sequence cleanup after cancellation. In the 12.2.2 ETRM, the package is documented with six procedures and is referenced by two other packages, confirming its role as a shared utility invoked by higher-level engineering and change management flows.
Key Procedures and Functions
The documented procedures are CANCEL_ECO, CANCEL_REVISED_ITEM, CANCEL_REVISED_COMPONENT, CHANGE_ATT_STATUS, DELETE_REVISED_ITEM, and DELETE_PENDING_STRUCTURE. CANCEL_ECO is the top-level entry point; it accepts the organization, change order name, user, and login context and orchestrates the full cancellation of an ECO by driving the subordinate procedures. CANCEL_REVISED_ITEM processes the individual revised items attached to the ECO, reversing the engineering revisions introduced by the change. CANCEL_REVISED_COMPONENT reverses revised component assignments on the affected bills of material. CHANGE_ATT_STATUS updates the status of attachments associated with the change, reconciling the ENG_ATTACHMENT_CHANGES records during cancellation. DELETE_REVISED_ITEM and DELETE_PENDING_STRUCTURE perform the physical removal of revised item rows and pending (unreleased) structure records. Notably, CANCEL_ECO deliberately excludes revised items already in certain terminal statuses (status_type not in 5 and 6), and its internal cursor logic distinguishes cancelled routing sequences from those still referenced by pending ECOs.
Tables Accessed
The package operates across the engineering and manufacturing schema. Core change records are held in ENG_ENGINEERING_CHANGES (looked up by organization_id and change_notice) and ENG_REVISED_ITEMS, which is queried and updated to identify affected change lines. Related revised objects are touched through ENG_REVISED_COMPONENTS and ENG_REVISED_OPERATIONS. Attachment status is maintained in ENG_ATTACHMENT_CHANGES. Bill of material and routing structures are read and restored via BOM_STRUCTURES_B, BOM_COMPONENTS_B, BOM_SUBSTITUTE_COMPONENTS, BOM_OPERATION_SEQUENCES, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_RESOURCES, BOM_SUB_OPERATION_RESOURCES, and BOM_REFERENCE_DESIGNATORS. Item revision context is resolved through EGO_MTL_SY_ITEMS_EXT_B and EGO_MTL_SY_ITEMS_EXT_TL. The routing cursor c_cancelled_RI and the check cursor c_check_rtg_header_del illustrate the defensive logic that clears orphaned operational routing headers only when no other pending ECO references them.
Usage Notes
ENG_CANCEL_ECO is not a public user API and should not be called directly from custom code without careful validation. It is normally invoked indirectly through the Oracle Engineering or Bills of Material forms and change management concurrent programs when a user cancels an ECO that has not yet been released. Because cancellation permanently reverses revised items, components, and routing structures, it should be treated as a high-impact operation limited to unreleased or partially processed change orders. Integrations that must cancel ECOS through interfaces should follow the sanctioned engineering change APIs rather than calling this internal package, since its procedure signatures (CANCEL_ECO takes org_id, change_order, user_id, and login) are undocumented and subject to change between point releases. Its presence in the ETRM referenced-by list confirms it is a supporting utility within the broader Oracle Engineering change management framework.
-
PACKAGE: APPS.ENG_CANCEL_ECO 12.2.2
-
PACKAGE: APPS.ENG_CANCEL_ECO 12.1.1
-
PACKAGE: APPS.ENG_CANCEL_ECO 12.1.1
-
PACKAGE: APPS.ENG_CANCEL_ECO 12.2.2
-
Lookup Type: PO_DRAFT_TYPE 12.2.2
Draft type
-
Setup page change process type lookup type
-
Control item type classes
-
Control item type classes
-
PACKAGE: APPS.BOMPKMUD 12.1.1
-
PACKAGE: APPS.BOMPKMUD 12.2.2
-
APPS.BOMPKMUD SQL Statements 12.1.1
-
PACKAGE BODY: APPS.BOMPKMUD 12.2.2
-
APPS.BOMPKMUD SQL Statements 12.2.2
-
PACKAGE BODY: APPS.BOMPKMUD 12.1.1
-
PACKAGE BODY: APPS.BOMPKMUD 12.2.2
-
PACKAGE BODY: APPS.BOMPKMUD 12.1.1