Search Results ou_name




Overview
Explore in AI Chat

Overview

APPS.PA_R_HIERARCHIES_V is a reporting view in Oracle EBS Projects (PA) that exposes the organizational hierarchy structures configured on the PA Implementation setup — specifically the Expenditure Organization Structure and the Project Organization Structure. It presents, for each implementation business group, the organization structure name and version together with the individual organizations that belong to the hierarchy, unresolved against the operating unit context (org_id). Because it unifies the Expenditure and Project structure hierarchies into a single result set, the view is commonly used by reports, integrations, and diagnostic queries that must enumerate the organizations valid for a given hierarchy type. The user search term ou_name maps directly to a column in this view, which returns the operating unit name associated with the implementation.

Underlying Base Objects

The view is defined over the following documented objects:

  • PA_IMPLEMENTATIONS_ALL — supplies the implementation-level keys: exp_org_structure_id, exp_org_structure_version_id, proj_org_structure_id, proj_org_structure_version_id, business_group_id, and org_id.
  • PER_ORG_STRUCTURE_VERSIONS — provides the version number (posv.version_number) and links the version record to the structure.
  • PER_ORGANIZATION_STRUCTURES — supplies the structure name (pos.name) which is aliased to org_structure_name.
  • PA_ALL_ORGANIZATIONS — joins the implementation org_id to the valid organizations having a matching pa_org_use_type of 'EXPENDITURES' or 'PROJECTS', filtered to active records (inactive_date is null).
  • PA_RESOURCE_UTILS (package) — the get_organization_name function is invoked on both paorg.organization_id and imp.org_id, the latter producing the ou_name column.

Join conditions are driven through exp_org_structure_version_id = posv.org_structure_version_id and posv.organization_structure_id = pos.organization_structure_id. The view is a UNION of the Expenditure branch and the Project branch, distinguished by the literal structure_type value.

Key Columns

  • structure_type — literal 'EXPENDITURE' or 'PROJECT', indicating the originating hierarchy.
  • org_structure_id / org_structure_version_id — identifiers for the structure and its active version.
  • org_structure_name / version_number — human-readable structure and version labels.
  • organization_id and the returned get_organization_name(...) value — the organization within the hierarchy and its name.
  • business_group_id — the HR business group owning the implementation.
  • org_id — the operating unit identifier from the implementation.
  • ou_name — the operating unit name resolved by pa_resource_utils.get_organization_name(imp.org_id).

Common Use Cases and Queries

Typical uses include validating Operating Unit to organization hierarchy mapping, driving integration extracts, and reconciling PA implementation setup. A representative query to inspect the Operating Unit name and its hierarchies is:

SELECT structure_type, org_structure_name, version_number,
       organization_id, ou_name, business_group_id, org_id
FROM   apps.pa_r_hierarchies_v
WHERE  ou_name = '&ou_name'
ORDER BY structure_type, org_structure_name;

To obtain distinct operating units per hierarchy type:

SELECT DISTINCT structure_type, org_id, ou_name
FROM   apps.pa_r_hierarchies_v
ORDER BY structure_type, ou_name;

All access should be granted through the APPS schema, and because the view returns no MOAC-restricted filter, callers should apply org_id predicates when reporting across multiple operating units.