Search Results pa_utilization_options_all




Overview

PA_UTILIZATION_OPTIONS_ALL is a Projects (PA) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the parameters and defaults that define the various utilization options used by the utilization reporting and forecasting engine. Utilization reporting compares applied effort against available capacity for resources, organizations, and projects; the options held in this table determine which accounting periods are included, which thresholds drive date ranges, and which actual-versus-forecast basis is applied when the utilization process runs.

The table is organization-partitioned by operating unit. If the installation is multi-organization, one row is defined for each operating unit; a single organization installation would hold a single configuration row. Every row carries the ORG_ID column, which is the business key and is enforced by the unique index PA_UTILIZATION_OPTIONS_ALL_U1 (ORG_ID). This makes the table a one-row-per-operating-unit configuration store rather than a transactional ledger. In Data Vault modeling terms, the mined FK structure classifies this table as satellite-leaning: it holds descriptive, non-key attributes (flags, dates, and run timestamps) that describe a business entity — the operating unit defined in HR_ALL_ORGANIZATION_UNITS — and its foreign key references that parent entity rather than forming an independent hub or a many-to-many link.

Key Information Stored

The table exposes 13 documented columns. The most significant are:

  • ORG_ID — Operating unit identifier and the unique business-key candidate (index PA_UTILIZATION_OPTIONS_ALL_U1). It is the FK to HR_ALL_ORGANIZATION_UNITS and the column that makes the table operating-unit specific.
  • GL_PERIOD_FLAG — Controls whether General Ledger periods are used as the basis for utilization period selection.
  • PA_PERIOD_FLAG — Controls whether Oracle Projects periods drive the utilization period selection, allowing the process to use PA-defined period boundaries.
  • GLOBAL_EXP_PERIOD_FLAG — Governs the use of a global expenditure period convention, relevant when expenditure items must be grouped consistently across operating units.
  • FORECAST_THRU_DATE — The cutoff date through which forecast utilization is calculated.
  • ACTUALS_THRU_DATE — The cutoff date through which actual utilization is calculated.
  • ACTUALS_LAST_RUN_DATE — Timestamp of the last actuals utilization run, used for incremental processing and audit.
  • FORECAST_LAST_RUN_DATE — Timestamp of the last forecast utilization run.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit and concurrency tracking.

No standalone surrogate primary key column is documented in the ETRM extract; ORG_ID functions as the de facto primary key via the unique index.

Common Use Cases and Queries

Typical uses include reviewing or validating the utilization configuration for each operating unit, diagnosing why a utilization report returns an unexpected date range, and building reporting queries over the actuals and forecast run timestamps to monitor process freshness.

SELECT org_id,
       gl_period_flag,
       pa_period_flag,
       global_exp_period_flag,
       actuals_thru_date,
       forecast_thru_date,
       actuals_last_run_date,
       forecast_last_run_date
FROM   pa.pa_utilization_options_all
WHERE  org_id = :p_org_id;

A monitoring query can flag operating units whose forecast has not been refreshed recently:

SELECT org_id,
       forecast_last_run_date,
       SYSDATE - forecast_last_run_date AS days_since_run
FROM   pa.pa_utilization_options_all
WHERE  forecast_last_run_date IS NULL
   OR  SYSDATE - forecast_last_run_date > 1
ORDER BY org_id;

Because the table is one row per operating unit, it is frequently joined to organization and operating-unit reference data for cross-unit dashboard reporting.

Related Objects

  • HR_ALL_ORGANIZATION_UNITS — Parent of the ORG_ID foreign key; supplies the operating unit name and context for each configuration row.
  • PA_UTILIZATION_OPTIONS_ALL unique index PA_UTILIZATION_OPTIONS_ALL_U1 — Enforces one row per ORG_ID.
  • GL_PERIODS / PA_PERIODS — Referenced indirectly through the GL_PERIOD_FLAG and PA_PERIOD_FLAG settings to determine utilization period boundaries.
  • PA_PROJECTS_ALL and PA_PROJECTS — Provide project context for the resources whose utilization is evaluated under these options.
  • PER_ALL_PEOPLE_F and HR_EMPLOYEES — Supply resource records whose applied effort is measured against the configured utilization options.
  • ORG_ORGANIZATION_DEFINITIONS / HR_OPERATING_UNITS — Operating unit definitions used to resolve ORG_ID into a reporting label.
  • PA_UTILIZATION APIs and concurrent programs — The utilization calculation programs read this table to obtain defaults at run time.