Search Results inv_onhand

Overview

ENGPKIMP is the core PL/SQL package body in Oracle E-Business Suite that drives Engineering Change Order (ECO) implementation within Oracle Engineering. Its principal responsibility is to translate a scheduled ECO release into concrete manufacturing and inventory artifacts: revised item definitions, revised bills of material, revised routings, and — where the ECO is dispositioned to create new work in process — new WIP jobs. The package operates against the revised item model (ENG_REVISED_ITEMS) and applies approved changes to the production BOM and routing structures, generating WIP job schedule interface rows as required.

The package header history indicates a long lineage of maintenance spanning ERES (event-based) integration, 8i compliance, and bug fixes covering BOM and Routing event flags. Several named constants define lifecycle states — cancelled_status (5) and implemented_status (6) — and action codes derived from the ECG_ACTION domain (add, change, delete). The package also declares G_OrderEntry and internal tables for revised operation and component disable dates, together with a PLSQL_COMPILE_ERROR exception used to trap failures raised through dynamic SQL invocation.

Although the user search term was "inv_onhand," the ETRM metadata indicates that ENGPKIMP does not directly reference on-hand inventory tables. ECO implementation focuses on engineering and BOM/routing structures rather than on-hand balances. Where inventory interactions occur, they are mediated through WIP entities and the WIP job schedule interface, which the inventory and WIP modules subsequently process.

Key Procedures and Functions

The documented procedures within ENGPKIMP cover the full lifecycle of revised item implementation and cleanup:

• IMPLEMENT_REVISED_ITEM — The primary entry point that applies an approved revised item from ENG_REVISED_ITEMS, updating item revisions, BOM structures, and routing structures according to the ECO’s defined changes.
• REVERSE_STANDARD_BOM — Reverses or unwinds a standard BOM when an ECO implementation must be rolled back or replaced, restoring prior structure definitions.
• GENERATE_NEW_WIP_NAME — Generates a unique WIP job name for jobs created as a result of ECO disposition, feeding the WIP job schedule interface.
• IMPLEMENT_ECO_WO_REVISED_ITEM — Handles the work-order-specific path of revised item implementation, coordinating with WIP entities and job creation logic.
• LOG_IMPLEMENT_FAILURE — Records implementation failures for an ECO, capturing context including the revised item sequence identifier (added as a parameter in the 2004 lineage) to support troubleshooting and retry.
• UPDATE_BSB_REQUEST_ID_COLUMN — Updates the request identifier column associated with BOM structure/setback processing, linking asynchronous concurrent request output to the affected BOM records.

The header notes reference an internal event_acknowledgement local procedure used to acknowledge ERES events (copyToManufacturing, transferToManufacturing, billCreate/billUpdate, routingCreate/routingUpdate) in the event of errors, along with flags bERES_Flag_for_BOM and bERES_Flag_for_Routing added for specific bug fixes.

Tables Accessed

ENGPKIMP reads and writes the following documented tables through APPS synonyms:

• ENG_REVISED_ITEMS — The central ECO working table, holding the requested changes to be implemented or logged.
• MTL_ITEM_REVISIONS / MTL_RTG_ITEM_REVISIONS — Item and routing revision records that receive the implemented revision changes.
• BOM_STRUCTURES_B, BOM_COMPONENTS_B, BOM_SUBSTITUTE_COMPONENTS, BOM_REFERENCE_DESIGNATORS, BOM_DELETE_ENTITIES — Bill of material structure and component tables, including deletion tracking.
• BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_OPERATION_RESOURCES, BOM_SUB_OPERATION_RESOURCES — Routing and resource definitions updated by revised routing changes.
• BOM_PARAMETERS — System parameters controlling BOM processing behavior.
• WIP_ENTITIES, WIP_JOB_SCHEDULE_INTERFACE — WIP job and interface tables written when an ECO disposition creates or schedules new work orders.

Usage Notes

ENGPKIMP is invoked indirectly by the Oracle Engineering ECO implementation flow rather than by end users directly. Typical callers include the Engineering Change Order forms and associated concurrent programs that process approved ECOs, and the package is referenced by at least one other package in the ETRM inventory. It should be treated as an internal, non-public API: customizations that need to trigger ECO implementation are advised to use the supported ECO release mechanism or the documented Engineering public APIs rather than calling ENGPKIMP procedures directly. Because it writes WIP interface rows and BOM/routing structures, any direct invocation must respect open interface processing and BOM validation, and failures should be routed through LOG_IMPLEMENT_FAILURE to preserve auditability.