Search Results schedule_at_completion




Overview

The view PA_TASK_DET_EARNED_VALUES belongs to the Oracle Projects (PA) module and is intended to expose detailed earned value data at the project task level. In the Oracle E-Business Suite reporting and integration model, views of this type act as reporting façades layered over the core Projects transactional tables. They allow developers, report authors, and integrators to query a normalized set of earned value management (EVM) attributes — such as budgeted cost of work scheduled, physical percent complete, estimate at completion, and performance indices — without directly joining the underlying element and structure tables.

The view is documented in the ETRM metadata for release 12.2.2. The metadata explicitly records the implementation/DBA status as "Not implemented in this database," meaning the view definition exists in the data dictionary but is not created in every environment. Report and integration code that references this object must therefore confirm its existence before execution. The metadata does not document an owner or any referenced base objects.

Underlying Base Objects

The ETRM excerpt does not formally document referenced base objects. However, the supplied view text identifies three tables in the FROM clause: PA_PROJECTS_ALL, PA_PROJ_ELEMENT_VERSIONS, and PA_LOOKUPS.

  • PA_PROJECTS_ALL supplies the project identifier and the project currency code, joined on PROJECT_ID.
  • PA_PROJ_ELEMENT_VERSIONS provides the element version, project element, object type, and parent structure version identifiers, and is joined to PA_PROJECTS_ALL on PROJECT_ID.
  • PA_LOOKUPS is joined with LOOKUP_TYPE = 'UNIT' and LOOKUP_CODE = 'HOURS', returning the unit of measure meaning for the HOURS column.

The remaining columns are populated as NULL placeholders by the view text. These placeholders correspond to earned value, percent complete, cost, and schedule attributes that are normally aggregated from Projects and earned value tables. Because the metadata states no base objects are documented, the authoritative join logic should be confirmed against the actual deployment.

Key Columns

The column list recorded in the metadata represents the earned value reporting interface:

Common Use Cases and Queries

Typical scenarios include reviewing earned value performance by task, producing EVM status reports, and extracting performance indices for integration with external scheduling or financial systems. Performance indices and physical percent complete are commonly aggregated up the task hierarchy using PARENT_STRUCTURE_VERSION_ID and PROGRESS_ROLLUP_METHOD. A representative query follows:

  • SELECT PROJECT_ID, PROJ_ELEMENT_ID, EARNED_VALUE, COST_PERFORMANCE_INDEX, SCHEDULE_PERFORMANCE_INDEX, PROGRESS_ROLLUP_METHOD FROM PA_TASK_DET_EARNED_VALUES WHERE PROJECT_ID = :project_id;
  • SELECT PROJECT_ID, PHYSICAL_PERCENT_COMPLETE, COST_VARIANCE, SCHEDULE_VARIANCE, PROJECT_CURRENCY_CODE FROM PA_TASK_DET_EARNED_VALUES;

Before use, verify that the view is actually deployed in the target environment, given the documented "Not implemented" status.