Results for “mtl_consumption_definition_v”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MTL_CONSUMPTION_DEFINITION_V is a PL/SQL view owned by the APPS schema within Oracle E-Business Suite. It is categorized under the Inventory (INV) product family and is documented as supporting the consumption setup forms. In functional terms, the view exposes the consumption definition configuration maintained for the Inventory module, including transaction types, organization and subinventory context, locator routing, item qualification, and consignment or Vendor Managed Inventory (VMI) flags.
The view does not store data itself. It is a denormalized, join-driven presentation layer constructed over MTL_CONSUMPTION_DEFINITION and a set of reference objects, translating internal identifiers into human-readable business attributes. Because it is exposed in the APPS schema, it is available to reporting tools, custom concurrent programs, and integration interfaces without requiring direct navigation of the underlying base tables. The view is marked VALID in the documented metadata, indicating its dependencies are compiled and intact.
Underlying Base Objects
The documented base objects for this view are MTL_CONSUMPTION_DEFINITION (synonym), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_KFV (synonym), MTL_TRANSACTION_TYPES (synonym), PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), and FND_GLOBAL (package, referenced in the broader object registry).
The driving entity is MTL_CONSUMPTION_DEFINITION (aliased MCD), which supplies the consumption setup rows, including organization, subinventory, locator, item, and consumption flags. MTL_PARAMETERS (MP) is joined on ORGANIZATION_ID to resolve ORGANIZATION_CODE. MTL_SYSTEM_ITEMS_KFV (MSIT) supplies the CONCATENATED_SEGMENTS value used as the ITEM column, resolved on ORGANIZATION_ID and INVENTORY_ITEM_ID. MTL_TRANSACTION_TYPES (MTT) provides the TRANSACTION_TYPE_NAME for the referenced TRANSACTION_TYPE_ID.
Vendor information is resolved through two outer-joined pairs. PO_VENDORS and PO_VENDOR_SITES_ALL are joined twice: once via PLANNING_ORGANIZATION_ID against VENDOR_SITE_ID, producing the PLANNING_PARTY concatenation, and again via OWNING_ORGANIZATION_ID, producing the OWNING_PARTY concatenation. All optional joins are outer joins, allowing consumption definitions to exist even when the item, organization, or party attributes are not fully populated.
Key Columns
The view exposes the following significant columns:
- TRANSACTION_TYPE_NAME / TRANSACTION_TYPE_ID — The transaction type associated with the consumption definition, resolved from MTL_TRANSACTION_TYPES.
- ORGANIZATION_CODE / ORGANIZATION_ID — The inventory organization in which the consumption setup applies, with the code resolved from MTL_PARAMETERS.
- SUBINVENTORY_CODE / XFER_SUBINVENTORY_CODE — The source and transfer destination subinventories.
- FROM_LOCATOR_ID / TO_LOCATOR_ID — Locator routing for the consumption transaction.
- INVENTORY_ITEM_ID / ITEM — The item identifier and its concatenated segment description.
- PLANNING_ORGANIZATION_ID / PLANNING_PARTY — The planning entity, presented as vendor name concatenated with vendor site code.
- OWNING_ORGANIZATION_ID / OWNING_PARTY — The owning entity, similarly presented as vendor name and site code.
- CONSUME_CONSIGNED_FLAG / CONSUME_VMI_FLAG — Indicators controlling whether consigned or Vendor Managed Inventory stock is consumed.
- WEIGHT, ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — Descriptive flexfield and weighting attributes carried from the base table.
- Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and ROW_ID.
Common Use Cases and Queries
The view is typically used to report and validate consumption configuration across organizations, and to drive custom integrations that reference transaction type and party details without manually joining the vendor and transaction type tables. A representative query follows:
SELECT ORGANIZATION_CODE, SUBINVENTORY_CODE, TRANSACTION_TYPE_NAME, ITEM, PLANNING_PARTY, OWNING_PARTY, CONSUME_CONSIGNED_FLAG, CONSUME_VMI_FLAG FROM APPS.MTL_CONSUMPTION_DEFINITION_V WHERE ORGANIZATION_ID = :p_org_id ORDER BY SUBINVENTORY_CODE, TRANSACTION_TYPE_NAME;
The user search term planning_organization_id is directly relevant here: it is both a projected column and a join key used to resolve PLANNING_PARTY against PO_VENDOR_SITES_ALL. Queries filtering on PLANNING_ORGANIZATION_ID therefore return the associated vendor name and site code, making the view convenient for consignment and VMI reconciliation reporting.
-
For Consumption setup forms
APPS.MTL_CONSUMPTION_DEFINITION_V·↳ FND_GLOBAL·↳ MTL_CONSUMPTION_DEFINITION·↳ MTL_PARAMETERS·Explore INV module →
-
For Consumption setup forms
APPS.MTL_CONSUMPTION_DEFINITION_V·↳ MTL_CONSUMPTION_DEFINITION·↳ MTL_PARAMETERS·↳ MTL_SYSTEM_ITEMS_KFV·Explore INV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.PO_VENDORS 12.1.1
-
VIEW: APPS.PO_VENDORS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
Set Distribution Table.
-
Set Distribution Table.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
Set Distribution Table.
-
Set Distribution Table.
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2