Results for “mtl_supply”

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

Overview

MTL_SUPPLY is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores incoming supply information. It functions as a consolidated staging and planning repository for anticipated receipts, tracking quantities that are expected to arrive into an organization from both internal and external sources. Records in this table represent supply that has not yet been received into stock but is expected based on open purchasing documents, requisitions, in-transit inter-org transfers, and receiving events.

Because MTL_SUPPLY serves as a junction between supply-generating documents (purchase orders, requisitions, receiving transactions, inter-org transfers) and the planning engine's supply picture, the heuristic Data Vault classification mined from its foreign-key structure is link. This classification is a modeling suggestion: the table's composite primary key and its role as a connector between many parent entities align with link semantics rather than pure hub or satellite behavior.

The table is owned by the INV schema and contains 48 documented columns. Its composite primary key, MTL_SUPPLY_PK, is defined on SUPPLY_TYPE_CODE and SUPPLY_SOURCE_ID.

Key Information Stored

Each row identifies a discrete unit of incoming supply, keyed by the combination of the supply type classification and the source document identifier. The most operationally significant columns include:

• SUPPLY_TYPE_CODE and SUPPLY_SOURCE_ID — the composite primary key that distinguishes the origin of a supply record (for example, PO, requisition, or receiving transaction) and ties it to the originating document identifier.
• ITEM_ID and ITEM_REVISION — the inventory item and its revision receiving the supply.
• QUANTITY, UNIT_OF_MEASURE and TO_ORG_PRIMARY_QUANTITY, TO_ORG_PRIMARY_UOM — the expected quantity in the source UOM and its conversion to the destination organization's primary UOM.
• RECEIPT_DATE, NEED_BY_DATE, EXPECTED_DELIVERY_DATE — the temporal drivers used by planning to schedule supply availability.
• FROM_ORGANIZATION_ID, FROM_SUBINVENTORY, TO_ORGANIZATION_ID, TO_SUBINVENTORY — the source and destination stocking locations for internal supply.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — concurrent program context identifying the process that created or last refreshed the record.
• CHANGE_FLAG and CHANGE_TYPE — indicators supporting incremental refresh and synchronization logic.
• EXCLUDE_FROM_PLANNING — a flag allowing specific supply records to be suppressed from MRP planning consideration.

Audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY and LAST_UPDATE_DATE are present but are standard WHO columns rather than business-key candidates. The primary composite key is the sole unique identifier documented; additional candidate keys are not enumerated in the available metadata.

Common Use Cases and Queries

MTL_SUPPLY is consulted heavily by the MRP/MPS planning engine, by supply-and-demand reporting, and by custom reconciliation extracts. Typical usage includes verifying expected receipts against open purchase orders, checking in-transit inter-org balances, and diagnosing planning discrepancies where expected supply did not appear in the netting calculation.

SELECT s.item_id, s.supply_type_code, s.quantity,
       s.expected_delivery_date, s.to_organization_id
FROM   mtl_supply s
WHERE  s.to_organization_id = :org_id
  AND  NVL(s.exclude_from_planning, 'N') = 'N'
ORDER BY s.expected_delivery_date;

Because MTL_SUPPLY is populated and maintained by concurrent programs, records carry REQUEST_ID, PROGRAM_ID and PROGRAM_APPLICATION_ID, enabling support teams to trace which process wrote a given supply row. The CHANGE_FLAG column supports delta queries for reporting layers that only extract modified rows. Reports frequently join MTL_SUPPLY to MTL_SYSTEM_ITEMS_B for descriptions and to MTL_PARAMETERS for organization context.

Related Objects

MTL_SUPPLY participates in an extensive foreign-key network. The most significant related objects and their join columns are:

• PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL — joined via PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID and PO_DISTRIBUTION_ID, providing the purchasing document chain behind external supply.
• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — joined via REQ_HEADER_ID and REQ_LINE_ID for requisition-sourced supply.
• RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES and RCV_TRANSACTIONS — joined via SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID and RCV_TRANSACTION_ID, linking supply to receiving activity.
• MTL_SYSTEM_ITEMS_B — joined via ITEM_ID (and TO_ORGANIZATION_ID) for item master attributes.
• MTL_PARAMETERS — joined via TO_ORGANIZATION_ID, INTRANSIT_OWNING_ORG_ID and MRP_TO_ORGANIZATION_ID for organization definition.
• MTL_SECONDARY_INVENTORIES — joined via FROM_SUBINVENTORY and TO_SUBINVENTORY to resolve subinventory names.
• MTL_INTERORG_PARAMETERS — joined via FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID to validate inter-org transfer relationships.
• MTL_ITEM_REVISIONS_B, MTL_ITEM_LOCATIONS, MTL_CATEGORIES_B — supporting reference joins for revisions, locators and categories.