Search Results transaction_rejection_code




Overview
Explore in AI Chat

Overview

PA_TRANSACTION_INTERFACE is a Projects (PA) module view in Oracle EBS 12.1.1 and 12.2.2 that exposes the contents of the pre-processing interface for project expenditures. It presents a readable, denormalized projection of the transaction interface staging area, resolving internal identifiers for projects, tasks, employees, organizations, and non-labor resources into their user-facing number and name equivalents. The view is not a base table and, per the ETRM metadata, is "not implemented in this database" as a physical object; it is a query layer defined over the interface data model.

Functionally, PA_TRANSACTION_INTERFACE serves as the canonical inquiry point for rows awaiting validation, costing, and import by the Projects transaction import programs (for example, the Transaction Import process invoked through PRC: Transaction Import). Because labor, expense, usage, and supplier cost transactions are all staged through a common interface before they become expenditure items, this view is widely used for reconciliation, error triage, and pre-import reporting.

Underlying Base Objects

The ETRM metadata does not document specific referenced base objects; the view is described as referencing none in the documented metadata. In practice the view is a join across the Projects transaction interface and related reference entities. The primary source is the transaction interface staging entity that stores interface rows keyed by TXN_INTERFACE_ID / INTERFACE_ID. Lookup joins resolve PROJECT_NUMBER from PROJECT_ID, TASK_NUMBER from TASK_ID, EMPLOYEE_NUMBER from PERSON_ID, ORGANIZATION_NAME from ORGANIZATION_ID, NON_LABOR_RESOURCE_ORG_NAME from NON_LABOR_RESOURCE_ORG_ID, VENDOR_NUMBER from VENDOR_ID, and WORK_TYPE_NAME from WORK_TYPE. Additional joins resolve expenditure type names, batch names, and transaction status meanings. Because it is a view rather than a table, no DDL seats data in it; rows are visible only as long as their staging rows exist prior to successful import and purge.

Key Columns

Common Use Cases and Queries

Typical uses include identifying transactions that failed import, reconciling staged amounts to source systems, and reviewing currency conversion before posting. A representative query returns pending interface rows by project:

  • SELECT txn_interface_id, project_number, task_number, expenditure_type, expenditure_item_date, quantity, raw_cost, transaction_status_code, transaction_rejection_code FROM pa_transaction_interface WHERE project_number = :p_project ORDER BY expenditure_item_date;
  • Error triage: SELECT batch_name, transaction_status_code, transaction_rejection_code, COUNT(*) FROM pa_transaction_interface GROUP BY batch_name, transaction_status_code, transaction_rejection_code;
  • Currency review: SELECT txn_interface_id, denom_currency_code, denom_raw_cost, acct_currency_code, acct_raw_cost, acct_exchange_rate FROM pa_transaction_interface WHERE acct_exchange_rate IS NULL;

Because the view is read-only and staging-scoped, it should be treated as a transient reporting surface; records disappear once imported and purged, so persistence requirements should be met by capturing query output or by relying on the resulting PA_EXPENDITURE_ITEMS records.