Search Results daily_demand_rate




Overview
Explore in AI Chat

Overview

APPS.MRP_DAILY_DEMAND_VIEW is a reporting view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 supply chain and manufacturing modules. It is designed to present a daily breakdown of demand for a given inventory item within a specified organization and plan, enabling material planners, buyers, and production schedulers to examine how gross requirements are distributed across individual calendar days. Rather than storing any data of its own, the view derives its output dynamically from planning and calendar data, aggregating demand quantities per calendar date through the grouping clause defined in its text.

Its principal role is to translate gross requirement records, which may be expressed either as a discrete demand quantity or as a daily demand rate, into a normalized daily figure that spans a defined window of valid working calendar days. This makes it particularly useful in reporting and integration scenarios where demand must be spread deterministically across a timeline, such as feeding a scheduling or capacity report.

The view is most relevant to the search term "daily_demand_rate" because the DECODE expression at its core selects DAILY_DEMAND_RATE values wherever present, and substitutes USING_REQUIREMENTS_QUANTITY otherwise. This is the mechanism that converts multiple demand representations into a single consistent daily metric.

Underlying Base Objects

The view is owned by APPS and is defined over four base objects, each referenced through public synonyms:

  • MRP_GROSS_REQUIREMENTS (SYNONYM) — the driving demand table, supplying inventory item, organization, compile designator, and the demand quantities/dates.
  • MRP_PLANS (SYNONYM) — provides the plan context, including the CUTOFF_DATE that bounds the reporting horizon.
  • MTL_PARAMETERS (SYNONYM) — supplies the organization's inventory calendar settings (calendar code and exception set), used to resolve valid calendar days.
  • BOM_CALENDAR_DATES (SYNONYM) — provides each valid CALENDAR_DATE, restricted by SEQ_NUM IS NOT NULL.

These objects are joined on organization, calendar attributes, and compile designator, ensuring that demand is projected only across valid calendar days that fall within the interval defined by USING_ASSEMBLY_DEMAND_DATE and ASSEMBLY_DEMAND_COMP_DATE.

Key Columns

  • INVENTORY_ITEM_ID — identifier of the demanded item.
  • COMPILE_DESIGNATOR — the MRP plan identifier under which the requirement was compiled.
  • ORGANIZATION_ID — the inventory organization in which the demand applies.
  • CALENDAR_DATE — the specific day on which the aggregated demand quantity applies.
  • SUM(DECODE(DAILY_DEMAND_RATE, NULL, USING_REQUIREMENTS_QUANTITY, DAILY_DEMAND_RATE)) — the aggregated daily demand quantity; where a daily rate exists it is used, otherwise the using-requirements quantity is applied.

Common Use Cases and Queries

Typical use cases include daily demand profiling for a plan, projecting requirement quantities onto working days for downstream capacity analysis, and validating how rates versus discrete quantities are resolved. A representative query:

SELECT inventory_item_id,
       organization_id,
       compile_designator,
       calendar_date,
       daily_demand
FROM   apps.mrp_daily_demand_view
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id
AND    compile_designator = :plan_id
ORDER BY calendar_date;

Because the view already aggregates and spreads demand across calendar dates, it can be consumed directly by custom reports or interfaces without additional date-expansion logic.