Search Results bom_imploder_pub




Overview
Explore in AI Chat

Overview

APPS.BOM_IMPLODER_PUB is the public API package body that drives Bill of Materials (BOM) implosion — the multi-level, "where-used" traversal of a product structure from a component upward to its parent assemblies. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the package supports the Oracle Bills of Material and Oracle Engineering modules by resolving indented component relationships, applying exclusion and selection rules, enforcing organization and item security, and returning the flattened result set to the caller. Its designation as a PUB package indicates it is intended for external invocation by forms, concurrent programs, and customer extensions rather than being an internal-only implementation detail.

The body operates against the standard BOM base tables and temporary staging tables, and it depends on shared services such as BOM_SECURITY_PUB, EGO_DATA_SECURITY, INV_ORGHIERARCHY_PVT, FND_GLOBAL, FND_PROFILE, and FND_LOAD_UTIL. This dependency set confirms that implosion is executed under a validated application session and is subject to the same organization-access and data-security model that governs the rest of the BOM schema. The documented metadata records the body as VALID, and it is referenced by two other packages while itself referencing no other database object, positioning it as a terminal public entry point in the dependency chain.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions in this package body, including the following:

  • IMPLODER_USEREXIT — The primary implosion driver. It performs the recursive multi-level where-used expansion of a given assembly or component, applying user-defined criteria such as exclusion rules, structure types, and revision ranges, and populating the implosion staging tables with the resulting hierarchy.
  • IMPLOSION_CAD — Executes implosion for the CAD (Computer-Aided Design) integration path, returning indented BOM results in the format required by CAD and external engineering interfaces.
  • ML_IMPLODER_CAD — The multi-lingual counterpart to IMPLOSION_CAD, providing the same CAD-oriented implosion output while honoring the session language for item and component descriptions.
  • CHECK_USER_VIEW_PRIV — Validates that the current user holds the required view privilege for the structures being imploded, integrating with BOM_SECURITY_PUB and EGO_DATA_SECURITY to prevent unauthorized disclosure of BOM data.
  • CALCULATE_COMP_COUNT — Computes the count of components returned by an implosion, used to size result sets and to report summary quantities back to the caller.

The remaining documented routines follow the same pattern of rule evaluation, security checking, and result assembly. Because parameter signatures are not exposed in the metadata, callers should obtain the exact PL/SQL specification from the deployed package header before coding against these entry points.

Tables Accessed

The package reads and writes a defined set of BOM and inventory tables, all reached through APPS synonyms:

Usage Notes

BOM_IMPLODER_PUB is typically invoked from the Oracle Bills of Material "Where Used" and indented-implosion windows, from BOM-related concurrent programs, and from CAD/engineering integration routines that require flattened product structures. Custom code should call the public procedures only, invoking them after FND_GLOBAL initialization so that organization access and security checks resolve correctly. Callers should expect the implosion results to be materialized in the temporary staging tables rather than returned as a simple scalar result, and should clean up or re-query those tables after execution. Because the package relies on EGO_DATA_SECURITY and BOM_SECURITY_PUB, authorization failures surface through CHECK_USER_VIEW_PRIV rather than as raw SQL errors. The package is not referenced by any database object, so it is safe to treat as a stable public API surface.