Search Results pa_transaction_sources

Overview

The PA_TRANSACTION_SOURCES table is a core reference table within the Oracle E-Business Suite Projects (PA) module. It serves as a master repository for implementation-defined sources that identify the origin of imported financial transactions. These transactions, such as costs, revenue, or commitments, typically originate from external feeder systems like Oracle Payables, Oracle Purchasing, or third-party applications. The table's primary role is to provide a controlled, validated list of source codes that ensure transactional integrity and accurate sourcing during the project costing and billing lifecycle. By defining and using these sources, organizations can trace project expenditures and other financial items back to their original system entry point, which is critical for audit trails, reconciliation, and system integration processes.

Key Information Stored

The table's structure is designed to manage unique transaction source identifiers. The central column is TRANSACTION_SOURCE, which serves as the primary key. This column stores the short name or code for the source system (e.g., 'AP' for Payables, 'PO' for Purchasing, or custom codes for external interfaces). While the provided metadata does not list all columns, standard implementation typically includes descriptive columns such as a NAME or DESCRIPTION for the source, along with ENABLED_FLAG and START_DATE_ACTIVE columns to control its active status. A critical foreign key column is SYSTEM_LINKAGE_FUNCTION, which links the transaction source to a specific system linkage definition in the PA_SYSTEM_LINKAGES table, thereby formally defining the integration pathway between the external system and Projects.

Common Use Cases and Queries

This table is primarily referenced during the transaction import process and for validation and reporting. A common operational query is to retrieve all active transaction sources for setup or maintenance purposes. For example: SELECT transaction_source, name FROM pa_transaction_sources WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);. When troubleshooting data in the transaction interface (PA_TRANSACTION_INTERFACE_ALL), queries frequently join to this table to validate source codes or provide meaningful descriptions in reports. For instance, a report summarizing interfaced items by source would use a join: SELECT pts.transaction_source, pts.name, COUNT(*) FROM pa_transaction_interface_all ptia, pa_transaction_sources pts WHERE ptia.transaction_source = pts.transaction_source GROUP BY pts.transaction_source, pts.name;.

Related Objects

As indicated by the foreign key relationships, PA_TRANSACTION_SOURCES is a parent table to several key transactional and control tables. The PA_TRANSACTION_INTERFACE_ALL table directly references it, storing raw transactions awaiting import. The PA_EXPENDITURE_ITEMS_ALL and PA_EXPENDITURE_GROUPS_ALL tables, which hold processed project expenditure details, also use it to record the transaction's origin. Furthermore, it has a defining relationship with PA_SYSTEM_LINKAGES via the SYSTEM_LINKAGE_FUNCTION column, which configures the integration setup. Understanding these relationships is essential for tracing the flow of transactions from external systems through the interface and into final project expenditure records.