Search Results bom_explosions_u1

Overview

BOM.BOM_EXPLOSIONS is a permanent staging and reference table in the Oracle E-Business Suite Bills of Material module. It stores fully exploded bill of material structures for model and option-class items, materialized on a recurring basis so that Oracle Order Management can retrieve component, option, and configuration information without performing a recursive explosion at order entry time. Records are retained with all applicable effectivity dates bounded within configured limits, and each component row is tagged as Optional, Included, or Both, indicating whether the component is mandatory or selectable when a configured item is ordered.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, and its indexes are created in APPS_TS_TX_IDX. In Oracle EBS 12.1.1 and 12.2.2 the physical definition documents 95 columns with two foreign keys, from TOP_ITEM_ID and COMPONENT_ITEM_ID to MTL_SYSTEM_ITEMS_B. The heuristic Data Vault classification mined from the foreign key structure is link, suggesting this object behaves as an associative entity connecting the item master (as top-level model and as component) through the explosion event. It should not be treated as a classical hub; the unique key includes a non-identifying attribute (SORT_ORDER), and rows are regenerated rather than accumulated.

Key Information Stored

BOM_EXPLOSIONS_U1 is the unique index on the column combination TOP_BILL_SEQUENCE_ID, EXPLOSION_TYPE, and SORT_ORDER. TOP_BILL_SEQUENCE_ID is the closest analogue to a business key: it identifies the level-zero (top) bill being exploded. EXPLOSION_TYPE qualifies the row as OPTIONAL, INCLUDED, or ALL, and SORT_ORDER sequences components within the explosion so that configuration screens and pick logic present them deterministically. The remaining important columns are:

• BILL_SEQUENCE_ID — the parent bill of material identifier for the current level.
• ORGANIZATION_ID — the inventory organization in which the structure is valid.
• TOP_ITEM_ID and ASSEMBLY_ITEM_ID — the model item at the top of the explosion and the current parent assembly.
• COMPONENT_ITEM_ID and COMPONENT_SEQUENCE_ID — the component item and the bill line from which the row was exploded.
• PLAN_LEVEL — depth of the component in the indented bill.
• COMPONENT_QUANTITY and EXTENDED_QUANTITY — usage per assembly and quantity rolled up across levels.
• EFFECTIVITY_DATE, DISABLE_DATE, and IMPLEMENTATION_DATE — the effectivity window bounding the row.
• OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, and so-basis flags (SO_BASIS, CHECK_ATP, SHIPPING_ALLOWED, REQUIRED_TO_SHIP, REQUIRED_FOR_REVENUE) — order-management behavior for the component.
• COMP_COMMON_BILL_SEQ_ID, COMMON_BILL_SEQUENCE_ID, and SOURCE_BILL_SEQUENCE_ID — links back to the common bill structures used to build the explosion.
• REXPLODE_FLAG and EXPLODE_GROUP_ID — control and group markers used when an explosion is invalidated and rebuilt.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and the CONTEXT/ATTRIBUTE1–15 flexfield set are also present.

Common Use Cases and Queries

The primary use case is configuration validation during order entry: Oracle Order Management and Oracle Configurator read BOM_EXPLOSIONS to present optional components and to validate included ones. Supply chain and planning analysts also query it to report multi-level component usage without invoking BOM exploder APIs. A typical query retrieves all included components for a given top bill:

• SELECT component_item_id, plan_level, component_quantity, sort_order FROM bom.bom_explosions WHERE top_bill_sequence_id = :p_top_bill AND explosion_type = 'INCLUDED' AND TRUNC(SYSDATE) BETWEEN effectivity_date AND NVL(disable_date, TRUNC(SYSDATE)+1) ORDER BY sort_order;
• SELECT DISTINCT component_item_id, organization_id FROM bom.bom_explosions WHERE assembly_item_id = :p_item AND organization_id = :p_org; — the N11 index (ASSEMBLY_ITEM_ID, ORGANIZATION_ID, TOP_BILL_SEQUENCE_ID, IMPLEMENTATION_DATE, EFFECTIVITY_DATE, DISABLE_DATE, SORT_ORDER) supports this pattern.
• Re-explosion monitoring: SELECT top_bill_sequence_id, explode_group_id, COUNT(*) FROM bom.bom_explosions WHERE rexplode_flag = 'Y' GROUP BY top_bill_sequence_id, explode_group_id;

Because the table is periodically rebuilt, reports should be run against a stable snapshot or accept that values may change after the explosion program next executes.

Related Objects

• MTL_SYSTEM_ITEMS_B — joined via TOP_ITEM_ID and COMPONENT_ITEM_ID for item descriptions and attributes.
• BOM_BILL_OF_MATERIALS and BOM_COMPONENTS — the source structures from which explosions are generated.
• BOM_EXPLOSION_TEMP — the temporary working table used by the explosion process before permanent rows are written.
• BOM_STRUCTURES_B — parent assembly definitions referenced through BILL_SEQUENCE_ID.
• OE_ORDER_LINES_ALL — consumed by Order Management when validating configured model lines.
• MTL_SYSTEM_ITEMS_B / MTL_ITEM_REVISIONS — for revision and effectivity context.
• Public APIs including BOM_EXPLOSION_PUB and the BOM Exploder concurrent program, which populate this table.