Search Results mrpbv_plan_supplies




Overview
Explore in AI Chat

Overview

MRPBV_PLAN_SUPPLIES is an APPS-owned database view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. In EBS 12.1.1 and 12.2.2, it exposes the supply-side recommendations produced by an MRP, MPS, or DRP plan, presenting them in a denormalized, reporting-ready form. The view is primarily intended to drive the Planner Workbench and related supply/rescheduling reports, where planners review suggested new planned orders, reschedules, cancellations, and firming actions before implementation. Because it joins planning recommendations against items, organizations, plans, and lookup tables, it allows both online inquiries and custom integrations to consume supply recommendations without traversing the underlying MRP recommendation and item tables directly.

Underlying Base Objects

Per the documented metadata for ETRM 12.2.2, the view is defined over the following base objects: MRP_PLANS, MRP_PLAN_ORGANIZATIONS, MRP_RECOMMENDATIONS, MRP_SYSTEM_ITEMS, MRP_ITEM_PURCHASE_ORDERS, MRP_ITEM_WIP_ENTITIES, MTL_SYSTEM_ITEMS, MTL_PARAMETERS, WIP_SCHEDULE_GROUPS, and MFG_LOOKUPS. MRP_RECOMMENDATIONS is the core driver table containing the individual supply recommendations (order type, quantities, dates, and implement actions). MRP_PLANS and MRP_PLAN_ORGANIZATIONS scope those recommendations to a plan and its included organizations. MRP_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS resolve item and organization context. MRP_ITEM_PURCHASE_ORDERS supplies purchase-order-specific attributes such as line identifier, while MRP_ITEM_WIP_ENTITIES supplies WIP/work-order build sequence and related entity details. MFG_LOOKUPS translates coded values (firm planned type, release status, implement-as flags, rescheduled flag, WIP job status) into user-readable meanings, and WIP_SCHEDULE_GROUPS provides schedule group references for implementation.

Key Columns

The view exposes plan identity through COMPILE_DESIGNATOR and planning context through ORGANIZATION_ID and PLANNING_GROUP. Supply attributes include ORDER_TYPE, NEW_SCHEDULE_DATE, NEW_ORDER_QUANTITY, OLD_ORDER_QUANTITY, NEW_DOCK_DATE, NEW_WIP_START_DATE, NEW_ORDER_PLACEMENT_DATE, and LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE / FIRST_UNIT_START_DATE. Firming and implementation columns include FIRM_PLANNED_TYPE, FIRM_DATE, FIRM_QUANTITY, IMPLEMENT_DATE, IMPLEMENT_QUANTITY, IMPLEMENT_AS, IMPLEMENT_STATUS_CODE, RESCHEDULED_FLAG, and IMPLEMENT_BUILD_SEQUENCE. Several source/supplier columns are directly relevant to searches for source_supplier_id: REC.SOURCE_ORGANIZATION_ID, REC.SOURCE_VENDOR_ID, REC.SOURCE_VENDOR_SITE_ID, together with their implement counterparts IMPLEMENT_SOURCE_ORG_ID, IMPLEMENT_VENDOR_ID, and IMPLEMENT_VENDOR_SITE_ID. Item and routing context is provided by INVENTORY_ITEM_ID, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, and IMPLEMENT_ALTERNATE_BOM / IMPLEMENT_ALTERNATE_ROUTING. Project and task references appear via PROJECT_ID, TASK_ID, IMPLEMENT_PROJECT_ID, and IMPLEMENT_TASK_ID.

Common Use Cases and Queries

Typical usage includes reviewing planned supplies for a single plan, identifying reschedule or compression actions, exporting recommendations for external scheduling systems, and tracing vendor or source organization detail for make-or-buy analysis. Because the view uses synonyms over MRP tables, queries are normally executed as APPS or a responsibility with MRP read privileges.

  • List all supplies for a plan: SELECT COMPILE_DESIGNATOR, INVENTORY_ITEM_ID, ORDER_TYPE, NEW_SCHEDULE_DATE, NEW_ORDER_QUANTITY FROM MRPBV_PLAN_SUPPLIES WHERE COMPILE_DESIGNATOR = :plan AND ORGANIZATION_ID = :org;
  • Find reschedules or firming actions: SELECT INVENTORY_ITEM_ID, NEW_SCHEDULE_DATE, OLD_SCHEDULE_DATE, RESCHEDULED_FLAG FROM MRPBV_PLAN_SUPPLIES WHERE COMPILE_DESIGNATOR = :plan AND RESCHEDULED_FLAG = 1;
  • Trace supplier / source organization: SELECT INVENTORY_ITEM_ID, SOURCE_ORGANIZATION_ID, SOURCE_VENDOR_ID, SOURCE_VENDOR_SITE_ID, NEW_ORDER_QUANTITY FROM MRPBV_PLAN_SUPPLIES WHERE COMPILE_DESIGNATOR = :plan AND SOURCE_VENDOR_ID = :vendor;
  • Review implement attributes: SELECT INVENTORY_ITEM_ID, IMPLEMENT_VENDOR_ID, IMPLEMENT_SOURCE_ORG_ID, IMPLEMENT_AS, IMPLEMENT_STATUS_CODE FROM MRPBV_PLAN_SUPPLIES WHERE COMPILE_DESIGNATOR = :plan;

Note that the requested column name source_supplier_id is not exposed verbatim; the corresponding documented attributes are SOURCE_VENDOR_ID / SOURCE_VENDOR_SITE_ID (and the IMPLEMENT_VENDOR_ID equivalents). When searching for supplier-related data, these are the effective equivalents to apply in report filters.