Search Results transaction_status_code




Overview
Explore in AI Chat

Overview

The view PA_TXN_INTERFACE_AUDIT belongs to the Oracle Projects (PA) module and is classified in the ETRM reference metadata as a Single-Org object. It presents an audit-oriented projection of transactional data staged for the Oracle Projects transaction interface, exposing the identifiers, source attributes, costing figures, currency conversion details, and status codes associated with each interface record. Its principal role is to allow implementers, support analysts, and integration developers to inspect the contents of the Projects interface staging area without directly querying the underlying interface table.

Because the view surfaces the column TRANSACTION_STATUS_CODE, it is frequently consulted during reconciliation and error-resolution activities. Users searching on that term typically do so to determine why an expenditure or transaction line has not been processed into Oracle Projects, to confirm whether a record has been accepted, rejected, or left pending, and to correlate the rejection with TRANSACTION_REJECTION_CODE. The view therefore functions as a diagnostic and reporting layer over the Projects transaction interface, complementing the standard concurrent programs that import interface data.

Underlying Base Objects

The ETRM metadata records the owner as unspecified and lists no documented referenced base objects. The documentation excerpt states that the view is “Not implemented in this database,” meaning the definition is catalogued but not instantiated in the reference environment from which the metadata was extracted. Consequently, no authoritative base table list is available within the supplied material.

By convention within Oracle Projects, audit views of this kind are defined over the transaction interface staging table, commonly PA_TRANSACTION_INTERFACE_ALL, and its associated audit columns. The view text selects interface-centric identifiers such as TXN_INTERFACE_ID, INTERFACE_ID, and EXPENDITURE_ID, together with descriptive and financial attributes that mirror the columns of the interface table. The absence of documented base objects should be treated as a metadata limitation rather than evidence that the view is unbound; the exact definition should be confirmed against the deployed instance, since the view text provided appears truncated.

Key Columns

Common Use Cases and Queries

The view is used to audit interface loads, isolate failed records, and validate costing and currency conversion before import. A representative query returns all rejected or pending records for a given batch:

  • SELECT txn_interface_id, batch_name, project_number, expenditure_type, transaction_status_code, transaction_rejection_code, raw_cost FROM pa_txn_interface_audit WHERE transaction_status_code = 'REJECTED';
  • SELECT batch_name, transaction_status_code, COUNT(*) FROM pa_txn_interface_audit GROUP BY batch_name, transaction_status_code ORDER BY batch_name;
  • SELECT txn_interface_id, raw_cost, acct_raw_cost, project_raw_cost, acct_exchange_rate FROM pa_txn_interface_audit WHERE acct_exchange_rate IS NULL;

These patterns support reconciliation of interface batches, verification of exchange-rate application, and confirmation that records have been costed before the import process transfers them into Projects expenditure tables.