Search Results pa_resource_txn_attributes_v




Overview
Explore in AI Chat

Overview

PA_RESOURCE_TXN_ATTRIBUTES_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) product family. The ETRM metadata identifies its status as VALID and its description as "10Sc only," indicating that the object originated in an early Projects release (release 10SC) and has been retained for backward compatibility. The view presents a denormalized, human-readable projection of the transaction attributes stored in PA_RESOURCE_TXN_ATTRIBUTES, resolving surrogate identifiers into names, codes, and classifications.

Because resource transaction attributes qualify how a resource is used on a project or task—by expenditure category, revenue category, expenditure type, event type, non-labor resource, job, organization, or vendor—this view plays a central role in Projects reporting, cross-module integration, and legacy interfaces that still reference the 10SC-era object name. Report developers and integrators query it rather than joining the underlying attribute table to a dozen descriptive entities manually.

Underlying Base Objects

The view text joins the driving table PA_RESOURCE_TXN_ATTRIBUTES (aliased RTA) to a broad set of descriptive and validation objects, all defined under the APPS schema:

All descriptive joins except the resource key are outer joins, so attribute rows are preserved even when a descriptive value is absent. Additional dependencies documented in 12.2.2 include HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, PA_CROSS_BUSINESS_GRP, and PA_UTILS, reflecting organization security and name-formatting behavior applied through the underlying view chain.

Key Columns

Common Use Cases and Queries

The view is typically used to report which attribute combinations a resource may use, and to export attributes to external costing or billing systems. A representative query lists attributes for an employee resource:

SELECT resource_id, full_name, job_id, name,
       expenditure_type, expenditure_category,
       non_labor_resource, vendor_name
FROM   apps.pa_resource_txn_attributes_v
WHERE  person_id = :person_id;

A second pattern, useful for validation or migration checks, enumerates non-labor attributes for a given organization:

SELECT resource_txn_attribute_id, resource_id,
       non_labor_resource, nlro.organization_id,
       revenue_category_code
FROM   apps.pa_resource_txn_attributes_v
WHERE  non_labor_resource IS NOT NULL
ORDER BY resource_id, non_labor_resource;

Because the object is marked "10Sc only," new development should generally favor the base table PA_RESOURCE_TXN_ATTRIBUTES joined to current descriptive views; existing reports and interfaces that depend on PA_RESOURCE_TXN_ATTRIBUTES_V should be validated against the 12.1.1 or 12.2.2 instance before upgrade, since the underlying organization and person views enforce HR security and effective-dating.