Results for “demand_quantity”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MRP_WEEKLY_DEMAND_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, validated and available under the Master Scheduling/MRP (MRP) product family. Its purpose is to present gross demand information in a weekly bucketed form for a given plan and organization. Rather than exposing raw, date-stamped requirements, the view aggregates demand into calendar weeks defined by an organization's manufacturing calendar.

This object is primarily a reporting and integration artifact. It serves planning analysts, custom dashboards, and downstream extracts that require demand expressed at weekly granularity instead of the daily granularity stored in the underlying requirement records. The bucketing logic derives from the enterprise calendar configuration, so the resulting weeks align with the same working-day and exception-set definitions used by Oracle's planning engine. Because the view is read-only and defined in the APPS schema, it is not intended for direct transaction processing; it is consumed through ad hoc SQL or embedded in custom reports.

Underlying Base Objects

The view is defined over five base objects, each referenced through a public synonym:

• MRP_GROSS_REQUIREMENTS — supplies the raw demand records, including inventory item, organization, compile designator, assembly demand date, and using-requirements quantity.
• BOM_CAL_WEEK_START_DATES — provides the week start date and the next week boundary for a given calendar and exception set.
• BOM_CALENDAR_DATES — expands the calendar into individual dated rows, each carrying a sequence number to distinguish valid working days.
• MTL_PARAMETERS — links an organization to its calendar code and calendar exception set, enabling calendar join alignment per organization.
• MRP_PLANS — constrains the demand to plan cutoff dates and matches the plan's compile designator to the requirement rows.

The joins tie the demand record to an organization's calendar, then fan out each requirement across the individual calendar dates falling between the requirement's demand date and its compliance date. These dates are grouped back to their owning week to produce the final weekly totals.

Key Columns

• INVENTORY_ITEM_ID — identifier of the demanded item.
• COMPILE_DESIGNATOR — the plan identifier, matching MRP_PLANS.COMPILE_DESIGNATOR.
• ORGANIZATION_ID — the inventory organization in which demand is evaluated.
• WEEK_START_DATE — the first date of the weekly bucket, sourced from the calendar.
• DEMAND_QUANTITY — the summed demand for the bucket. It is computed as SUM(DECODE(DAILY_DEMAND_RATE, NULL, USING_REQUIREMENTS_QUANTITY, DAILY_DEMAND_RATE)), meaning that when DAILY_DEMAND_RATE is populated it is used as the daily rate; otherwise the using-requirements quantity is applied. Note that DAILY_DEMAND_RATE is a column of the base requirement table, not a column of this view.

Common Use Cases and Queries

Typical usage includes weekly demand trend reports, master production schedule reviews, and feeding external planning or business-intelligence repositories with bucketed demand.

A representative query selecting weekly demand for a specific item and organization:

• SELECT inventory_item_id, organization_id, week_start_date, demand_quantity
• FROM apps.mrp_weekly_demand_view
• WHERE organization_id = :org_id
• AND inventory_item_id = :item_id
• AND compile_designator = :plan
• ORDER BY week_start_date;

Because the view already performs the calendar fan-out and weekly aggregation, it is best suited for display and reporting rather than heavy iterative computation. Users requiring finer granularity should query MRP_GROSS_REQUIREMENTS directly and apply their own bucketing.