Results for “organization_name”

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

Overview

The PA_ORG_AUTHORITY_V view is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. It is documented as VALID in ETRM 12.2.2 and remains applicable to the 12.1.1 and 12.2.2 releases. Its stated purpose is to expose the identifiers of the organizations over which a resource (typically a person) holds any authority, together with the identifiers of organizations that fall beneath a specified hierarchy. In effect, the view consolidates two distinct security and hierarchy models — role-based FND grant authority and parent/child organization structure traversal — into a single, query-friendly result set.

Because the view returns organization identifiers paired with descriptive organization names, it is well suited to reporting, concurrent program logic, and integration layers that must resolve "which organizations can this user act upon" or "which organizations sit under this hierarchy node." The user search term organization_id_child maps directly to a column referenced in the view's definition and to the underlying PER_ORG_STRUCTURE_ELEMENTS table, reinforcing that hierarchy descent is a primary function of this object.

Underlying Base Objects

Per the documented ETRM metadata, PA_ORG_AUTHORITY_V is defined over the following referenced objects:

• FND_GRANTS (SYNONYM) — supplies grant records; INSTANCE_PK1_VALUE is cast to a number to yield the authorized organization ID, and grantee/object linkage drives role association.
• FND_OBJECTS (SYNONYM) — filtered to OBJ_NAME = 'ORGANIZATION' so that only organization-level grants qualify.
• PER_ALL_PEOPLE_F (SYNONYM) — provides the effective-dated person record, resolved through PA_RESOURCE_UTILS.GET_PERSON_ID.
• WF_ROLES (VIEW) — joins the grantee key to the workflow role, restricted to ORIG_SYSTEM = 'HZ_PARTY' and matched to PER.PARTY_ID.
• PER_ORG_STRUCTURE_ELEMENTS (SYNONYM) — the hierarchical source traversed via a CONNECT BY PRIOR ORGANIZATION_ID_CHILD = ORGANIZATION_ID_PARENT clause, bounded by ORG_STRUCTURE_VERSION_ID.
• PA_RESOURCE_UTILS (PACKAGE) — supplies the driving runtime values, including GET_PERSON_ID, GET_SELECTED_FLAG, GET_VERSION_ID, GET_START_ORG_ID, and GET_ORGANIZATION_NAME.
• DUAL (SYNONYM) — used to emit the starting organization when the selected flag is 'O' or 'B'.

The view is assembled from three UNION branches: a grants-based branch (selected flags 'R'/'B'), a hierarchy-descent branch ('O'/'B'), and a start-node branch ('O'/'B').

Key Columns

• ORG_ID — the organization identifier. In the grant branch this is TO_NUMBER(FG.INSTANCE_PK1_VALUE); in the hierarchy branch it is ORGANIZATION_ID_CHILD; in the seed branch it is the start organization.
• ORGANIZATION_NAME — the descriptive name derived from PA_RESOURCE_UTILS.GET_ORGANIZATION_NAME, applied uniformly across all three UNION branches.

The DISTINCT keyword in the first branch ensures duplicate organization IDs from multiple grants are collapsed.

Common Use Cases and Queries

Typical usage resolves authorized organizations for the current resource context established by PA_RESOURCE_UTILS, or verifies hierarchy membership.

• List organizations a user is authorized to see:

SELECT org_id, organization_name
FROM   apps.pa_org_authority_v
ORDER BY organization_name;

• Confirm a specific child organization is present in the authority set:

SELECT org_id
FROM   apps.pa_org_authority_v
WHERE  org_id = :organization_id_child;

• Populate a report parameter LOV or integrate with external systems requiring authorized organization lists.

Because results depend on session-level PA_RESOURCE_UTILS state, callers must ensure the correct person and selected-flag context is initialized before querying.