Search Results inv_material_transcation_id

Overview

APPS.CSI_TXN_ERRORS_V is a supplementary Oracle E-Business Suite view in the CSI (Enterprise Inventory / Trackable Item) schema. It exposes transaction-level error records captured by the CSI transaction processing engine, presenting the diagnostic context required to identify, analyze, and reprocess failed or rejected inventory and trackable item transactions. The view is defined with FND Design Data reference CSI.CSI_TXN_ERRORS_V and carries a VALID status in both Release 12.1.1 and 12.2.2.

Because this is an Oracle-maintained supplementary view used to simplify forms coding, Oracle explicitly warns against querying or altering data through it directly; its definition may change materially across minor or major releases. Consumers that require stability should treat the view as a diagnostic reporting surface only, and should expect column availability to shift between releases. Its primary role is to support error investigation workflows in forms and, where permitted, read-only reporting on failed CSI material transactions.

Underlying Base Objects

The view is defined over a set of APPS synonyms that resolve to core inventory and HR tables. The documented referenced base objects are:

• CSI_TXN_ERRORS — the primary error repository holding the transaction failure rows.
• MTL_MATERIAL_TRANSACTIONS — the inventory material transaction that generated or is associated with the error.
• MTL_UNIT_TRANSACTIONS — unit-level (serialized) transaction detail.
• MTL_TRANSACTION_LOT_NUMBERS — lot and lot quantity detail for the affected transaction.
• MTL_SECONDARY_INVENTORIES — the subinventory definition referenced by INV_SUBINVENTORY.
• MTL_SYSTEM_ITEMS — the inventory item master, used for item attributes.
• HR_ALL_ORGANIZATION_UNITS — the inventory organization context.

The join across these objects allows a single error row to carry both the failing transaction attributes (item, organization, revision, subinventory, locator, lot, serial) and the inventory control codes needed to evaluate whether the source and destination attribute combinations are legal.

Key Columns

TRANSACTION_ERROR_ID is the unique internal identifier for the error row, while TRANSACTION_ID, SOURCE_TYPE, and SOURCE_ID identify the originating transaction and its source. TRANSACTION_TYPE_ID and INV_MATERIAL_TRANSCATION_ID link the error to the specific inventory transaction type and material transaction record.

Physical inventory context is supplied by INVENTORY_ITEM_ID, INV_ORGANIZATION_ID, REVISION, INV_SUBINVENTORY, LOCATOR_ID, LOT_NUMBER, and SERIAL_NUMBER. The INV_SUBINVENTORY column (VARCHAR2(10)) holds the subinventory name that is the frequent subject of user searches such as "inv_subinventory". SHIPPED_QUANTITY, TRANSACTION_UOM, and TRANSACTION_DATE capture the quantity and timing of the attempted movement.

Control-code columns — SRC_LOT_CTRL_CODE, SRC_SERIAL_NUM_CTRL_CODE, SRC_LOCATION_CTRL_CODE, SRC_REV_QTY_CTRL_CODE and their DST_ counterparts — encode the source and destination control requirements that govern whether a transaction is valid. PROCESSED_FLAG indicates whether the error has been resolved or actioned, and COMMS_NL_TRACKABLE_FLAG flags trackable-item handling. RESERVABLE_TYPE, HR_LOCATION_ID, and SUBINV_LOCATION_ID provide additional location and reservation context.

Common Use Cases and Queries

Typical usage includes diagnosing failed subinventory transfers, investigating serial or lot control violations, and reporting unprocessed errors awaiting correction. A representative query filtering on subinventory is:

• SELECT TRANSACTION_ERROR_ID, TRANSACTION_ID, INVENTORY_ITEM_ID, INV_ORGANIZATION_ID, INV_SUBINVENTORY, REVISION, LOT_NUMBER, SERIAL_NUMBER, PROCESSED_FLAG FROM APPS.CSI_TXN_ERRORS_V WHERE INV_SUBINVENTORY = :p_subinventory AND PROCESSED_FLAG = 'N';
• SELECT TRANSACTION_ERROR_ID, INV_ORGANIZATION_ID, INVENTORY_ITEM_ID, TRANSACTION_DATE, SHIPPED_QUANTITY FROM APPS.CSI_TXN_ERRORS_V WHERE INV_ORGANIZATION_ID = :p_org_id ORDER BY TRANSACTION_DATE DESC;
• SELECT TRANSACTION_ERROR_ID, SRC_SERIAL_NUM_CTRL_CODE, DST_SERIAL_NUM_CTRL_CODE, SRC_LOT_CTRL_CODE, DST_LOT_CTRL_CODE FROM APPS.CSI_TXN_ERRORS_V WHERE TRANSACTION_ERROR_DATE >= :p_from_date AND COMMS_NL_TRACKABLE_FLAG = 'Y';

These queries support error triage and reconciliation. Given Oracle's warning about querying this supplementary view, production integrations should consume the underlying CSI_TXN_ERRORS base table where a stable interface is required.