Search Results create_new_item_requests

Overview

The APPS.ENG_NEW_ITEM_REQ_UTIL package is a utility PL/SQL package within the Oracle E-Business Suite Engineering (ENG) module. Its principal business function is to automate the creation of new item requests (NIR) that are generated as a consequence of engineering change activity. When an engineering change order (ECO) introduces a new item, replaces an existing item, or otherwise requires that a new item be defined in the item master, the Engineering application must translate that requirement into structured records that the item-definition workflow can consume. ENG_NEW_ITEM_REQ_UTIL encapsulates that translation logic.

The package is classified as a UTIL (utility) API and is owned by the APPS schema. It is validated and present in both EBS 12.1.1 and 12.2.2. Its scope is deliberately narrow: it builds and persists new-item request records derived from engineering change data, thereby bridging the Engineering module and the inventory/item master data model.

Key Procedures and Functions

ETRM documents two procedures for this package:

• CREATE_NEW_ITEM_REQUEST — Creates a single new item request. This routine assembles one request record from the relevant engineering change context and writes it to the appropriate interface storage so that the new item can subsequently be defined and introduced into the item master.
• CREATE_NEW_ITEM_REQUESTS — Creates new item requests in bulk (plural). This is the set-based counterpart to the singular routine, intended for processing multiple qualifying change lines or affected items in a single invocation rather than one record at a time.

No parameter lists are reproduced here, consistent with the documented metadata. The two routines differ primarily in cardinality: one processes an individual request, the other processes a collection derived from the change context.

Tables Accessed

The package reads and writes a documented set of tables accessible through APPS synonyms. On the Engineering side it references ENG_ENGINEERING_CHANGES, ENG_CHANGE_LINES (and its _S and _TL variants), ENG_CHANGE_ORDER_TYPES (and _TL), ENG_AUTO_NUMBER_ECN, ENG_LIFECYCLE_STATUSES, ENG_SUBJECTS_B, and ENG_SUBJECT_ENTITIES. These supply the change order, affected line, subject/lifecycle, and numbering context required to determine what new item is needed.

On the inventory side it references MTL_SYSTEM_ITEMS_INTERFACE (the standard interface table used to stage item master records), MTL_ITEM_CATALOG_GROUPS_B, and MTL_PARAMETERS. It also uses FND_LANGUAGES for translation handling and PLITBLM for PL/SQL table-to-integer-table mappings. The central write target is MTL_SYSTEM_ITEMS_INTERFACE, which queues the new item for import into the item master.

Usage Notes

ENG_NEW_ITEM_REQ_UTIL is not a user-facing API; it is invoked internally by Engineering application logic and by at least one dependent package, INV_EGO_REVISION_VALIDATE. It is therefore typically triggered indirectly, when an ECO that requires new item creation is processed and the Engineering module must stage the corresponding request. Because it writes directly into the item interface, callers must ensure that a valid import concurrent program (such as the Item Import process) subsequently runs to promote the staged records into MTL_SYSTEM_ITEMS_B.

Customizations should invoke the package only in a controlled engineering-change context, respecting the parent transactions that supply the ECO and change-line identifiers. Direct calls outside that context risk orphaned interface records.