Search Results item_ord
Overview
MTL_MATERIAL_TXNS_VAL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined against the Inventory (INV) product. As its name implies, it presents validated material transaction data — that is, transactions from MTL_MATERIAL_TRANSACTIONS that have been transformed into a business-readable form through joins to transaction types, lookups, reason codes, item definitions, and organizational data. In Oracle EBS 12.1.1 and 12.2.2 the view is delivered with a VALID status and is described in the ETRM repository as "Retrofitted," indicating it was carried forward from earlier releases into the current code line.
The view plays a central role in inventory reporting and integration. Rather than requiring report authors to manually resolve numeric lookup codes, transaction type IDs, and item IDs, it exposes decoded columns such as TRANSACTION_ACTION, COSTED_FLAG_1, and the concatenated item identifier ITEM_ORD. This makes it suitable for inventory valuation reporting, transaction audit extracts, and feeds into downstream cost accounting or warehouse analysis.
Underlying Base Objects
The view is defined primarily over the MTL_MATERIAL_TRANSACTIONS synonym, aliased as M, and joins outward to a set of reference and descriptive objects. The documented base objects are:
- MTL_MATERIAL_TRANSACTIONS — the driving transaction table.
- MTL_TRANSACTION_TYPES — supplies TRANSACTION_TYPE_NAME.
- MTL_TXN_SOURCE_TYPES — supplies TRANSACTION_SOURCE_TYPE_NAME.
- MTL_TRANSACTION_REASONS — supplies REASON_NAME.
- MTL_SYSTEM_ITEMS_VL — supplies ITEM_ORD, PRIMARY_UOM_CODE, and DESCRIPTION.
- MFG_LOOKUPS — decodes COSTED_FLAG and PM_COST_COLLECTED into meanings and lookup codes.
- BOM_DEPARTMENTS — supplies DEPARTMENT_CODE.
- HR_ALL_ORGANIZATION_UNITS_TL — supplies TRANSFER_ORGANIZATION_NAME.
- HR_ORG_UNITS_NO_JOIN, HR_GENERAL, HR_SECURITY — supporting organization/security views and packages.
- CST_COST_GROUPS and WMS_LICENSE_PLATE_NUMBERS — additional cost and license plate references.
The joins are essentially lookup-driven: the driving table supplies foreign keys, and each joined object contributes a descriptive attribute, producing a denormalized, self-describing transaction row.
Key Columns
The view exposes identity and audit columns (TRANSACTION_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, REVISION, CREATION_DATE, LAST_UPDATE_DATE, and the WHO columns), quantities (TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM), and descriptive item data (ITEM_ORD, DESCRIPTION, PRIMARY_UOM_CODE). Decoded attributes include TRANSACTION_TYPE_NAME, TRANSACTION_ACTION, COSTED_FLAG_1, COSTED_LOOKUP_CODE, PM_COST_COLLECTED_1, TRANSACTION_SOURCE_TYPE_NAME, REASON_NAME, and DEPARTMENT_CODE.
Transactional context is carried by TRANSACTION_DATE, TRANSACTION_REFERENCE, SUBINVENTORY, LOCATOR_ID, TRANSFER_TRANSACTION_ID, and the RCV/MOVE/COMPLETION transaction references. Fifteen ATTRIBUTE columns preserve the flexible descriptive flexfield, and the ROW_ID column exposes the physical row identifier for row-level operations.
Common Use Cases and Queries
Typical scenarios include reconciling costed versus uncosted transactions, extracting period activity for valuation, auditing transfer and receipt transactions, and building interfaces for downstream systems that require decoded lookup values.
- Transaction detail report filtered by organization and date range.
- Costing completeness audit using COSTED_FLAG_1 and PM_COST_COLLECTED_1.
- Transfer tracking using TRANSFER_ORGANIZATION_NAME and TRANSFER_SUBINVENTORY.
A representative query:
- SELECT TRANSACTION_ID, ORGANIZATION_ID, ITEM_ORD, TRANSACTION_TYPE_NAME, TRANSACTION_ACTION, TRANSACTION_QUANTITY, TRANSACTION_UOM, TRANSACTION_DATE, COSTED_FLAG_1 FROM APPS.MTL_MATERIAL_TXNS_VAL_V WHERE ORGANIZATION_ID = :org AND TRANSACTION_DATE BETWEEN :start_date AND :end_date ORDER BY TRANSACTION_DATE;
Because the view performs multiple outer joins, queries should be filtered by organization and date to limit execution cost. It is a read-only reporting construct; no DML should be attempted against it.
-
View: MTL_MATERIAL_TXNS_VAL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:INV.MTL_MATERIAL_TXNS_VAL_V, object_name:MTL_MATERIAL_TXNS_VAL_V, status:VALID, product: INV - Inventory , description: - Retrofitted , implementation_dba_data: APPS.MTL_MATERIAL_TXNS_VAL_V ,
-
View: MTL_MATERIAL_TXNS_VAL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:INV.MTL_MATERIAL_TXNS_VAL_V, object_name:MTL_MATERIAL_TXNS_VAL_V, status:VALID, product: INV - Inventory , description: - Retrofitted , implementation_dba_data: APPS.MTL_MATERIAL_TXNS_VAL_V ,
-
VIEW: APPS.MTL_MATERIAL_TXNS_VAL_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:INV.MTL_MATERIAL_TXNS_VAL_V, object_name:MTL_MATERIAL_TXNS_VAL_V, status:VALID,
-
VIEW: APPS.MTL_MATERIAL_TXNS_VAL_V
12.2.2
-
VIEW: APPS.MTL_MATERIAL_TXNS_VAL_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:INV.MTL_MATERIAL_TXNS_VAL_V, object_name:MTL_MATERIAL_TXNS_VAL_V, status:VALID,
-
VIEW: APPS.MTL_MATERIAL_TXNS_VAL_V
12.1.1
-
eTRM - INV Tables and Views
12.1.1
-
eTRM - INV Tables and Views
12.2.2