Search Results pa_proj_org_structures_v




Overview
Explore in AI Chat

Overview

PA_PROJ_ORG_STRUCTURES_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Within the Projects (PA) product, it exposes the implementation-defined Project organization hierarchy — that is, the reporting and security structure an enterprise has configured for the organizations that own and execute projects. Unlike tables that simply store organization units, this view flattens and resolves the parent-child relationships defined in the Project organization structure version selected in PA_IMPLEMENTATIONS, joining them to descriptive organization names and enforcing the security predicate that identifies valid project-owning organizations.

Because it is a view rather than a table, it holds no data of its own; it is a query surface intended for reporting, integration, and configuration validation. It is commonly referenced when developers or analysts need to determine which organization is the effective project-owning organization and where it sits in the hierarchy, or when building hierarchy-based reporting against the standard PA implementation setup.

Underlying Base Objects

The view is defined over a mix of PA and HR objects. The core hierarchical data comes from PER_ORG_STRUCTURE_ELEMENTS, which stores parent and child organization pairs for a given organization structure version. PA_IMPLEMENTATIONS supplies the implementation context, providing PROJ_ORG_STRUCTURE_VERSION_ID and PROJ_START_ORG_ID, which anchor the hierarchy traversal.

Organization attributes are drawn from HR_ORGANIZATION_UNITS (ORG1, the child), HR_ORG_UNITS_NO_JOIN (ORG2, the parent, outer-joined), and HR_ALL_ORGANIZATION_UNITS_TL (ORG2T, the parent's translated name, outer-joined with a language predicate against USERENV('LANG')). A CONNECT BY subquery walks PER_ORG_STRUCTURE_ELEMENTS recursively to confirm the child organization resides beneath the implementation start organization, unioned with the start organization itself. The EXISTS clause on HR_ORGANIZATION_INFORMATION restricts results to organizations classified as PA_PROJECT_ORG with ORG_INFORMATION2 equal to 'Y'. Documented base objects include HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_INFORMATION, HR_ORGANIZATION_UNITS, HR_ORG_UNITS_NO_JOIN, PA_IMPLEMENTATIONS, PER_ORG_STRUCTURE_ELEMENTS, DUAL, and the packages HR_GENERAL and HR_SECURITY. All PA, HR, and DUAL references resolve through APPS synonyms within the APPS schema.

Key Columns

Common Use Cases and Queries

Typical uses include resolving project organization ancestry for reporting, validating hierarchy configuration after setup changes, and confirming which organization heads the project hierarchy. The following example lists each project organization with its parent:

  • SELECT organization_id, organization_name, parent_org_id, parent_org_name
  • FROM apps.pa_proj_org_structures_v
  • WHERE org_id = :p_org_id
  • ORDER BY parent_org_id, organization_name;

To list only the top-level project organizations where no parent is defined, developers filter on PARENT_ORG_ID IS NULL. Because the view joins translated name columns and the language is resolved from USERENV('LANG'), results returned through a reporting tool reflect the session language. Joining this view to PA_PROJECTS on the owning organization allows projects to be grouped by hierarchical parent organization for portfolio and security reporting.