Results for “mtl_transact_interface_view”

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

Overview

MTL_TRANSACT_INTERFACE_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite Inventory (INV). It is documented in ETRM as a "Transaction interface status view." Its purpose is to present an aggregated, consolidated snapshot of the rows staged in the transaction interface table, MTL_TRANSACTIONS_INTERFACE, rather than the individual interface records themselves. The view groups pending interface rows and reports the count of records associated with a given transaction header, transaction mode, and concurrent request, allowing users and support staff to determine how much work remains to be processed by the transaction manager.

In both Oracle EBS 12.1.1 and 12.2.2 the object remains a standard APPS-owned view with VALID status. Because it summarizes rather than details the interface contents, it is particularly useful for monitoring batch loads, diagnosing stalled transaction workers, and distinguishing between an empty interface and one holding large unprocessed volumes.

Underlying Base Objects

The view is defined over a single documented base object: MTL_TRANSACTIONS_INTERFACE, referenced through a SYNONYM. This table is the principal staging area into which inventory transactions are inserted before the transaction manager validates and processes them. Every row in the view is derived exclusively from that table; no other base table, join, or external source is documented. This dependency means the view's contents change directly with the state of the interface table: when the transaction manager consumes and deletes interface rows, the corresponding view rows disappear or their counts decrease.

Key Columns

The documented column set is small and purpose-built:

• REQUEST_ID — Identifies the concurrent request (and implicitly the transaction manager run) under which the interface rows were created or are being processed, enabling monitoring per request.
• TRANSACTION_MODE — Indicates the processing mode of the interface rows, such as immediate or concurrent, allowing grouping by how the data is intended to be consumed.
• HEADER_ID — Corresponds to the transaction header identifier (TRANSACTION_HEADER_ID in the underlying table) and groups interface rows belonging to the same transaction header.
• NUMBER_OF_RECORDS — The COUNT(*) of interface rows for the grouped combination, providing the volume of pending or staged records.

Common Use Cases and Queries

Typical uses include tracking outstanding interface volume during a batch transaction load, verifying that a specific concurrent request generated the expected rows, and confirming that the interface table has been fully consumed after processing completes. Because the view aggregates on request, mode, and header, it answers "how many" rather than "which" rows.

Sample query to review pending interface volume by request and header:

• SELECT request_id, transaction_mode, header_id, number_of_records FROM apps.mtl_transact_interface_view ORDER BY request_id, header_id;
• SELECT request_id, SUM(number_of_records) total_rows FROM apps.mtl_transact_interface_view GROUP BY request_id;
• SELECT * FROM apps.mtl_transact_interface_view WHERE request_id = :request_id;

To inspect the individual rows behind a given view row, users join back to MTL_TRANSACTIONS_INTERFACE on TRANSACTION_HEADER_ID, TRANSACTION_MODE, and REQUEST_ID. This view should not be used for transaction correction or deletion; remediation is performed against the interface table itself through the standard transaction manager and interface error handling procedures.