Results for “mtl_user_supply”

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

Overview

MTL_USER_SUPPLY is an Oracle Inventory (INV) table that stores externally supplied information used by Oracle's Available-to-Promise (ATP) engine. Its documented purpose is to record "external supply information to be considered in ATP," meaning it allows planners and order management processes to factor in supply that originates outside the standard inventory, purchasing, or work-in-process flows. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the INV schema and is classified as VALID in the data dictionary. The table contains 13 documented columns and is keyed primarily by item and organization context.

From a data-vault modeling perspective, the mined foreign-key structure suggests MTL_USER_SUPPLY functions as a link entity. It connects an inventory item (via MTL_SYSTEM_ITEMS_B) and an organization (via MTL_PARAMETERS) to a polymorphic source reference (SOURCE_ID) that can resolve to purchase orders, WIP entities, GL code combinations, or generic dispositions depending on SOURCE_TYPE_ID. This many-to-many-style bridging behavior is characteristic of a link table rather than a pure hub or satellite.

Key Information Stored

The most significant columns capture item identity, organizational scope, supply source, and timing:

• ORGANIZATION_ID — Identifies the inventory organization in which the external supply is considered; foreign key to MTL_PARAMETERS.
• INVENTORY_ITEM_ID — The item for which external supply is declared; foreign key to MTL_SYSTEM_ITEMS_B.
• SOURCE_TYPE_ID — Classifies the supply source; foreign key to MTL_TXN_SOURCE_TYPES.
• SOURCE_ID — The polymorphic pointer to the originating document (PO_HEADERS_ALL, WIP_ENTITIES, GL_CODE_COMBINATIONS, or MTL_GENERIC_DISPOSITIONS).
• SOURCE_NAME — Human-readable label for the external source.
• PRIMARY_UOM_QUANTITY — The quantity of external supply expressed in the item's primary unit of measure; this is the ATP-relevant value.
• EXPECTED_DELIVERY_DATE — The date on which the external supply is anticipated, driving ATP time-phasing.
• DEMAND_CLASS — Categorizes the demand or supply class used in ATP and planning calculations.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns maintained by the WHO columns convention.

The documented metadata does not name a single surrogate primary key column beyond the audit set; identity is effectively established by the combination of ORGANIZATION_ID, INVENTORY_ITEM_ID, SOURCE_TYPE_ID, and SOURCE_ID. No explicit unique index is listed in the excerpt, so treat this composite as a business-key candidate.

Common Use Cases and Queries

Typical uses include ATP supply visibility, planning analysis, and reconciliation of external supply against source documents. A common query pattern joins the table to items and organizations:

• Reporting external supply by item and organization for a delivery window, filtering on EXPECTED_DELIVERY_DATE and summing PRIMARY_UOM_QUANTITY.
• Resolving the polymorphic SOURCE_ID by joining on SOURCE_TYPE_ID to the appropriate source table (PO_HEADERS_ALL for purchase orders, WIP_ENTITIES for work orders).
• Validating that DEMAND_CLASS and SOURCE_NAME align with planning policies.
• Auditing recently changed supply records using LAST_UPDATE_DATE for incremental ETL or BI extraction.

Sample pattern: SELECT organization_id, inventory_item_id, primary_uom_quantity, expected_delivery_date FROM mtl_user_supply WHERE expected_delivery_date BETWEEN :from_date AND :to_date ORDER BY expected_delivery_date;

Related Objects

The following objects are referenced or depended upon through the documented foreign keys:

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item definitions.
• MTL_PARAMETERS — joined on ORGANIZATION_ID for organization context.
• MTL_TXN_SOURCE_TYPES — joined on SOURCE_TYPE_ID to interpret the source classification.
• PO_HEADERS_ALL — one resolution target for SOURCE_ID when the supply originates from purchasing.
• WIP_ENTITIES — resolution target for SOURCE_ID when supply relates to work orders.
• GL_CODE_COMBINATIONS — resolution target for SOURCE_ID for accounting-related sources.
• MTL_GENERIC_DISPOSITIONS — resolution target for SOURCE_ID for disposition-based supply.

These relationships make MTL_USER_SUPPLY a connective link between ATP supply records and the transactional and master-data objects that define and originate that supply.