Results for “dsp_segment1”

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

Overview

MTL_TRANSACTIONS_INTERFACE is the inventory transaction staging table owned by the INV schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the gateway for externally generated material transactions — that is, transactions originating outside the standard Inventory transaction forms. Records are inserted into this interface, validated and processed by the Inventory Transaction Manager concurrent program, and then transferred into the permanent transaction tables such as MTL_MATERIAL_TRANSACTIONS. The table is documented as VALID with 305 columns in the ETRM 12.2.2 physical schema.

From a dimensional modeling perspective, the mined FK structure suggests a link classification: the table records the association between inventory items, organizations, locators, subinventories, cost groups, accounts, and various source documents. Each row is a transaction event that references multiple hub entities rather than describing the attributes of a single business key.

Key Information Stored

The unique index MTL_TRANSACTIONS_INTERFACE_U1 on TRANSACTION_INTERFACE_ID identifies the surrogate primary key for each staged row. Several columns act as business-key candidates in query practice.

• TRANSACTION_INTERFACE_ID — surrogate primary key, unique per interface row.
• TRANSACTION_HEADER_ID — groups interface lines belonging to a single logical transaction.
• PROCESS_FLAG — controls whether the row is picked up by the transaction manager (1 = ready, 2 = processed, 3 = error).
• VALIDATION_REQUIRED — indicates whether the transaction needs validation before processing.
• TRANSACTION_MODE — the type of transaction being staged, such as issue, receipt, or transfer.
• INVENTORY_ITEM_ID — FK to MTL_SYSTEM_ITEMS_B, identifying the item.
• ORGANIZATION_ID — the inventory organization in which the transaction occurs.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM — the quantity and unit of measure.
• SUBINVENTORY_CODE and LOCATOR_ID — the source subinventory and locator (FK to MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS respectively).
• TRANSFER_SUBINVENTORY, TRANSFER_ORGANIZATION, TRANSFER_LOCATOR — the destination for transfer transactions.
• TRANSACTION_DATE and ACCT_PERIOD_ID — the effective transaction date and accounting period.
• TRANSACTION_SOURCE_TYPE_ID — FK to MTL_TXN_SOURCE_TYPES, identifying the source system.
• DISTRIBUTION_ACCOUNT_ID — FK to GL_CODE_COMBINATIONS for the accounting distribution.
• ERROR_CODE and ERROR_EXPLANATION — populated when processing rejects the row.

Common Use Cases and Queries

The most frequent operational query monitors rows that have not yet been processed or that have failed validation:

• Monitoring backlog: SELECT transaction_interface_id, inventory_item_id, organization_id, process_flag FROM mtl_transactions_interface WHERE process_flag IN (1,3);
• Isolating errors: SELECT transaction_interface_id, error_code, error_explanation FROM mtl_transactions_interface WHERE process_flag = 3;
• Reconciling source document flow by joining TRANSACTION_SOURCE_TYPE_ID to MTL_TXN_SOURCE_TYPES.
• Auditing transfers by comparing SUBINVENTORY_CODE/LOCATOR_ID with TRANSFER_SUBINVENTORY/TRANSFER_LOCATOR.
• Reporting on accounting impact by joining DISTRIBUTION_ACCOUNT_ID to GL_CODE_COMBINATIONS.

Purge jobs and interface monitoring reports commonly depend on PROCESS_FLAG and CREATION_DATE filters.

Related Objects

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_ITEM_LOCATIONS — joined on LOCATOR_ID and TRANSFER_LOCATOR.
• MTL_SECONDARY_INVENTORIES — joined on SUBINVENTORY_CODE and TRANSFER_SUBINVENTORY.
• GL_CODE_COMBINATIONS — joined on DISTRIBUTION_ACCOUNT_ID and TRANSPORTATION_ACCOUNT.
• MTL_TXN_SOURCE_TYPES — joined on TRANSACTION_SOURCE_TYPE_ID.
• WIP_FLOW_SCHEDULES — joined on SCHEDULE_NUMBER and ORGANIZATION_ID.
• MTL_MOVEMENT_STATISTICS — joined on MOVEMENT_ID.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID.
• SO_PICKING_LINES_ALL — joined on PICKING_LINE_ID.

Downstream, the Inventory Transaction Manager writes processed rows into the permanent transaction tables, which remain the authoritative source for inventory balances and accounting entries.