Results for “mass_update”

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

Overview

APPS.BOMPKMUD is a PL/SQL package body in Oracle E-Business Suite that supports mass update processing for bills of material and engineering change data. The package encapsulates the business logic required to apply bulk modifications to component, structure, routing, and ECO (Engineering Change Order) records without requiring users to edit each record individually. It operates against the Oracle Bills of Material and Engineering foundation tables and provides a procedural interface for changes that would otherwise be performed manually through the Bills of Material forms.

The package name carries a "PK" infix consistent with Oracle's internal package naming conventions, where "MU" denotes mass update and "D" indicates the body. The package body declares a substantial set of named constants that map to Oracle lookup domains, including BOM_CO_ACTION values for add, change, delete, and replace, as well as bom_item_type designations for model, option class, planning, and standard items. Additional defaults cover approval status, operation sequence number, component quantity, yield factor, planning factor, cost rollup inclusion, ATP checking, and disposition. These constants document the intended semantic values used when mass updates are written to interface and base tables.

Key Procedures and Functions

The documented interface exposes a single program unit, MASS_UPDATE. This procedure orchestrates the mass update process by reading staged records from the Bills of Material interface tables, validating and transforming them, and writing the results into the corresponding base tables. It also carries responsibility for raising the ECO create event after an engineering change order is created, a behavior noted in the package history where the Raise_ECO_Create_Event procedure was added. The history further records that ERES calls were made 8i compliant and that a performance fix was applied in May 2006. No additional documented procedures or functions are exposed through the ETRM classification, and the package is not referenced by any other packages, indicating it is an entry-point module rather than a shared utility library.

Tables Accessed

BOMPKMUD reads and writes a defined set of Bills of Material, Engineering, and reference tables through APPS synonyms. On the BOM side, it works with BOM_COMPONENTS_B, BOM_INVENTORY_COMPS_INTERFACE, BOM_LISTS, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_PARAMETERS, BOM_REFERENCE_DESIGNATORS, BOM_STRUCTURES_B, and BOM_STRUCTURE_TYPES_B. These support component additions and changes, routing and operation sequence maintenance, reference designator assignment, structure definition, and retrieval of BOM parameters. The interface table BOM_INVENTORY_COMPS_INTERFACE serves as the staging area from which mass changes are consumed.

On the Engineering side, the package accesses ENG_ENGINEERING_CHANGES, ENG_ENG_CHANGES_INTERFACE, ENG_REVISED_ITEMS, and ENG_REVISED_ITEMS_INTERFACE to create and apply engineering change orders and revised item records. HR_ALL_ORGANIZATION_UNITS supplies organization validation, while MTL_ITEM_LOCATIONS provides inventory location references. The combination of interface and base tables confirms that the package follows the standard Oracle interface-table pattern of staging, validating, and applying changes.

Usage Notes

BOMPKMUD is typically invoked from the Bills of Material mass update concurrent program or from the mass update forms within the Oracle Manufacturing application. Because the package is not referenced by any other package, it is not intended as a general-purpose API for custom code; integrators requiring component or ECO changes should generally use the documented public APIs such as BOMPKIMP or the ECO interface instead. In Oracle EBS 12.1.1 and 12.2.2, the package remains part of the core BOM and Engineering foundation, and its constants and interface logic remain compatible across both releases. Customizations that call MASS_UPDATE directly should account for the interface tables being populated beforehand and for the ECO create event being raised as a side effect of the update.