Search Results bom_lists_s




Overview
Explore in AI Chat

Overview

APPS.BOM_BOMRBOMS_XMLP_PKG is the package body that implements the Oracle EBS Bill of Materials explosion and "where-used" reporting engine published as an Oracle XML Publisher (BI Publisher) concurrent program. In Oracle EBS 12.1.1 and 12.2.2 the package encapsulates the data extraction, formatting, and user-exit logic required to produce the BOM Bill of Materials Report (BOMRBOMS). It resolves organization hierarchy context, item descriptions, revisions, and component attributes, then hands a structured result set to the XML Publisher template layer for rendering.

The user search term "bom_lists_s" corresponds to the BOM_LISTS_S sequence referenced by this package. That sequence supplies surrogate primary keys for the BOM_LISTS table, and it is used inside the explosion logic to materialize temporary or derived list structures while the report is executing.

Key Procedures and Functions

The package exposes nineteen documented program units, organized into four functional groups:

Tables Accessed

The package reads from the following APPS-synonym tables:

  • BOM_LISTS and BOM_LISTS_S: the bill of materials list headers and the associated sequence used to generate list identifiers during explosion.
  • MTL_SYSTEM_ITEMS_TL, MTL_ITEM_REVISIONS, MTL_DESCRIPTIVE_ELEMENTS: item descriptions, revision data, and descriptive element values.
  • MTL_CATEGORY_SETS: category set definitions used when category-based selective explosion is requested.
  • MTL_PARAMETERS: organization-level defaults such as the default category set and supply type behavior.
  • DBMS_SQL, DUAL, PLITBLM: dynamic SQL support, dual-row dummy queries, and the PL/SQL table-of-varchar2 type used to hold in-memory result collections.

Usage Notes

BOM_BOMRBOMS_XMLP_PKG is not referenced by any other database object, confirming it is an entry-point package rather than a shared utility. It is normally invoked by the BOM Bill of Materials Report concurrent program through the XML Publisher engine, which calls BEFOREREPORT, executes EXPLOSION_REPORT (with EXPLODER_USEREXIT as the user exit hook), and then invokes AFTERREPORT. The formula functions are referenced from the RTF or eText template so that raw flag columns are rendered as descriptive text. Because it depends on FND_GLOBAL, FND_PROFILE, FND_MESSAGE, and INV_ORGHIERARCHY_PVT, callers must run it in a properly initialized EBS session with a valid responsibility and organization context. Custom code should not call the procedures directly; the supported integration point is the concurrent program and its XML Publisher template.