Search Results pa_project_type_distributions




Overview
Explore in AI Chat

Overview

The PA_PROJECT_TYPE_DISTRIBUTIONS view is a single-organization (Single-Org) reporting object within the Oracle Projects (PA) module. It exposes project type distribution rule assignments, which govern how a given project type distributes costs, revenue, or other amounts according to a defined distribution rule. In Oracle EBS 12.1.1 and 12.2.2, this view is the operational, Org-secured form of the underlying project type distributions data, presented for querying by users and application logic that operate within a specific operating unit.

Because it is a view rather than a table, it carries no independent storage. Its primary role is to deliver a filtered, business-friendly projection of the multi-organization base data, allowing reports, concurrent programs, and integrations to read only the rows relevant to the current organization context. The view is documented as single-org, which means the operating unit filter is applied automatically through the session context rather than being supplied explicitly by the caller.

Underlying Base Objects

The view is defined over PA_PROJ_TYPE_DISTRIBUTIONS_ALL, the multi-organization table that stores project type distribution records for every operating unit. The view text selects the same columns from this base table but constrains the result set using the current organization identifier, so that callers see only rows belonging to the active operating unit.

The filtering predicate compares ORG_ID to a value derived from the session's CLIENT_INFO, using ORG_ID from the base table. Where ORG_ID is null, the view treats the row as global data applicable to all organizations, returning it through the NVL logic. Only rows whose ORG_ID matches the session organization (or that are global) are returned. No additional base objects are documented for this view, and the ETRM metadata records no implementations of the view in the reference database.

Key Columns

  • PROJECT_TYPE — The project type to which the distribution rule applies. This is the principal classifier and joins to the project type definition.
  • DISTRIBUTION_RULE — Identifies the distribution rule assigned to the project type, controlling how amounts are allocated.
  • DEFAULT_FLAG — Indicates whether the distribution rule is the default for the project type.
  • ORG_ID — The operating unit that owns the record. Null values represent global entries visible to all organizations.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns capturing who created and last modified the row and when.

Common Use Cases and Queries

Typical uses include validating project type configuration before project creation, auditing which distribution rules are default per project type, and feeding downstream reporting that must respect operating unit security. A representative query lists distribution rules and default status for the current organization:

  • SELECT PROJECT_TYPE, DISTRIBUTION_RULE, DEFAULT_FLAG, ORG_ID FROM PA_PROJECT_TYPE_DISTRIBUTIONS ORDER BY PROJECT_TYPE, DEFAULT_FLAG;
  • SELECT PROJECT_TYPE, DISTRIBUTION_RULE FROM PA_PROJECT_TYPE_DISTRIBUTIONS WHERE DEFAULT_FLAG = 'Y';
  • SELECT d.PROJECT_TYPE, d.DISTRIBUTION_RULE FROM PA_PROJECT_TYPE_DISTRIBUTIONS d WHERE NVL(d.ORG_ID, -99) = NVL(:org_id, -99);

Because the view enforces Org security automatically, it is preferable to the _ALL table in user-facing reports and for integration interfaces that must not expose cross-organization data. When a process legitimately requires all organizations, the base table PA_PROJ_TYPE_DISTRIBUTIONS_ALL should be queried instead, with appropriate access controls.