Search Results pa_task_progress_amg_v

Overview

The view PA_TASK_PROGRESS_AMG_V, owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, exposes progress data for structure tasks within the Projects (PA) module. Its stated purpose is to provide a consolidated, query-ready presentation of physical and effort-based progress information for tasks associated with a project structure. The view is classified as VALID and is documented in ETRM as a VIEW object under Product/Module PA - Projects.

The suffix "AMG" and its presence in the ETRM repository indicate it is intended primarily for reporting and integration consumption, rather than as a transactional base object. Downstream reporting tools, Oracle Business Intelligence Applications, custom concurrent programs, and interface extracts commonly rely on views of this type to retrieve task-level percent-complete, rollup, and cost/effort metrics without directly joining the underlying normalized tables.

Underlying Base Objects

The view text joins a substantial set of Projects tables and one external view. The documented referenced base objects are:

• PA_PROJ_ELEMENTS (synonym) — the project element master, filtered to OBJECT_TYPE = 'PA_TASKS' and LINK_TASK_FLAG <> 'Y'.
• PA_PROJ_ELEMENT_VERSIONS (synonym) — versioned project element records, linked to the latest effective published structure.
• PA_PROJ_ELEM_VER_STRUCTURE (synonym) — structure hierarchy; the join restricts to LATEST_EFF_PUBLISHED_FLAG = 'Y'.
• PA_PERCENT_COMPLETES (synonym) — published percent-complete entries, outer-joined to the element versions.
• PA_PROGRESS_ROLLUP (synonym) — rollup progress metrics such as effective rollup percent complete and cumulative work quantity.
• PA_PROJECT_STATUSES (synonym) — project status code and name, aliased twice (PPS and PPS1) to provide both the project and structure status context.
• PA_TASK_TYPES (synonym) — task type classification; joined with the outer (+) operator.
• PA_PROJ_STRUCTURE_TYPES and PA_STRUCTURE_TYPES (synonyms) — structure type definitions supplying STRUCTURE_TYPE_CLASS_CODE.
• PJI_XBS_PLANS_V (view) — the project plans view supplying effort and cost metrics, including labor, equipment, ETC, and actual cost/effort columns.
• PA_PROGRESS_UTILS (package) — referenced in metadata as a supporting Program Unit for progress computations.

All base table references resolve through APPS synonyms, meaning the view executes in the APPS schema and inherits its security and privileges.

Key Columns

The view exposes identifiers, descriptive attributes, progress percentages, dates, and cost/effort measures. Notable columns include:

• PROJECT_ID, PROJ_ELEMENT_ID, ELEMENT_VERSION_ID — the primary keys linking the row back to the project, task element, and element version.
• NAME, ELEMENT_NUMBER — the task name and number for readable output.
• COMPLETED_PERCENTAGE — computed via NVL(PPR.COMPLETED_PERCENTAGE, NVL(PPR.BASE_PERCENT_COMPLETE, PPR.EFF_ROLLUP_PERCENT_COMP)), providing the most relevant available progress figure.
• STATUS_CODE / PROJECT_STATUS_CODE / PROJECT_STATUS_NAME — a DECODE selects the published status code when PPC.PUBLISHED_FLAG is 'N', otherwise the element status code.
• DATE_COMPUTED — the date the percent-complete entry was calculated.
• ACTUAL_START_DATE, ACTUAL_FINISH_DATE, ESTIMATED_START_DATE, ESTIMATED_FINISH_DATE — task scheduling milestones.
• CUMULATIVE_WORK_QUANTITY — accumulated work quantity for the task.
• EST_REMAINING_EFFORT (PXPV.ETC_LABOR_HRS) — estimate-to-complete labor hours.
• ACTUAL_COST (PXPV.ACT_BRDN_COST) — actual burdened cost.
• ACTUAL_EFFORT — sum of actual labor and equipment hours.
• ESTIMATE_AT_COMPLETION_COST — actual burdened cost plus estimate-to-complete burdened cost.
• PLANNED_EFFORT — labor plus equipment effort from the plans view.
• PROG_ENTRY_ENABLE_FLAG — indicates whether progress entry is enabled for the task type.
• STRUCTURE_TYPE_CLASS_CODE — the structural classification of the task's structure.

Common Use Cases and Queries

The most frequent use case involves retrieving task-level progress for a project, emphasizing items where progress data is available or in progress. A representative query follows:

SELECT project_id, proj_element_id, name, element_number, completed_percentage, status_code, actual_cost FROM apps.pa_task_progress_amg_v WHERE project_id = :p_project_id ORDER BY element_number;

Because the user search term was "in_progress," a targeted query filtering on status or incomplete progress is also common:

SELECT project_id, name, completed_percentage, est_remaining_effort, actual_effort FROM apps.pa_task_progress_amg_v WHERE completed_percentage < 100 AND prog_entry_enable_flag = 'Y';

Other typical scenarios include feeding project status dashboards, feeding planning extracts through PJI, comparing actual versus estimated effort across tasks, and reporting estimate-at-completion cost at the task level. Because the view joins the latest effective published structure, results reflect published structure versions only, which is important when validating progress against the baseline.