Results for “internal_external_flag”

4 results




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

Overview

PABV_ORGANIZATIONS is an APPS-owned, read-only view in the Oracle E-Business Suite Projects (PA) module. It presents a consolidated, security-filtered list of organizations that are enabled for use within Oracle Projects, joining human resources organization data with Projects-specific configuration. The "PABV" prefix indicates that this is a Projects (PA) Business View, a class of views that Oracle Projects exposes for reporting, inquiry, and integration purposes rather than as an application base table.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as the primary reporting interface for project and expenditure organizations. It answers the recurring question of which HR organizations may be assigned as project organizations or expenditure organizations, and it resolves the descriptive information (name, location, dates, use type) required for display in forms, concurrent programs, and custom reports. Because the view contains a security predicate based on the Projects implementation Org ID, its results are scoped to the operating unit or organization context in which the query is executed.

Underlying Base Objects

The view is defined over the following documented objects:

Key Columns

Common Use Cases and Queries

The view is typically queried as a validation list source, an LOV backing query, or a reporting data source. A common pattern is to list all project organizations available to the current session:

  • SELECT organization_id, organization_name, org_use_type, meaning FROM apps.pabv_organizations WHERE org_use_type = 'PA_PROJECT_ORG'
  • SELECT organization_id, organization_name, location_name, inactive_date FROM apps.pabv_organizations WHERE inactive_date IS NULL ORDER BY organization_name
  • Use as a security-filtered validation query in a custom concurrent program or OAF page where the effective Org ID must be respected.

Because the view includes a WITH READ ONLY clause and a security predicate, no DML is permitted and results are restricted to the accessible implementation. It is most reliable when queried within the correct Projects responsibility and operating unit context.