Search Results bill of materials




The CST_EXPLOSION_TEMP table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical temporary table used by the Cost Management module to store intermediate data during the bill of materials (BOM) explosion process. This table plays a pivotal role in cost rollup calculations, standard cost updates, and inventory valuation processes. Below is a detailed analysis of its structure, purpose, and operational context.

Purpose and Functional Context

The CST_EXPLOSION_TEMP table acts as a staging area for BOM explosion data during cost processing. When Oracle EBS performs cost rollups or standard cost updates, the system recursively explodes BOM structures to calculate component costs at each level. This table temporarily stores exploded component details, including item IDs, quantities, cost elements, and hierarchical relationships, before final cost calculations are persisted in permanent tables like CST_ITEM_COSTS or CST_ITEM_COST_DETAILS.

Key Columns and Data Structure

The table's structure typically includes the following columns:

  • EXPLOSION_ID: A unique identifier for each BOM explosion session.
  • INVENTORY_ITEM_ID: References the item being costed.
  • ORGANIZATION_ID: Identifies the inventory organization.
  • LEVEL_NUM: Indicates the BOM hierarchy level (0 for top-level assemblies).
  • COMPONENT_ITEM_ID: Stores child components in multi-level BOMs.
  • EXTENDED_QUANTITY: Cumulative quantity after accounting for usage rates.
  • COST_ELEMENT_ID: Breakdown of material, resource, overhead, etc.
  • PROCESS_FLAG: Controls workflow steps (e.g., 'Y' for processed records).

Operational Workflow

During cost processing, the following steps involve CST_EXPLOSION_TEMP:

  1. Initialization: The table is truncated at the start of a new explosion.
  2. Recursive Explosion: The BOM processor populates the table with component data level by level.
  3. Cost Rollup: The system aggregates costs using the exploded structure.
  4. Cleanup: Processed records are purged or flagged upon completion.

Performance Considerations

In large-scale implementations, proper indexing on EXPLOSION_ID and INVENTORY_ITEM_ID is critical. Partitioning may be employed for high-volume environments. Concurrent manager jobs like "Cost Update" and "Cost Rollup" heavily utilize this table, making its optimization essential for batch processing efficiency.

Integration Points

The table interacts with:

  • BOM_BILL_OF_MATERIALS: Sources component relationships.
  • CST_ITEM_COSTS: Receives final cost data post-explosion.
  • MTL_SYSTEM_ITEMS_B: Validates item attributes.

Version-Specific Notes

Between 12.1.1 and 12.2.2, the table structure remains largely consistent, though 12.2.2 may include additional columns for enhanced cost granularity. The introduction of Online Patching in 12.2.2 affects how temporary tables are handled during patching cycles.

Customization Risks

Modifications to this table are strongly discouraged as it's core to cost processing logic. Custom reports querying this table should account for its transient nature—data exists only during active cost sessions.

In summary, CST_EXPLOSION_TEMP serves as the computational backbone for BOM-based cost calculations in Oracle EBS, bridging hierarchical component relationships with financial valuation processes while maintaining transactional integrity through its temporary design.