Search Results pa_operating_units_v




Overview
Explore in AI Chat

Overview

APPS.PA_UTILIZATION_OPTIONS_V is a reporting and integration view in Oracle Projects (PA) that exposes utilization processing options at the operating unit level. Utilization options in Oracle Projects control how the application evaluates and reports on resource utilization, including which period basis (GL period, PA period, or a global expenditure period) is used for utilization calculations, and the date boundaries through which forecast and actual amounts are considered valid. The view joins the transactional configuration table PA_UTILIZATION_OPTIONS to the operating unit reference view PA_OPERATING_UNITS_V, translating the numeric ORG_ID into a recognizable operating unit name. Because it is owned by APPS and resolves operating units by name, the view is well suited for multi-organization reporting, cross-operating-unit comparisons, and integration extracts that must present human-readable operating unit context rather than raw organization identifiers.

Underlying Base Objects

The view is defined with the following ETRM-documented text:

  • PA_UTILIZATION_OPTIONS — the base table (referenced through the APPS synonym PA_UTILIZATION_OPTIONS) holding the actual utilization flags and date settings per organization.
  • PA_OPERATING_UNITS_V — the operating unit reference view that supplies the OPERATING_UNIT name. The join condition is PUO.ORG_ID = POUV.ORG_ID.
  • MO_GLOBAL — the package referenced as a documented dependency, used to resolve the current operating unit context (MO_GLOBAL is the standard Multi-Org access initialization package).

Because the join is an equi-join on ORG_ID without an outer join, only utilization option records whose ORG_ID matches a valid operating unit in PA_OPERATING_UNITS_V are returned. The view also selects PUO.ROWID, exposing the row identifier of the underlying PA_UTILIZATION_OPTIONS row, which supports updateable-view and locking scenarios.

Key Columns

  • ROWID — row identifier of the underlying PA_UTILIZATION_OPTIONS record.
  • ORG_ID — the organization (operating unit) identifier from the base table.
  • OPERATING_UNIT — the operating unit name obtained from PA_OPERATING_UNITS_V.
  • GL_PERIOD_FLAG — indicates whether the GL period drives the utilization period basis.
  • PA_PERIOD_FLAG — indicates whether the PA (Projects) period drives the utilization period basis.
  • GLOBAL_EXP_PERIOD_FLAG — indicates whether a global expenditure period is used as the utilization period basis.
  • FORECAST_THRU_DATE — the date through which forecast utilization data is considered.
  • ACTUALS_THRU_DATE — the date through which actual utilization data is considered.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns propagated from the base table.

The three period flags are mutually exclusive in practice; typically exactly one is set to indicate the active utilization period basis for the operating unit.

Common Use Cases and Queries

This view is commonly queried to audit utilization configuration across operating units, to reconcile period-basis settings before running utilization reports, and to drive integration extracts. A representative query listing configuration for all operating units follows:

  • SELECT operating_unit, gl_period_flag, pa_period_flag, global_exp_period_flag, forecast_thru_date, actuals_thru_date FROM apps.pa_utilization_options_v ORDER BY operating_unit;
  • SELECT operating_unit, actuals_thru_date FROM apps.pa_utilization_options_v WHERE pa_period_flag = 'Y';
  • SELECT operating_unit FROM apps.pa_utilization_options_v WHERE org_id = :p_org_id;

Because Multi-Org security applies through MO_GLOBAL and the ORG_ID policy on the base table, the rows returned in a session depend on the operating unit context set at runtime. When validating configuration for a specific operating unit, callers should initialize the Org context before querying, or filter explicitly by ORG_ID where privileged access permits.