Search Results baselined_asgmt_start_date




Overview
Explore in AI Chat

Overview

PA_TASK_ASGMTS_V is an Oracle EBS Projects (PA) schema view owned by APPS. It presents task-level resource assignments—planned staffing of people, organizations, and other resource classes against specific WBS elements in a project structure—enriched with currency-denominated planned cost, quantity, and baselined figures. In Oracle EBS 12.1.1 and 12.2.2, planning data for a project resides in versioned structures (project structure versions, WBS element versions), and the base assignment tables store identifiers and measures that are not directly consumable by reporting tools. This view bridges that gap: it joins the resource assignment rows to their structural context (project, budget version, WBS element version, proj element) and resolves descriptions, unit-of-measure meanings, and multi-currency plan amounts.

Its principal role is in Projects reporting and integration. It is the standard read interface for extracting planned assignment detail—quantities, raw cost, burdened cost, and baselined comparisons—without requiring the caller to reconstruct the versioning joins or invoke the PA_TASK_ASSIGNMENT_UTILS package functions independently. Because it exposes both transaction-currency and project/projfunc-currency measures, it supports cross-currency reporting and plan-versus-baseline analysis.

Underlying Base Objects

The documented base objects underlying the view are:

The view therefore acts as a denormalized projection over these objects, hiding versioning and currency-resolution logic behind a single row per resource assignment.

Key Columns

Common Use Cases and Queries

Typical uses include staffing/plan extracts, cost-loaded plan reports, and reconciliations between planned and baselined assignment values. Note that columns returned by the PA_TASK_ASSIGNMENT_UTILS functions are not filterable efficiently, so restrict by indexed base columns first.

  • Assignment detail for a project: 
    SELECT resource_assignment_id, proj_element_id, alias,
       planned_quantity, planned_raw_cost_proj_cur
  FROM pa_task_asgmts_v
 WHERE project_id = :p_project_id
 ORDER BY planning_start_date;
  • Planned versus baselined quantity variance: 
    SELECT resource_assignment_id, planned_quantity,
       pa_task_asgmts_v.planned_quantity
         - TO_NUMBER(baselined_planned_qty) AS qty_variance
  FROM pa_task_asgmts_v
 WHERE project_id = :p_project_id
   AND unplanned_flag = 'N';
  • Person-level staffing by resource class: 
    SELECT person_id, resource_class_code, alias,
       SUM(planned_quantity) planned_qty
  FROM pa_task_asgmts_v
 WHERE project_id = :p_project_id
 GROUP BY person_id, resource_class_code, alias;