Search Results task_level

Overview

PA_STRUCT_TASK_WBS_V is a Projects (PA) module view owned by the APPS schema and defined over the core task and work breakdown structure tables of Oracle Projects. It presents the hierarchical task structure of a project alongside version, parent, scheduling, and financial attributes in a single flattened result set. Its primary role is to expose task-level WBS relationships — including the parent/child linkage between task versions — so that reporting, integration, and downstream processing can traverse the task hierarchy without directly joining the underlying element and version tables. The view is particularly relevant where the parent task version identifier is required, since it surfaces PARENT_TASK_VERSION_ID as a first-class column derived from the element version of each task.

Underlying Base Objects

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

• PA_PROJECTS_ALL — the project header, supplying PROJECT_ID.
• PA_PROJ_ELEMENTS — the project structure elements, restricted by OBJECT_TYPE = 'PA_TASKS' to isolate task-level elements.
• PA_PROJ_ELEMENT_VERSIONS — the versioned structure elements, providing version identifiers and the parent structure version.
• PA_PROJ_ELEM_VER_SCHEDULE — scheduling dates for each element version, joined with outer joins.
• PA_TASKS — the task definition table, joined to the element by TASK_ID with an outer join and used to derive the task number.
• PA_PROJ_ELEMENTS_UTILS — a PL/SQL utility package whose functions resolve top task, task level, and parent task identifiers.

The joins connect project to element, element to version, version to schedule (outer), and element to task (outer), yielding one row per task element version reflecting its position in the WBS.

Key Columns

• PROJECT_ID — identifier of the owning project.
• TASK_ID / TASK_NUMBER / TASK_NAME — the task element identifier, number, and name.
• ELEMENT_VERSION_ID — the specific version of the task element, the anchor for version-based hierarchy resolution.
• PARENT_TASK_ID and PARENT_TASK_VERSION_ID — the parent task's identifier and the parent task's version identifier, resolved via PA_PROJ_ELEMENTS_UTILS.GET_PARENT_TASK_ID and GET_PARENT_TASK_VERSION_ID respectively. PARENT_TASK_VERSION_ID is the column most commonly sought when reconciling hierarchy across versions.
• TOP_TASK_ID / TOP_TASK_VER_ID — the top-level task and its version for the branch.
• TASK_LEVEL — depth of the task within the WBS.
• PARENT_STRUCTURE_ID / PARENT_STRUCTURE_VERSION_ID — the containing structure and its version.
• START_DATE / COMPLETION_DATE / TRANSACTION_START_DATE / TRANSACTION_COMPLETION_DATE — scheduling dates projected from PA_PROJ_ELEM_VER_SCHEDULE.
• ACTUAL_START_DATE / ACTUAL_FINISH_DATE / ESTIMATED_START_DATE / ESTIMATED_FINISH_DATE — actual and estimated milestone dates.
• FINANCIAL_TASK_FLAG — DECODE of TASK_NUMBER yielding 'Y' or 'N', indicating whether the row corresponds to a defined financial task.

Common Use Cases and Queries

Typical uses include reporting the WBS hierarchy for a project, identifying parent task versions for integration or migration, and validating task levels. A representative query for the parent task version column follows:

SELECT project_id,
       task_id,
       task_number,
       task_name,
       task_level,
       parent_task_id,
       parent_task_version_id,
       element_version_id
FROM   apps.pa_struct_task_wbs_v
WHERE  project_id = :p_project_id
ORDER  BY task_level, task_number;

To locate the children of a specific parent version:

SELECT task_number, task_name, element_version_id
FROM   apps.pa_struct_task_wbs_v
WHERE  parent_task_version_id = :p_parent_version_id;

Because the view resolves version-scoped hierarchy through the utility package, it is suited to reports that must distinguish structurally identical tasks across versions. Queries should filter on PROJECT_ID for performance, as the underlying joins span several large project element tables.