Results for “pa_tasks”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_TASKS is the Projects (PA) module table that stores user-defined subdivisions of project work. In Oracle EBS 12.1.1 and 12.2.2, it is the master record for tasks and lowest-level work breakdown structure (WBS) elements against which project costs, budgets, commitments, billing, and revenue are transacted. Each row represents one task belonging to a project, with hierarchical relationships to parent and top tasks enabling multi-level WBS structures. The table has 99 documented columns and resides in the PA schema, owned by the Projects application. Heuristically, the FK structure mined from the metadata classifies PA_TASKS as a hub in Data Vault terms: it is a central business entity with a single-column surrogate key, referenced by well over one hundred dependent tables across Projects, Payables, Purchasing, Assets, Grants, and Contract modules. That classification is a modeling suggestion, not an EBS-native concept.

Key Information Stored

The surrogate primary key is TASK_ID (constraint PA_TASKS_PK), a system-generated identifier used by every dependent transaction table. Two unique indexes define business-key candidates: PA_TASKS_U1 on TASK_ID and PA_TASKS_U2 on (PROJECT_ID, TASK_NUMBER), confirming that the task number is unique only within a project. The most significant columns include: PROJECT_ID, the owning project; TASK_NUMBER and TASK_NAME (with LONG_TASK_NAME for extended text), the user-facing identifiers; PARENT_TASK_ID and TOP_TASK_ID, self-referencing FKs that define the WBS hierarchy; WBS_LEVEL, indicating depth in the structure; and CARRYING_OUT_ORGANIZATION_ID, the performing organization. Financial control columns include LABOR_COST_MULTIPLIER_NAME (FK to PA_LABOR_COST_MULTIPLIERS), COST_IND_RATE_SCH_ID / REV_IND_RATE_SCH_ID / INV_IND_RATE_SCH_ID (FKs to PA_IND_RATE_SCHEDULES_ALL_BG) with corresponding fixed-date columns, OVR_ variants for overrides, and their fixed-date counterparts. Billing behavior is governed by READY_TO_BILL_FLAG, BILLABLE_FLAG, CHARGEABLE_FLAG, LABOR_TP_SCHEDULE_ID and NL_TP_SCHEDULE_ID (FKs to PA_CC_TP_SCHEDULES_BG), and REVENUE_ACCRUAL_METHOD / INVOICE_METHOD. Scheduling dates such as START_DATE, COMPLETION_DATE, SCHEDULED_START_DATE, and ACTUAL_START_DATE support project planning. ADDRESS_ID, WORK_TYPE_ID, TASK_MANAGER_PERSON_ID, and the ten ATTRIBUTE flex columns complete the descriptive profile.

Common Use Cases and Queries

PA_TASKS is queried whenever project costs must be resolved to a task, whether for expenditure inquiry, budget versus actual reporting, or billing review. A typical query lists active tasks for a project:

  • SELECT t.task_id, t.task_number, t.task_name, t.parent_task_id, t.wbs_level FROM pa_tasks t WHERE t.project_id = :project_id AND t.chargeable_flag = 'Y' ORDER BY t.task_number;
  • Expenditure detail joins PA_EXPENDITURE_ITEMS_ALL.TASK_ID = PA_TASKS.TASK_ID to produce task-level cost reports.
  • WBS hierarchy traversal uses the self-referencing PARENT_TASK_ID or TOP_TASK_ID columns, frequently with CONNECT BY for indented structures.
  • Billing analysis combines PA_TASKS with PA_DRAFT_INVOICE_ITEMS and PA_EVENTS on TASK_ID to reconcile revenue by task.
  • Rate-schedule audits join COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, and INV_IND_RATE_SCH_ID back to PA_IND_RATE_SCHEDULES_ALL_BG to verify which burdens apply.

Because task numbering is project-scoped, all practical lookups should filter by PROJECT_ID alongside TASK_NUMBER or TASK_NAME.

Related Objects

The most significant dependents and related objects, based on the documented foreign-key relationships, include:

These relationships confirm PA_TASKS as the central hub through which project transactions in multiple Oracle EBS modules are attributed to task-level work.