Search Results mrp_planning_code_desc

Overview

MRP_FORECAST_ITEMS_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product. It presents forecast item information by joining the forecast item definition table MRP_FORECAST_ITEMS to the item master view MTL_SYSTEM_ITEMS_VL and to three lookup code resolutions sourced from MFG_LOOKUPS. The view is documented as VALID and is available in both 12.1.1 and 12.2.2 environments, retaining an identical column list across releases as confirmed by the ETRM metadata.

The view's primary role is to expose forecast item records with human-readable, decoded attribute values. Rather than returning raw lookup codes, it resolves BOM_ITEM_TYPE, ATO_FORECAST_CONTROL, and MRP_PLANNING_CODE into their descriptive meanings through outer and inner joins to MFG_LOOKUPS. This makes the view well suited for reporting, concurrent program extraction, and integration feeds where downstream consumers require descriptive text rather than encoded values. The user search term "bom_item_type_desc" corresponds directly to the BOM_ITEM_TYPE_DESC column exposed by this view, which is derived from the LOOKUP_TYPE 'BOM_ITEM_TYPE'.

Underlying Base Objects

The documented base objects referenced by MRP_FORECAST_ITEMS_V are:

• MRP_FORECAST_ITEMS (SYNONYM) — the driving table, aliased MFI, which stores forecast item assignments by organization and forecast designator.
• MTL_SYSTEM_ITEMS_VL (VIEW) — aliased KFV, supplying item concatenated segments, description, primary UOM, BOM item type, pick components flag, ATO forecast control, and MRP planning code.
• MFG_LOOKUPS (VIEW) — referenced three times as L1, L2, and L3 to decode BOM_ITEM_TYPE, ATO_FORECAST_CONTROL, and MRP_PLANNING_CODE respectively.

The joins are defined such that MFI.INVENTORY_ITEM_ID equals KFV.INVENTORY_ITEM_ID and MFI.ORGANIZATION_ID equals KFV.ORGANIZATION_ID, anchoring each forecast item to its organization-specific item definition. L1 and L3 use equijoins with LOOKUP_TYPE values of 'BOM_ITEM_TYPE' and 'MRP_PLANNING_CODE'; L2 uses an outer join (denoted by the (+) operator) against LOOKUP_TYPE 'MRP_ATO_FORECAST_CONTROL', permitting null ATO forecast control values without dropping rows.

Key Columns

The view returns 34 columns. Notable columns include:

• ROW_ID — the ROWID of the underlying MRP_FORECAST_ITEMS row.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — the composite identifier linking to the item master.
• CONCATENATED_SEGMENTS — the concatenated item flexfield segments from MTL_SYSTEM_ITEMS_VL.
• ITEM_DESCRIPTION and PRIMARY_UOM_CODE — item description and primary unit of measure.
• BOM_ITEM_TYPE and BOM_ITEM_TYPE_DESC — the BOM item type code and its decoded meaning, central to the user's search.
• PICK_COMPONENTS_FLAG — indicates pick component configuration for the item.
• ATO_FORECAST_CONTROL_DESC and MRP_PLANNING_CODE_DESC — decoded meanings for the ATO forecast control and MRP planning code.
• ALTERNATE_BOM_DESIGNATOR and FORECAST_DESIGNATOR — forecast context columns.
• Standard WHO and program columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, and so on), plus fifteen attribute columns.

Common Use Cases and Queries

Typical scenarios include retrieving forecast items with decoded BOM item types for planning reports, validating item configuration for a given organization and forecast, and building integration extracts. A representative query follows:

• SELECT inventory_item_id, concatenated_segments, item_description, bom_item_type_desc, mrp_planning_code_desc FROM mrp_forecast_items_v WHERE forecast_designator = :forecast AND organization_id = :org;

To isolate items by their decoded BOM item type:

• SELECT concatenated_segments, bom_item_type_desc FROM mrp_forecast_items_v WHERE bom_item_type_desc = 'Standard';

Because ATO_FORECAST_CONTROL is resolved via an outer join, records with a null ATO forecast control are retained, and ATO_FORECAST_CONTROL_DESC will return null for those rows. Queries should therefore not assume that column is always populated. All access should be performed against the APPS schema or through a synonym granted to the reporting user.