Results for “forecast_entry_id”

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

Overview

MRPBV_MDS_ENTRIES is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MRP (Master Scheduling/MRP) product family. It exposes master demand schedule (MDS) entries as denormalized, report-friendly rows, joining schedule date records to item, schedule designator, demand, and lookup information. The view is marked Retrofit in the ETRM documentation, reflecting its role as an upgrade-compatible presentation layer over the underlying MRP scheduling tables.

The view presents one row per schedule date entry, carrying the planned quantity (exposed as CURRENT_QUANTITY), the original scheduled quantity, the schedule date, repetitive daily rate, origination type, comments, and a set of foreign keys to item, organization, forecast, project, task, and sales order entities. It is declared WITH READ ONLY, so it is intended strictly for query and reporting rather than DML.

Users searching for "current_quantity" are typically looking for the current scheduled demand quantity against an MDS entry — the field that answers "how much is currently scheduled for this item on this date?" In this view that value is sourced from MRP_SCHEDULE_DATES.SCHEDULE_QUANTITY and surfaced as CURRENT_QUANTITY.

Underlying Base Objects

The view text joins several objects:

• MRP_SCHEDULE_DATES (SCDA) — the driving table; supplies SCHEDULE_DATE, RATE_END_DATE, SCHEDULE_QUANTITY (CURRENT_QUANTITY), ORIGINAL_SCHEDULE_QUANTITY, REPETITIVE_DAILY_RATE, comments, transaction and reservation identifiers, and project/task keys.
• MRP_SCHEDULE_ITEMS (SCIT) — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and SCHEDULE_DESIGNATOR to validate the item/schedule combination.
• MRP_SCHEDULE_DESIGNATORS (SCDE) — joined on ORGANIZATION_ID and SCHEDULE_DESIGNATOR, restricted to SCHEDULE_TYPE = 1 (master demand schedules).
• MTL_DEMAND_OMOE (DEMAND) — outer-joined via SCDA.RESERVATION_ID = DEMAND.DEMAND_ID to bring in DEMAND_SOURCE_LINE (SALES_ORDER_LINE_ID), preserving schedule rows without a matching sales order demand.
• MFG_LOOKUPS (LKUP) — decoded on LOOKUP_TYPE = 'MRP_SCHEDULE_ORIG' and LOOKUP_CODE = SCDA.SCHEDULE_ORIGINATION_TYPE to yield the ORIGINATION_TYPE meaning.

Documented 12.2.2 metadata lists additional referenced objects: INV_DECIMALS_PUB, INV_SALESORDER, MRP_OE, and OE_INSTALL packages, plus the MRP_* synonyms that resolve to the MRP base tables.

Key Columns

• CURRENT_QUANTITY — the current scheduled quantity for the MDS entry date; the primary quantity field for demand visibility.
• ORIGINAL_QUANTITY — the originally entered schedule quantity, useful for variance analysis against CURRENT_QUANTITY.
• SCHEDULE_DATE / END_DATE — the date range the entry applies to; for repetitive schedules, REPETITIVE_ITEM_DAILY_RATE carries the daily rate.
• ORIGINATION_TYPE — decoded lookup meaning describing how the entry was created (for example, sales order, forecast, manual).
• INVENTORY_ITEM_ID, ORGANIZATION_ID, SCHEDULE_NAME — item and schedule context.
• MDS_ENTRY_ID, FORECAST_ENTRY_ID, PLAN_SUPPLY_ID — surrogate identifiers for downstream joins.
• SOURCE_FORECAST_NAME, SOURCE_ORGANIZATION_ID, SOURCE_SCHEDULE_NAME, UNIT_NUMBER — source lineage for the demand.
• PROJECT_ID, TASK_ID, SALES_ORDER_LINE_ID, LINE_ID — project and order references.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Note that some column names in the published column list (aliases such as END_DATE, CURRENT_QUANTITY, ORIGINAL_QUANTITY, REPETITIVE_ITEM_DAILY_RATE, ORIGINATION_TYPE, MDS_ENTRY_ID) map to differently named underlying columns in the view text.

Common Use Cases and Queries

Typical uses include MDS demand reporting, reconciliation of current versus original scheduled quantities, and integration extracts feeding planning or BI layers. A representative query filters by organization and schedule and surfaces the quantity columns:

SELECT organization_id, inventory_item_id, schedule_name, schedule_date, current_quantity, original_quantity, repetitive_item_daily_rate, origination_type
FROM apps.mrpbv_mds_entries
WHERE organization_id = :org_id
AND schedule_date BETWEEN :start_date AND :end_date
ORDER BY inventory_item_id, schedule_date;

Variance and source analysis can compare quantities and trace demand origin:

SELECT schedule_name, inventory_item_id, schedule_date, current_quantity, original_quantity, (current_quantity - original_quantity) AS qty_variance, origination_type, source_schedule_name, unit_number
FROM apps.mrpbv_mds_entries
WHERE organization_id = :org_id
AND NVL(current_quantity,0) <> NVL(original_quantity,0);

Because the view is read-only and drives off MRP_SCHEDULE_DATES, queries should always constrain ORGANIZATION_ID (and, where relevant, SCHEDULE_NAME and SCHEDULE_DATE) to limit row counts. The view is a safe reporting construct; it must not be used for inserts or updates to MDS data.