Results for “perc_comp_derivative_code”

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

Overview

PA_PROJ_ROLLUP_TEMP is a transient working table owned by the PA (Projects) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM repository, its purpose is to generate schedules for sets of dates in a project. Records are inserted during processing and deleted at the end of the user session, making the table a session-scoped staging area rather than a permanent repository of project data.

The table is central to rollup and scheduling operations within Oracle Projects. When a user requests project schedule generation, date rollups, or earned value rollups across a WBS hierarchy, rows are written to PA_PROJ_ROLLUP_TEMP for the duration of the session, processed, and then purged. Because the population is short-lived, DBAs should expect churn and should not treat the contents as a system of record.

From a Data Vault modeling perspective, the metadata's heuristic classification is link. This classification is sensible: the table's identity is defined by the combination of PROCESS_NUMBER, OBJECT_TYPE, and OBJECT_ID (the documented unique index PA_PROJ_ROLLUP_TEMP_U1), and it carries multiple foreign key references to PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS on both OBJECT_ID and PARENT_OBJECT_ID — a pattern characteristic of an associative or relationship table capturing parent/child rollup contexts.

Key Information Stored

The documented physical schema exposes 36 columns. The most significant for functional understanding include:

• PROCESS_NUMBER — Identifies the processing run or session that populated the row; part of the unique business key.
• OBJECT_ID and OBJECT_TYPE — Identify the project element (task, resource, etc.) being rolled up; together with PROCESS_NUMBER these form the unique index PA_PROJ_ROLLUP_TEMP_U1. OBJECT_ID is also a foreign key to PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS.
• PARENT_OBJECT_ID and PARENT_OBJECT_TYPE — Establish the hierarchy used during rollup; PARENT_OBJECT_ID similarly references PA_PROJ_ELEMENTS and PA_PROJ_ELEMENT_VERSIONS.
• CALENDAR_ID — The project calendar applied when deriving schedule dates.
• CONSTRAINT_TYPE_CODE and CONSTRAINT_DATE — Scheduling constraint enforced on the element and the associated date.
• WBS_LEVEL — Depth of the element within the work breakdown structure, used to order rollup processing.
• START_DATE, START_DATE_OVERRIDE, FINISH_DATE, and DURATION — The computed scheduling window and any manual overrides.
• TASK_STATUS, PROGRESS_STATUS_WEIGHT, PROGRESS_OVERRIDE, PERCENT_COMPLETE, PERCENT_OVERRIDE, and TASK_WEIGHT — Progress tracking inputs and overrides applied during rollup.
• REMAINING_EFFORT, ETC_COST, and related PPL/EQPMT and SUB_PRJ columns — Estimated-to-complete and remaining effort measures rolled up across the hierarchy.
• EARNED_VALUE, BAC_VALUE, and PERC_COMP_DERIVATIVE_CODE — Earned value metrics derived during processing.
• ROLLUP_NODE and DIRTY_FLAG — Flag whether the row is a rollup aggregation point and whether it requires recomputation.

The unique index PA_PROJ_ROLLUP_TEMP_U1 on (PROCESS_NUMBER, OBJECT_TYPE, OBJECT_ID) is the documented business-key candidate; no separate surrogate primary key column is enumerated in the metadata.

Common Use Cases and Queries

Typical scenarios include diagnosing rollup performance, verifying schedule output for a specific process, and debugging parent/child aggregation. Because rows are session-scoped, queries must run against an active session or a captured snapshot.

Sample query to inspect a process run:

SELECT PROCESS_NUMBER, OBJECT_ID, OBJECT_TYPE, WBS_LEVEL,
       START_DATE, FINISH_DATE, PERCENT_COMPLETE, EARNED_VALUE
  FROM PA.PA_PROJ_ROLLUP_TEMP
 WHERE PROCESS_NUMBER = :process_number
 ORDER BY WBS_LEVEL, OBJECT_ID;

To identify elements needing recomputation:

SELECT OBJECT_ID, OBJECT_TYPE, PARENT_OBJECT_ID, ROLLUP_NODE
  FROM PA.PA_PROJ_ROLLUP_TEMP
 WHERE DIRTY_FLAG = 'Y';

Reporting use cases include validating WBS-level cost and effort rollups (ETC_COST, SUB_PRJ_ETC_COST), auditing earned value output (EARNED_VALUE, BAC_VALUE), and confirming that override flags (PROGRESS_OVERRIDE, START_DATE_OVERRIDE) were honored.

Related Objects

The documented foreign keys tie this table to the core project structure tables. Significant related objects include:

• PA_PROJ_ELEMENTS — referenced via OBJECT_ID and PARENT_OBJECT_ID; holds the project element definitions used in the rollup.
• PA_PROJ_ELEMENT_VERSIONS — referenced via OBJECT_ID and PARENT_OBJECT_ID; provides versioned attributes of elements used during scheduling.
• PA_PROJECTS — parent project context for the elements being rolled up.
• PA_TASKS — task-level details subordinate to the element hierarchy.
• PA_CALENDARS — source of CALENDAR_ID used for date derivation.
• PA_BUDGET_VERSIONS and PA_COST_DISTRIBUTION_LINES — cost sources feeding ETC_COST and EARNED_VALUE calculations.
• Oracle Projects APIs such as PA_SCHEDULE_PUB and rollup concurrent programs that populate and consume this table.