Search Results eng_new_item_req_util




Overview
Explore in AI Chat

Overview

ENG_NEW_ITEM_REQ_UTIL is an Oracle Engineering (ENG) utility package in the APPS schema that encapsulates the creation of New Item Requests (NIRs) within Oracle E-Business Suite. A New Item Request is the engineering change management mechanism by which a user proposes a new item for entry into the item master, routing the request through the engineering change order (ECO) approval workflow before the item is finally created and released. This package isolates the complex sequence of operations required to instantiate such a request — generating or validating the change order header, associating the requested item and organization, and staging data for downstream processing through the item open interface.

The package is classified as a UTIL API in the ETRM registry and is documented against Oracle EBS 12.1.1 and 12.2.2. Its presence as a companion utility to the Engineering Change Order public APIs reflects Oracle's R12-era architecture, where the Create New Item Request flow was extended to support the Item Open Interface.

Key Procedures and Functions

The package body exposes three documented entry points: CREATE_NEW_ITEM_REQUEST and CREATE_NEW_ITEM_REQUESTS. These are overloaded/procedural variants that perform the same essential business task — programmatically creating one or more New Item Requests — differing in their calling signature and return payload.

  • CREATE_NEW_ITEM_REQUEST (first variant) — The original interface. It accepts a change number, change name, change type code, item number, organization code, and requestor user name, along with an optional batch identifier, and returns only a status indicator. Internally it delegates to the second variant, discarding the generated change identifier.
  • CREATE_NEW_ITEM_REQUEST (second variant, added in R12) — The extended implementation. It returns both a status and the newly created engineering change identifier (x_change_id). This identifier is significant because the Item API writes the returned NIR change ID into the Item Open Interface table, enabling downstream item creation. It declares local records and tables based on the public ENG_ECO_PUB and BOM_BO_PUB types (Eco_Rec_Type, Eco_Revision_Tbl_Type, Revised_Item_Tbl_Type) to drive the engineering change engine and revision logic.
  • CREATE_NEW_ITEM_REQUESTS — The plural form, used to process multiple new item requests in a single invocation, typically for batch or bulk creation scenarios.

Tables Accessed

The package operates across the engineering change, item, and interface schemas through APPS synonyms:

Usage Notes

ENG_NEW_ITEM_REQ_UTIL is invoked programmatically rather than from a standalone form. It is the underlying engine called by the New Item Request form path and by other engineering packages; the ETRM registry records it as referenced by one other package. Custom developers use CREATE_NEW_ITEM_REQUEST in integration code — PL/SQL scripts, concurrent program wrappers, or interfaces — to raise NIRs automatically from external systems. In R12, callers should prefer the extended variant when the generated change ID is needed to correlate the request with the row staged in MTL_SYSTEM_ITEMS_INTERFACE. Because the package delegates to the ENG_ECO_PUB public APIs, standard validation and error-message handling apply, and callers must inspect x_return_status on completion.