Search Results source_forecast_name




Overview
Explore in AI Chat

Overview

APPS.MRPBV_MDS_ENTRIES is a Business Intelligence (BI) system view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, registered under FND Design Data MRP.MRPBV_MDS_ENTRIES with a status of VALID. It presents the schedule entries belonging to a Master Demand Schedule (MDS) in Oracle Advanced Supply Chain Planning / Material Requirements Planning. Each row represents a demand entry for a given master demand schedule item, for a specified quantity, on a specified date. Because the object is a view rather than a table, it exposes already-joined and decoded information drawn from the base MDS tables and supporting utilities, making it suitable for reporting, extract, and integration use without requiring direct navigation of the underlying normalized structures.

Underlying Base Objects

The view is defined over a set of documented base objects. The schedule structure itself is sourced from MRP_SCHEDULE_ITEMS, which holds the item-level entries for a master demand schedule, while MRP_SCHEDULE_DATES supplies the bucket and date information associated with those entries. MRP_SCHEDULE_DESIGNATORS supplies the schedule designation (the named MDS, referenced in the SCHEDULE_NAME and SOURCE_SCHEDULE_NAME columns). Demand originating from sales orders is resolved through MTL_DEMAND_OMOE, with the packaged logic of MRP_OE and INV_SALESORDER handling order-management linkage, and OE_INSTALL guarding references to Order Management installation. Lookup decoding is provided by MFG_LOOKUPS, and numeric formatting by the package INV_DECIMALS_PUB. No database object is documented as referencing this view; it is a terminal, read-only reporting construct.

Key Columns

Common Use Cases and Queries

Typical usage includes validating MDS loads, reconciling demand quantities by schedule and item, tracing the origin of a demand entry back to a source schedule, and extracting MDS data into planning or BI repositories. The following example lists all entries for a given schedule, filtered by source schedule name:

SELECT msa.schedule_name, msa.source_schedule_name, msa.schedule_date, msa.inventory_item_id, msa.current_quantity, msa.original_quantity, msa.origination_type FROM apps.mrpbv_mds_entries msa WHERE msa.schedule_name = :schedule_name AND msa.source_schedule_name = :source_schedule_name ORDER BY msa.schedule_date, msa.inventory_item_id;

A second common pattern aggregates current demand per item within a schedule for comparison against a source bucket:

SELECT inventory_item_id, SUM(current_quantity) AS total_qty FROM apps.mrpbv_mds_entries WHERE schedule_name = :schedule_name AND schedule_date BETWEEN :from_date AND :to_date GROUP BY inventory_item_id;

Because the view performs the joins to schedule dates, designators, and sales order demand internally, these queries avoid direct manipulation of the underlying MDS tables and remain stable across the 12.1.1 and 12.2.2 releases.