Results for “bom_lists_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOMPKMUD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the mass update of bill of material components within Oracle Bills of Material. The package coordinates the creation of engineering change orders for a set of revised items, driving the change directly from interface tables that are populated ahead of execution. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner, a convention that requires the caller to hold the necessary object privileges on the underlying BOM and Engineering tables.

The package header carries a copyright notice dated 1992 and a revision marker of 120.1 dated 2005/06/21, indicating its lineage as a long-standing component of the discrete manufacturing application family. In the Oracle EBS 12.1.1 and 12.2.2 releases, BOMPKMUD remains an internal package rather than a published, supported public API. Its original design intent, documented in the package header comments, was to be called by the C program BMCMUD, which handled user interaction and then delegated the database processing to this package.

Key Procedures and Functions

The documented package exposes a single procedure, MASS_UPDATE. Its purpose is to iterate over the items listed in the BOM_LISTS table and create change orders for each revised item, using selection criteria held in the engineering change and component interface tables. The procedure thereby performs the bulk of the mass update logic: it reads the pending changes, resolves the target structures and components, and writes the resulting change order and revised item records into the base Engineering tables. Consistent with the documented metadata, no parameter list is reproduced here.

The package also declares global constants and a record type. The constants yes and no are defined as numeric literals, with yes valued at 1 and no valued at 2. The record type ProgramInfoStruct groups profile option and runtime context values, including user id, concurrent request id, application id, program id, login id, and model, planning, and standard item access flags. These declarations support the access control behavior described in the procedure comments, where item access flags determine whether particular revisions are processed.

Tables Accessed

BOMPKMUD reads and writes a broad set of Bills of Material and Engineering tables. The interface tables BOM_INVENTORY_COMPS_INTERFACE, ENG_ENG_CHANGES_INTERFACE, and ENG_REVISED_ITEMS_INTERFACE supply the staged change criteria and component details. The BOM_LISTS table identifies the set of revised items to process. Base tables including BOM_COMPONENTS_B, BOM_STRUCTURES_B, BOM_STRUCTURE_TYPES_B, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_PARAMETERS, and BOM_REFERENCE_DESIGNATORS provide the current bill structure, routing, and reference designator data required to construct valid change orders. Engineering tables ENG_ENGINEERING_CHANGES and ENG_REVISED_ITEMS receive the generated change order headers and revised item lines. HR_ALL_ORGANIZATION_UNITS supplies organization context, and MTL_ITEM_LOCATIONS is referenced during component processing.

Usage Notes

Because its original caller was the BMCMUD C program, BOMPKMUD is normally invoked through the Oracle Bills of Material mass change user interface rather than by direct application code. In Oracle EBS 12.1.1 and 12.2.2, that interface continues to stage rows into the BOM and Engineering interface tables and then execute the mass update logic. The package is classified as OTHER in the documented API metadata, signifying that it is not part of Oracle's supported public API set. Custom code should therefore not call BOMPKMUD directly; any integration requirement should rely on the supported interface tables or the mass change functionality itself, since the package signature and internal behavior may change between releases without notice. No other packages reference BOMPKMUD, reinforcing its role as a terminal, internally invoked implementation unit.