Search Results mtl_user_supply




Overview
Explore in AI Chat

Overview

The MTL_USER_SUPPLY table is a core data structure within the Oracle E-Business Suite Inventory (INV) module, specifically for releases 12.1.1 and 12.2.2. It serves as a repository for manually entered or externally managed supply information that must be factored into Available-to-Promise (ATP) calculations. Unlike supply generated automatically from transactions within Purchasing (PO) or Work in Process (WIP), this table allows planners to define supplemental supply streams, such as consigned stock or third-party vendor-managed inventory, ensuring ATP inquiries reflect a complete picture of material availability.

Key Information Stored

The table's primary function is to define a supply record linked to a specific item and organization. Its critical foreign key relationships reveal the key data points stored. Each record is anchored by INVENTORY_ITEM_ID and ORGANIZATION_ID, linking it to the item master (MTL_SYSTEM_ITEMS_B). The SOURCE_TYPE_ID column, referencing MTL_TXN_SOURCE_TYPES, categorizes the nature of the external supply. The SOURCE_ID column is a dynamic foreign key, whose referenced table (e.g., PO_HEADERS_ALL, WIP_ENTITIES, MTL_GENERIC_DISPOSITIONS) depends on the source type, pointing to the specific external document or entity. Additional columns, implied by the foreign key to GL_CODE_COMBINATIONS, would store accounting information for the supply transaction.

Common Use Cases and Queries

The primary use case is the creation and maintenance of user-defined supply for ATP. A common operational query involves reviewing all active external supply for a critical component. A sample SQL pattern is:

  • SELECT mus.inventory_item_id, msi.segment1 item_code, mus.organization_id, mus.source_type_id, mus.source_id, mus.quantity FROM inv.mtl_user_supply mus, inv.mtl_system_items_b msi WHERE mus.inventory_item_id = msi.inventory_item_id AND mus.organization_id = msi.organization_id AND msi.segment1 = '&ITEM_CODE';

This data is critical for ATP-driven processes in Order Management and Planning. During an ATP check, the engine aggregates supply from standard sources and the MTL_USER_SUPPLY table to compute accurate availability dates. Reporting use cases include auditing manually overridden supply quantities and analyzing the impact of external supply on fulfillment commitments.

Related Objects

MTL_USER_SUPPLY is centrally connected to several key EBS tables via foreign key constraints. Its definition is validated against the item master (MTL_SYSTEM_ITEMS_B) and organization parameters (MTL_PARAMETERS). The polymorphic SOURCE_ID links it to various transaction source entities, including purchase orders (PO_HEADERS_ALL), jobs (WIP_ENTITIES), and generic dispositions (MTL_GENERIC_DISPOSITIONS). The SOURCE_TYPE_ID is validated by MTL_TXN_SOURCE_TYPES, and it holds accounting references via GL_CODE_COMBINATIONS. This table is directly read by the ATP engine and is often accessed through Inventory and Planning APIs for data maintenance.