Results for “pji_xtd_act_cmt_by_task_v”

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

Overview

APPS.PJI_XTD_ACT_CMT_BY_TASK_V is an Oracle E-Business Suite database view owned by the APPS schema and categorized under the PJI — Project Intelligence product. Project Intelligence is flagged as obsolete in ETRM 12.2.2, so the view is retained primarily for backward compatibility with external reporting and integration consumers. Its stated purpose is to present actual cost, revenue totals, and commitments aggregated by project and task across four time horizons: period-to-date (PTD), quarter-to-date (QTD), year-to-date (YTD), and inception-to-date (ITD). The view is principally consumed by external project management systems that import actuals from Oracle Projects, and it serves as the reporting interface through which burdened and billable cost figures are exposed at the task level.

For a user searching on the column name billable_burdened_cost, this view is the relevant object: it projects BILLABLE_BURDENED_COST_PTD (and its QTD, YTD, and ITD counterparts) derived from the underlying accumulation table. Because PJI is obsolete, the view should be treated as a legacy reporting surface rather than a foundation for new development.

Underlying Base Objects

The documented base objects referenced by the view are:

• PA_PROJECTS_ALL (SYNONYM) — the master project definition table, providing PROJECT_ID and related project attributes.
• PJI_FP_XBS_ACCUM_F (SYNONYM) — the Project Intelligence accumulation fact table that stores the raw cost, burdened cost, billable cost, revenue, hours, and commitment measures rolled up by calendar and period.
• PJI_ORG_EXTR_INFO (SYNONYM) — organization extraction information supporting organizational context for the rolled-up figures.
• PJI_TIME_CAL_PERIOD_V (VIEW) — a time calendar period view supplying PERIOD_NAME, PERIOD_START_DATE, and PERIOD_END_DATE.
• PJI_TIME_CAL_RPT_STRUCT_V (VIEW) — the reporting structure view that supplies CALENDAR_TYPE and CALENDAR_ID and drives the PTD/QTD/YTD/ITD mask logic applied to the fact measures.

The view text confirms this design: it selects PROJECT_ID, TASK_ID, CALENDAR_TYPE, CALENDAR_ID, PERIOD_NAME and the period boundary dates, then applies SUM(... * PTD_MASK) style expressions to each measure in PJI_FP_XBS_ACCUM_F to produce the period-bucketed totals.

Key Columns

• PROJECT_ID, TASK_ID — the grain of the view; one row per task per period per calendar.
• CALENDAR_TYPE, CALENDAR_ID, PERIOD_NAME, PERIOD_START_DATE, PERIOD_END_DATE — the reporting calendar context for every measure.
• BILLABLE_BURDENED_COST_PTD — billable burdened cost for the period-to-date, the column most relevant to the billable_burdened_cost search term.
• BURDENED_COST_PTD, RAW_COST_PTD — total burdened and raw actual cost for the period.
• BILLABLE_RAW_COST_PTD — billable raw cost before burden.
• REVENUE_PTD and LABOR_REVENUE_PTD — revenue recognized for the period.
• LABOR_RAW_COST_PTD, LABOR_BRDN_COST_PTD, LABOR_HOURS_PTD, BILL_LABOR_HRS_PTD, BILL_LABOR_RAW_COST_PTD, BILL_LABOR_BRDN_COST_PTD — labor cost and quantity detail.
• EQUIPMENT_RAW_COST_PTD, EQUIPMENT_BRDN_COST_PTD, EQUIPMENT_HOURS_PTD, BILLABLE_EQUIPMENT_HOURS_PTD — equipment cost and usage.
• CAPITAL_RAW_COST_PTD, CAPITAL_BURDENED_COST_PTD — capitalized cost components.
• SUP_INV_COMMITTED_COST_PTD, PO_COMMITTED_COST_PTD, PR_COMMITTED_COST_PTD, OTH_COMMITTED_COST_PTD, CMT_BURDENED_COST_PTD — commitment balances by source (supplier invoice, purchase order, requisition, other).
• BILLABLE_QUANTITY_PTD, BILLABLE_LABOR_HOURS_PTD, CMT_QUANTITY_PTD — derived quantity measures computed from labor hours with the same mask.

Common Use Cases and Queries

A typical use is extracting billable burdened cost by task for integration into an external project management system. The following query returns period-level billable burdened cost for a given project and task:

SELECT project_id, task_id, period_name, period_start_date, period_end_date,
       billable_burdened_cost_ptd
 FROM apps.pji_xtd_act_cmt_by_task_v
 WHERE project_id = :p_project_id
   AND task_id = :p_task_id
   AND calendar_type = 'PA'
ORDER BY period_start_date;

Another common pattern compares billable burdened cost against total burdened cost and commitments to assess margin and remaining exposure on a task:

SELECT task_id,
       SUM(billable_burdened_cost_ptd) billable_burdened,
       SUM(burdened_cost_ptd) total_burdened,
       SUM(po_committed_cost_ptd + pr_committed_cost_ptd) commitments
 FROM apps.pji_xtd_act_cmt_by_task_v
 WHERE project_id = :p_project_id
 GROUP BY task_id;

Because the view is defined at the task level with an explicit period grain, it supports period-by-period trend reporting and reconciliation between Oracle Projects actuals and external cost systems. Consumers should note the obsolete status of the PJI product and validate continued availability before building new dependencies on this view.