Search Results indented_task_name




Overview
Explore in AI Chat

Overview

APPS.PA_TASKS_AP_V is a lightweight Oracle E-Business Suite view owned by the APPS schema that exposes a condensed, task-oriented projection of project task data. Its defining characteristic is that it presents the indented task name — the hierarchical, whitespace-prefixed rendering of a task within its project work breakdown structure — through the alias DESCRIPTION, alongside the task identifier, the owning project identifier, and the task number. In Oracle Projects, task names are frequently stored and displayed as an indented label so that a child task visually nests beneath its parent, and this view surfaces exactly that representation without requiring the caller to invoke the PL/SQL utilities that generate it.

The view is intended for reporting and integration scenarios where a caller needs a compact task list keyed to a project and wants the human-readable indented label. Because it selects from PA_TASKS_EXPEND_V rather than from the base PA_TASKS table, it also inherits the security and eligibility filtering applied by that underlying view.

Underlying Base Objects

The view text is a single SELECT over PA_TASKS_EXPEND_V, aliased as PAT, projecting four columns: TASK_ID, PROJECT_ID, TASK_NUMBER, and INDENTED_TASK_NAME. Documented dependencies for APPS.PA_TASKS_AP_V include PA_TASKS_EXPEND_V (VIEW), PA_TASK_UTILS (PACKAGE), PA_UTILS4 (PACKAGE), and FND_PROFILE (PACKAGE). The two packages and the profile package are not referenced directly in the view text; they are exercised indirectly, because PA_TASKS_EXPEND_V and the underlying task utilities rely on PA_TASK_UTILS, PA_UTILS4, and FND_PROFILE to apply profile-option-driven behavior and to construct the indented task name.

The practical consequence is that PA_TASKS_AP_V should be treated as a presentation layer over PA_TASKS_EXPEND_V, not as an independent data source. Any row-limiting, operating-unit, or responsibility-based security enforced by PA_TASKS_EXPEND_V carries through unchanged.

Key Columns

  • TASK_ID — The unique identifier of the task (internally the primary key of PA_TASKS). This is the join key to other Projects tables and to task-level transaction data.
  • PROJECT_ID — The identifier of the project to which the task belongs. Used to filter tasks to a single project or to join to PA_PROJECTS.
  • TASK — The task number as stored on the task record. This is the short business identifier for the task, distinct from its descriptive name.
  • DESCRIPTION — The indented task name obtained from INDENTED_TASK_NAME. It reflects the task's position in the project hierarchy through leading indentation, making parent-child relationships visible in flat query output.

Common Use Cases and Queries

The view is typically used in list-of-values queries, custom reports, and interface extracts that need a task identifier together with a readable, hierarchically indented label. A conventional query restricted to one project is:

SELECT task_id,
       project_id,
       task,
       description
FROM   apps.pa_tasks_ap_v
WHERE  project_id = :p_project_id
ORDER  BY description;

Because DESCRIPTION carries the indentation, ordering by that column preserves the visual hierarchy in the result set. A second common pattern joins the view to transaction or expenditure tables on TASK_ID to attach the indented label to financial detail:

SELECT t.task_id, t.task, t.description, x.expenditure_item_date, x.denom_raw_cost
FROM   apps.pa_tasks_ap_v t,
       apps.pa_expenditure_items_all x
WHERE  t.task_id = x.task_id
AND    t.project_id = :p_project_id;

Analysts should note that the view exposes no project number, task name in unindented form, or start/end dates; where those attributes are required, the caller must join to PA_PROJECTS or query PA_TASKS_EXPEND_V directly. Visibility remains subject to the profile options and security rules applied by the underlying view and its utility packages.