Search Results orig_transaction_reference




Overview
Explore in AI Chat

Overview

The APPS.PA_TRX_INTF_ORIG_TRANSREF_V view is a reporting and integration utility object within the Oracle E-Business Suite Projects (PA) module. It presents a distinct, grouped listing of the transaction source, batch name, original transaction reference, and operating unit identifier held in the Projects transaction interface table. Its functional purpose is to expose the discrete combinations of these four attributes that currently exist in the interface staging area, effectively providing a deduplicated view of the incoming transactions grouped by their originating reference.

The view plays a supporting role in integration and reconciliation workflows. When external systems, feeder applications, or subledgers push transactions into Oracle Projects through the transaction interface, each record carries an ORIG_TRANSACTION_REFERENCE that ties the staged row back to the source document. This view allows users and processes to enumerate the distinct references, batches, and sources present in the interface, which is essential for confirming that a given load has arrived, was assigned to the correct batch, and belongs to the expected operating unit.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is owned by APPS and is defined over a single referenced base object: PA_TRANSACTION_INTERFACE, accessed through a synonym. The view definition is intentionally simple and consists of a projection over four columns with a GROUP BY clause applied to all four, producing one row per unique combination of transaction source, batch name, original transaction reference, and operating unit.

Because the view references only the interface table and performs no joins, it does not depend on the Projects transaction destination tables, the source application tables, or any lookup views. This makes it lightweight and independent of the downstream processing logic. The synonym resolution follows standard EBS convention, where the APPS-owned synonym points to the application object of the same name.

Key Columns

  • TRANSACTION_SOURCE — Identifies the source system or process that supplied the transaction, for example a feeder application or subledger indicator. It determines which interface processing logic applies to the staged rows.
  • BATCH_NAME — The batch identifier assigned to the group of transactions during the interface load. Batch names are used to control and track groups of transactions during import into Oracle Projects.
  • ORIG_TRANSACTION_REFERENCE — The original document reference from the source system. This is the column most closely associated with the user search term "orig_transaction_reference" and serves as the link between the staged interface row and its originating document.
  • ORG_ID — The operating unit identifier that governs multi-organization access and security. It ensures that transaction interface data is scoped to the correct business unit.

Common Use Cases and Queries

The view is typically used to confirm the presence of source transactions in the interface and to validate batch and operating unit assignment before running import or cost distribution processes. Because it returns only distinct grouped combinations, it is well suited to answering existence questions without scanning the full interface table.

A basic query lists all distinct references for a given batch and source:

  • SELECT transaction_source, batch_name, orig_transaction_reference, org_id FROM apps.pa_trx_intf_orig_transref_v WHERE batch_name = :batch AND transaction_source = :source;
  • SELECT orig_transaction_reference FROM apps.pa_trx_intf_orig_transref_v WHERE org_id = :org_id ORDER BY orig_transaction_reference;
  • SELECT COUNT(*) FROM apps.pa_trx_intf_orig_transref_v WHERE transaction_source = :source;

Typical scenarios include verifying that a feeder interface has staged all expected documents, reconciling the list of original references against the source system extract, and diagnosing import failures by identifying which references, batches, or operating units are present in the interface. Because the view is defined directly over PA_TRANSACTION_INTERFACE, its results reflect the current staging state and change as interface rows are inserted or purged during processing.