Search Results display_plan_level




Overview
Explore in AI Chat

Overview

BOM_EXPLOSION_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the BOM (Bills of Material) product family. Its documented purpose is to present an indented bill of material for reporting. In other words, the view flattens the hierarchical, multi-level structure of a manufactured assembly into a single denormalized row set, where each row represents one component occurrence at a specific level of the indented explosion. This makes the view suitable for report generation, cost rollup analysis, and integration extracts that must traverse an entire product structure without issuing recursive queries against the base bill of material tables.

The view is valid in the 12.1.1 and 12.2.2 releases and is defined in the APPS schema, which is the standard convention for EBS reporting objects. Because it consolidates parent assembly context, component detail, planning attributes, costing attributes, and item master descriptive attributes into one projection, it functions as a convenience layer for developers and report authors who would otherwise need to join BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS, and MTL_SYSTEM_ITEMS manually.

Underlying Base Objects

The documented view text references several underlying objects. The central source is BOM_EXPLOSION_TEMP, a temporary staging table that holds the pre-computed explosion rows (aliased BET), including level, quantity, and sequence identifiers. BOM_STRUCTURES_B (aliased BOM) supplies the parent bill header context, including ASSEMBLY_ITEM_ID and the alternate designator. BOM_INVENTORY_COMPONENTS (aliased BIC) and MTL_SYSTEM_ITEMS (aliased MSI) provide component and item master attributes respectively. FND_COMMON_LOOKUPS is joined for decoded lookup meanings such as BASIS_TYPE and SO_BASIS. The ETRM metadata lists the referenced base objects as BOM_EXPLOSION_TEMP, BOM_STRUCTURES_B, MFG_LOOKUPS, and MTL_ITEM_FLEXFIELDS, which are accessed through synonyms and views in the APPS schema. The view text additionally embeds explicit INDEX hints against BOM_EXPLOSION_TEMP_N3, BOM_INVENTORY_COMPONENTS_U2, BOM_BILL_OF_MATERIALS_U2, MTL_SYSTEM_ITEMS_U1, and FND_COMMON_LOOKUPS_U1, indicating that performance was tuned for large explosions.

Key Columns

The columns most relevant to consumers include:

Common Use Cases and Queries

Typical scenarios include reporting a full indented structure for a top assembly, analyzing extended quantities and extended costs at each level, and extracting component supply attributes for planning integrations. A common pattern filters on a specific parent assembly using the column the user searched for, PARENT_ITEM_ID:

  • SELECT plan_level, component_item_id, item_num, component_quantity, extended_quantity FROM apps.bom_explosion_view WHERE parent_item_id = :assembly_item_id ORDER BY top_bill_sequence_id, plan_level, sort_order;
  • SELECT item_num, description, item_cost, extended_cost FROM apps.bom_explosion_view WHERE top_item_id = :top_assembly ORDER BY plan_level;
  • SELECT component_item_id, SUM(extended_quantity) FROM apps.bom_explosion_view WHERE organization_id = :org_id GROUP BY component_item_id;

Because the view depends on the temporary explosion table, its contents are meaningful only after the BOM explosion program has populated that table for the relevant top bill and organization. Consumers should filter by TOP_BILL_SEQUENCE_ID or TOP_ITEM_ID and by ORGANIZATION_ID to scope results correctly.