Search Results implement_revised_item

Overview

ENGPKIMP is an Oracle EBS Engineering (ENG) module PL/SQL package owned by the APPS schema. Its principal business function is to implement revised items defined on an Engineering Change Order (ECO) and to propagate the resulting engineering changes into Oracle Work in Process and Bills of Material. The package is declared with AUTHID CURRENT_USER and exposes the constants yes (1) and no (2), together with several PL/SQL collection types (StringArray, NameArray, BooleanArray, and record/table types such as Rev_op_disable_date_Rec_Type and Rev_Comp_Disable_Date_Rec_Type) that support the disassembly of effective dates for revisions, operations, and components.

The package is called primarily from the enlimp C program, which orchestrates ECO implementation and performs the re-explosion of bills of material against in-progress work orders. It is classified in ETRM as an OTHER-type API rather than a formal public API. The header identifies the source as ENGEIMPS.pls, version 120.7.

Key Procedures and Functions

The documented callable units are:

• IMPLEMENT_REVISED_ITEM — Implements a single revised item defined on an Engineering Change Order. It accepts the revised item sequence identifier, WHO audit values, and a trial-mode flag; in trial mode all possible errors are returned, while in normal mode processing aborts on the first error. It returns an "update WIP" flag, a new item revision high date for the Update WIP routine, the bill sequence identifier, and an array of translated error messages.
• IMPLEMENT_ECO_WO_REVISED_ITEM — Implements the ECO/work-order variant of the revised item operation, handling ECO changes that are tied to work-order context.
• REVERSE_STANDARD_BOM — Reverses a standard bill of material, supporting undo/rollback semantics during ECO processing.
• GENERATE_NEW_WIP_NAME — Produces a new WIP entity name, used when ECO implementation requires the creation or renaming of work-in-process jobs.
• LOG_IMPLEMENT_FAILURE — Records implementation failures encountered during ECO processing. This is the routine referenced by the ETRM search term log_implement_failure. Its purpose is to capture diagnostic information so that failed implementations can be reviewed and remediated.
• UPDATE_BSB_REQUEST_ID_COLUMN — Updates the request identifier column associated with the bill/substitute/BSB structures, tying the implementation to a specific concurrent request.

Seven procedures/functions are documented in total; the remaining entry is a supporting unit within the same package.

Tables Accessed

The package reads and writes through APPS synonyms across engineering, bills of material, and WIP tables:

• ENG_REVISED_ITEMS — source of the revised items being implemented.
• MTL_ITEM_REVISIONS and MTL_RTG_ITEM_REVISIONS — creation and update of item and routing revisions.
• BOM_STRUCTURES_B, BOM_COMPONENTS_B, BOM_SUBSTITUTE_COMPONENTS, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_OPERATION_RESOURCES, BOM_SUB_OPERATION_RESOURCES, BOM_REFERENCE_DESIGNATORS, BOM_DELETE_ENTITIES, BOM_PARAMETERS — construction, modification, and reversal of bill and routing structures.
• WIP_ENTITIES and WIP_JOB_SCHEDULE_INTERFACE — re-explosion and update of WIP jobs.

These tables exist because implementing an ECO often requires simultaneously revising the item revision, the bill structure, the routing, and any affected work orders.

Usage Notes

ENGPKIMP is normally invoked indirectly: the enlimp C program calls IMPLEMENT_REVISED_ITEM as part of the ECO implementation flow, and the same program updates WIP with the re-exploded bill of material when the update_wip parameter is "yes". It is referenced by one other package. Because it is classified as OTHER rather than a certified public API, custom code should invoke it with care, always running in trial mode first to surface all errors before committing. The LOG_IMPLEMENT_FAILURE routine provides the diagnostic trail when implementation cannot complete.