Search Results operation_offset




Overview
Explore in AI Chat

Overview

APPS.BOM_PLM_EXPLOSION_TEMP is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the flattened output of the bill of materials (BOM) explosion process. The view is owned by the APPS schema and is defined as a SELECT over the intermediate explosion workspace, returning the multi-level hierarchy of assemblies, components, and their associated attributes. It is principally used by Oracle Product Lifecycle Management (PLM), engineering, and planning modules that require a denormalized view of exploded BOM structures without traversing the recursive BOM_EXPLOSIONS hierarchy at runtime.

The view carries a large number of columns that correspond directly to the columns of the underlying explosion temporary table, including quantity, yield, effectivity, alternate designators, and rollup indicators. It is not a transactional base table; rather, it is a queryable representation of the explosion result set, populated by the BOM explosion engine for consumption by downstream reporting, concurrent programs, and integration interfaces.

Underlying Base Objects

The view is defined over a single referenced base object: BOM_EXPLOSION_TEMP (referenced through a synonym). BOM_EXPLOSION_TEMP is the temporary staging structure into which the BOM explosion program writes the resolved hierarchy of parent and component relationships. Every column present in BOM_PLM_EXPLOSION_TEMP is projected directly from BOM_EXPLOSION_TEMP, so the view does not, by itself, join additional tables or apply transformation logic beyond the column projection. Because the underlying object is a temporary/workspace table, the contents of the view are typically meaningful only for the session or process that performed the explosion, and persistent reads should be scoped to a specific GROUP_ID or TOP_BILL_SEQUENCE_ID to isolate one explosion run from another.

Key Columns

Common Use Cases and Queries

The view supports multi-level BOM reporting, where-used-style structure listings, cost and quantity rollup validation, and data extraction for PLM or integration feeds. A typical query filters by the explosion group and top bill to retrieve a single exploded structure:

SELECT TOP_ITEM_ID, COMPONENT_ITEM_ID, PLAN_LEVEL, COMPONENT_QUANTITY,
       EXTENDED_QUANTITY, INCLUDE_IN_ROLLUP_FLAG, LOOP_FLAG
  FROM APPS.BOM_PLM_EXPLOSION_TEMP
 WHERE GROUP_ID = :p_group_id
   AND TOP_BILL_SEQUENCE_ID = :p_top_bill_seq
 ORDER BY SORT_ORDER;

For rollup-focused analysis, analysts filter on INCLUDE_IN_ROLLUP_FLAG to restrict results to components that contribute to rolled-up quantities:

SELECT COMPONENT_ITEM_ID, EXTENDED_QUANTITY
  FROM APPS.BOM_PLM_EXPLOSION_TEMP
 WHERE INCLUDE_IN_ROLLUP_FLAG = 1
   AND GROUP_ID = :p_group_id;

Because the underlying storage is a temporary workspace, consumers should always constrain the query by GROUP_ID or the relevant sequence identifiers and should not assume that records persist beyond the explosion process that populated them.