Search Results new_scheduled_start_date




Overview
Explore in AI Chat

Overview

APPS.PA_TASKS_PUBLISHING_V is a publishing view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. Its FND design data reference is PA.PA_TASKS_PUBLISHING_V. The view exposes a flattened, reporting-oriented representation of project tasks and work breakdown structure (WBS) elements, combining element identification, milestone and critical flags, progress status, scheduling dates, variance figures, task manager assignment, and completion percentage into a single result set. Because it consolidates attributes normally distributed across several Projects tables, it is intended for publishing task-level detail to downstream reporting, integration, and external presentation layers rather than for transactional processing.

The ETRM record marks the object with the standard Oracle restriction that it is for internal use only and that Oracle does not support direct access to applications data through it except from standard Oracle Applications programs. Query behavior should therefore be expected to be governed by the same naming and decoding conventions Oracle applies elsewhere in Projects, and any custom use should be validated as non-supported.

Underlying Base Objects

The view is documented as defined over the following base objects: PA_PROJ_ELEMENTS (SYNONYM), PA_PROJ_ELEMENT_VERSIONS (SYNONYM), PA_PROJ_ELEM_VER_SCHEDULE (SYNONYM), PER_ALL_PEOPLE_F (SYNONYM), and the package PA_PROJ_ELEMENTS_UTILS. In practice, PA_PROJ_ELEMENTS supplies the core element identity (element number, name, project association, parent structure), PA_PROJ_ELEMENT_VERSIONS provides versioned element attributes such as milestone and critical indicators and the version identifier, and PA_PROJ_ELEM_VER_SCHEDULE delivers scheduled and previous scheduled start and finish dates along with the derived variance values. PER_ALL_PEOPLE_F resolves the task manager to a person, while PA_PROJ_ELEMENTS_UTILS is referenced by the view logic for element-based utility operations, commonly including display sequencing and WBS numbering. The joins key primarily on PROJ_ELEMENT_ID and ELEMENT_VERSION_ID, with the versioned schedule and parent structure identifiers linking the hierarchy.

Key Columns

Common Use Cases and Queries

The view is typically used to publish task schedules and status to dashboards, to compare current and previous scheduled dates for variance reporting, and to feed milestone or critical-path extracts. The most direct response to the "new_scheduled_start_date" search is a filtered schedule report:

  • Schedule lookup: SELECT element_number, element_name, new_scheduled_start_date, new_scheduled_finish_date, start_date_variance FROM apps.pa_tasks_publishing_v WHERE project_id = :project_id ORDER BY wbs_level, display_sequence;
  • Slippage review: SELECT element_number, previous_sch_start_date, new_scheduled_start_date, start_date_variance FROM apps.pa_tasks_publishing_v WHERE start_date_variance > 0;
  • By task manager: SELECT task_manager, element_number, progress_status_meaning, completed_percentage FROM apps.pa_tasks_publishing_v WHERE task_manager_id = :person_id;
  • Milestone reporting: SELECT element_number, new_scheduled_start_date, milestone_flag_meaning, critical_flag_meaning FROM apps.pa_tasks_publishing_v WHERE milestone_flag = 'Y';

Because of the internal-use restriction, these queries should be treated as read-only extracts and reconciled against supported Oracle reporting objects where auditability is required.