Results for “confidence_percentage”

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

Overview

MRP_FORECAST_INTERFACE is a staging (interface) table owned by the MRP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exists to accept forecast records from external sources — typically flat files, spreadsheets, or third-party planning systems — and feed them into the Oracle Master Scheduling/MRP forecast engine for validation and loading into the master forecast tables. Records inserted here are processed by the Forecast Load concurrent program, which validates each row, applies business rules, and either promotes the record into the working forecast or writes a failure reason back to the interface row.

Because the table is transient in nature, it holds data only for the duration of a load cycle. Successful rows are typically purged or archived after processing, while failed rows remain with a populated ERROR_MESSAGE column for correction and resubmission.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is best modeled as a link. It resolves multiple business concepts — item, organization, forecast designator, forecast date, and optionally project/task and WIP line — into a single association row, which is the classic signature of a link entity rather than a hub or satellite.

Key Information Stored

The table contains 44 documented columns. The most significant for integration and reporting purposes are:

• INVENTORY_ITEM_ID and ORGANIZATION_ID — together they identify the item/organization combination the forecast applies to; foreign key to MTL_SYSTEM_ITEMS_B.
• FORECAST_DESIGNATOR — the forecast definition (e.g., MPS, DRP); foreign key to MRP_FORECAST_DESIGNATORS with ORGANIZATION_ID.
• FORECAST_DATE and FORECAST_END_DATE — the bucket start and end dates for which quantity is being loaded.
• QUANTITY — the forecast quantity for that bucket.
• CONFIDENCE_PERCENTAGE — the weight applied to the forecast.
• BUCKET_TYPE and WORKDAY_CONTROL — control how the load program interprets the date range.
• PROCESS_STATUS — the load outcome (e.g., pending, processed, error).
• ERROR_MESSAGE — text describing why a row failed validation; the primary diagnostic column.
• TRANSACTION_ID — foreign key to MRP_FORECAST_DATES, linking to the forecast date group.
• SOURCE_CODE and SOURCE_LINE_ID — traceability back to the originating system.
• LINE_ID — foreign key to WIP_LINES when the forecast is tied to a repetitive line.
• PROJECT_ID and TASK_ID — optional project/task association for project-driven forecasts.
• REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — identify the concurrent request that processed the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield storage.

No separate surrogate primary key is documented; the row is functionally identified by the combination of item, organization, designator, and forecast date, making those the natural business-key candidates.

Common Use Cases and Queries

The most common requirement is to load a forecast from an external file and then verify the result. A typical query would join the interface to the item master to resolve descriptions and to the designator table to identify the forecast:

SELECT mfi.organization_id, msi.segment1, mfi.forecast_designator, mfi.forecast_date, mfi.quantity, mfi.process_status, mfi.error_message FROM mrp.mrp_forecast_interface mfi JOIN mtl_system_items_b msi ON msi.inventory_item_id = mfi.inventory_item_id AND msi.organization_id = mfi.organization_id WHERE mfi.request_id = :request_id;

Failed rows are routinely extracted for correction: SELECT * FROM mrp.mrp_forecast_interface WHERE process_status = 'ERROR'. Because the table is transient, developers should not rely on it for historical reporting — the production forecast lives in the MRP forecast tables once the load succeeds. Interface rows are also useful for reconciliation, confirming that the number of rows submitted equals the number processed.

Related Objects

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for the item definition.
• MRP_FORECAST_DESIGNATORS — joined on FORECAST_DESIGNATOR and ORGANIZATION_ID to resolve the forecast name.
• MRP_FORECAST_DATES — joined on TRANSACTION_ID to obtain date-group context.
• WIP_LINES — joined on LINE_ID for repetitive manufacturing forecasts.
• MRP_FORECAST_ITEMS / MRP_FORECAST_UPDATES — the target forecast tables populated by the Forecast Load program.
• WIP_LINES, FND_CONCURRENT_REQUESTS — used with REQUEST_ID for load diagnostics.