Search Results mtl_transaction_lots_int_pk

Overview

The MTL_TRANSACTION_LOTS_INTERFACE table is a critical staging table within the Oracle E-Business Suite Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It functions as a temporary lot storage area for the transaction processor. Its primary role is to serve as an intermediate repository for lot-level information associated with pending material transactions before they are validated and processed into the permanent transaction history tables. This interface-based design is fundamental to Oracle's open interface architecture, allowing for the high-volume, programmatic import of inventory transactions from external systems, such as manufacturing execution systems (MES), warehouse management systems (WMS), or custom legacy applications, via tools like SQL*Loader or custom PL/SQL programs.

Key Information Stored

The table stores lot-specific attributes that must be associated with a transaction line staged in the MTL_TRANSACTIONS_INTERFACE table. While the provided ETRM metadata does not list specific columns, the table's primary key is documented as TRANSACTION_INTERFACE_ID, which links each lot record to its parent transaction interface record. Based on its purpose and standard Oracle Inventory interface design, typical columns would include identifiers for the lot number (LOT_NUMBER), the transaction quantity allocated to that specific lot (TRANSACTION_QUANTITY), and the secondary transaction quantity if applicable. It also stores the lot expiration date and other lot-controlled item attributes required for successful transaction processing and validation against inventory lot balances.

Common Use Cases and Queries

The primary use case is the batch loading of lot-controlled inventory transactions. A typical data flow involves first populating MTL_TRANSACTIONS_INTERFACE, then inserting corresponding lot details into MTL_TRANSACTION_LOTS_INTERFACE. The Transaction Manager concurrent program (INVTIMM) is then run to validate and process the records from these interfaces into the core transaction tables (e.g., MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_LOT_NUMBERS). Common queries involve monitoring the interface for errors. For example, to identify lot interface records that have failed processing, one might join to the parent interface table on TRANSACTION_INTERFACE_ID to see the associated error message and transaction header details. Another critical query is to check for orphaned lot records that have no corresponding parent in MTL_TRANSACTIONS_INTERFACE, which would indicate a data integrity issue in the load process.

Related Objects

• Primary Key Relationship: The table's primary key constraint, MTL_TRANSACTION_LOTS_INT_PK, is on the TRANSACTION_INTERFACE_ID column. This column is a foreign key to the MTL_TRANSACTIONS_INTERFACE table, establishing the core parent-child relationship for the transaction interface.
• Foreign Key Relationship: As per the documented metadata, a foreign key exists where MTL_TRANSACTION_LOTS_INTERFACE.SERIAL_TRANSACTION_TEMP_ID references the MTL_SERIAL_NUMBERS_INTERFACE table. This relationship supports complex transactions where both lot and serial number information must be specified for the same transaction line, linking the lot and serial interface records together.
• Processing Dependency: The table is directly processed by the Inventory Transaction Manager concurrent program, which moves validated data into permanent tables such as MTL_TRANSACTION_LOT_NUMBERS.