Results for “mrp_daily_supply_view”

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

Overview

MRP_DAILY_SUPPLY_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Daily bucketed supply view," and it is classified under the MRP — Master Scheduling/MRP product family. The view materializes the daily distribution of planned supply quantities generated by the MRP planning engine, transforming the schedule date ranges held on planning recommendations into one row per item, organization, plan, and calendar date.

In the standard planning data model, MRP_RECOMMENDATIONS stores discrete recommendations with start and completion dates. Reporting tools, however, frequently require supply expressed in fixed-daily buckets so that planners and downstream systems can align supply with a shop calendar. MRP_DAILY_SUPPLY_VIEW performs exactly that bucketing. Because it carries the COMPILE_DESIGNATOR, the view is plan-aware: a single query can return supply for the same item across multiple named plans without ambiguity.

The view's status is VALID in the ETRM metadata, indicating it is a supported, queryable APPS object rather than an obsolete legacy artifact. Its principal integration value lies in exposing the SUPPLY_QUANTITY column — the exact attribute most commonly sought in searches for "supply_quantity" — in a calendar-aligned format suitable for join to date dimensions, exception-set calendars, and capacity reports.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

• BOM_CALENDAR_DATES — supplies the daily calendar rows, filtered on EXCEPTION_SET_ID and CALENDAR_CODE, and excludes rows where SEQ_NUM is null. This is the source of CALENDAR_DATE.
• MRP_PLANS — joined on COMPILE_DESIGNATOR and ORGANIZATION_ID; provides CUTOFF_DATE, which caps the calendar dates returned.
• MRP_RECOMMENDATIONS — the supply driver. Joined on INVENTORY_ITEM_ID, COMPILE_DESIGNATOR, and ORGANIZATION_ID, and restricted to DISPOSITION_STATUS_TYPE = 1 (firm/planned orders).
• MTL_PARAMETERS — supplies the organization's CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID, linking the calendar to the correct organization.

The WHERE clause constrains each recommendation's dates to the intersection of its NEW_SCHEDULE_DATE and either NEW_SCHEDULE_DATE (when LAST_UNIT_COMPLETION_DATE is null) or LAST_UNIT_COMPLETION_DATE. In effect, the view intersects the MRP recommendation schedule window with the manufacturing calendar to produce daily rows.

Key Columns

• INVENTORY_ITEM_ID — the item for which supply is being reported.
• COMPILE_DESIGNATOR — the MRP plan identifier; distinguishes supply from different plans (e.g., MPS vs. MRP).
• ORGANIZATION_ID — the inventory organization supplying the quantity.
• CALENDAR_DATE — the daily calendar bucket derived from BOM_CALENDAR_DATES.
• SUPPLY_QUANTITY — the aggregated daily supply. This is computed as the SUM of a DECODE: where LAST_UNIT_COMPLETION_DATE is null, MRP_RECOMMENDATIONS.NEW_ORDER_QUANTITY is used; otherwise, DAILY_RATE. This DECODE is critical: single-date recommendations take their full order quantity, while multi-day recommendations are spread at the daily rate.

Common Use Cases and Queries

Typical usage includes daily supply pegging against demand, MRP exception review, and extract generation for external planning or APS systems.

Sample query — daily supply for a given item and plan:

• SELECT inventory_item_id, compile_designator, organization_id, calendar_date, supply_quantity
• FROM apps.mrp_daily_supply_view
• WHERE inventory_item_id = :item_id
• AND compile_designator = :plan
• AND organization_id = :org_id
• ORDER BY calendar_date;

Aggregate supply by month for capacity planning:

• SELECT compile_designator, organization_id,
• TRUNC(calendar_date,'MM') month,
• SUM(supply_quantity) total_supply
• FROM apps.mrp_daily_supply_view
• WHERE inventory_item_id = :item_id
• GROUP BY compile_designator, organization_id,
• TRUNC(calendar_date,'MM')
• ORDER BY 3;

Because data originates from MRP recommendations, the view reflects the state of the last successful plan run and is not cumulative across reruns unless the plan is refreshed. Queries should therefore be scoped by COMPILE_DESIGNATOR and ORGANIZATION_ID to avoid mixing plans or organizations.