Search Results duration_uom_code

Overview

PA_XC_TASKS_ALL_V is a Projects (PA) module view that consolidates detailed task information across the Oracle E-Business Suite project structure. The name and documentation describe it as a "View All Task Details" object, exposing task-level attributes spanning project identification, hierarchy, progress reporting, and workflow status. In Oracle EBS 12.1.1 and 12.2.2, such views are typically used for reporting and integration against project tasks, particularly where progress reports maintained in PA_PROJ_PROGRESS_REPORTS must be joined to the underlying PA_TASKS records.

The view returns one row per task combined with its associated progress report, task manager party, carrying-out organization, and related lookup meanings. Because it references HZ_PARTIES and FND_USER, it also surfaces party and user context — a pattern common to cross-application (XC) reporting views used by Oracle Projects reporting and by external integrations that need denormalized task data without writing multi-table joins.

Underlying Base Objects

The view text documents the following base objects in its FROM clause and join predicates:

• PA_TASKS (aliased T and ST) — the primary task table, providing TASK_ID, PROJECT_ID, TASK_NUMBER, DESCRIPTION, hierarchy columns, dates, and descriptive flexfield attributes.
• PA_PROJ_PROGRESS_REPORTS (PPR) — joined on PROJECT_ID and TASK_ID, supplying progress status, estimated/actual dates, percent complete, and workflow columns.
• PA_PROJECTS_ALL (PRJ1, PRJ2) — project segments and names, for the task's project and a related project reference.
• HZ_PARTIES (PTY1, PTY2) — party names for the carrying-out organization and task manager.
• FND_USER (USR) — user ID and user name, outer-joined via CUSTOMER_ID.
• PA_LOOKUPS (PAL, PAL1, PAL2) — lookup meanings for progress status, unit type, and attribute values.

The ETRM metadata notes "Not implemented in this database" for the implementation/DBA data and lists no separately documented base objects, so the view text above is the authoritative source for its structure. The joins are inner joins except for PTY2, which is outer-joined, meaning tasks without an assigned task manager may still appear depending on the join path.

Key Columns

Notable columns include identity and hierarchy fields (TASK_ID, PROJECT_ID, SEGMENT1, NAME, TASK_NUMBER, TOP_TASK_ID, WBS_LEVEL, PARENT_TASK_ID), organizational context (CARRYING_OUT_ORGANIZATION_ID, PARTY_NAME, TASK_MANAGER_PERSON_ID, USER_NAME), and scheduling data (START_DATE, COMPLETION_DATE). Progress-related columns from PPR include PROGRESS_STATUS_CODE, PROGRESS_ASOF_DATE, PERCENT_COMPLETE, ESTIMATE_TO_COMPLETE, UNIT_TYPE, ESTIMATED_START_DATE, ESTIMATED_END_DATE, ACTUAL_START_DATE, and ACTUAL_END_DATE. Two derived date-difference expressions compute variance between planned and actual/estimated milestones. Workflow columns (WF_STATUS_CODE, WF_ITEM_TYPE, WF_ITEM_KEY, WF_PROCESS) and flexfield attributes (ATTRIBUTE1 through ATTRIBUTE10) are also exposed. The user's search term, duration_uom_code, is not among the columns listed in the documented view text; duration unit-of-measure values are typically handled on the underlying project/task definitions rather than directly in this view.

Common Use Cases and Queries

Typical scenarios include project task status reporting, progress-report reconciliation, and integration extracts. A representative query:

• SELECT TASK_ID, PROJECT_ID, TASK_NUMBER, DESCRIPTION, PROGRESS_STATUS_CODE, PERCENT_COMPLETE, ACTUAL_END_DATE FROM PA_XC_TASKS_ALL_V WHERE PROJECT_ID = :project_id;
• Filtering on WBS_LEVEL or PARENT_TASK_ID to reconstruct task hierarchies for reporting.
• Joining to lookup views on PROGRESS_STATUS_CODE or UNIT_TYPE to resolve meanings.