Results for “labor_hrs”

50+ results




Overview
Explore in AI Chat

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

Overview

PJI_ACCUM_RL_ACT_V is a Project Intelligence (PJI) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes accumulated actual amounts at the resource-list-member level, combining standard Oracle Projects actuals with results generated by the PJI forecast/commitment extraction process. The view is a union of two sources: current actuals drawn from PA_ACCUM_RSRC_ACT_V for projects whose PJI_SOURCE_FLAG is null, and staged extracted balances drawn from the temporary table PJI_FM_XBS_ACCUM_TMP1 for projects whose PJI_SOURCE_FLAG is 'Y'. This design allows Project Intelligence dashboards and extracts to present a single, consistent row set regardless of whether the figures originate from native Projects accumulations or from a PJI-specific data pull. Users searching for "pji_fm_xbs_accum_tmp1" reach this object because that temporary table is one of the two definitive sources feeding the view; the matching records are the ones flagged with PJI_SOURCE_FLAG = 'Y'.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_ACCUM_RSRC_ACT_V (VIEW) — the standard Oracle Projects actuals accumulation view, supplying project, task, resource list member, raw cost, burdened cost, revenue, and labor hours for non-PJI-sourced projects.
  • PJI_FM_XBS_ACCUM_TMP1 (SYNONYM) — a PJI staging table holding extracted or externally sourced accumulation rows, contributing the same measures for projects where PJI_SOURCE_FLAG = 'Y'.
  • PA_PROJECTS_ALL (SYNONYM) — joined in both branches of the union as the project master, filtering and qualifying PROJECT_ID against valid projects defined in Oracle Projects.

Because both branches are joined to PA_PROJECTS_ALL on PROJECT_ID, the view returns only rows whose project exists in the Projects repository, providing a natural validation boundary for either source.

Key Columns

Common Use Cases and Queries

Typical usage includes Project Intelligence performance reporting, reconciliation of PJI-extracted balances against native Projects actuals, and resource-level cost/revenue analysis. A basic query retrieves accumulated actuals for a project:

  • SELECT project_id, task_id, res_list_mem_id, raw_cost, burdened_cost, revenue, labor_hrs FROM apps.pji_accum_rl_act_v WHERE project_id = :p_project_id;
  • To isolate rows originating from the PJI staging table (the "pji_fm_xbs_accum_tmp1" source), compare the view output against PJI_FM_XBS_ACCUM_TMP1 joined through PA_PROJECTS_ALL on PROJECT_ID for projects where PJI_SOURCE_FLAG = 'Y'.
  • Aggregation by resource list member supports margin and utilization reporting: SELECT res_list_mem_id, SUM(burdened_cost), SUM(revenue), SUM(labor_hrs) FROM apps.pji_accum_rl_act_v WHERE project_id = :p_project_id GROUP BY res_list_mem_id;

Because the view already enforces the PJI_SOURCE_FLAG split and the PA_PROJECTS_ALL join, consumers should not re-apply those predicates; doing so can inadvertently suppress the branch they intended to include.