Results for “mtl_material_transactions_temp”

50+ results




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

Overview

MTL_MATERIAL_TRANSACTIONS_TEMP is the inventory transaction staging and interface table owned by the INV schema in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2). It holds material transaction rows prior to validation, costing, and permanent posting to MTL_MATERIAL_TRANSACTIONS. The table is the working area for the transaction processor: callers such as the Inventory transaction forms, the open interface, and various subledger processes insert rows here, then the transaction manager (INVTTMTX / inventory transaction worker) validates each row, derives cost, resolves accounts, and writes the posted result to the final transaction tables before the temporary row is cleared.

The documented primary key is MTL_MATERIAL_TRANSACTIONS_T_PK on TRANSACTION_HEADER_ID, with a documented unique index MTL_MATERIAL_TRANS_TEMP_U1 on TRANSACTION_TEMP_ID. That combination implies that a temp row is technically keyed by its transaction header ID while the transaction temp ID functions as the business-key candidate used for row-level processing and concurrency. From a heuristic Data Vault modeling perspective, this object is satellite-leaning: it carries very wide descriptive attributes and transactional measurements attached to transaction keys that ultimately resolve to the core inventory transaction hub, rather than serving as a hub or link in its own right.

Key Information Stored

The 243 documented columns span transaction identity, item and location context, quantities, costing, and source document references. The most operationally significant columns are:

Common Use Cases and Queries

This table is primarily queried to diagnose inventory transaction failures and to reconcile pending work against posted results. Typical reporting includes locating rows that failed validation, inspecting the error text, and confirming which accounting period a transaction will land in.

  • Find unprocessed or errored rows for a given organization:
    SELECT TRANSACTION_TEMP_ID, INVENTORY_ITEM_ID, TRANSACTION_QUANTITY, PROCESS_FLAG, ERROR_CODE, ERROR_EXPLANATION FROM MTL_MATERIAL_TRANSACTIONS_TEMP WHERE ORGANIZATION_ID = :org AND (PROCESS_FLAG = 'N' OR ERROR_CODE IS NOT NULL);
  • Reconcile transactions pending in temp against the posted table by joining on TRANSACTION_HEADER_ID to MTL_MATERIAL_TRANSACTIONS.
  • Review transactions awaiting a specific accounting period via ACCT_PERIOD_ID against ORG_ACCT_PERIODS.
  • Trace source documents by joining RCV_TRANSACTION_ID to RCV_TRANSACTIONS or MOVE_TRANSACTION_ID to WIP_MOVE_TRANSACTIONS.

Related Objects

Foreign key metadata identifies the most significant dependencies referenced by this table and those that reference it:

  • MTL_MATERIAL_TRANSACTIONS — the final posted transaction table; rows migrate here upon successful processing.
  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item master attributes.
  • MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES — provide locator and subinventory validation for LOCATOR_ID, TRANSFER_TO_LOCATION, and SUBINVENTORY_CODE.
  • GL_CODE_COMBINATIONS — referenced by DISTRIBUTION_ACCOUNT_ID and TRANSPORTATION_ACCOUNT for accounting resolution.
  • ORG_ACCT_PERIODS — joined on ACCT_PERIOD_ID and ORGANIZATION_ID for period validation.
  • RCV_TRANSACTIONS and WIP_MOVE_TRANSACTIONS — source document linkage for receiving and WIP move transactions.
  • MTL_RESERVATIONS and MTL_TXN_REQUEST_LINES — reservation and move-order line references.
  • WMS_EXCEPTIONS and WMS_SKIP_TASK_EXCEPTIONS — these tables reference MTL_MATERIAL_TRANSACTIONS_TEMP via TRANSACTION_HEADER_ID, tying warehouse task exceptions back to the staged transaction.