Results for “task_manager_person_id”

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

Overview

PA_PROJ_WBS_VIEW is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It presents project work breakdown structure (WBS) information by joining project header data to its constituent tasks, producing a flat, presentation-ready result set in which task numbers and names are visually indented according to their position in the WBS hierarchy. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

Its principal value lies in exposing the WBS_LEVEL attribute alongside parent-child relationships and indented display columns, allowing reporting tools, concurrent programs, and integrations to render a hierarchical project structure without recursive SQL. Because it encapsulates the join and indentation logic, it serves as a reusable source for project task inquiries, extracts, and third-party interfaces.

Underlying Base Objects

The view text defines an outer join across three primary sources: PA_PROJECTS (P), PA_TASKS (T), and PER_PEOPLE_F (PER). PA_PROJECTS supplies project-level attributes such as PROJECT_ID, SEGMENT1, and NAME; PA_TASKS supplies the WBS task rows including TASK_ID, TASK_NUMBER, PARENT_TASK_ID, and WBS_LEVEL. The join condition links P.PROJECT_ID to T.PROJECT_ID and relates T.TASK_MANAGER_PERSON_ID to PER.PERSON_ID using an Oracle outer join (+), constrained further by TRUNC(SYSDATE) falling between the person record's effective start and end dates.

ETRM additionally documents the referenced base objects as HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), PA_PROJECTS (SYNONYM), PA_TASKS (SYNONYM), and PER_PEOPLE_F (VIEW). The presence of HR_SECURITY and HR_PERSON_NAME reflects standard Oracle HR security and name-formatting packages that govern access to person data and how manager names are resolved in the session's context.

Key Columns

• PROJECT_ID / PROJECT_NUMBER / PROJECT_NAME — Project identifier, the project number (from P.SEGMENT1), and the project name.
• TASK_ID / TASK_NUMBER / TASK_NAME — The individual WBS task identifier, task number, and task name.
• INDENTED_TASK_NUMBER / INDENTED_TASK_NAME — Task number and name prefixed with two spaces per level of the hierarchy, enabling hierarchical display in reports.
• PARENT_TASK_ID — Reference to the parent task, defining the WBS tree relationship.
• WBS_LEVEL — Numeric depth of the task within the WBS, the attribute most relevant to the "wbs_level" search term and the driver of the indentation logic.
• DESCRIPTION — Descriptive text for the task.
• TASK_START_DATE / TASK_COMPLETION_DATE — Scheduled or actual start and completion dates of the task.
• TASK_MANAGER_PERSON_ID / TASK_MANAGER_NAME — Task manager identifier and resolved full name from PER_PEOPLE_F.

Common Use Cases and Queries

A typical reporting query filters to a single project and orders by task number to reproduce the WBS sequence, optionally using WBS_LEVEL to control drill-down behavior:

SELECT project_number, indented_task_number, task_name, wbs_level, task_manager_name FROM pa_proj_wbs_view WHERE project_number = :p_project_number AND wbs_level <= :p_max_level ORDER BY task_number;

The view is equally suited to extracting the complete task structure for data migration or interface purposes, grouping by WBS_LEVEL to summarize task counts per hierarchy depth, or joining TASK_ID to other Projects tables such as PA_TASK_ASSIGNMENTS or expenditure fact tables. Because indentation is pre-computed, BI Publisher and Oracle Reports templates can render hierarchical project structures directly from the indented columns without additional formatting logic.