Results for “pa_earned_values”

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

Overview

PA_EARNED_VALUES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the earned value history for the lowest-level tasks and resources, as well as project-task level rows. The table is owned by the PA schema and holds 26 documented columns. Its purpose is to persist periodic snapshots of Earned Value Management (EVM) metrics computed against a project structure, so that historical trending, variance analysis, and progress reporting can be performed without recomputing values from transaction detail. Each row is keyed by the combination of project, task, and resource list member, and is additionally qualified by an as-of date and a current flag, meaning the table behaves as a slowly changing history of EVM measurements rather than a single live record.

Under the heuristic Data Vault classification derived from its foreign key structure, PA_EARNED_VALUES is best modeled as a link. Its primary key (PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID) is composed entirely of foreign key references to other entities, which is the characteristic signature of an association or link table connecting project, task, and resource dimensions. The measured amounts (BCWS, ACWP, BCWP and their variants) act as effectivity or descriptive attributes carried on that relationship.

Key Information Stored

The primary key PA_EARNED_VALUES_PK is a composite surrogate/business key of PROJECT_ID, TASK_ID, and RESOURCE_LIST_MEMBER_ID. These three columns are business-key candidates, as each is a documented foreign key to a parent entity and together they uniquely identify the measurement context. PROJECT_ID references PA_PROJECTS_ALL, TASK_ID references PA_TASKS, and RESOURCE_LIST_MEMBER_ID references PA_RESOURCE_LIST_MEMBERS.

• AS_OF_DATE – the effective date of the earned value snapshot, governing which historical row applies to a given reporting period.
• CURRENT_FLAG – indicates whether the row is the most recent (current) measurement for the project/task/resource combination.
• BCWS / BCWP / ACWP / BAC – the classic EVM base amounts (Budgeted Cost of Work Scheduled, Budgeted Cost of Work Performed, Actual Cost of Work Performed, and Budget at Completion) for the period.
• BCWS_ITD / BCWP_ITD / ACWP_ITD / BAC_ITD – the corresponding inception-to-date cumulative values.
• BQWS / BQWP / AQWP / BAQ – quantity-based counterparts to the cost metrics (budgeted and actual quantities of work), enabling quantity-variance analysis where resources are measured in units rather than currency.
• BQWS_ITD / BQWP_ITD / AQWP_ITD / BAQ_ITD – inception-to-date cumulative quantity values.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard EBS WHO (Who) audit columns recording creation and modification provenance.

Common Use Cases and Queries

The most common use case is retrieving the current or latest earned value position for a project and task, typically filtered on CURRENT_FLAG or on the maximum AS_OF_DATE. Analysts frequently report cost and schedule performance indices derived from the stored amounts, for example CPI = BCWP / ACWP and SPI = BCWP / BCWS. Historical trending against AS_OF_DATE supports period-over-period variance reporting, while the ITD columns support cumulative project-to-date cost and schedule performance dashboards.

SELECT project_id, task_id, resource_list_member_id,
       as_of_date, bcws, bcwp, acwp, bac
FROM   pa.pa_earned_values
WHERE  project_id = :p_project_id
AND    current_flag = 'Y';

A second pattern joins the parent entities to produce business-named reports, joining to PA_PROJECTS_ALL and PA_TASKS on the respective key columns. A third pattern identifies the latest snapshot per key using a correlated MAX(AS_OF_DATE) subquery or analytic ranking when CURRENT_FLAG is not maintained.

Related Objects

The following objects are the most significant for integration and join purposes, based on the documented foreign key relationships:

• PA_PROJECTS_ALL – join on PA_EARNED_VALUES.PROJECT_ID = PA_PROJECTS_ALL.PROJECT_ID to resolve project name, number, and status.
• PA_TASKS – join on PA_EARNED_VALUES.TASK_ID = PA_TASKS.TASK_ID for task name and structure.
• PA_RESOURCE_LIST_MEMBERS – join on PA_EARNED_VALUES.RESOURCE_LIST_MEMBER_ID = PA_RESOURCE_LIST_MEMBERS.RESOURCE_LIST_MEMBER_ID to identify the resource or role measured.

Reporting typically layers earned value metrics from this table over the project and task hierarchies provided by PA_PROJECTS_ALL and PA_TASKS, while the resource context is resolved through PA_RESOURCE_LIST_MEMBERS.