Results for “pa_xc_progress_status”

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

Overview

PA_XC_MY_TASKS_V is a Projects (PA) module view titled "View My Task Details." It is designed to expose task-level information from Oracle Projects, filtered to a task manager or resource context, and enriched with project progress report status. The view is intended to support the "My Tasks" style inquiry used within the Projects workbench and related self-service pages, allowing an end user or a reporting layer to retrieve a consolidated picture of the tasks a person owns or manages.

Functionally, the view presents one row per task per progress report association. It surfaces descriptive project attributes (project number, project name), task attributes (task number, description, WBS level, start date, completion date, milestone flag), and a meaningful progress status derived from a Projects lookup. Because the view already joins to the progress report entity and resolves lookup codes to meanings, it can be consumed directly by reports, dashboards, or integration programs without repetitive join logic.

Underlying Base Objects

The view is defined over four principal base objects, with additional lookups and parties joining into subsequent branches of the UNION:

• PA_TASKS T — the primary entity providing task identifiers, numbering, description, WBS level, dates, the milestone attribute, and task manager person.
• PA_PROJECTS_ALL PRJ — supplies the project segment (number) and project name.
• PA_PROJ_PROGRESS_REPORTS PPR — the task/project progress report association, joining by PROJECT_ID and TASK_ID.
• PA_LOOKUPS LKP — resolves PROGRESS_STATUS_CODE against the lookup type PA_XC_PROGRESS_STATUS, exposing the MEANING.
• PA_PROJECT_PARTIES PPP — used in the second branch, keyed by RESOURCE_TYPE_ID = 101 and OBJECT_TYPE = 'PA_TASKS', to relate the task to an associated party/resource.
• Resource / subject relationships (REL) — referenced in the third UNION branch by subject identifier.

The task manager identity is projected in the first branch from PA_TASKS; the second and third branches substitute a resource source identifier and a subject identifier respectively, which is how the view produces the "my tasks" perspective across direct ownership, party/resource association, and relationship assignment.

Key Columns

• TASK_ID, PROJECT_ID — primary keys linking the row back to PA_TASKS and PA_PROJECTS_ALL.
• SEGMENT1, NAME — the project number and project name.
• TASK_NUMBER, DESCRIPTION — the task identifier and descriptive text.
• WBS_LEVEL — the task's position within the WBS hierarchy.
• START_DATE, COMPLETION_DATE — scheduling dates for the task.
• ATTRIBUTE1 — carries the milestone flag (identified in the view text as "MILE STONE FLAG").
• PROGRESS_STATUS_CODE, MEANING — the status code and its human-readable meaning from the PA_XC_PROGRESS_STATUS lookup.
• TASK_MANAGER_PERSON_ID / RESOURCE_SOURCE_ID / SUBJECT_ID — the person or resource each row is attributed to, depending on the UNION branch.
• ATTRIBUTE5 — an additional descriptive key carried through all branches.
• Direct-child indicator — the NVL/(SELECT FROM DUAL WHERE EXISTS ...) expression returns 'Y' when a task has child tasks, otherwise 'N'.
• Connection type literal — the constant 'DIRECT' returned in all branches.

Common Use Cases and Queries

The view is commonly used to populate task lists, to answer "what tasks are assigned to me," and to aggregate project progress status reporting. A representative query retrieves open tasks with their meaning:

• SELECT task_id, project_id, segment1, name, task_number, description, wbs_level, start_date, completion_date, attribute1 milestone_flag, meaning progress_status, attribute5 FROM pa_xc_my_tasks_v WHERE task_manager_person_id = :person_id;
• SELECT segment1, name, task_number, meaning FROM pa_xc_my_tasks_v WHERE meaning = 'Open' ORDER BY start_date;
• SELECT task_id, description FROM pa_xc_my_tasks_v WHERE wbs_level = 1 AND attribute1 = 'Y';

Note that the ETRM metadata records the view as not implemented in this database, and no base objects are formally documented; the structure above is drawn directly from the view text supplied in the metadata.