Search Results pa_organizations_v




Overview
Explore in AI Chat

Overview

PA_ORGANIZATIONS_V is a public APPS-schema view in the Oracle E-Business Suite Projects (PA) module. Its purpose is to expose organization records from Oracle Human Resources in a form suited to Projects reporting and integration. In the documented metadata the view is labeled simply "View: PA_ORGANIZATIONS_V," with a status of VALID and an owner of APPS, confirming it is a seeded, supported database object rather than a customer-defined customization.

The view projects the core descriptive attributes of organization units — identifier, name, business group, effective dates, and type — and appends a derived column, WITHIN_CURRENT_OPERATING_UNIT. This last attribute is populated at runtime through HR security logic rather than stored on the organization record itself, which is the principal reason a view exists instead of direct table access. The view therefore serves as a stable, security-aware read interface for Projects code, concurrent programs, and external integrations that need the set of organizations visible in the user's current operating unit.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists the base objects referenced by the view as HR_ORGANIZATION_UNITS (a view), HR_GENERAL (a package), and HR_SECURITY (a package). The published view text confirms the core projection:

At the stored level, HR_ORGANIZATION_UNITS is itself a view over HR_ALL_ORGANIZATION_UNITS. The remaining NULL position in the SELECT list corresponds to WITHIN_CURRENT_OPERATING_UNIT; in the shipped definition this is resolved by calling the HR security and general utility packages (notably HR_SECURITY and HR_GENERAL) rather than being read from a column. The net effect is a lightweight wrapper that inherits standard HR organization attributes while adding operating-unit scoping.

Key Columns

  • ORGANIZATION_ID — Primary key of the organization unit. This is the value stored on Projects entities (for example projects, tasks, and expenditure organizations) and the join key back to HR.
  • NAME — The organization's display name as maintained in the HR organization hierarchy.
  • BUSINESS_GROUP_ID — The business group that owns the organization; organizations with a NULL business group are typically operating units or internal classifications.
  • DATE_FROM / DATE_TO — Effective start and end dates of the organization record, used to determine whether an organization is active as of a given date.
  • TYPE — The organization classification code, distinguishing business groups, operating units, inventory organizations, and other HR organization types.
  • WITHIN_CURRENT_OPERATING_UNIT — A derived indicator (typically 'Y' or 'N') showing whether the organization falls within the operating unit of the current session, based on HR security profiles.

Common Use Cases and Queries

The view is most often used to populate organization-related list of values, to validate that a selected organization is visible within the current operating unit, and to join Projects transaction data to organization names for reporting. A typical query lists active organizations in the present operating unit:

  • SELECT organization_id, name, business_group_id, date_from, date_to
    FROM pa_organizations_v
    WHERE within_current_operating_unit = 'Y'
    AND SYSDATE BETWEEN NVL(date_from, SYSDATE)
    AND NVL(date_to, SYSDATE);

Because WITHIN_CURRENT_OPERATING_UNIT depends on HR security context, results differ by responsibility and operating unit; queries run in a background or multi-org session may not return the expected rows unless the security context is initialized. The view is best treated as a reporting and lookup aid — persistent references should store ORGANIZATION_ID, not the derived indicator, since that value is context-dependent and not part of the underlying organization record.