Search Results nlr_organization_id




Overview
Explore in AI Chat

Overview

APPS.PA_RESOURCE_TXN_ATTRIBUTES_V is a reporting and integration view in Oracle EBS Projects (PA) that exposes a denormalized, security-aware representation of resource transaction attribute assignments. It is owned by the APPS schema and carries the FND design data reference PA.PA_RESOURCE_TXN_ATTRIBUTES_V. The view joins the transactional attribute table PA_RESOURCE_TXN_ATTRIBUTES to descriptive entities such as people, jobs, organizations, vendors, expenditure types, event types, non-labor resources, and resource formats, so that a single row presents both the stored keys and their human-readable names.

Because it resolves names and applies HR security, the view is suited to reporting layers, concurrent programs, Oracle Discoverer workbooks, and interface extraction logic where the raw ID columns of the base table would otherwise require multiple lookups. The user search term nlr_organization_id identifies a column specific to this view; it captures the owning organization of a non-labor resource, distinct from the person/assignment organization exposed through ORGANIZATION_ID.

Underlying Base Objects

The documented dependencies include base synonyms and views such as PA_RESOURCE_TXN_ATTRIBUTES, PA_RESOURCES, PA_EXPENDITURE_TYPES, PA_EXPENDITURE_CATEGORIES, PA_NON_LABOR_RESOURCES, PA_EVENT_TYPES, and PA_JOBS_V, together with lookup views PA_REVENUE_CATEGORIES_V, PA_EVENT_TYPE_CLASSES_V, PA_SYSTEM_LINKAGES_V, HR_ALL_ORGANIZATION_UNITS_TL, HR_ORG_UNITS_NO_JOIN, PER_PEOPLE_F, and PO_VENDORS. Supporting packages HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, PA_CROSS_BUSINESS_GRP, and PA_UTILS are invoked to derive employee names, enforce organization-level access, and resolve cross-business-group behavior.

The primary base object is PA_RESOURCE_TXN_ATTRIBUTES, which stores the assignment of attributes to a resource transaction. Descriptive lookups are outer-joined to the base so that a row is not lost when, for example, a vendor or job is not applicable. HR_SECURITY restricts the returned organizations according to the responsibility's security profile, while PA_CROSS_BUSINESS_GRP supports cross-business-group queries.

Key Columns

Common Use Cases and Queries

Typical uses include extracting resource transaction attributes for interface or reconciliation, listing non-labor resources with their owning organizations, and building reporting queries that require resolved organization or vendor names. Security is enforced automatically, so results differ by responsibility.

Example: retrieving non-labor resource attributes with owning organization.

  • SELECT RESOURCE_TXN_ATTRIBUTE_ID, NON_LABOR_RESOURCE, NLR_ORGANIZATION_ID, NLR_ORGANIZATION_NAME, VENDOR_NAME, EXPENDITURE_TYPE FROM APPS.PA_RESOURCE_TXN_ATTRIBUTES_V WHERE NLR_ORGANIZATION_ID = :org_id;

Example: person-oriented attribute listing.

  • SELECT RESOURCE_ID, PERSON_ID, EMPLOYEE_NAME, JOB_NAME, ORGANIZATION_NAME, EVENT_TYPE FROM APPS.PA_RESOURCE_TXN_ATTRIBUTES_V WHERE PERSON_ID = :person_id;

Because the view performs many outer-joined lookups, queries should filter on indexed base columns such as RESOURCE_ID, RESOURCE_TXN_ATTRIBUTE_ID, or ORGANIZATION_ID rather than on derived name columns, and callers should confirm security profile effects when NLR_ORGANIZATION_ID appears unexpectedly null or filtered.