Search Results rollup_record_version_number




Overview
Explore in AI Chat

Overview

APPS.PA_DELIVERABLE_PROGRESS_V is a reporting and integration view within the Oracle E-Business Suite Projects (PA) module. It consolidates deliverable-level progress information for project tasks, joining project structures, progress rollup data, percent-complete entries, schedule dates, and status lookups into a single denormalized result set. In ETRM 12.1.1 and 12.2.2, the view serves as the primary access point for querying how deliverables are tracking against schedule and completion targets without manually joining the underlying progress tables.

The view exposes both task-level context (task name, task number, task element identifiers) and deliverable-level detail (deliverable name, number, manager, status, and system status). Progress metrics are surfaced through columns such as completed_percentage, base_percent_complete, and eff_rollup_percent_comp, while scheduling context is provided by scheduled and actual start/finish dates. A computed column invokes pa_progress_utils.GET_NEXT_PROGRESS_CYCLE to derive the next progress cycle for the deliverable, making the view useful for workflow and notification logic in addition to ad hoc reporting.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS-owned synonyms:

Because the view depends on PER_ALL_PEOPLE_F (a date-tracked table) and multiple status lookups, performance is best when queries filter by project_id or project_number before applying status or date predicates.

Key Columns

  • project_id, name, segment1, long_name — project identification and descriptive attributes
  • task_name, task_number, str_task_proj_element_id, str_task_object_type — task-level context
  • del_id, del_name, del_number, del_object_type — deliverable identification
  • del_manager_id, del_manager_name — deliverable owner
  • del_status_name, del_system_status_code — deliverable status and system status
  • progress_status_name, progress_system_status_code — progress status lookups with icon indicators
  • completed_percentage, base_percent_complete, eff_rollup_percent_comp — completion measures at entry and rollup levels
  • scheduled_start_date, scheduled_finish_date, actual_start_date, actual_finish_date — schedule versus actual tracking
  • published_flag, current_flag, published_by_party_id, progress_comment — publishing and commentary metadata
  • prog_entry_req_flag, progress_outdated_flag — workflow and staleness indicators for progress entry
  • percomp_record_version_number, rollup_record_version_number — optimistic locking support for OAF-based updates

Common Use Cases and Queries

Typical scenarios include deliverable progress dashboards, exception reporting for stalled or outdated progress, and integration feeds that publish percent-complete status to external planning tools. A representative query filtering by project follows:

SELECT del_name, del_number, task_name, completed_percentage,
       eff_rollup_percent_comp, scheduled_finish_date,
       actual_finish_date, progress_status_name, progress_outdated_flag
FROM   apps.pa_deliverable_progress_v
WHERE  project_id = :p_project_id
AND    nvl(published_flag, 'N') = 'Y'
ORDER  BY task_number, del_number;

To identify deliverables requiring progress entry, filter on prog_entry_req_flag and the progress_outdated_flag. Ensure the APPS schema is used with appropriate MO: Operating Unit security applied through project access controls.