Search Results mrp_ap_bom_components_v

Overview

MRP_AP_BOM_COMPONENTS_V is an Oracle E-Business Suite database view that belongs to the Master Scheduling/MRP (MRP) product family. It exposes bill of materials (BOM) component information in a form consumed by the Oracle MRP planning engine—specifically the memory-based snapshot structure used during a planning run. The view flattens the relationship between a planning assembly (the using assembly), its bill of materials, and the components that make up that bill, returning usage quantities, effectivity windows, and planning attributes for each component line.

The name prefix MRP_AP_ indicates that the view is built over the MRP "AP" (application planner) snapshot tables—the temporary, planning-run-specific copies of master data that Oracle MRP materializes when it launches a plan. Because these underlying snapshot tables are populated only while a planning run is active and are typically cleared or refreshed between runs, the view is primarily intended for diagnostics, debugging, and internal engine access rather than for steady-state end-user reporting. In the documented environment it is noted as "Not implemented in this database," meaning it may exist as engine infrastructure rather than as a standalone deployed object in every instance.

Underlying Base Objects

The view selects from five snapshot base tables, joined on organization and bill/item keys:

• MRP_AP_MRP_PARAS_SN MP — planning parameters snapshot, joined on ORGANIZATION_ID.
• MRP_AP_BOMS_SN BBOM — BOM header snapshot, supplying BILL_SEQUENCE_ID, ORGANIZATION_ID, and ASSEMBLY_ITEM_ID.
• MRP_AP_INV_COMPS_SN BIC — inventory component snapshot, supplying component item, quantity, yield factor, planning factor, and effectivity dates.
• MRP_AP_ERIS_SN ERI — engineering revised item snapshot, joined via REVISED_ITEM_SEQUENCE_ID, supplying status, use-up, and change-notice data.
• MRP_AP_SYS_ITEMS_SN MSIK / MSIK2 — item snapshot tables referenced twice, once for the component item and once for the assembly item.

The joins are outer and filter-based: BIC joins to BBOM on COMMON_BILL_SEQUENCE_ID, ERI joins to BIC with an outer (+) on REVISED_ITEM_SEQUENCE_ID, and the item snapshots restrict which BOM item types are eligible. No base objects are documented in the ETRM metadata, so these relationships follow directly from the view text.

Key Columns

• COMPONENT_SEQUENCE_ID — primary identifier of the component line.
• INVENTORY_ITEM_ID — the component item (aliased from COMPONENT_ITEM_ID).
• USAGE_QUANTITY — computed as (COMPONENT_QUANTITY/COMPONENT_YIELD_FACTOR)*PLANNING_FACTOR/100.
• DRIVING_ITEM_ID — the user's search term. Produced by DECODE(NVL(ERI.STATUS_TYPE,6),6,NULL,ERI.USE_UP_ITEM_ID). It returns the use-up item when a non-6 (non-active) status applies, otherwise NULL. This is central to use-up/obsolescence planning.
• USING_ASSEMBLY_ID — the assembly the component belongs to.
• EFFECTIVITY_DATE / DISABLE_DATE — the component's effective window.
• COMPONENT_TYPE, OPTIONAL_COMPONENT, WIP_SUPPLY_TYPE, ATP_FLAG — planning behavior flags.
• STATUS_TYPE, MRP_ACTIVE, USE_UP_CODE, CHANGE_NOTICE — engineering change context.

Common Use Cases and Queries

Typical uses include verifying component usage for a given assembly and inspecting use-up (driving item) relationships during change planning.

SELECT inventory_item_id, using_assembly_id,
       usage_quantity, driving_item_id, use_up_code
FROM   mrp_ap_bom_components_v
WHERE  using_assembly_id = :assembly_item_id;

To find components driving substitution, filter on non-null driving items:

SELECT component_sequence_id, inventory_item_id, driving_item_id
FROM   mrp_ap_bom_components_v
WHERE  driving_item_id IS NOT NULL
AND    organization_id = :org_id;

Because results depend on an active planning snapshot, these queries are most meaningful while a plan is running or against a populated snapshot schema.