Search Results shrinkage_rate




Overview
Explore in AI Chat

Overview

APPS.BOM_CONSOLIDATE_EXPLOSION_VIEW is a reporting view in Oracle E-Business Suite (EBS) that exposes a consolidated, aggregated representation of bill-of-material (BOM) explosion data. It is defined in the APPS schema and is available in both release 12.1.1 and 12.2.2. The view reads from the temporary explosion table BOM_EXPLOSION_TEMP and applies a GROUP BY aggregation across a defined set of grouping columns.

The view plays a supporting role in BOM and cost-rollup reporting. Where BOM_EXPLOSION_TEMP holds the row-level output of an explosion or rollup process, this view collapses that output into one row per group, giving report and integration layers a denormalized, pre-aggregated result set. This is particularly relevant to cost rollup and consolidated explosion reporting, where individual component occurrences must be summed into a meaningful total for a given top assembly and organization.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over a single referenced base object:

  • BOM_EXPLOSION_TEMP — referenced through a synonym (SYNONYM). This is the temporary working table populated by the BOM explosion and rollup routines. It carries the transient rows produced during an explosion run, keyed by a group identifier.

Because the view reads from a temporary staging table, its contents are only meaningful within the lifespan of an explosion or rollup run. The GROUP_ID column, which is both selected and used as the leading grouping criterion, provides the boundary that isolates one explosion run's rows from another. Consumers of the view must therefore restrict results by GROUP_ID to obtain a coherent data set.

Key Columns

The view exposes the following columns, several of which are positionally typed but unnamed in the underlying definition:

  • GROUP_ID — identifier distinguishing an individual explosion or rollup run. Primary correlation key.
  • TOP_BILL_SEQUENCE_ID — sequence identifier for the top-level bill structure being processed. Directly relevant to searches for TOP_ITEM_ID, as it is closely associated with the top assembly context.
  • TOP_ITEM_ID — inventory item identifier of the top-level assembly that seeds the explosion. This is the column most frequently used to anchor a query to a specific parent item.
  • ORGANIZATION_ID — the inventory organization in whose context the explosion was executed.
  • COMPONENT_ITEM_ID — the component item returned by the explosion.
  • MAX(SORT_ORDER) — aggregate of the sort ordering value, preserving structural ordering information.
  • SUM(EXTENDED_QUANTITY) — aggregated extended quantity, the summed per-assembly requirement for the grouped component.
  • ITEM_COST — unit cost associated with the component item.
  • WIP_SUPPLY_TYPE — supply type governing how the component is sourced in a work-in-process context (for example, push, pull, or operation-based supply).
  • BASED_ON_ROLLUP_FLAG — indicates whether the cost basis is derived from a rollup.
  • ACTUAL_COST_TYPE_ID — identifies the cost type used for actual costing of the component.
  • SHRINKAGE_RATE — the shrinkage factor applied during exploitation/costing.
  • INVENTORY_ASSET_FLAG — indicates whether the component is treated as an inventory asset.
  • EXTEND_COST_FLAG — controls whether the component cost is extended (multiplied by quantity) in downstream consolidation.
  • Several TO_NUMBER(NULL) placeholder columns — these occupy fixed positions in the column list, providing type alignment for consumers expecting a defined column shape.

Common Use Cases and Queries

Typical usage centers on retrieving consolidated component requirements for a specified top assembly, organization, or explosion run. A common pattern filters by GROUP_ID and TOP_ITEM_ID:

  • SELECT TOP_ITEM_ID, COMPONENT_ITEM_ID, SUM(EXTENDED_QUANTITY) qty, ITEM_COST FROM APPS.BOM_CONSOLIDATE_EXPLOSION_VIEW WHERE GROUP_ID = :p_group_id AND TOP_ITEM_ID = :p_top_item GROUP BY TOP_ITEM_ID, COMPONENT_ITEM_ID, ITEM_COST;
  • Cost rollup reporting, where SUM(EXTENDED_QUANTITY) is multiplied by ITEM_COST to derive extended component value, respecting EXTEND_COST_FLAG.
  • Integration extracts that require a compact, aggregated snapshot of an explosion rather than row-level detail.

Because the view references a temporary table, queries should be executed within the same session or transaction scope as the explosion routine that populated BOM_EXPLOSION_TEMP. Outside that scope, the view may return no rows or stale data. The tight GROUP_ID filter is essential for correct results.