Search Results bom_implosion_temp




Overview
Explore in AI Chat

Overview

BOM.BOM_IMPLOSION_TEMP is a transient staging table owned by the Bills of Material (BOM) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to hold temporary data generated during item usage analysis, specifically for the Item Where Used Report. When a user launches this report, the BOM engine performs an implosion — walking upward through the bill of material structure from a given component to identify every parent assembly that consumes it. The intermediate and final results of that traversal are materialized in BOM_IMPLOSION_TEMP, where they can be sorted, filtered, and formatted for presentation.

Because the table is populated and consumed within a single report request, it is not a master or transactional entity. Records are written under a specific concurrent REQUEST_ID and are typically purged or overwritten on subsequent runs. This behavior makes the table a candidate for a satellite-leaning classification under a heuristic Data Vault model: it records descriptive, context-dependent attributes about an implosion event rather than serving as a durable hub of business entities or a pure associative link. It carries foreign key references to upstream entities, but its rows are meaningful only within the lifecycle of one report execution.

Key Information Stored

The table contains 28 documented columns. The most significant include:

The surrogate key is SEQUENCE_ID. Business-key candidates are composite and contextual, centered on the combination of COMPONENT_SEQUENCE_ID, REVISED_ITEM_SEQUENCE_ID, ORGANIZATION_ID, and REQUEST_ID.

Common Use Cases and Queries

The primary use case is diagnostic and reporting: determining every parent assembly affected by a component change, failure, or obsolescence. Typical queries filter by REQUEST_ID to isolate a specific report run:

  • Where-used by component: SELECT PARENT_ITEM_ID, CURRENT_LEVEL, ALTERNATE_DESIGNATOR FROM BOM_IMPLOSION_TEMP WHERE LOWEST_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id ORDER BY SORT_CODE.
  • Multi-level hierarchy validation: join CURRENT_ITEM_ID and PARENT_ITEM_ID to MTL_SYSTEM_ITEMS_B to resolve item names and descriptions for display.
  • Impact analysis: filter on CHANGE_NOTICE or IMPLEMENTED_FLAG to identify assemblies affected by a pending ECO.
  • Alternate BOM comparison: group by ALTERNATE_DESIGNATOR to compare usage across alternates.

Related Objects

The table's FK metadata identifies two principal dependencies, and additional relationships follow from the implosion logic:

  • BOM_COMPONENTS_B — joined on COMPONENT_SEQUENCE_ID; the authoritative source of the component row being imploded.
  • ENG_REVISED_ITEMS — joined on REVISED_ITEM_SEQUENCE_ID; supplies revision context.
  • MTL_SYSTEM_ITEMS_B — resolves LOWEST_ITEM_ID, CURRENT_ITEM_ID, and PARENT_ITEM_ID to descriptive item data.
  • BOM_BILL_OF_MATERIALS and BOM_STRUCTURES_B — define the assembly structure traversed during implosion.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the report run that populated the staging rows.

Because the table is populated only during the Item Where Used report, direct DML by external interfaces is neither expected nor supported; integrations should read from BOM_COMPONENTS_B and the bill structures directly, or invoke the report and query the staging table within its execution window.