Results for “current_forecast_quantity”

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

Overview

MRPBV_FORECAST_ENTRIES is a read-only view owned by the APPS schema in Oracle E-Business Suite, classified under the MRP – Master Scheduling/MRP product family. It is documented in ETRM as a retrofitted object, meaning it was introduced or re-pointed to support backward compatibility with earlier releases of the application while the underlying forecast entry model evolved. In 12.1.1 and 12.2.2 the view exposes forecast date records maintained by Oracle Master Demand Schedule and Master Production Schedule processing, presenting them in a denormalized, reporting-friendly form.

The view is primarily a presentation layer: it wraps the base table MRP_FORECAST_DATES and renames several columns through its column aliases, while embedding flexible-attribute style references for lookup-driven fields. Its role is to provide external reports, custom concurrent programs, and integration interfaces with a stable, descriptive projection of forecast entries without requiring direct access to the transactional base table.

Underlying Base Objects

The view is defined exclusively over the single base object MRP_FORECAST_DATES, referenced in the view text through the alias FO. The synonym resolves to the APPS-owned table in the MRP schema. Because the view is defined WITH READ ONLY, no DML can be issued against it; inserts, updates, and deletions must target the base table or use supported Oracle forecasting APIs.

Two of the projected columns are not simple column references but lookup descriptors: "_LA:FO.BUCKET_TYPE:MFG_LOOKUPS:MRP_BUCKET_TYPE:MEANING" and "_LA:FO.ORIGINATION_TYPE:MFG_LOOKUPS:MRP_FORECAST_ORIG:MEANING". These are exposed as BUCKET_TYPE and ORIGINATION_TYPE attributes whose values are derived from the MFG_LOOKUPS table using the MRP_BUCKET_TYPE and MRP_FORECAST_ORIG lookup types respectively.

Key Columns

• FORECAST_NAME – forecast designator identifying the forecast or schedule set.
• "_LA:BUCKET_TYPE" – bucket type meaning from MFG_LOOKUPS (MRP_BUCKET_TYPE).
• FORECAST_DATE – the date on which the forecast quantity applies.
• END_DATE – rate end date for the forecast entry bucket.
• CURRENT_FORECAST_QUANTITY / ORIGINAL_FORECAST_QUANTITY – current and originally entered forecast quantities.
• CONFIDENCE_PERCENT – confidence percentage associated with the entry.
• "_LA:ORIGINATION_TYPE" – origination type meaning from MFG_LOOKUPS (MRP_FORECAST_ORIG).
• DEMAND_CLASS – demand class assigned to the forecast entry.
• END_PLANNING_BOM_PERCENT – the BOM planning percent applied to the end item.
• FORECAST_ENTRY_ID – unique identifier of the forecast entry record (TRANSACTION_ID in the base table).
• ORGANIZATION_ID, INVENTORY_ITEM_ID – owning organization and inventory item.
• END_ITEM_ID, FORECAST_RULE_ID, PROJECT_ID, TASK_ID, LINE_ID – associated end item, forecast rule, project, task, and line references.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Report writers use this view to list forecast entries with their lookup meanings already resolved, for example to review bucket types and origination types without joining MFG_LOOKUPS separately. A typical query is:

• SELECT FORECAST_NAME, FORECAST_DATE, END_DATE, CURRENT_FORECAST_QUANTITY, "_LA:BUCKET_TYPE" BUCKET_TYPE, "_LA:ORIGINATION_TYPE" ORIGINATION_TYPE, DEMAND_CLASS, END_PLANNING_BOM_PERCENT FROM MRPBV_FORECAST_ENTRIES WHERE ORGANIZATION_ID = :org AND INVENTORY_ITEM_ID = :item ORDER BY FORECAST_DATE;

This supports demand-versus-forecast analysis, item-level forecast review, and interfaces that populate planning systems. Because the view is read-only, any corrective maintenance must be directed to the underlying forecast data through the standard MRP forecast maintenance forms rather than through SQL.