Search Results pa_resource_txn_attributes

Overview

The PA_RESOURCE_TXN_ATTRIBUTES table is a core transactional data object within the Oracle E-Business Suite Projects (PA) module, specifically in versions 12.1.1 and 12.2.2. It serves a critical function in the resource mapping and transaction processing architecture. As defined in the ETRM documentation, its primary role is to store combinations of transaction attributes for a resource that define which specific expenditure transactions are mapped to that resource. This mapping is essential for accurately assigning costs, such as labor hours, expense reports, or supplier invoices, to the correct project resource, ensuring proper cost collection, billing, and reporting.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which collectively form the unique transaction attribute combination. The primary key is RESOURCE_TXN_ATTRIBUTE_ID. The foreign keys define the specific attributes of a transaction that must be matched for a mapping to occur. Key columns include RESOURCE_ID, linking to PA_RESOURCES, and a set of attribute columns that typically function as foreign keys to other master data tables. Based on the provided metadata, these critical attribute columns are NON_LABOR_RESOURCE, EXPENDITURE_CATEGORY, SYSTEM_LINKAGE_FUNCTION, NON_LABOR_RESOURCE_ORG_ID, PARTY_ID, RESOURCE_FORMAT_ID, JOB_ID, EXPENDITURE_TYPE, VENDOR_ID, and EVENT_TYPE. Each record represents a unique rule that dictates when a transaction with a matching set of these attributes should be associated with a given resource.

Common Use Cases and Queries

The primary use case is troubleshooting transaction processing and resource assignment. For instance, if an expenditure item is not being picked up by the correct resource, consultants would query this table to verify a matching attribute rule exists. A common diagnostic query would join PA_RESOURCE_TXN_ATTRIBUTES to PA_RESOURCES and relevant master data tables (like PA_EXPENDITURE_TYPES) to review all mapping rules for a specific resource or expenditure type.

• Sample Query (Find rules for a resource): SELECT prta.*, pr.resource_name FROM pa_resource_txn_attributes prta, pa_resources pr WHERE prta.resource_id = pr.resource_id AND pr.resource_name = '<Resource_Name>';
• Reporting Use Case: Generating a report of all transaction mapping rules defined in the system, often for audit or configuration review purposes, by joining to all referenced lookup tables.
• Implementation Use Case: During setup, data is populated into this table, often via the API PA_RESOURCE_PUB, to establish the logical links between transaction sources (like Payroll, AP, PO) and project resources.

Related Objects

As indicated by its extensive foreign key relationships, PA_RESOURCE_TXN_ATTRIBUTES is a central hub connecting transactional mapping rules to master data. Key related objects, as documented, include:

• PA_RESOURCES: The master definition of the resource being mapped to.
• PA_EXPENDITURE_TYPES / PA_EXPENDITURE_CATEGORIES: Define the type and category of the expenditure transaction.
• PA_SYSTEM_LINKAGES: Identifies the source system (e.g., Payroll, Accounts Payable) for the transaction.
• PA_NON_LABOR_RESOURCES and PA_NON_LABOR_RESOURCE_ORGS: Define non-labor resources and their organizations.
• HZ_PARTIES and PO_VENDORS: Supplier or party information.
• PER_JOBS: Job definitions for labor-related mappings.
• PA_RESOURCE_FORMATS and PA_EVENT_TYPES: Provide additional formatting and event classification for transactions.

Data is typically created and maintained in this table through the public API PA_RESOURCE_PUB, rather than via direct DML, to maintain integrity with all related entities.