Search Results mrp_schedule_interface




Overview
Explore in AI Chat

Overview

The MRP_SCHEDULE_INTERFACE table is a critical data interface within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It functions as a staging area for importing master schedule entries from external systems or legacy data sources. Its primary role is to facilitate the bulk loading of schedule data, which is subsequently validated and processed by Oracle's concurrent programs to populate the core master production schedule (MPS) and material requirements planning (MRP) tables. This interface-driven approach ensures data integrity, allows for error correction prior to final import, and is a standard pattern for high-volume data migration and integration in Oracle EBS.

Key Information Stored

The table stores transactional records representing planned supply. While the full column list is extensive, the core fields, as indicated by its foreign key relationships, include identifiers for the item, organization, and schedule. Essential columns typically include a unique transaction identifier (TRANSACTION_ID), the INVENTORY_ITEM_ID, ORGANIZATION_ID, and SCHEDULE_DESIGNATOR to define the schedule context. It also holds key schedule attributes such as the SCHEDULE_DATE, QUANTITY, and SCHEDULE_GROUP_ID for grouping related entries. Each record maintains a PROCESS_STATUS flag (e.g., 'PENDING', 'RUNNING', 'ERROR', 'COMPLETE') to manage the interface workflow, and an ERROR_CODE column to capture validation failures.

Common Use Cases and Queries

The predominant use case is the automated population of the master schedule from an external planning system or during an implementation data conversion. A standard operational pattern involves inserting records with a PROCESS_STATUS of 'PENDING' and then submitting the "Master Schedule/MRP Planning Manager" or "Load Schedule from Open Interface" concurrent request to process them. Common diagnostic queries include checking for pending or errored records. For example:

  • To identify pending interface lines: SELECT transaction_id, inventory_item_id, schedule_date, quantity FROM mrp_schedule_interface WHERE process_status = 'PENDING' AND organization_id = :org_id;
  • To analyze import errors: SELECT transaction_id, error_code, last_update_date FROM mrp_schedule_interface WHERE process_status = 'ERROR';
  • To purge successfully processed records: DELETE FROM mrp_schedule_interface WHERE process_status = 'COMPLETE'; (Typically executed via a standard concurrent program).

Related Objects

As documented in the provided ETRM metadata, MRP_SCHEDULE_INTERFACE has defined foreign key relationships with several foundational EBS tables, ensuring referential integrity for key attributes:

  • MTL_SYSTEM_ITEMS_B: Validates that the INVENTORY_ITEM_ID and ORGANIZATION_ID in the interface correspond to a valid item in the inventory master.
  • MRP_SCHEDULE_DESIGNATORS: Validates that the SCHEDULE_DESIGNATOR and ORGANIZATION_ID correspond to a defined master schedule.
  • WIP_LINES: Validates that the LINE_ID (if populated for a line-specific schedule) is a valid manufacturing line.

Successful processing by the interface concurrent programs moves data into core planning tables such as MRP_SCHEDULE and MRP_FORECAST_DATES. The standard API for loading this interface is MRP_SCHEDULE_PUB, which provides PL/SQL procedures for controlled data insertion.