Results for “pa_resource_txn_attributes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_RESOURCE_TXN_ATTRIBUTES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores combinations of transaction attributes that determine which expenditure or event transactions map to a specific resource when the resource mapping process runs. In practical terms, each row defines a matching rule: given a resource and an associated set of attributes such as expenditure type, expenditure category, non-labor resource, vendor, job, party, or organization, the system uses the row to resolve which resource should be assigned to an incoming transaction.

The table is owned by the PA schema and is documented as VALID in ETRM 12.2.2 with 26 columns. From a modeling perspective, the mined relationship structure suggests a link classification, since the table primarily resolves relationships between a resource (PA_RESOURCES) and numerous attribute dimensions rather than acting as a pure descriptive satellite or a single-subject hub. It should be treated as a rule or mapping table that sits between transactional facts and resource master data.

Key Information Stored

The surrogate primary key is RESOURCE_TXN_ATTRIBUTE_ID, enforced by PA_RESOURCE_TXN_ATTRIBUTES_PK. The unique index PA_RESOURCE_TXN_ATTRIBUTES_U1 also covers RESOURCE_TXN_ATTRIBUTE_ID, so the identifier is the documented business-key candidate rather than a composite of attribute columns.

• RESOURCE_ID — the resource to which matching transactions are mapped; foreign key to PA_RESOURCES.
• NON_LABOR_RESOURCE and NON_LABOR_RESOURCE_ORG_ID — identify the non-labor resource and its owning organization, referencing PA_NON_LABOR_RESOURCES and PA_NON_LABOR_RESOURCE_ORGS.
• EXPENDITURE_TYPE and EXPENDITURE_CATEGORY — restrict mapping to specific expenditure classifications, joining to PA_EXPENDITURE_TYPES and PA_EXPENDITURE_CATEGORIES.
• REVENUE_CATEGORY — supports revenue-side categorization of the mapped resource.
• VENDOR_ID — supplier used to scope the mapping rule; foreign key to PO_VENDORS.
• JOB_ID and PERSON_ID — job and person qualifiers; JOB_ID references PER_JOBS.
• PARTY_ID — trading partner or party reference, joining to HZ_PARTIES.
• ORGANIZATION_ID — organization context for the resource attribute combination.
• EVENT_TYPE and EVENT_TYPE_CLASSIFICATION — event attributes used when mapping event transactions; EVENT_TYPE references PA_EVENT_TYPES.
• SYSTEM_LINKAGE_FUNCTION — links the rule to a system linkage definition in PA_SYSTEM_LINKAGES.
• RESOURCE_FORMAT_ID and PROJECT_ROLE_ID — reference PA_RESOURCE_FORMATS and PA_PROJECT_ROLE_TYPES respectively.
• Audit columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN and the PROGRAM_* request columns provide standard EBS auditing and concurrent program traceability.

Common Use Cases and Queries

Typical usage includes auditing resource mapping rules, troubleshooting why a transaction mapped to an unexpected resource, and reporting the attribute combinations configured for a given resource. A common query joins the rule table to resource master data:

• SELECT rta.resource_id, r.name, rta.expenditure_type, rta.expenditure_category, rta.non_labor_resource, rta.vendor_id FROM pa.pa_resource_txn_attributes rta, pa.pa_resources r WHERE rta.resource_id = r.resource_id;
• To inspect non-labor mappings, join NON_LABOR_RESOURCE to PA_NON_LABOR_RESOURCES and NON_LABOR_RESOURCE_ORG_ID to PA_NON_LABOR_RESOURCE_ORGS.
• To analyze vendor-specific rules, join VENDOR_ID to PO_VENDORS and filter by EXPENDITURE_CATEGORY.
• Discovery queries can group by SYSTEM_LINKAGE_FUNCTION to see which mapping rules participate in each system linkage.

Reporting use cases include resource utilization setup validation, mapping rule gap analysis (resources with no attribute rows), and impact analysis before changing expenditure type or category definitions.

Related Objects

• PA_RESOURCES — master resource table; joined on RESOURCE_ID.
• PA_NON_LABOR_RESOURCES and PA_NON_LABOR_RESOURCE_ORGS — non-labor resource and organization dimensions.
• PA_EXPENDITURE_TYPES and PA_EXPENDITURE_CATEGORIES — expenditure classification dimensions.
• PA_SYSTEM_LINKAGES — linkage function definitions referenced by SYSTEM_LINKAGE_FUNCTION.
• PA_RESOURCE_FORMATS and PA_PROJECT_ROLE_TYPES — resource format and project role dimensions.
• PO_VENDORS — supplier dimension via VENDOR_ID.
• HZ_PARTIES — party dimension via PARTY_ID.
• PER_JOBS — job dimension via JOB_ID.
• PA_EVENT_TYPES — event type dimension via EVENT_TYPE.