Search Results labor_hrs_ptd




Overview
Explore in AI Chat

Overview

PJI_XTD_ACT_CMT_BY_RSRC_V is an APPS-owned database view within the PJI – Project Intelligence product family of Oracle E-Business Suite. It is classified as a VALID view and is documented for both EBS 12.1.1 and 12.2.2 releases. The view exposes actual cost, revenue totals, and commitments aggregated across four time-phased reporting horizons — Period-to-Date (PTD), Quarter-to-Date (QTD), Year-to-Date (YTD), and Inception-to-Date (ITD) — broken down by task and by resource. Its principal purpose is to serve as an integration surface for external project management systems that import actuals from Oracle; rather than querying the transactional PA and PJI tables directly, such systems consume this pre-aggregated view.

The "XTD" in the view name denotes the aggregated date-horizon logic, and "BY_RSRC" indicates the resource-level grain. This makes the view particularly suited to reporting and extract workloads that must reconcile committed, actual, and revenue amounts across multiple calendar granularities without reimplementing the PTD/QTD/YTD/ITD formulas in the calling application.

Underlying Base Objects

The documented referenced base objects for PJI_XTD_ACT_CMT_BY_RSRC_V are:

  • PA_PROJECTS_ALL (SYNONYM) — the Projects foundation table supplying project identifiers and project-level context.
  • PJI_FP_XBS_ACCUM_F (SYNONYM) — the Project Intelligence accumulation fact object that stores the raw cost, revenue, commitments, and quantity measures across reporting periods and resource breakdown structure elements.
  • PJI_ORG_EXTR_INFO (SYNONYM) — organizational extract information used to qualify and enrich the extract.
  • PJI_TIME_CAL_PERIOD_V (VIEW) — the time calendar period view that resolves period names, start dates, and end dates against the project or reporting calendar.
  • PJI_TIME_CAL_RPT_STRUCT_V (VIEW) — the reporting structure view that supplies the PTD, QTD, YTD, and ITD mask columns referenced repeatedly in the view text.

The view text joins these objects and applies masks such as PTD_MASK to the base measures, producing derived XTD columns. Because the cumulative logic is driven by PJI_TIME_CAL_RPT_STRUCT_V, the reported horizontal boundaries follow the calendar identified by CALENDAR_TYPE and CALENDAR_ID.

Key Columns

The view returns the dimensionality keys PROJECT_ID, TASK_ID, CALENDAR_TYPE, CALENDAR_ID, PERIOD_NAME, PERIOD_START_DATE, PERIOD_END_DATE, RBS_VERSION_ID, and RBS_ELEMENT_ID. Resource reporting is anchored on RBS_VERSION_ID and RBS_ELEMENT_ID, which identify the resource breakdown structure element for the reported row.

Measure columns are exposed for each time horizon using the _PTD suffix convention in the excerpt, with equivalent QTD, YTD, and ITD variants that follow the same naming pattern. The principal measures include:

Note that in the view text several quantity columns are aliased from BILL_LABOR_HRS or LABOR_HRS under the PTD mask, so BILLABLE_QUANTITY_PTD, BILLABLE_LABOR_HOURS_PTD, and BILL_LABOR_HRS_PTD resolve to the same underlying expression.

Common Use Cases and Queries

The most frequent use case is extracting period-aligned actuals and commitments for an external project system that imports data from Oracle. The user search term "qtd_mask" likely relates to the mask concept: the QTD horizon is derived by applying a QTD_MASK to the same base measures that the PTD_MASK uses. Analysts can confirm which horizon columns exist by querying the data dictionary, since the excerpt lists only the _PTD aliases explicitly.

A representative query filters to a single project and resource version and returns PTD, QTD, YTD, and ITD amounts per task and period:

  • SELECT project_id, task_id, period_name, rbs_version_id, rbs_element_id, revenue_ptd, burdened_cost_ptd, labor_hours_ptd FROM apps.pji_xtd_act_cmt_by_rsrc_v WHERE project_id = :p_project_id AND rbs_version_id = :p_rbs_version_id ORDER BY rbs_element_id, period_start_date;

A second common pattern aggregates commitments by period to support funding and burn-rate reporting:

  • SELECT project_id, period_name, SUM(po_committed_cost_ptd) po_cmt, SUM(pr_committed_cost_ptd) pr_cmt, SUM(sup_inv_committed_cost_ptd) sup_inv_cmt, SUM(cmt_burdened_cost_ptd) total_cmt FROM apps.pji_xtd_act_cmt_by_rsrc_v WHERE project_id = :p_project_id GROUP BY project_id, period_name ORDER BY period_name;

Because the view is built over PJI accumulation structures, queries benefit from filtering on PROJECT_ID and the calendar identifiers, and from restricting RBS_VERSION_ID to the active version, to avoid redundant rows across resource versions.