Search Results as_of_date




Overview
Explore in AI Chat

Overview

The PA_PROG_ACT_BY_PERIOD_V view is a Projects (PA) module database object that exposes incremental actual cost and effort figures for project progress reporting, aggregated by progress period. It is not a standalone reporting table but a computed view layered over PA_PROGRESS_ROLLUP and related assignment structures. Its central role is to answer the question "how much actual cost and actual effort has accrued against a project, task assignment, or resource for a given progress period, as evaluated at a specific point in time?" That point in time is supplied by the as_of_date parameter, which is the term most frequently used when searching for this object.

Unlike static cost tables, this view returns values calculated on demand by calling PA_PROGRESS_UTILS package functions. The results therefore always reflect the state of transactions relative to the supplied as-of date and progress period rather than a pre-stored summary.

Underlying Base Objects

The documented view text references the following base objects:

  • PA_PROGRESS_ROLLUP (PPR) — supplies the project, object, structure version, project element, progress period name, currency code, and object version identifiers that drive each row.
  • PA_TASK_ASSIGNMENTS_V (PTAV) — supplies the resource assignment and resource list member identifiers associated with the task.
  • PA_PROJ_ELEMENT_VERSIONS (ELEM) — supplies the parent structure version identifier linking the element to its hierarchy.

Note that ETRM lists no formally documented base tables for this view, so the relationships above are inferred directly from the view definition. The heavy lifting is performed by the PA_PROGRESS_UTILS functions, which resolve the actual figures at runtime.

Key Columns

Common Use Cases and Queries

Typical usage includes progress and earned-value reporting, period-over-period cost comparison, and reconciliation of incremental actuals for a specific as-of date.

SELECT project_id,
       proj_element_id,
       prog_pa_period_name,
       as_of_date,
       txn_currency_code
FROM   pa_prog_act_by_period_v
WHERE  project_id = :p_project_id
AND    as_of_date = :p_as_of_date
AND    prog_pa_period_name = :p_period;

Because all monetary and effort columns are computed, filter as narrowly as possible on project, period, and as-of date before selecting the calculated columns to control runtime cost. The view is best suited to reporting and integration scenarios where the caller can supply an explicit as-of date rather than requiring pre-aggregated stored balances.