Results for “pa_tasks_v”

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

Overview

PA_TASKS_V is an Oracle EBS Projects (PA) view owned by the APPS schema. It is documented in ETRM as "10Sc only," indicating that it is intended primarily for Oracle Projects 10SC (a former public-sector/contracts-specific variant) rather than as a general-purpose 11i/R12 development interface. The view presents a denormalized, reportable representation of project task (WBS element) records. Its role is to expose the core task attributes from PA_TASKS together with the descriptive values that reporting and integration consumers typically require, such as organization name, task manager name, service type meaning, and structured address information. Because it joins lookup and HR/HZ descriptive data at the database level, it removes the need for consumers to reproduce those joins themselves.

Underlying Base Objects

The view text selects primarily from PA_TASKS (referenced as the TASK alias). Descriptive data is joined from several supporting objects:

• HR_ORGANIZATION_UNITS (ORG) supplies the loading/carrying-out organization name for CARRYING_OUT_ORGANIZATION_ID.
• PA_LOOKUPS (LK, LK2) provides lookup meanings, including SERVICE_TYPE_M for the service type code and the PM-related meaning.
• PER_ALL_PEOPLE_F (EMP) supplies TASK_MANAGER_NAME via FULL_NAME for the task manager person identifier.
• HZ_LOCATIONS, HZ_PARTY_SITES, and HZ_CUST_ACCT_SITES_ALL are referenced through the address identifier to return ADDRESS1 through ADDRESS4, CITY, STATE, and COUNTRY.
• PA_WORK_TYPES_VL, PA_TASK_UTILS, HR_GENERAL, and HR_SECURITY are also referenced; PA_TASK_UTILS provides the inline CHECK_CHILD_EXISTS function used to derive the WBS expand indicator.

Key Columns

The view exposes the full set of task attributes from PA_TASKS, including:

• TASK_ID, PROJECT_ID, TASK_NUMBER, TASK_NAME, DESCRIPTION — the core task identity.
• TOP_TASK_ID, PARENT_TASK_ID, WBS_LEVEL — hierarchical WBS position, plus a derived '+' or blank flag showing whether child tasks exist.
• READY_TO_BILL_FLAG, READY_TO_DISTRIBUTE_FLAG, CHARGEABLE_FLAG, BILLABLE_FLAG — billing and charging controls.
• CARRYING_OUT_ORGANIZATION_ID / ORGANIZATION_NAME and TASK_MANAGER_PERSON_ID / TASK_MANAGER_NAME — organizational ownership and responsibility.
• START_DATE, COMPLETION_DATE together with actual, early, late, and scheduled dates — task scheduling data.
• Bill rate, cost multiplier, and rate-schedule identifiers for labor and non-labor charging.
• ADDRESS_ID plus address1–4, city, state, country — task location reference.
• Standard WHO attributes (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, etc.) and the ATTRIBUTE1–10 and attribute category flexfield columns.

Common Use Cases and Queries

The view is typically used to build task-level reports and to feed downstream processes that need task names, manager names, and organization names in a single query.

List tasks for a project:

• SELECT task_id, task_number, task_name, wbs_level, organization_name, task_manager_name, ready_to_bill_flag FROM pa_tasks_v WHERE project_id = :project_id ORDER BY task_number;

Identify billable vs chargeable tasks:

• SELECT task_number, task_name, service_type_m, chargeable_flag, billable_flag FROM pa_tasks_v WHERE project_id = :project_id AND ready_to_bill_flag = 'Y';

Because the view is documented as 10Sc-specific, developers should verify its availability and column set in 12.1.1 and 12.2.2 before relying on it, and prefer supported PA APIs or PA_TASKS-based queries where portability is required.