Results for “bom_explosion_temp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_EXPLOSION_TEMP is a transient working table owned by the BOM schema within the Bills of Material module of Oracle E-Business Suite (documented against 12.1.1 and 12.2.2). Its documented purpose is to hold temporary data for indented bills of material generated by batch processes. When Oracle Bills of Material performs a multi-level explosion of an assembly — whether for the Indented Bill of Material report, a cost rollup, an ATP or pick-component computation, or an engineering change mass re-explosion — the flattened hierarchy is materialized row by row in this table rather than being computed entirely in memory. Each row therefore represents a single occurrence of a component within an exploded structure, carrying both the hierarchical position of that component and the descriptive, costing, planning, sourcing, and revision attributes inherited from the parent assembly and the component master.

Because the table is populated and consumed within the lifespan of a single concurrent request, it is not a system of record. Rows are keyed by the requesting concurrent program (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) and frequently by GROUP_ID or SESSION_ID, allowing concurrent or multi-request processing to remain isolated. In a Data Vault modeling sense, the heuristic classification for this object is link: it captures the association between a top-level bill structure (BOM_STRUCTURES_B) and the component definitions (BOM_COMPONENTS_B) that participate in an exploded hierarchy, rather than acting as a durable hub of business entities or a descriptive satellite.

Key Information Stored

Although the documented physical schema contains 196 columns, a small subset carries the structural and transactional meaning of each row:

• TOP_BILL_SEQUENCE_ID — foreign key to BOM_STRUCTURES_B identifying the assembly at the apex of the explosion.
• BILL_SEQUENCE_ID — foreign key to BOM_STRUCTURES_B identifying the bill from which the current row was exploded.
• COMPONENT_SEQUENCE_ID — foreign key to BOM_COMPONENTS_B identifying the component record on that bill.
• ORGANIZATION_ID — the inventory organization in which the structure is being exploded.
• TOP_ITEM_ID, TOP_ALTERNATE_DESIGNATOR — the top assembly and its alternate BOM designator (part of the composite key to BOM_STRUCTURES_B).
• COMPONENT_ITEM_ID, COMPONENT_QUANTITY, COMPONENT_YIELD_FACTOR — the component identity and per-assembly usage quantity/yield.
• PLAN_LEVEL, SORT_ORDER, PARENT_SORT_ORDER — the indentation depth and ordering that drive the indented report layout.
• EXTENDED_QUANTITY — the accumulated quantity of the component at that level of the explosion.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, GROUP_ID, SESSION_ID — the concurrency and grouping controls that scope a given explosion run.
• EFFECTIVITY_DATE, DISABLE_DATE, CHANGE_NOTICE, CURRENT_REVISION — the effectivity and revision context under which the row was generated.
• ITEM_COST, INCLUDE_IN_ROLLUP_FLAG, BASED_ON_ROLLUP_FLAG, ACTUAL_COST_TYPE_ID — costing attributes populated when the explosion supports a cost rollup.
• STRUCTURE_TYPE_ID — foreign key to BOM_STRUCTURE_TYPES_B identifying whether the exploded structure is a manufacturing or engineering bill.
• EXPLOSION_TYPE, EXPLODED_DATE, EXPLODED_UNIT_NUMBER, EXPLODED_END_ITEM_REV — the run characteristics and end-item context associated with the explosion.

No single surrogate primary key column is documented; the table is defined by its foreign-key relationships and by its request-scoped grouping columns, which serve as the practical de facto identifiers for a given explosion run.

Common Use Cases and Queries

The primary consumers of BOM_EXPLOSION_TEMP are the concurrent programs that populate it: the Indented Bill of Material report, the Bill of Material Comparison and Cost Rollup processes, and mass change / re-explosion utilities. A common diagnostic pattern is to correlate the table with the concurrent request that produced it:

• Inspect the exploded result for a specific run: SELECT * FROM BOM.BOM_EXPLOSION_TEMP WHERE REQUEST_ID = :request_id ORDER BY SORT_ORDER;
• Trace the hierarchy by level: SELECT PLAN_LEVEL, COMPONENT_ITEM_ID, EXTENDED_QUANTITY FROM BOM.BOM_EXPLOSION_TEMP WHERE TOP_BILL_SEQUENCE_ID = :top_id ORDER BY PLAN_LEVEL, SORT_ORDER;
• Join back to the source structure for descriptive validation: SELECT t.*, b.ASSEMBLY_ITEM_ID FROM BOM.BOM_EXPLOSION_TEMP t, BOM.BOM_STRUCTURES_B b WHERE t.BILL_SEQUENCE_ID = b.BILL_SEQUENCE_ID;

Because contents are ephemeral, reports and integrations should treat any query against this table as run-specific diagnostics rather than as a persistent data source.

Related Objects

• BOM_STRUCTURES_B — referenced through TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, TOP_ITEM_ID, ORGANIZATION_ID, and TOP_ALTERNATE_DESIGNATOR; the parent bill definitions being exploded.
• BOM_COMPONENTS_B — referenced through COMPONENT_SEQUENCE_ID; the component records underlying each exploded row.
• BOM_STRUCTURE_TYPES_B — referenced through STRUCTURE_TYPE_ID; defines manufacturing vs. engineering structure types.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to associate an explosion with its concurrent program run.
• MTL_SYSTEM_ITEMS_B — joined via COMPONENT_ITEM_ID, TOP_ITEM_ID, and ASSEMBLY_ITEM_ID for item descriptions and attributes.
• BOM_BILL_OF_MATERIALS and BOM_INVENTORY_COMPONENTS — the operational parent/child tables whose logic the explosion mirrors.
• CST_COST_ROLLUP_TEMP and related costing temporary tables — populated in parallel when the explosion feeds a cost rollup.