Search Results indented_task_name




Overview
Explore in AI Chat

Overview

The APPS.PA_TASKS_ALL_V view is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. Its documented description is "10SC Only," indicating that the view was originally introduced to support a specific functional requirement (the "10SC" designation) rather than as a general-purpose task listing. The qualifying suffix "_ALL_V" follows Oracle naming conventions for views in the APPS schema that expose a denormalized, joined, or computed representation of one or more base entities to reporting tools, concurrent programs, or downstream integrations.

Functionally, the view presents project task (work breakdown structure, or WBS) records from the PA_TASKS table, augmenting them with two derived columns that render the task hierarchy in a human-readable, indented form. It is registered as VALID in the 12.1.1 and 12.2.2 releases, and is documented in ETRM under Product/Module PA - Projects. Because it lives in the APPS schema, it can be referenced directly by custom reports, Oracle Reports/BI Publisher data models, Oracle XML Publisher templates, and SQL*Plus or SQL Developer sessions without qualifying a product schema.

Underlying Base Objects

The documented base objects referenced by the view are PA_TASKS (accessed via a synonym in the APPS schema) and the PA_TASK_UTILS package. The view text selects from PA_TASKS T and exposes eight columns from that table directly, plus a ninth column computed by calling PA_TASK_UTILS.SORT_ORDER_TREE_WALK. PA_TASK_UTILS is a PL/SQL package used throughout the Projects module to sequence WBS elements in a depth-first, tree-walk order so that a task's position in the hierarchy can be rendered consistently. The view does not join to any other project or task-related table; it is a thin projection over a single base table with one packaged function call and two inline string expressions. This makes it lightweight but also means it inherits the row-level security and org context behavior of PA_TASKS itself.

Key Columns

  • PROJECT_ID — The project identifier to which the task belongs; the primary foreign key into PA_PROJECTS.
  • TASK_ID — The unique identifier of the task (PID).
  • TASK_NUMBER — The user-visible task number.
  • TASK_NAME — The user-visible task (WBS element) name.
  • INDENTED_TASK_NUMBER — The task number prefixed with leading spaces computed as LPAD(' ', (NVL(WBS_LEVEL,1)-1)*2, ' '), producing two spaces of indentation per WBS level.
  • INDENTED_TASK_NAME — The task name with the same level-based indentation, and the column most directly relevant to the search term "indented_task_name."
  • PARENT_TASK_ID — The TASK_ID of the immediate parent, enabling recursive traversal.
  • TOP_TASK_ID — The TASK_ID of the top-level (root) task of the WBS branch.
  • WBS_SORT_ORDER — The value returned by PA_TASK_UTILS.SORT_ORDER_TREE_WALK(PARENT_TASK_ID, TASK_NUMBER), used to ORDER BY so that displayed rows follow the tree hierarchy.

Common Use Cases and Queries

The primary use case is producing a hierarchical task list for a given project, ordered correctly and indented for readability in a report or spreadsheet. A typical query is:

SELECT indented_task_number,
       indented_task_name,
       task_id,
       parent_task_id,
       top_task_id
  FROM apps.pa_tasks_all_v
 WHERE project_id = :p_project_id
 ORDER BY wbs_sort_order;

A second use case is drilling into a subtree by filtering on TOP_TASK_ID or walking from a known PARENT_TASK_ID. Because the view returns only PA_TASKS columns plus the derived fields, callers that require project numbers, project names, or task attributes stored in other PA tables must join to PA_PROJECTS, PA_PROJECT_TASKS, or similar objects. Note also that, given its "10SC Only" status, the view should be validated against the specific environment before being adopted as a long-term integration interface; where a supported alternative such as PA_TASKS or the standard WBS APIs exists, those are preferable for general use. The view remains nonetheless useful as a read-only convenience layer for reporting the WBS in presentation-ready form.