Search Results mrp_daily_demand_view




Overview
Explore in AI Chat

Overview

The MRP_DAILY_DEMAND_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It is delivered as part of the MRP (Master Scheduling/MRP) product family. As its description states, it is a "Daily bucketed demand view," meaning it presents gross requirements that have been expanded or spread across individual calendar days rather than aggregated into weekly or periodic buckets.

This view occupies a specific niche in the E-Business Suite data model: it sits on top of the planning engine's persistent tables and translates assembly-level demand into a day-by-day demand series. It is not a transactional entry object; rather, it is a query-only construct used for reporting, integration, and analysis where a planner or downstream system needs to see how demand from assembly requirements distributes across the manufacturing calendar. Its role is particularly useful when daily resolution is required for material planning, capacity load profiling, or exporting demand signals to external planning tools.

Underlying Base Objects

The view is defined over four base objects, all referenced through APPS synonyms in the documented metadata:

  • BOM_CALENDAR_DATES — Provides the sequence of valid manufacturing calendar dates, including sequence numbers used to identify working days.
  • MRP_GROSS_REQUIREMENTS — Supplies the assembly-level requirements, including assembly demand dates and completion dates, that drive demand expansion.
  • MRP_PLANS — Supplies the plan context, most importantly the cutoff date and compile designator that define the planning horizon.
  • MTL_PARAMETERS — Supplies the organization's calendar code and exception set, linking the correct calendar to the operating organization.

The joins enforce that dates fall within the plan cutoff, that the organization matches across parameters, plans, and requirements, and that the calendar exception set and code are consistent. The demand quantity is then derived using the DAILY_DEMAND_RATE, falling back to USING_REQUIREMENTS_QUANTITY when the daily rate is null.

Key Columns

The documented columns exposed by the view are:

  • INVENTORY_ITEM_ID — The inventory item for which demand is being reported.
  • COMPILE_DESIGNATOR — The plan or compile designator that identifies the planning run or simulation.
  • ORGANIZATION_ID — The operating organization in which the demand applies.
  • CALENDAR_DATE — The specific calendar day to which the bucketed demand is assigned.
  • DEMAND_QUANTITY — The aggregated demand quantity for the item, organization, plan, and date combination.

Because the view groups by compile designator, organization, item, and calendar date, each row represents a unique item-day-plan-organization combination, making it directly suitable for time-phased reporting.

Common Use Cases and Queries

The view is typically consumed to produce daily time-phased demand extracts, to profile demand across a planning horizon, or to feed external systems. A representative query returns daily demand for a specific plan and organization:

  • Daily demand series per item: SELECT inventory_item_id, organization_id, calendar_date, demand_quantity FROM apps.mrp_daily_demand_view WHERE compile_designator = :plan AND organization_id = :org ORDER BY inventory_item_id, calendar_date;
  • Total demand within a date range: aggregate SUM(demand_quantity) filtered by calendar_date BETWEEN :start_date AND :end_date.
  • Peak demand identification: order by demand_quantity DESC to isolate the highest daily load periods.

Because the view relies on join logic against calendar and parameter tables, queries should always supply a plan designator and organization to ensure efficient execution and meaningful results.