Results for “mrp_ato_forecast_control”

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

Overview

APPS.BOM_PRODUCTFAMILY_MEM_V is a reporting view in Oracle E-Business Suite that exposes the relationship between product family members and their bill of materials components, enriched with descriptive lookup meanings. Its central purpose is to flatten the join between a bill of materials header, its component lines, the master item definition, and three decoding lookups (Forecast Control, Planning Method, and BOM Item Type) into a single queryable result set. The view is particularly relevant to the search term "mrp_ato_forecast_control" because it decodes the ATO_FORECAST_CONTROL item attribute against the MRP_ATO_FORECAST_CONTROL lookup type, translating the stored code into a human-readable FORECAST_CONTROL meaning. In EBS 12.1.1 and 12.2.2, this view supports planning and product family analysis by allowing report writers, concurrent programs, and integration extracts to retrieve forecast-control, planning-method, and item-type information directly without repeated lookup joins.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects for the 12.2.2 release, all owned by APPS:

• BOM_BILL_OF_MATHEMATICS (VIEW) — supplies the bill of materials header and organization context; note the ETRM records this as BOM_BILL_OF_MATERIALS (VIEW), i.e. the BOM header entity.
• BOM_INVENTORY_COMPONENTS (VIEW) — supplies the component lines, including COMPONENT_ITEM_ID, BILL_SEQUENCE_ID, and BOM_ITEM_TYPE.
• MFG_LOOKUPS (VIEW) — referenced three times (aliases ML1, ML2, ML3) to decode Forecast Control, Planning Method, and BOM Item Type.
• MTL_SYSTEM_ITEMS (SYNONYM) — provides the master item attributes, notably ATO_FORECAST_CONTROL and MRP_PLANNING_CODE.
• FND_GLOBAL (PACKAGE) — referenced for session/context resolution, commonly for organization and user context in EBS views.

The view text defines the join as: BIC.BILL_SEQUENCE_ID = BOM.BILL_SEQUENCE_ID; BIC.COMPONENT_ITEM_ID = MSI.INVENTORY_ITEM_ID with matching ORGANIZATION_ID; and the three outer joins to MFG_LOOKUPS on the respective lookup codes and types. The forecasts and planning lookups are outer joins (denoted by (+)), so components without a defined forecast-control or planning code still appear.

Key Columns

• ORGANIZATION_ID — the inventory organization owning the bill and item; sourced from the BOM header.
• COMPONENT_ITEM_ID — the inventory item identifier of the component line.
• BILL_SEQUENCE_ID — the unique identifier of the bill of materials instance linking header to components.
• FORECAST_CONTROL — decoded meaning of MSI.ATO_FORECAST_CONTROL against lookup type MRP_ATO_FORECAST_CONTROL; the attribute most closely tied to the user's search term.
• PLANNING_METHOD — decoded meaning of MSI.MRP_PLANNING_CODE against lookup type MRP_PLANNING_CODE.
• BOM_ITEM_TYPE — decoded meaning of BIC.BOM_ITEM_TYPE against lookup type BOM_ITEM_TYPE, identifying whether the component is a standard, model, option class, or planning item.

Common Use Cases and Queries

Typical uses include product family/BOM membership extracts, ATO forecast-control audits, and planning-method validation. A representative query retrieves all family members in an organization with their forecast and 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;

A second scenario isolates ATO-related components by filtering on the decoded forecast-control meaning:

SELECT component_item_id, forecast_control
FROM   apps.bom_productfamily_mem_v
WHERE  forecast_control IS NOT NULL
AND    organization_id = :org_id;

Because the view applies SELECT DISTINCT, callers should treat it as a reporting aid rather than a transactional source; joins to additional tables should account for row deduplication. The outer joins also mean FORECAST_CONTROL and PLANNING_METHOD may be null and must be handled with NVL or NULL checks.