Results for “res_list_mem_id”

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

Overview

APPS.PJI_ACCUM_RL_ACT_V is a reporting and integration view in Oracle EBS Projects (PA) and Enterprise Resource Planning, owned by the APPS schema. It presents accumulated actual cost, burdened cost, revenue, and labor hour balances at the project, task, and resource list member level. The view is defined as a UNION ALL of two distinctly sourced result sets, selected by the PJI_SOURCE_FLAG column of PA_PROJECTS_ALL. The first branch reads native, existing project accumulations from PA_ACCUM_RSRC_ACT_V; the second reads staging rows from PJI_FM_XBS_ACCUM_TMP1 populated when PJI_SOURCE_FLAG equals 'Y'. This design makes the view a consolidated projection of "as-is" actuals plus any supplemental or externally sourced accumulations staged for a project, which is central to Project Intelligence (PJI) fact extraction and downstream reporting.

Underlying Base Objects

The view is defined over three documented objects:

• PA_ACCUM_RSRC_ACT_V (VIEW) — supplies the standard accumulated actuals for projects where PJI_SOURCE_FLAG IS NULL.
• PA_PROJECTS_ALL (SYNONYM) — the project master, joined on PROJECT_ID in both branches; also the driver of the PJI_SOURCE_FLAG discriminator.
• PJI_FM_XBS_ACCUM_TMP1 (SYNONYM) — the staging object providing supplemental accumulated values for projects flagged as externally sourced.

Both branches join to PA_PROJECTS_ALL on PROJECT_ID, ensuring project validity and enabling the source-flag filter that determines which physical source contributes rows. Because the join is inner, only project IDs present in PA_PROJECTS_ALL are returned.

Key Columns

• PROJECT_ID — the project identifier, common to both branches.
• TASK_ID — derived from ACT.TASK_ID in the first branch and from TMP.PROJECT_ELEMENT_ID in the second, providing a unified task/project element key.
• RES_LIST_MEM_ID (RESOURCE_LIST_MEMBER_ID) — the resource list member identifier, the column most directly matched by the search term "res_list_mem_id". It identifies the resource within a project's resource list to which the accumulated amounts apply.
• RAW_COST — raw cost ITD (RAW_COST_ITD / POU_RAW_COST).
• BURDENED_COST — burdened cost ITD (BURDENED_COST_ITD / POU_BRDN_COST).
• REVENUE — revenue ITD (REVENUE_ITD / POU_REVENUE).
• LABOR_HRS — actual labor hours ITD (ACTUALS_LABOR_HOURS_ITD / LABOR_HOURS).

Common Use Cases and Queries

Typical use cases include reconciliation of project cost and revenue balances by resource, PJI fact loading, and exception reporting where supplemental XBS accumulations are combined with native actuals. A representative query follows:

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 ORDER BY task_id, res_list_mem_id;

To isolate the supplemental-source population, join to PA_PROJECTS_ALL:

SELECT v.project_id, v.res_list_mem_id, v.raw_cost, v.burdened_cost FROM apps.pji_accum_rl_act_v v, apps.pa_projects_all p WHERE v.project_id = p.project_id AND p.pji_source_flag = 'Y';

For aggregate reporting, SUM the monetary columns grouped by project and resource list member. Because the view is a UNION ALL, callers should expect potential duplication if a project appears in both sources; the PJI_SOURCE_FLAG predicate is the documented mechanism for controlling which branch contributes rows.