Results for “child_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_XC_TASKS_BY_PROJECT_V is an Oracle Projects (PA) cross-functional reporting view that exposes task-level detail for a single project, filtered dynamically by the current session context. In Oracle EBS 12.1.1 and 12.2.2, it functions within the Project Management and Project Collaboration (XC) reporting layer, where views prefixed with PA_XC_ supply data to project workbench, task drill-down, and self-service project manager pages. The view's documented purpose is "View All Task Details," and it is designed to return the complete set of tasks belonging to the project identified by the session utility PA_XC_VIEW_UTILS.GETPROJECTID.

A distinguishing characteristic is its embedded security and hierarchy logic. Rather than exposing all tasks unconditionally, the view restricts rows based on runtime parameters obtained from PA_XC_VIEW_UTILS: when no specific TASK_ID is supplied, access depends on the project manager flag (GETPROJECTMANAGER); when it equals 'Y', all project tasks are visible, and when 'N', rows are limited to the descendant tree rooted at tasks managed by the requesting person (GETTASKMANAGERID). When a specific TASK_ID is supplied, the view returns that task and its hierarchical descendants via a CONNECT BY PRIOR T3.TASK_ID = T3.PARENT_TASK_ID traversal. This makes the view inherently context-sensitive and unsuitable for unfiltered bulk extraction.

Underlying Base Objects

The documented view text selects exclusively from PA_XC_TASKS_ALL_V, aliased as T. All projected columns — from USER_ID through DISPLAY_SEQ — are passed through from that intermediate view. The ETRM metadata lists no additional referenced base objects, reflecting the layered design: PA_XC_TASKS_BY_PROJECT_V wraps PA_XC_TASKS_ALL_V, which in turn consolidates the underlying PA_TASKS and related project tables. The metadata also notes the view is "Not implemented in this database" in the documented environment, meaning it must exist and be deployed in the target instance before use.

Two subqueries against PA_TASKS appear in the WHERE clause, both using the hierarchical START WITH ... CONNECT BY PRIOR syntax to resolve task lineage through PARENT_TASK_ID. The view therefore depends functionally on PA_TASKS for hierarchy resolution and on PA_XC_VIEW_UTILS for its session-level filter values.

Key Columns

• TASK_ID — Primary task identifier; the central search key that drives the view's single-task branch.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — Project context for each task row.
• TASK_NUMBER, TASK_NAME, DESCRIPTION — Task identification and narrative detail.
• TOP_TASK_ID, PARENT_TASK_ID, WBS_LEVEL, CHILD_FLAG — WBS hierarchy descriptors.
• TASK_MANAGER_ID, TASK_MANAGER_NAME — Manager assignment used by the security filter.
• START_DATE, END_DATE, DURATION, DURATION_UOM, MILESTONE_FLAG — Scheduling attributes.
• SUB_PROJECT_ID, SUB_PROJECT_NUMBER, SUB_PROJECT_NAME — Sub-project association.
• PROGRESS_STATUS_CODE, PROGRESS_STATUS, PROGRESS_ASOF_DATE, PROGRESS_COMMENT, PROGRESS_REPORT, PROGRESS_ISSUES, PROGRESS_IMAGE — Task progress reporting fields.
• TAG, DISPLAY_SEQ, USER_ID, USER_NAME — Presentation and personalization attributes.

Common Use Cases and Queries

Typical uses include task drill-down pages, project manager dashboards, and progress-reporting extracts. A representative query retrieving all tasks for the current session project:

SELECT task_id, task_number, task_name, wbs_level,
       parent_task_id, task_manager_name,
       progress_status, start_date, end_date
  FROM pa_xc_tasks_by_project_v
 ORDER BY display_seq;

To isolate a single task and its children, populate the utility context (via PA_XC_VIEW_UTILS) with the target TASK_ID and query without additional predicates. For reporting, administrators should note that the view returns only rows permitted by the manager-based security filter; independent extracts should query PA_XC_TASKS_ALL_V or PA_TASKS directly.