Results for “as_mrp_interface_lines”

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

Overview

The AS_MRP_INTERFACE_LINES table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores interface line information exchanged between Oracle Sales Management (OSM) and Material Requirements Planning (MRP), serving as the transactional bridge that conveys forecast and interest-related demand records into the planning engine. Each row represents a single interface line tied to a parent interface batch, carrying item, forecast date, quantity, confidence, and processing status attributes required for MRP consumption.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table hangs off a parent interface header (AS_MRP_INTERFACE) and references reference data such as AS_INTEREST_TYPES_B, indicating it captures descriptive, changing attributes recorded against a stable business key rather than acting as a pure hub or link. Modelers should treat it as a satellite candidate anchored to the interface header rather than a standalone integration entity.

Key Information Stored

The documented physical schema comprises 21 columns. The most significant are:

• LINE_SEQUENCE_ID — the surrogate primary key, enforced by AS_MRP_INTERFACE_LINES_PK and also the sole column in unique index AS_MRP_INTERFACE_LINES_U1, making it the business-key candidate as well.
• SEQUENCE_ID — foreign key to AS_MRP_INTERFACE, tying the line to its parent interface batch.
• INTEREST_TYPE_ID — foreign key to AS_INTEREST_TYPES_B, classifying the demand interest.
• PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID — primary and secondary interest class codes.
• ITEM_ID and PF_ITEM_ID — the inventory item and planning item references for the forecast line.
• FORECAST_DATE and FORECAST_UPSIDE_FLAG — the forecast bucket date and upside indicator.
• QUANTITY and UOM — the forecast quantity and its unit of measure.
• CONFIDENCE_PERCENTAGE — the confidence weighting applied to the forecast.
• PROCESS_STATUS, ERROR_MESSAGE, and COMMENTS — processing outcome, failure diagnostics, and free-text remarks.
• TRANSACTION_ID — the associated transaction identifier.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases center on monitoring forecast feed health into MRP, diagnosing failed interface rows, and reporting forecasted demand by item or date. Common query patterns join the lines to the parent header to retrieve batch context, and filter on PROCESS_STATUS to isolate errors:

• Retrieve all lines for a given interface batch:
  SELECT l.* FROM as_mrp_interface_lines l WHERE l.sequence_id = :batch_id;
• Identify failed or pending lines and their diagnostics:
  SELECT line_sequence_id, item_id, forecast_date, quantity, error_message FROM as_mrp_interface_lines WHERE process_status = 'ERROR';
• Aggregate forecasted quantities by item for a date range:
  SELECT item_id, SUM(quantity) FROM as_mrp_interface_lines WHERE forecast_date BETWEEN :from AND :to GROUP BY item_id;
• Validate confidence-weighted upside forecasts using FORECAST_UPSIDE_FLAG and CONFIDENCE_PERCENTAGE.

Related Objects

Several objects reference or depend on this table through documented relationships:

• AS_MRP_INTERFACE — parent header table; joined on AS_MRP_INTERFACE_LINES.SEQUENCE_ID = AS_MRP_INTERFACE.SEQUENCE_ID.
• AS_INTEREST_TYPES_B — interest type reference; joined on INTEREST_TYPE_ID.
• AS_MRP_INTERFACE_LINES_PK — the primary key constraint on LINE_SEQUENCE_ID.
• AS_MRP_INTERFACE_LINES_U1 — the unique index on LINE_SEQUENCE_ID.
• Inventory and MRP planning tables referenced indirectly through ITEM_ID and PF_ITEM_ID.