Results for “etc_labor_brdn_cost”

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

Overview

The PJI_AC_PLN_BY_RSRC_V view is an Oracle Applications (APPS) database object owned by the APPS schema within the PJI – Project Intelligence product family. It exposes budgeted cost and revenue information aggregated by project task and by resource, aligned to both Oracle Projects (PA) and General Ledger (GL) accounting periods. Its principal role is to serve as a reporting and integration interface for external project management systems that import financial data from Oracle Projects. Rather than requiring downstream systems to replicate the complex join logic between project-planning fact data and project master records, the view presents a consolidated, pre-joined result set keyed at the project, task, and resource breakdown structure (RBS) level.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view references two base objects:

• PA_PROJECTS_ALL (SYNONYM) – the master project definition table in Oracle Projects, supplying project-level context such as project identifiers and attributes.
• PJI_FP_XBS_ACCUM_F (SYNONYM) – the Project Intelligence accumulated financial fact table, which stores the planned, committed, and actual cost and revenue measures used by the view.

The view is defined primarily over the PJI fact table and derives its dimensional keys (PROJECT_ID, PROJECT_ELEMENT_ID, RBS_ELEMENT_ID, RBS_VERSION_ID, PLAN_TYPE_ID, PLAN_VERSION_ID) and its numeric measures from that source, using PA_PROJECTS_ALL to resolve project-level attributes. Because the underlying object is a fact table, the view applies SUM aggregations across the exposed measures to produce a task- and resource-level rollup that is suitable for plan-versus-actual analysis.

Key Columns

The view exposes a broad set of cost, revenue, quantity, and commitment measures. Notable columns include:

• PROJECT_ID, TASK_ID (PROJECT_ELEMENT_ID), RBS_ELEMENT_ID, RBS_VERSION_ID – dimensional keys identifying the project, task, and resource breakdown structure element.
• PLAN_TYPE_ID, PLAN_VERSION_ID – identify the budget or forecast plan and version to which the amounts belong.
• REVENUE, RAW_COST, BURDENED_COST, CAPITAL_RAW_COST, CAPITAL_BURDENED_COST – planned revenue and cost measures, including capitalizable portions.
• LABOR_RAW_COST, LABOR_BRDN_COST, LABOR_REVENUE, EQUIPMENT_RAW_COST, EQUIPMENT_BRDN_COST – resource-specific cost and revenue breakdowns for labor and equipment.
• QUANTITY, BILLABLE_QUANTITY, LABOR_HRS, BILL_LABOR_HRS, EQUIPMENT_HOURS, BILLABLE_EQUIPMENT_HOURS – planned hours and billable quantities.
• SUP_INV_COMMITTED_COST, PO_COMMITTED_COST, PR_COMMITTED_COST, OTH_COMMITTED_COST, CMT_BURDENED_COST – committed cost components from supplier invoices, purchase orders, requisitions, and other sources, with a rolled-up committed burdened cost.
• ACT_LABOR_HRS, ACT_EQUIP_HRS, ACT_LABOR_BRDN_COST, ACT_EQUIP_BRDN_COST, ACT_BRDN_COST, ACT_RAW_COST, ACT_REVENUE – corresponding actual amounts, enabling variance comparisons. The ACT_EQUIP_BRDN_COST column in particular answers the common search term "act_equip_brdn_cost", giving actual burdened equipment cost.
• Estimated-to-complete (ETC) measures such as ETC_LABOR_* columns appear at the tail of the SELECT list to support forecasting.

Common Use Cases and Queries

Typical scenarios include exporting planned and actual cost/revenue by task and resource to an external planning tool, and analysing budget-versus-actual burdened equipment or labor cost at the resource level.

• Retrieving actual burdened equipment cost for a project's resources:

  SELECT project_id, task_id, rbs_element_id,
         act_equip_brdn_cost, act_equip_hrs
  FROM   apps.pji_ac_pln_by_rsrc_v
  WHERE  project_id = :p_project_id;

• Comparing budgeted versus actual burdened cost by plan version:

SELECT project_id, plan_type_id, plan_version_id,
       SUM(burdened_cost)     budgeted_burdened,
       SUM(act_brdn_cost)     actual_burdened
FROM   apps.pji_ac_pln_by_rsrc_v
GROUP  BY project_id, plan_type_id, plan_version_id;

Because the view pre-aggregates fact data, queries should apply filters on PROJECT_ID and plan identifiers to constrain result sets, and report consumers should note that measures are summed across the underlying accumulation records.