Search Results ptd_mask




Overview
Explore in AI Chat

Overview

APPS.PJI_XTD_ACT_CMT_BY_RSRC_V is a reporting view in Oracle EBS Project Manufacturing/Projects Intelligence (PJI) that aggregates actual and committed project cost and revenue by resource. It presents period-to-date (PTD), and by extension quarter-to-date (QTD) and year-to-date (YTD), balances keyed by project, task, calendar, and reporting structure element (RBS). The view is most commonly referenced when reporting labor hours, burdened and raw costs, billable and non-billable labor, equipment usage, and commitment amounts. Users searching the term "labor_hrs" encounter this object because the view exposes several aliases of the LABOR_HRS column, including LABOR_HOURS_PTD, LABOR_HRS_PTD, CMT_QUANTITY_PTD, and QUANTITY_PTD, all derived from SUM(LABOR_HRS * PTD_MASK).

Underlying Base Objects

The view is documented in ETRM 12.2.2 as owned by APPS and defined over the following referenced objects:

The underlying fact data flows from the Projects Intelligence extraction process, which populates PJI_FP_XBS_ACCUM_F from Oracle Projects and Manufacturing transaction sources. The view applies the appropriate PTD, QTD, and YTD masks to the accumulated facts to produce the reporting periods.

Key Columns

Common Use Cases and Queries

Typical uses include labor hour reporting by resource, project cost and commitment dashboards, and extract feeds into external data warehouses. A representative query returns labor hours and cost for a project and period:

  • SELECT project_id, task_id, period_name, labor_hrs_ptd, bill_labor_hrs_ptd, labor_raw_cost_ptd, labor_brdn_cost_ptd FROM apps.pji_xtd_act_cmt_by_rsrc_v WHERE project_id = :p_project_id AND period_name = :p_period_name;
  • SELECT rbs_element_id, SUM(labor_hrs_ptd) hours, SUM(labor_brdn_cost_ptd) cost FROM apps.pji_xtd_act_cmt_by_rsrc_v GROUP BY rbs_element_id;
  • SELECT period_name, SUM(cmt_quantity_ptd) FROM apps.pji_xtd_act_cmt_by_rsrc_v WHERE rbs_version_id = :p_version AND project_id = :p_project_id GROUP BY period_name;

Because the view aggregates accumulated facts, it is appropriate for reporting and extraction but not for transactional updates. Performance depends on filtering by PROJECT_ID, PERIOD_NAME, and RBS identifiers.