Results for “mrp_schedule_interface”

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

Overview

The MRP.MRP_SCHEDULE_INTERFACE table is a staging and open-interface table within the Oracle E-Business Suite Master Scheduling/MRP module. It serves as the designated landing zone for master production schedule records originating from external systems — including legacy planning engines, partner supply-chain applications, and custom integrations — that must be loaded into Oracle's planning and scheduling repositories. Rows inserted here are consumed by concurrent programs in the MRP product, which validate, transform, and ultimately apply the schedule entries to the active master schedule designator and organization.

The table carries a heuristic Data Vault classification of link. This reflects the fact that its primary role is to associate business entities — an inventory item within an organization, a schedule designator, and (optionally) a work-in-process line and project — rather than to own descriptive master data. A Data Vault modeler would likely implement this as a link table anchored on the item/organization/schedule-designator combination, with satellite structures carrying the transactional quantity and date attributes.

Key Information Stored

The table contains 43 documented columns. The most operationally significant are:

• INVENTORY_ITEM_ID and ORGANIZATION_ID — foreign-key pair identifying the item and the inventory organization for which the schedule entry applies. Both reference MTL_SYSTEM_ITEMS_B.
• SCHEDULE_DESIGNATOR — the master schedule designator under which the entry is recorded; foreign key to MRP_SCHEDULE_DESIGNATORS (with ORGANIZATION_ID).
• SCHEDULE_DATE, NEW_SCHEDULE_DATE, RATE_END_DATE, and NEW_RATE_END_DATE — the effective dating of the schedule entry and any revised dating proposed by the source system.
• SCHEDULE_QUANTITY — the scheduled quantity for the item at the given date.
• LINE_ID — foreign key to WIP_LINES, linking the schedule entry to a discrete manufacturing line where applicable.
• PROCESS_STATUS, ERROR_MESSAGE, and SOURCE_CODE — the processing state of the row, validation failure text, and the source of the record.
• ACTION — the interface action to be taken (for example insert/update/delete semantics).
• TRANSACTION_ID and SOURCE_LINE_ID — traceability back to the originating transaction on the source system.

The documented schema does not enumerate a single-column surrogate primary key. Business-key candidates are the composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, and SCHEDULE_DESIGNATOR, together with the schedule date and transaction identifiers. Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the standard ATTRIBUTE1–ATTRIBUTE15 DFF columns are present, along with PROJECT_ID and TASK_ID for project-aware scheduling.

Common Use Cases and Queries

Typical usage centres on integration monitoring and pre-load validation. A planner or support analyst checks whether inbound schedule records have been accepted or rejected before submitting the consuming concurrent program:

• Listing unprocessed rows: SELECT * FROM MRP_SCHEDULE_INTERFACE WHERE PROCESS_STATUS IS NULL OR PROCESS_STATUS = 'ERROR';
• Diagnosing failures: filtering on ERROR_MESSAGE to surface validation exceptions for items or designators.
• Reconciling an external feed: joining TRANSACTION_ID and SOURCE_LINE_ID back to the source system's staging records.
• Reporting scheduled quantities by date: aggregating SCHEDULE_QUANTITY by SCHEDULE_DATE, ORGANIZATION_ID, and SCHEDULE_DESIGNATOR.

Because this is an interface table, rows are typically transient — purged after successful processing — and it should not be treated as a historical reporting source.

Related Objects

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item attributes.
• MRP_SCHEDULE_DESIGNATORS — joined on SCHEDULE_DESIGNATOR and ORGANIZATION_ID for designator definition.
• WIP_LINES — joined on LINE_ID for production line context.
• MRP_SCHEDULE_INTERFACE processing concurrent programs and the MRP master schedule loaders consume these rows.
• Project tables (PROJECT_ID, TASK_ID) referenced where project manufacturing is enabled.