Search Results based_on_rollup_flag




Overview
Explore in AI Chat

Overview

BOM_CONSOLIDATE_EXPLOSION_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing within the Bills of Material (BOM) product family. It is documented as a "Consolidated Bill of Material structure for report," meaning its purpose is to present Bill of Material explosion data in an aggregated form suitable for reporting rather than for transactional processing. The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2, and its definition is stable across these releases, which simplifies upgrade and support considerations.

Rather than persisting its own data, the view reads from an interim working table, BOM_EXPLOSION_TEMP, and applies a GROUP BY aggregation to collapse multiple rows representing the same component into a single summarized row. This aggregation produces a consolidated picture of a BOM structure — a useful basis for roll-up reports, cost summarization, and structure analysis. Because the underlying table is a temporary staging object, the view is designed to be used in the context of a BOM explosion process that first populates BOM_EXPLOSION_TEMP.

Underlying Base Objects

The only documented referenced base object is BOM_EXPLOSION_TEMP, listed in the ETRM metadata as a SYNONYM in the APPS schema. The view's SQL confirms this relationship: it selects from BOM_EXPLOSION_TEMP and aggregates by GROUP_ID, TOP_BILL_SEQUENCE_ID, TOP_ITEM_ID, ORGANIZATION_ID, COMPONENT_ITEM_ID, ITEM_COST, WIP_SUPPLY_TYPE, BASED_ON_ROLLUP_FLAG, ACTUAL_COST_TYPE_ID, SHRINKAGE_RATE, INVENTORY_ASSET_FLAG, and EXTEND_COST_FLAG.

The aggregation collapses duplicate component rows using MAX(SORT_ORDER) and SUM(EXTENDED_QUANTITY). Several positional output columns are returned as TO_NUMBER(NULL) placeholders, indicating that the view deliberately suppresses certain fields in its consolidated output. Practically, this means the view is intended to be consumed only after a BOM explosion has populated the temp table; querying it at other times returns no meaningful rows.

Key Columns

  • GROUP_ID — Identifier tying together rows belonging to a single explosion run or grouping context.
  • TOP_BILL_SEQUENCE_ID / TOP_ITEM_ID — Identify the top-level assembly whose BOM structure is being reported.
  • ORGANIZATION_ID — The inventory organization in which the exploded structure resides.
  • COMPONENT_ITEM_ID — The component item appearing within the structure.
  • SORT_ORDER — Aggregated via MAX; reflects the ordering sequence of the component within the structure.
  • EXTENDED_QUANTITY — Aggregated via SUM; the total quantity of the component required across the consolidated structure.
  • ITEM_COST — Unit or extended cost associated with the component for costing reports.
  • WIP_SUPPLY_TYPE — Supply type, distinguishing how the component is supplied (push, pull, operation, etc.).
  • BASED_ON_ROLLUP_FLAG / ACTUAL_COST_TYPE_ID — Costing indicators governing whether the component participates in cost rollup and under which cost type.
  • SHRINKAGE_RATE / INVENTORY_ASSET_FLAG — Shrinkage percentage and asset-accounting indicator for the component.
  • EXTEND_COST_FLAG — Indicates whether the cost should be extended for reporting.
  • BILL_SEQUENCE_ID, INCLUDE_IN_ROLLUP_FLAG, PLAN_LEVEL, OPERATION_SEQ_NUM, COMPONENT_SEQUENCE_ID, COMPONENT_YIELD_FACTOR, COMPONENT_QUANTITY — Exposed columns that are mapped to TO_NUMBER(NULL) or otherwise not meaningfully populated in the consolidated output.

Common Use Cases and Queries

The view is typically used to produce consolidated structure and costing reports for a top-level assembly, aggregating component quantities and costs across all occurrences of a component. A representative query:

SELECT group_id, top_item_id, organization_id, component_item_id, sort_order, extended_quantity, item_cost, wip_supply_type FROM apps.bom_consolidate_explosion_view WHERE group_id = :p_group_id ORDER BY sort_order;

Because the view depends on BOM_EXPLOSION_TEMP, the caller must first run the BOM explosion program that populates the temp table for the relevant group before this join produces output. Typical reporting scenarios include consolidated material requirement summaries, component cost roll-ups, and structure complexity analysis for assemblies. When using the view, note that several columns return NULL by design; applications requiring those values should query the base explosion source directly.