Search Results progress_status_weight

Overview

PA_TASK_PROGRESS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the PA (Projects) product family and consolidates task-level (project element) progress information into a single denormalized row. The view joins project headers, project element versions, element schedules, rollup progress, percent-complete records, and status lookup descriptions so that report writers, Oracle Business Intelligence queries, and custom extensions can retrieve progress metrics without recreating the underlying multi-table joins.

The object appears in the ETRM reference with a status of VALID and is referenced heavily by progress reporting infrastructure. Because it also resolves descriptive meaning columns (through PA_LOOKUPS and the PA_PROJ_ELEMENTS_UTILS and PA_CONTROL_ITEMS_UTILS packages), it is frequently used as a source for task-level dashboards and for progress publication reporting.

Underlying Base Objects

The view is defined primarily over these PA synonyms and views: PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_STRUCTURE_TYPES, PA_TASK_TYPES, PA_PROJECT_STATUSES, PA_LOOKUPS, PA_PERCENT_COMPLETES, and PA_PROGRESS_ROLLUP. It also calls the PL/SQL packages PA_PROJ_ELEMENTS_UTILS, PA_CONTROL_ITEMS_UTILS, and PA_PROGRESS_UTILS for derived values such as lookup meanings and progress status processing.

The join model links the project header (PPA) to its element (PPE), then to the current element version (PPEV), the version schedule (PPVSCH), percent-complete records (PPC), rollup records (PPR), and status definitions (PPS). The leading hint on PPE indicates the optimizer is steered toward driving from PA_PROJ_ELEMENTS, which is typical for hierarchical WBS/task traversal.

Key Columns

• PROJECT_ID, NAME, SEGMENT1, LONG_NAME — project header identifiers and names.
• PROJ_ELEMENT_ID, ELEMENT_VERSION_ID, ELEMENT_NUMBER — task/WBS element identity and version context.
• WBS_NUMBER, WBS_LEVEL, DISPLAY_SEQUENCE — WBS hierarchy positioning and ordering.
• MILESTONE_FLAG, CRITICAL_FLAG, PRIORITY_CODE — task classification attributes.
• MANAGER_PERSON_ID, CARRYING_OUT_ORGANIZATION_ID — ownership and performing organization.
• PROJECT_STATUS_CODE, PROJECT_STATUS_NAME, PROJECT_SYSTEM_STATUS_CODE — status at both project and progress level, resolved through PA_PROJECT_STATUSES.
• PLANNED_EFFORT, WQ_PLANNED_QUANTITY, WQ_ITEM_CODE, WQ_UOM_CODE — planned work quantity attributes.
• COMPLETED_PERCENTAGE, PERCENT_COMPLETE_ID, PUBLISHED_FLAG, CURRENT_FLAG — progress completion and publication state.
• BASE_PERCENT_COMPLETE, EFF_ROLLUP_PERCENT_COMP — computed and effective rollup percentages.
• AS_OF_DATE (DATE_COMPUTED) — the point in time at which percent complete was calculated.
• BASELINE_START_DATE, SCHEDULED_START_DATE, ACTUAL_START_DATE, ESTIMATED_START_DATE and corresponding finish dates — the schedule comparison set.
• EST_SCH_START_VAR, ACT_SCH_START_VAR and related variance columns — derived schedule variances.
• PROCESS_STATUS_NAME, PROCESS_STATUS_CODE — publication process state via PA_PROJ_ELEMENTS_UTILS.

Common Use Cases and Queries

Typical usage centers on project progress reporting, task-level dashboards, and schedule variance analysis. A common query retrieves the latest current percent-complete row per task:

• Reporting task completion by project, filtering on CURRENT_FLAG = 'Y' and PUBLISHED_FLAG = 'Y'.
• Comparing planned versus actual progress to derive schedule variance using the supplied variance columns.
• Extracting WBS hierarchy for reporting tools that cannot traverse PA_PROJ_ELEM_VER_STRUCTURE directly.
• Feeding data warehouses with published progress snapshots keyed on AS_OF_DATE.

Example: SELECT project_id, name, element_number, wbs_level, completed_percentage, as_of_date FROM apps.pa_task_progress_v WHERE current_flag = 'Y' AND published_flag = 'Y';

Because the view aggregates progress from multiple transactional sources, filters on PROJECT_ID, CURRENT_FLAG, and AS_OF_DATE are recommended to keep query performance predictable on large implementations.