Search Results default_as_of_date




Overview
Explore in AI Chat

Overview

The APPS.PA_DELIVERABLE_PROG_HIST_V view is a denormalized reporting layer within the Oracle EBS Project Manufacturing and Project Management (PA) modules. It presents a historical and current picture of deliverable-level progress information, combining structural project and task hierarchies with percentage-complete records, rollup values, and status indicators. In Oracle EBS 12.1.1 and 12.2.2 this view is classified as an Oracle Internal Use Only object, meaning Oracle does not support direct data access except from standard Oracle Applications programs.

The view is particularly relevant to applications and reports dealing with deliverable progress tracking, published progress history, and the "as-of-date" dimension. The presence of the AS_OF_DATE column and the user query "default_as_of_date" indicate that the view is typically filtered by a point-in-time date to reconstruct progress snapshots. The view reconciles multiple progress records per deliverable, exposing fields such as progress system status, percent complete, published flags, and record version numbers that allow consumers to select the correct default or current progress row.

Underlying Base Objects

The view is defined over several documented base objects owned by the APPS schema, accessed largely through synonyms. The primary transactional table is PA_PERCENT_COMPLETES, which stores percentage-complete records keyed by element version and as-of-date. PA_PROGRESS_ROLLUP supplies effective rollup percentages and rollup record version numbers, while the PA_PROGRESS_UTILS package provides the PL/SQL functions that map percentage-complete and progress status codes to their display names and system status codes.

Project and task structure comes from PA_PROJECTS_ALL (project header, name, number, long name), PA_PROJ_ELEMENTS (tasks, structures and deliverables), PA_PROJ_ELEMENT_VERSIONS (versioned elements), PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_ELEM_VER_SCHEDULE (scheduled start/finish), PA_PROJ_STRUCTURE_TYPES, and PA_TASK_TYPES. Progress status definitions and their system equivalents are resolved via PA_PROJECT_STATUSES. Relationships between objects are governed by PA_OBJECT_RELATIONSHIPS, which links project elements, deliverables, and their structure versions. Together these objects let the view project a flat, reporting-friendly record from a normalized, versioned data model.

Key Columns

Common Use Cases and Queries

A frequent requirement is retrieving the latest progress record per deliverable, where the caller supplies a default_as_of_date or derives it from the current system date. Because PA_PERCENT_COMPLETES stores multiple rows across as-of dates, consumers filter with equality or a subquery on MAX(AS_OF_DATE). A representative query is:

SELECT project_number, del_name, del_number, completed_percentage, progress_status_name, as_of_date
FROM apps.pa_deliverable_prog_hist_v
WHERE project_id = :p_project_id
AND as_of_date = NVL(:default_as_of_date, (SELECT MAX(as_of_date) FROM apps.pa_deliverable_prog_hist_v WHERE project_id = :p_project_id))
AND progress_published_flag = 'Y';

Other use cases include deliverable progress history reporting across snapshots, dashboard status icons driven by STATUS_ICON_IND and STATUS_ICON_ACTIVE_IND, rollup reconciliation comparing BASE_PERCENT_COMPLETE to EFF_ROLLUP_PERCENT_COMP, and integration extracts where the view serves as the source for downstream progress publication. Because the object is Oracle Internal Use Only, custom reports should preferably call supported public APIs (such as PA_PROGRESS_UTILS) rather than relying on direct view access, and any custom SQL must account for record version numbers to avoid duplicate rows.