Search Results plan_supply_id




Overview
Explore in AI Chat

Overview

APPS.MRPBV_PLAN_DEMANDS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, registered as FND Design Data object MRP.MRPBV_PLAN_DEMANDS. It exposes the demand side of a material plan — the gross requirements that a Master Production Schedule (MPS), Material Requirements Plan (MRP), or Distribution Requirements Plan (DRP) must satisfy for a given item. Each row represents a demand element (for example a sales order, a discrete manufacturing job component requirement, or a manually entered MDS entry) together with its scheduled and suggested due dates and quantities, as computed by the Oracle planning engine for a specific plan and organization. Because it is documented as a read-only BIS view, it is intended for reporting, ad hoc analysis, and integration rather than for transactional update. The view is not referenced by any other database object, so it functions as a terminal presentation layer. Users searching for plan_supply_id will find that the view surfaces PLAN_SUPPLY_ID as a denormalized linkage column, allowing demand records to be traced back to the supply element that the planning engine pegged against them.

Underlying Base Objects

The view is defined over a join of transactional and setup tables. The documented dependencies are MFG_LOOKUPS (itself a view, supplying order type and status decoding), MRP_PLANS, MRP_PLAN_ORGANIZATIONS, MRP_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS, and MTL_PARAMETERS for plan, organization, and item context; MRP_GROSS_REQUIREMENTS as the principal demand fact source; MRP_RECOMMENDATIONS, MRP_SCHEDULE_DATES, and MRP_ITEM_WIP_ENTITIES for planning output such as suggested dates and WIP entity associations; MRP_ITEM_PURCHASE_ORDERS for buy-side detail; and MTL_SALES_ORDERS for sales order demand. In the documented 12.2.2 metadata, the referenced base objects resolve as synonyms (except MFG_LOOKUPS, which is a view), reflecting the ONT/Oracle Applications synonym layer over the underlying MRP and MTL tables. The view therefore inherits the planner run context: rows are meaningful only in the context of a completed plan identified by PLAN_NAME and ORGANIZATION_ID.

Key Columns

Common Use Cases and Queries

Typical uses include demand-versus-supply analysis, reschedule-in/reschedule-out reporting, and drill-down from a plan to pegged supplies. A simple plan-level demand listing:

SELECT plan_name, order_type, suggested_due_date, quantity_rate, days_from_today FROM apps.mrpbv_plan_demands WHERE plan_name = :plan AND organization_id = :org ORDER BY suggested_due_date;

To trace the supply pegged to a demand (the plan_supply_id search):

SELECT d.plan_demand_id, d.inventory_item_id, d.quantity_rate, d.plan_supply_id FROM apps.mrpbv_plan_demands d WHERE d.plan_supply_id IS NOT NULL AND d.plan_name = :plan;

For project-driven demand, filter on PROJECT_ID and TASK_ID; for sales order demand specifically, join MTL_SALES_ORDERS on the sales order identifier. Because the view is a BIS reporting object with no dependent database objects, it can be queried freely without impacting planning transactions.