Search Results top_task_ver_id

Overview

APPS.PA_STRUCT_TASK_WBS_V is an Oracle E-Business Suite internal view owned by the APPS schema, registered in FND Design Data as PA.PA_STRUCT_TASK_WBS_V. The view exposes the structural hierarchy of project tasks and Work Breakdown Structure (WBS) elements, resolving the relationship between financial and non-financial tasks within a project. It is one of the principal interfaces used by Oracle Projects reporting and integration logic to traverse the task hierarchy without repeatedly joining the base task, element, and element-version tables directly.

The object is documented with the Oracle warning that it is for internal use only and is not supported for direct customer access except from standard Oracle Applications programs. In practice, however, many customers and partners query the view for custom reporting, since it is a convenient denormalized projection of the WBS tree. Access should be granted with the understanding that Oracle may change or remove the view between releases. It exists in 12.1.1 and 12.2.2 with equivalent semantics.

The primary purpose of the view, as evidenced by the TASK_LEVEL column, is to classify each financial (or non-financial) task by its position in the WBS: Top-level, Middle-level, Lowest-level, or non-financial. This classification is the foundation of most Projects costing, budgeting, and progress reporting logic.

Underlying Base Objects

Per the ETRM dependency metadata, the view is defined over the following base objects:

• PA_PROJECTS_ALL — supplies the owning project context for each task.
• PA_PROJ_ELEMENTS — the generic project element table that stores task and WBS structure rows.
• PA_PROJ_ELEMENT_VERSIONS — versioned attributes for each project element.
• PA_PROJ_ELEM_VER_SCHEDULE — the scheduling information (start/completion dates) attached to an element version.
• PA_TASKS — task-specific attributes linked to the project element.
• PA_PROJ_ELEMENTS_UTILS (PACKAGE) — a PL/SQL package invoked by the view to derive calculated values such as the WBS level.

The view therefore joins the generic element model (PA_PROJ_ELEMENTS and its versions) with the task-specific extension (PA_TASKS) and the schedule table, producing one row per task with its hierarchy and scheduling context resolved. The package reference indicates that some columns (notably TASK_LEVEL) are computed at runtime rather than stored as plain columns in the base tables.

Key Columns

• PROJECT_ID — unique identifier of the project that owns the task.
• TASK_ID / TASK_NUMBER / TASK_NAME — the task identifier, its user-facing number, and its descriptive name.
• TOP_TASK_ID / TOP_TASK_VER_ID — the top-level task and its version for the current node, enabling WBS roll-up.
• TASK_LEVEL — the WBS level of the financial task. Documented values are T (Top Task), M (Middle Task), L (Lowest Task), and X (Not a Financial Task). This is the column that most users search for under "task_level."
• PARENT_TASK_ID / PARENT_TASK_VERSION_ID / PARENT_STRUCTURE_ID / PARENT_STRUCTURE_VERSION_ID — the parent task and structure identifiers and their versions, allowing upward traversal of the hierarchy.
• ELEMENT_VERSION_ID — the specific version of the project element represented by the row.
• START_DATE / COMPLETION_DATE — planned span of the task.
• TRANSACTION_START_DATE / TRANSACTION_COMPLETION_DATE — transactional effective dates.
• ACTUAL_START_DATE / ACTUAL_FINISH_DATE — recorded actual execution dates.
• ESTIMATED_START_DATE / ESTIMATED_FINISH_DATE — forecast dates for the task.
• FINANCIAL_TASK_FLAG — indicates whether the task participates in financial processing.

Common Use Cases and Queries

The view is most often used to report on WBS structure, to identify lowest-level tasks for cost collection, and to reconcile the financial task hierarchy. A typical query retrieving top-level financial tasks for a project is:

SELECT task_id, task_number, task_name, task_level, financial_task_flag
FROM   apps.pa_struct_task_wbs_v
WHERE  project_id = :p_project_id
AND    task_level = 'T';

To identify all lowest-level tasks, change the predicate to task_level = 'L'; to exclude non-financial tasks, add financial_task_flag = 'Y'. Because TASK_LEVEL is derived via PA_PROJ_ELEMENTS_UTILS, queries that filter on this column over large projects can be costly; restricting by PROJECT_ID first is advisable.

Integration scenarios include interfaces that must flatten the WBS into reporting hierarchies, populate custom costing extracts, or validate that every task has a resolved top-task and parent-task chain. The scheduling columns support date-based reporting such as comparing estimated versus actual dates across the WBS.

Given the Oracle internal-use warning, any custom dependency on this view should be isolated behind a wrapper view or interface table so that changes in a future patch or upgrade do not propagate directly into custom code.