Search Results pa_latest_proj_task_prog_v




Overview
Explore in AI Chat

Overview

PA_LATEST_PROJ_TASK_PROG_V is an APPS-owned database view within the Oracle EBS Projects (PA) module. It consolidates the most recent published progress information for project workplan elements, presenting one denormalized row per project element version across projects, tasks, and structures. The view merges physical percent-complete records from PA_PERCENT_COMPLETES with rolled-up progress attributes from PA_PROGRESS_ROLLUP and scheduling data from element version schedules, producing a reporting-ready projection that pairs status, completion percentage, dates, and descriptive attributes in a single queryable surface.

Its central role is to expose the "latest" published progress state so that reporting tools, dashboards, and integrations need not resolve the complex temporal and versioned relationships among progress records themselves. The view's internal DECODE logic on PUBLISHED_FLAG and CURRENT_FLAG governs which records are surfaced as current and published, while PROJECT_ID, PROJ_ELEMENT_ID, and ELEMENT_VERSION_ID establish the key lineage from project to workplan element to specific version. In Oracle EBS 12.1.1 and 12.2.2 the view remains a VALID object under the APPS schema, and it is referenced heavily by Project Management and Project Status Inquiry style reporting that requires a flattened, workplan-oriented view of progress.

Underlying Base Objects

The view is defined over a documented set of tables, synonyms, and packages. The principal base tables accessed via public synonyms include PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_SCHEDULE, PA_PROJ_ELEM_VER_STRUCTURE, PA_PERCENT_COMPLETES, PA_PROGRESS_ROLLUP, PA_PROJ_PROGRESS_ATTR, PA_PROJECT_STATUSES, PA_TASK_TYPES, and PA_PROJ_STRUCTURE_TYPES. Supplemental sources include PJI_FM_XBS_ACCUM_TMP1, a temporary accumulation table for cross-business-set facts, joined with an explicit index hint to improve access performance.

Supporting logic is supplied by PL/SQL packages referenced in the view text: PA_PROJ_ELEMENTS_UTILS (used to derive SUMMARY_ELEMENT_FLAG and summary status), PA_PROGRESS_UTILS, PA_CURRENCY (for currency-sensitive context), and PA_RELATIONSHIP_UTILS. The view therefore acts as a functional join across transactional progress data (PA_PERCENT_COMPLETES), rolled-up metrics (PA_PROGRESS_ROLLUP), and structural/version metadata (PA_PROJ_ELEM_VER_STRUCTURE and its schedule), with task-type and project-status lookup tables contributing descriptive columns.

Key Columns

Common Use Cases and Queries

Typical scenarios include progress dashboards, workplan completion reports, and integrations feeding external analytics. Because the view already resolves object type, version, and latest published values, consumers avoid replicating that logic. A representative query joining project and rollup progress follows:

SELECT project_id, name, proj_element_id, element_version_id, object_type, completed_percentage, progress_status_code, scheduled_start_date, scheduled_finish_date FROM apps.pa_latest_proj_task_prog_v WHERE project_id = :p_project_id AND published_flag = 'Y';

For task-level reporting, filter on OBJECT_TYPE = 'PA_TASKS'; for structural summaries, filter on 'PA_STRUCTURES' or SUMMARY_ELEMENT_FLAG. Aggregated views can use CUMULATIVE_WORK_QUANTITY and rolled labor/equipment hours to reconcile execution against plan.