Search Results trx_source_line_id




Overview
Explore in AI Chat

Overview

GME_INV_TXNS_POSTED_ERES_V is a supplementary reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the GME (Process Manufacturing Process Execution) product family. In EBS 12.1.1 and 12.2.2, the object is documented with a status of VALID and is defined over the inventory transaction table MTL_MATERIAL_TRANSACTIONS (referenced via a synonym). Its stated purpose is to expose posted inventory transactions in a denormalized, display-ready form, joining auxiliary reference tables for reason names, locators, and transaction types so that downstream reporting, electronic records, and signature (ERES) requirements can consume inventory movement data without additional lookups.

The view is particularly relevant when auditing posted material movements, since the name implies posted transactions, and because it carries both the EBS internal transaction identifiers and a set of descriptive attributes. Search terms such as trx_source_line_id surface this view because the column is explicitly selected from MTL_MATERIAL_TRANSACTIONS.

Underlying Base Objects

The view text selects from five referenced objects, all resolved through APPS:

  • MTL_MATERIAL_TRANSACTIONS (SYNONYM) — the driving table, aliased MMT, holding the inventory transaction rows.
  • MTL_TRANSACTION_REASONS (SYNONYM) — outer-joined on REASON_ID and aliased MTR, supplying the reason description.
  • MTL_ITEM_LOCATIONS_KFV (VIEW) — outer-joined on organization, subinventory, and locator, providing the concatenated locator segment string.
  • MTL_TRANSACTION_TYPES (SYNONYM) — inner-joined on TRANSACTION_TYPE_ID, supplying the transaction type name.
  • FND_DATE (PACKAGE) — used to convert the transaction date into a display-formatted string.

All three lookup joins are outer joins, but the transaction type join is an equi-join, so it will restrict rows to transactions whose type exists in the transaction types table.

Key Columns

The view projects identifiers and descriptive attributes in a single row per transaction. Notable columns include:

Common Use Cases and Queries

Typical usage covers transaction audit reporting, reconciliation of posted movements, and tracing movements by source line. A representative query filtering by the searched column is:

  • SELECT transaction_id, inventory_item_id, organization_id, transaction_quantity, transaction_uom, trx_source_line_id, transaction_display_date FROM apps.gme_inv_txns_posted_eres_v WHERE trx_source_line_id = :p_line_id;
  • Summarizing movements by item and subinventory: SELECT organization_id, inventory_item_id, subinventory_code, SUM(transaction_quantity) FROM apps.gme_inv_txns_posted_eres_v GROUP BY organization_id, inventory_item_id, subinventory_code;
  • Auditing by reason: SELECT transaction_id, reason_name, transaction_type_name FROM apps.gme_inv_txns_posted_eres_v WHERE reason_name IS NOT NULL;

Because the view surfaces TRX_SOURCE_LINE_ID directly from the material transactions table, it is a convenient entry point for linking Oracle Process Manufacturing execution records back to the originating inventory transaction.