Search Results bom_explosions




Overview
Explore in AI Chat

Overview

BOM_EXPLOSIONS is a table owned by the BOM schema within the Oracle E-Business Suite Bills of Material module. Its documented purpose is to store pre-exploded model bills of material for use by Order Entry. Rather than recursively exploding a configured or model bill at order-entry time, Oracle Order Management and related modules consult the rows maintained in BOM_EXPLOSIONS to obtain a flattened, already-resolved representation of the assembly structure, including quantities, planning factors, and order-entry control flags at each level.

In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID and exposes a documented physical schema of 95 columns in the ETRM 12.2.2 metadata. The heuristic Data Vault classification mined from the foreign-key structure identifies this object as a link. As a modeling suggestion, BOM_EXPLOSIONS behaves as a relationship entity connecting a top-level assembly and its components — both of which resolve to inventory items — within a specific organization and explosion context. It is not a descriptive master (hub) nor a purely descriptive attribute store (satellite); its identity and grain are defined by the associations it records between items and between bill sequences.

Key Information Stored

The grain of the table is an exploded component occurrence within a top-level model bill. The most significant columns include:

The documented unique index BOM_EXPLOSIONS_U1 spans TOP_BILL_SEQUENCE_ID, EXPLOSION_TYPE, and SORT_ORDER, identifying the business-key candidate for a row. The table does not expose a documented single-column surrogate primary key in the metadata; the linkage is expressed through the composite business key and the item/bill sequence columns.

Common Use Cases and Queries

The principal use case is determining, without recursive explosion, which components belong to a configurable or model assembly and under what order-entry rules. Reporting scenarios include component availability analysis, order-line sourcing, and structured bill validation.

A typical query joins to the item master through both foreign keys to resolve descriptions and item numbers:

  • Selecting exploded components for a given top item and organization: filter on TOP_ITEM_ID and ORGANIZATION_ID, and order by PLAN_LEVEL and SORT_ORDER to reproduce indented structure.
  • Joining MTL_SYSTEM_ITEMS_B twice — once on TOP_ITEM_ID and once on COMPONENT_ITEM_ID, each alongside ORGANIZATION_ID — to obtain top and component item attributes.
  • Identifying optional or mutually exclusive components through the OPTIONAL and MUTUALLY_EXCLUSIVE_OPTIONS flags for order configuration validation.
  • Checking effectivity with EFFECTIVITY_DATE and DISABLE_DATE to report currently valid exploded components.

Related Objects

The dominant relationship is to the item master. The documented foreign keys establish two references from BOM_EXPLOSIONS to MTL_SYSTEM_ITEMS_B, joined on the combination of item identifier and ORGANIZATION_ID:

  • MTL_SYSTEM_ITEMS_B – joined via TOP_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • MTL_SYSTEM_ITEMS_B – joined again via COMPONENT_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • BOM_BILL_OF_MATERIALS and BOM_COMPONENTS_B – source structures from which explosions are derived, referenced through the bill and component sequence columns.
  • BOM_STRUCTURES_B – the recursive bill structure against which explosion levels and sort order correspond.
  • OE_ORDER_LINES_ALL – the Order Entry consumer that reads pre-exploded model bills during order capture.
  • MTL_SYSTEM_ITEMS_TL – joined for translated item descriptions in multilingual reporting.

Together these relationships confirm BOM_EXPLOSIONS as a link entity at the intersection of items, bills, and order-entry processing within the BOM and Order Management domains.