Search Results forecast_control




Overview
Explore in AI Chat

Overview

APPS.BOM_PRODUCTFAMILY_MEM_V is a Bills of Material (BOM) view that exposes the membership relationship between product family items and their assigned component items. Product families in Oracle EBS are a planning construct: they allow a group of related items to be forecasted and planned collectively rather than individually. This view surfaces the membership rows that define which components belong to which product family, together with descriptive lookup meanings for the component's forecast control, planning method, and BOM item type. It is implemented as a view over BOM_INVENTORY_COMPONENTS and MTL_SYSTEM_ITEMS, and the ETRM documentation notes it was introduced for the product family functionality in Release 11. It remains valid in 12.1.1 and 12.2.2 and is typically consumed by reporting, planning diagnostics, and integration extracts that need to resolve product family membership without navigating the underlying BOM structure directly.

Underlying Base Objects

The view is defined over the following referenced objects:

The three MFG_LOOKUPS joins use outer-join syntax ((+)) for forecast control and planning method, meaning components without a matching lookup still appear; the BOM item type join is an inner join.

Key Columns

  • ORGANIZATION_ID — the inventory organization that owns the bill and component.
  • COMPONENT_ITEM_ID — the inventory item identifier of the component belonging to the family.
  • BILL_SEQUENCE_ID — the bill header identifier linking the component to its parent bill.
  • FORECAST_CONTROL — lookup meaning derived from MSI.ATO_FORECAST_CONTROL (lookup type MRP_ATO_FORECAST_CONTROL); indicates how an ATO item's forecast is controlled.
  • PLANNING_METHOD — lookup meaning derived from MSI.MRP_PLANNING_CODE (lookup type MRP_PLANNING_CODE); identifies whether the component is planned (MPS/MRP) or not planned.
  • BOM_ITEM_TYPE — lookup meaning derived from BIC.BOM_ITEM_TYPE (lookup type BOM_ITEM_TYPE); this is the column most frequently associated with the search term bom_item_type. It classifies the component, commonly as a standard, model, option class, or planning bill item.

The DISTINCT clause eliminates duplicate rows arising from the lookup and item master joins.

Common Use Cases and Queries

Typical scenarios include auditing product family membership, validating component planning attributes, and feeding planning or reporting extracts. To list all components for a given organization with their planning attributes:

SELECT organization_id,
       component_item_id,
       bill_sequence_id,
       forecast_control,
       planning_method,
       bom_item_type
FROM   apps.bom_productfamily_mem_v
WHERE  organization_id = :org_id;

To filter by BOM item type (resolving the user's bom_item_type interest), for example to isolate planning bill components:

SELECT component_item_id, bom_item_type
FROM   apps.bom_productfamily_mem_v
WHERE  bom_item_type = 'Planning'
  AND  organization_id = :org_id;

To identify components that are not planned, aiding forecast diagnostics:

SELECT component_item_id, planning_method
FROM   apps.bom_productfamily_mem_v
WHERE  planning_method IS NULL
   OR  planning_method = 'Not Planned';

In 12.1.1 and 12.2.2 the view exhibits identical structure. Because it references the item master synonym and lookup view, it inherits organization-level item attribute resolution and requires the querying responsibility to have access to the inventory organization and item data.