Results for “as_mrp_interface_lines_v”

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

Overview

AS_MRP_INTERFACE_LINES_V is a reporting and integration view in the Oracle E-Business Suite Sales Foundation (AS) product family. It exposes the line-level detail of forecast data staged for consumption by Oracle Manufacturing Resource Planning (MRP) and, by extension, Advanced Supply Chain Planning. The view joins the MRP interface header table to its line table and resolves several foreign key identifiers into descriptive values, providing a denormalized, human-readable projection of forecast interface data.

The object resides in the schema associated with the Sales Foundation module and is documented as not implemented in the ETRM reference database, meaning the view is delivered by the application but may not be present in every environment. The view is read-oriented: it does not itself transform or validate data, but presents the current state of the interface staging tables, including processing status and error diagnostics, for review by planners and integration developers. The specific column FORECAST_UPSIDE_FLAG, referenced in the user's search, is exposed directly by this view and identifies whether a given forecast line represents upside potential rather than committed demand.

Underlying Base Objects

The view is defined over the following documented objects:

• AS_MRP_INTERFACE_LINES — the primary line-level staging table, aliased INTFLINES; supplies all line attributes and the driving ROWID.
• AS_MRP_INTERFACE — the header table, aliased INTF; joined on SEQUENCE_ID to supply ORGANIZATION_ID and FORECAST_DESIGNATOR.
• AS_INTEREST_TYPES_VL — aliased INTTYPE; outer-joined on INTEREST_TYPE_ID to resolve the interest type description.
• AS_INTEREST_CODES_VL — aliased INTCODE1 and INTCODE2; outer-joined twice on PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID respectively to resolve interest code values.

The join between the line and header tables is mandatory (inner join on SEQUENCE_ID), while the three descriptive lookups use outer joins, ensuring that lines with unpopulated or invalid interest references are still returned. All three lookup tables are "_VL" views, indicating they expose translated, language-specific descriptive columns.

Key Columns

• LINE_SEQUENCE_ID / SEQUENCE_ID — surrogate keys for the line and its parent interface header, respectively.
• ORGANIZATION_ID — the inventory organization for which the forecast is staged.
• FORECAST_DESIGNATOR — the forecast set identifier carried from the header.
• INTEREST_TYPE / PRIMARY_INTEREST_CODE / SECONDARY_INTEREST_CODE — descriptive classification of the forecast line.
• PF_ITEM_ID / ITEM_ID — the planning item and the inventory item identifiers for the forecast line.
• FORECAST_DATE — the date on which the forecasted quantity is applicable.
• FORECAST_UPSIDE_FLAG — indicates whether the line represents upside (uncommitted, best-case) demand as opposed to firm demand.
• QUANTITY — the forecasted quantity for the item and date.
• CONFIDENCE_PERCENTAGE — the planner-supplied confidence applied to the forecasted quantity.
• PROCESS_STATUS / ERROR_MESSAGE — the staging status of the line and any diagnostic text produced when the line failed validation or consumption.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is most frequently used to monitor the contents and health of the MRP forecast interface before and after a planning run, and to isolate upside forecast lines for targeted analysis.

Listing pending or errored forecast interface lines for an organization:

• SELECT line_sequence_id, item_id, forecast_date, quantity, forecast_upside_flag, process_status, error_message FROM as_mrp_interface_lines_v WHERE organization_id = :org_id AND process_status <> 'PROCESSED';

Isolating upside forecast lines for a forecast designator:

• SELECT item_id, forecast_date, quantity, confidence_percentage FROM as_mrp_interface_lines_v WHERE forecast_designator = :designator AND forecast_upside_flag = 'Y' ORDER BY forecast_date, item_id;

Summarizing forecasted quantity by interest type and upside status:

• SELECT interest_type, forecast_upside_flag, SUM(quantity) total_qty FROM as_mrp_interface_lines_v GROUP BY interest_type, forecast_upside_flag;

Because the view performs no aggregation or filtering, it can be queried directly for reconciliation against the base staging tables, and its descriptive columns make it suitable for building planner-facing reports without additional lookup joins.