Search Results pa_tasks_displayed

Overview

The APPS.PJM_PROJECT_TASK_V view is a Project Manufacturing (PJM) inquiry object that exposes task-level (WBS) information for Oracle E-Business Suite Web Inquiry pages. It is a read-only, denormalized presentation layer that joins task records from PA_TASKS to their parent project in PA_PROJECTS_ALL and to the task manager in PER_ALL_PEOPLE_F. The view exists primarily to support self-service and Web Inquiry screens that display the work breakdown structure (WBS) of a project, including task numbers, names, descriptions, managers, and schedule dates.

Its most distinctive behavior concerns the WBS_SORT_ORDER column, which is the element users search for in relation to this view. Rather than exposing a physical sort column, WBS_SORT_ORDER is computed at query time using a DECODE over the profile option PA_TASKS_DISPLAYED. When the profile is set to "ALL" (or is null), the column returns PA_TASK_UTILS.SORT_ORDER_TREE_WALK(TASK.PARENT_TASK_ID, TASK.TASK_NUMBER), producing a hierarchical, depth-first ordering key. Otherwise, the column simply returns TASK.TASK_NUMBER. This dual behavior allows inquiry pages to present the WBS either in its natural tree hierarchy or in a flat, number-sorted list.

Underlying Base Objects

The documented referenced base objects are:

• PA_TASKS (SYNONYM) — the primary driver, supplying TASK_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION, PARENT_TASK_ID, TASK_MANAGER_PERSON_ID, START_DATE, and COMPLETION_DATE.
• PA_PROJECTS_ALL (SYNONYM) — supplies PROJECT_ID, SEGMENT1 (project number), NAME, and DESCRIPTION.
• PER_ALL_PEOPLE_F (SYNONYM) — an outer-joined source (PEOP.PERSON_ID (+) = TASK.TASK_MANAGER_PERSON_ID) providing the manager's FULL_NAME, constrained to the effective-dated row covering TRUNC(SYSDATE).
• PA_TASK_UTILS (PACKAGE) — supplies the SORT_ORDER_TREE_WALK function used to build WBS_SORT_ORDER.
• FND_PROFILE (PACKAGE) — supplies VALUE_SPECIFIC('PA_TASKS_DISPLAYED'), the profile lookup driving the DECODE.

The joins are project-to-task on PROJECT_ID and the outer-joined manager lookup on person ID; the view is owned by APPS and documented as VALID.

Key Columns

• PROJECT_ID / PROJECT_NUMBER / PROJECT_NAME / PROJECT_DESCRIPTION — project identity, with SEGMENT1 exposed as PROJECT_NUMBER.
• TASK_ID / TASK_NUMBER / TASK_NAME / DESCRIPTION — task identity and descriptive text.
• WBS_SORT_ORDER — the computed ordering value described above; the key column for hierarchical WBS display.
• MANAGER — the full name of the effective-dated task manager (nullable via outer join).
• START_DATE / END_DATE — task schedule dates (START_DATE and COMPLETION_DATE in the base table).

Common Use Cases and Queries

The view is used in project inquiry, WBS reporting, and integration extracts where a single flattened WBS listing is required. A typical query orders results by the computed WBS key:

• List all tasks for a project in hierarchical order: SELECT project_number, task_number, task_name, wbs_sort_order, manager FROM apps.pjm_project_task_v WHERE project_id = :p_project_id ORDER BY wbs_sort_order;
• Locate tasks by manager: filter on MANAGER to review assignments.
• Schedule review: filter on START_DATE / END_DATE ranges for a given project.

Because WBS_SORT_ORDER depends on the PA_TASKS_DISPLAYED profile, results change with that setting, so reports relying on strict hierarchy should confirm the profile value before use.