Search Results days_until_start




Overview
Explore in AI Chat

Overview

APPS.PA_ASSIGNMENT_PROGRESS_V is a valid Oracle EBS internal view owned by the APPS schema and registered in FND Design Data as PA.PA_ASSIGNMENT_PROGRESS_V. It presents progress-tracking and effort-measurement information at the resource-assignment level, exposing measures such as actual, planned, and estimated effort; percent complete and percent spent; schedule dates across baseline, scheduled, estimated, and actual categories; and derived indices including DAYS_UNTIL_PROGRESS_DUE. Because it joins task, project, resource-assignment, and progress attributes into a single projection, it is commonly consumed by progress-entry pages, dashboards, and custom reporting on the PA side of ETRM.

The view is explicitly marked "Oracle Internal Use Only." Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Any custom SQL against it should be treated as unsupported and subject to change without notice across patch levels.

Underlying Base Objects

The view is defined over a combination of synonyms, packages, and one supporting view. Documented base objects include PA_PROJ_PROGRESS_ATTR and PA_PERCENT_COMPLETES, which supply progress-entry configuration and percent-complete values; PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_STRUCTURE, which resolve the project/task structure and versions; PA_PROJECTS_ALL and PA_TASK_TYPES for project and task context; and PA_PROGRESS_ROLLUP, which contributes rolled-up progress figures. Currency and unit-of-measure conversion is handled through the PA_CURRENCY and PA_PROGRESS_UTILS packages. Resource assignments and assignment-level attributes derive from the supporting view PA_TASK_ASGMTS_LPV_V and the PA_TASK_ASSIGNMENT_UTILS package. This layered construction explains why the view can surface both planning-baseline data and latest-version actuals in one row.

Key Columns

The date columns drive most reporting. NEXT_PROGRESS_DUE_DATE is the next scheduled progress-entry date for the assignment, and DAYS_UNTIL_PROGRESS_DUE is the derived number of days between that date and the reference date (typically sysdate or AS_OF_DATE). DEFAULT_AS_OF_DATE and AS_OF_DATE anchor the measurement point. Schedule comparisons are exposed through BASELINE_START_DATE, BASELINE_FINISH_DATE, SCHEDULED_START_DATE, SCHEDULED_FINISH_DATE, ESTIMATED_START_DATE, ESTIMATED_FINISH_DATE, and the corresponding ACTUAL_* columns, with variance columns such as ACT_SCH_FINISH_VAR, EST_BAS_FINISH_VAR, and SCH_BASE_START_VAR carrying the differences.

Effort and completion measures include ACTUAL_EFFORT, PLANNED_EFFORT, EST_REMAINING_EFFORT, ETC_EFFORT, EST_AT_COMPLETION_EFFORT, BASELINED_EFFORT, PERCENT_COMPLETE_EFFORT, and PERCENT_SPENT_EFFORT, plus the variance column VAR_AT_COMPLETION_EFFORT. Identity and context columns include PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, TASK_NAME, TASK_MANAGER_NAME, RESOURCE_ASSIGNMENT_ID, PERSON_ID, RESOURCE_ALIAS, UOM_CODE, TXN_CURRENCY_CODE, and the indicator flags CURRENT_FLAG, PUBLISHED_FLAG, EFFORT_ENABLED_FLAG, PROG_ENTRY_ENABLE_FLAG, and RATE_BASED_FLAG.

Common Use Cases and Queries

Typical scenarios include identifying assignments whose progress entry is overdue or imminent, reporting percent complete versus percent spent for a project or task, and comparing baseline against estimated or scheduled dates for schedule-health analysis. A representative query for imminent progress entry is:

  • SELECT project_number, task_number, resource_alias, next_progress_due_date, days_until_progress_due FROM apps.pa_assignment_progress_v WHERE days_until_progress_due BETWEEN 0 AND 7 AND current_flag = 'Y' ORDER BY days_until_progress_due;

Overdue progress entry can be isolated by filtering DAYS_UNTIL_PROGRESS_DUE < 0, while effort performance comparisons use PERCENT_SPENT_EFFORT against PERCENT_COMPLETE_EFFORT, and schedule variance reporting selects the *_VAR columns by project or task. The view may also be used to answer the common search term "days_until_progress_due," since that column is the primary driver of assignment-level progress-due reporting. As with any unsupported internal object, wrap access in a custom view or report layer rather than embedding direct references throughout the codebase.