Search Results mtl_supply




Overview
Explore in AI Chat

Overview

The MTL_SUPPLY table is a core transactional table within the Oracle E-Business Suite Inventory (INV) module. Its primary role is to serve as a central repository for storing detailed information about all incoming supply for an organization. This table is fundamental to the supply chain and material planning processes, acting as a unified source for data related to requisitions, purchase orders, inter-organization transfers, and receiving transactions. By consolidating this information, MTL_SUPPLY enables critical EBS functions such as Available-to-Promise (ATP) checks, supply-demand matching in planning engines like MRP, and providing visibility into the inbound supply pipeline.

Key Information Stored

The table's structure is defined by a composite primary key on SUPPLY_TYPE_CODE and SUPPLY_SOURCE_ID, which classifies and uniquely identifies each supply line. Key columns include identifiers for the item (ITEM_ID), revision (ITEM_REVISION), and category (CATEGORY_ID). It stores organizational context with FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID, as well as subinventory details (FROM_SUBINVENTORY, TO_SUBINVENTORY). Crucially, it holds foreign keys to the source transactional documents, such as REQ_LINE_ID, PO_LINE_ID, PO_DISTRIBUTION_ID, SHIPMENT_LINE_ID, and RCV_TRANSACTION_ID. Additional columns track quantities, dates, and planning parameters like MRP_TO_ORGANIZATION_ID, linking supply to specific planning contexts.

Common Use Cases and Queries

A primary use case is generating reports on open purchase order receipts. A typical query would join MTL_SUPPLY to PO_HEADERS_ALL and MTL_SYSTEM_ITEMS_B to list pending quantities. For ATP inquiries, the table is queried to sum all scheduled receipts for a specific item and organization within a given time fence. In support of inter-organization transfers, queries often join MTL_SUPPLY to MTL_INTERORG_PARAMETERS to validate transfer rules. A common pattern is to filter by SUPPLY_TYPE_CODE (e.g., 'PO', 'REQ', 'SHIPMENT') and a status to find active supply lines. For example:

  • SELECT ms.item_id, ms.primary_quantity, ms.expected_delivery_date FROM mtl_supply ms WHERE ms.to_organization_id = :p_org_id AND ms.supply_type_code = 'PO' AND ms.primary_quantity > 0;

Related Objects

As indicated by its extensive foreign key relationships, MTL_SUPPLY is a central hub connecting Inventory with Purchasing (PO) and Receiving (RCV) modules. Key related tables include PO_REQUISITION_LINES_ALL, PO_LINES_ALL, PO_DISTRIBUTIONS_ALL, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. It maintains referential integrity with master data tables like MTL_SYSTEM_ITEMS_B, MTL_CATEGORIES_B, and MTL_SECONDARY_INVENTORIES. For organizational and parameter context, it references MTL_PARAMETERS and MTL_INTERORG_PARAMETERS. This dense network of relationships underscores its role as the definitive record for inbound supply within the Oracle EBS architecture.