Results for “actuals_labor_hours_itd”

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

Overview

PA_ACCUM_WBS_ACT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. It is defined as a VIEW with VALID status and is supported across EBS 12.1.1 and 12.2.2. The view presents actual cost and revenue totals for projects and tasks, organized along the project Work Breakdown Structure (WBS). Its principal purpose is to expose summarized project performance data—cost, burden, labor hours, and revenue—at the task and project level, segmented into inception-to-date (ITD), year-to-date (YTD), prior period (PP), and period-to-date (PTD) accumulations. Reporting tools, custom concurrent programs, and downstream extracts routinely reference this view to produce project cost and revenue reports without needing to join the underlying accumulation tables directly.

Underlying Base Objects

The view is constructed over the following documented base objects:

• PA_PROJECTS (synonym) — provides project number (SEGMENT1) and project name.
• PA_TASKS (synonym) — supplies task number, task name, WBS level, start and completion dates, and the task manager person identifier.
• PA_PROJECT_ACCUM_HEADERS (synonym) — the accumulation header table, joined on PROJECT_ID with TASK_ID >= 0 and RESOURCE_LIST_ID = 0.
• PA_PROJECT_ACCUM_ACTUALS (synonym) — the actuals table holding the cost, hour, and revenue accumulators, joined via PROJECT_ACCUM_ID.
• PER_PEOPLE_F (view) — resolves the task manager's full name, joined on PERSON_ID with effective-date filtering against SYSDATE.

The documented metadata also lists HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages as referenced objects. These are invoked through the PER_PEOPLE_F view rather than directly in the view text, reflecting the standard Oracle HR security and name-resolution mechanisms applied to person data. All base tables are accessed through APPS synonyms, consistent with standard EBS schema design.

Key Columns

The view exposes project, task, and WBS descriptors alongside the accumulated financial and effort measures:

• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — project identification and descriptive fields.
• TASK_ID, TASK_NUMBER, TASK_NAME — task identification and description.
• INDENTED_TASK_NUMBER, INDENTED_TASK_NAME — task identifiers left-padded by two spaces per WBS level, producing a hierarchical display suitable for structured reporting.
• WBS_LEVEL, TASK_START_DATE, TASK_COMPLETION_DATE, TASK_MANAGER_PERSON — structural and ownership attributes of each task.
• Cost measures — RAW_COST, BILLABLE_RAW_COST, BURDENED_COST, and BILLABLE_BURDENED_COST, each returned in ITD, YTD, PP, and PTD variants and wrapped in NVL(...,0).
• LABOR_HOURS and BILLABLE_LABOR_HOURS — again in ITD, YTD, PP, and PTD variants.
• REVENUE_ITD, REVENUE_YTD, REVENUE_PP, REVENUE_PTD — accumulated revenue amounts.

The pervasive NVL defaulting to zero ensures that tasks lacking accumulated activity still return numeric values, which simplifies aggregation and arithmetic in report logic.

Common Use Cases and Queries

Typical applications include WBS cost performance reporting, revenue-versus-cost analysis, period-over-period comparisons, and labor utilization extracts. Because the view pre-joins the accumulation headers and actuals, it eliminates repetitive join logic in custom reports.

A representative query retrieving task-level cost and revenue for a project is shown below:

• SELECT project_number, project_name, indented_task_name, wbs_level, raw_cost_itd, burdened_cost_itd, revenue_itd
• FROM apps.pa_accum_wbs_act_v
• WHERE project_id = :p_project_id
• ORDER BY task_number, wbs_level;

For period-to-date reporting across projects, restricting on the accumulator columns is effective:

• SELECT project_number, task_number, raw_cost_ptd, billable_labor_hours_ptd, revenue_ptd
• FROM apps.pa_accum_wbs_act_v
• WHERE raw_cost_ptd <> 0 OR revenue_ptd <> 0;

Because the view joins PA_PROJECT_ACCUM_HEADERS with TASK_ID >= 0 and RESOURCE_LIST_ID = 0, results are limited to task-level accumulations that exclude resource-list-specific breakdowns. Queries should apply project and task filters wherever possible to keep execution efficient against the underlying accumulation tables.