Search Results mtl_forecast_rules




Overview
Explore in AI Chat

Overview

The MRP_FORECAST_DATES table is a core transactional data store within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the primary repository for detailed forecast entries, which are the fundamental time-phased demand data used by the planning engine. This table holds the disaggregated forecast quantities for specific items, organizations, and dates, forming the basis for generating master production schedules and material requirements plans. Its existence is critical for translating high-level forecast summaries into actionable, date-specific planned demand that drives procurement and production activities.

Key Information Stored

The table's primary key is TRANSACTION_ID, uniquely identifying each forecast date entry. Its structure is defined by key foreign key relationships that contextualize the forecast data. Essential columns include FORECAST_RULE_ID, linking to the aggregation and disaggregation rules in MTL_FORECAST_RULES. The item and organizational context is established through INVENTORY_ITEM_ID, ORGANIZATION_ID, and FORECAST_DESIGNATOR, linking to MRP_FORECAST_ITEMS and MRP_FORECAST_DESIGNATORS. For end-item forecasts, END_ITEM_ID is populated. The table also captures sourcing details via LINE_ID (from WIP_LINES) and source forecast information (SOURCE_FORECAST_DESIGNATOR, SOURCE_ORGANIZATION_ID). While the specific quantity and date columns are not listed in the provided metadata, this table typically stores the forecast quantity and its corresponding bucket date (e.g., FORECAST_DATE, CURRENT_FORECAST_QUANTITY).

Common Use Cases and Queries

This table is central to forecast analysis, adjustment, and planning execution. Common operational and reporting use cases include analyzing forecast consumption, auditing forecast accuracy by comparing entries to actual sales, and troubleshooting planning results. Data is typically inserted or updated via the MRP Forecast Interface (MRP_FORECAST_INTERFACE) or through the application's forecast maintenance forms. A fundamental query pattern retrieves forecast details for a specific item and designator:

  • SELECT transaction_id, forecast_date, current_forecast_quantity
  • FROM mrp_forecast_dates
  • WHERE inventory_item_id = 12345
  • AND organization_id = 101
  • AND forecast_designator = 'GLOBAL_FCAST'
  • ORDER BY forecast_date;

Another critical use case involves tracing the source of forecast entries, leveraging the SOURCE_FORECAST_DESIGNATOR and SOURCE_ORGANIZATION_ID columns to understand forecast propagation across organizations.

Related Objects

As indicated by its foreign keys, MRP_FORECAST_DATES is a central hub within the forecast data model. It is directly dependent on master data tables such as MRP_FORECAST_ITEMS, MRP_FORECAST_DESIGNATORS, MTL_FORECAST_RULES, and WIP_LINES. It is the primary source table for the MRP_SCHEDULE_DATES table, which consumes forecast data to generate the planned order schedule (the FORECAST_ID in MRP_SCHEDULE_DATES references the TRANSACTION_ID). Furthermore, it is the target for data integration via MRP_FORECAST_INTERFACE and for batch updates via MRP_FORECAST_UPDATES. Any custom reporting or integration involving detailed forecast quantities will invariably query this table.