Search Results pa_organizations_expend_v




Overview

PA_ORGANIZATIONS_EXPEND_V is a public Oracle E-Business Suite view owned by the APPS schema and classified under the Projects (PA) product family. Its purpose is to expose the set of organizations that may legitimately be selected as an expenditure organization during expenditure entry and related transactional processing. In Oracle Projects, not every organization defined in Human Resources is eligible to own or incur project expenditures; classification is governed by organization use types maintained in PA_ALL_ORGANIZATIONS. This view narrows the universe of HR organizations down to those explicitly flagged with the EXPENDITURES use type and that remain active.

Because the view performs the eligibility filtering centrally, it serves as a consistent, reusable source for reporting, validation, and integration. Oracle Forms, concurrent programs, and third-party interfaces that need to present or validate a list of valid expenditure organizations can query the view instead of reconstructing the classification logic. It also participates in Oracle's Multi-Org (MO) security model, so the rows returned are constrained by the operating unit context of the session.

Underlying Base Objects

The view is defined over two primary sources joined on ORGANIZATION_ID:

  • HR_ORGANIZATION_UNITS (aliased HRORG) — the HR organization definition, supplying the organization identifier, business group, name, and effective dates.
  • PA_ALL_ORGANIZATIONS (aliased PAORG) — the Projects organization classification table, supplying the use type, inactive date, and operating unit (ORG_ID).

The documented referenced objects also include the MO_GLOBAL package, HR_SECURITY, and HR_GENERAL. MO_GLOBAL is invoked in the WHERE clause through GET_CURRENT_ORG_ID and CHECK_ACCESS to enforce multi-org access. HR_SECURITY and HR_GENERAL are typically referenced via HR organization security logic and are listed as dependencies of the underlying HR views. The join predicate applies three filters: PA_ORG_USE_TYPE = 'EXPENDITURES', INACTIVE_DATE IS NULL, and an MO access condition ensuring that either no operating unit is set (with CHECK_ACCESS returning 'Y') or the organization's ORG_ID matches the session's current operating unit.

Key Columns

  • ORGANIZATION_ID — The HR organization identifier; the primary key value used to select an expenditure organization.
  • BUSINESS_GROUP_ID — The business group to which the organization belongs, relevant in multi-business-group deployments.
  • NAME — The organization name, used for display in lists of values and reports.
  • DATE_FROM / DATE_TO — The effective date range of the organization; useful for date-sensitive validation even though the view already excludes organizations with an inactive date.
  • ACTIVE_FLAG — A literal value of 'Y' projected by the view, indicating that returned rows are active and usable.
  • ORG_ID — The operating unit identifier from PA_ALL_ORGANIZATIONS, driving multi-org security and reporting by operating unit.

Common Use Cases and Queries

Typical scenarios include building a list of values for expenditure entry, auditing which organizations are enabled for project expenditures within an operating unit, and driving integration extracts that must respect organizational security. A basic query retrieves the eligible organizations visible to the current session:

  • SELECT organization_id, name, business_group_id, org_id FROM apps.pa_organizations_expend_v ORDER BY name;
  • SELECT organization_id, name FROM apps.pa_organizations_expend_v WHERE org_id = :p_org_id; — filters to a specific operating unit for reporting.
  • SELECT v.name, v.date_from, v.date_to FROM apps.pa_organizations_expend_v v WHERE v.organization_id = :p_org_id; — validates and displays details for a single organization.

Because membership is derived from the EXPENDITURES use type in PA_ALL_ORGANIZATIONS, organizations missing from this view generally require the corresponding use type to be assigned before they can be selected in expenditure entry.