Results for “org_util_calc_method”

7 results




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

Overview

PJI_DIS_ORGJOB_V is a Discoverer view delivered within the PJI (Project Intelligence) module of Oracle E-Business Suite. PJI is identified in ETRM metadata as obsolete, and this object is documented as "Not implemented in this database," meaning it may not exist in every environment and should not be relied upon for new development. Its purpose is to expose organization-and-job-level utilization data in a denormalized, reporting-friendly form suited to Oracle Discoverer workbooks and ad hoc analysis of resource capacity, effort, and billing.

The view consolidates two logical families of measures. The first carries the "_A" suffix, representing actual (historical or committed) amounts such as CAPACITY_HRS, TOTAL_HRS_A, BILL_HRS_A, TRAINING_HRS_A, and UNASSIGNED_HRS_A. The second carries the "_S" suffix, representing summarized or scheduled/forecast figures such as CONF_HRS_S, PROV_HRS_S, and UNASSIGNED_HRS_S. Because the search term "unassigned_hrs_s" maps directly to a column in this view, users are typically investigating capacity that remains unallocated to productive work within a given period.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the view text itself reveals its construction. The primary source is the materialized view PJI_RM_JOB_F_MV, aliased FACT, which supplies all measure columns. Supporting dimensions include PJI_PMV_ORG_DIM_TMP and PJI_PMV_ORGZ_DIM_TMP (temporary organization dimensions), PJI_ORG_DENORM (the denormalized organization hierarchy), and HR_ALL_ORGANIZATION_UNITS_TL, joined twice as HOU1 and HOU2 to resolve organization and sub-organization names. A time dimension, truncated in the excerpt as PJI_TIM..., joins to provide period, quarter, and year attributes.

Because the fact source is a materialized view, the data available through PJI_DIS_ORGJOB_V depends on the refresh schedule and completeness of that MV. Organizations, jobs, and time periods are resolved through the dimension joins, so the grain of the view is effectively one row per organization, sub-organization, job, and time period.

Key Columns

Common Use Cases and Queries

Typical usage centers on identifying where capacity is not being consumed. A common query aggregates unassigned hours by organization and period:

  • SELECT organization_name, period_name, SUM(unassigned_hrs_s) unassigned FROM pji_dis_orgjob_v GROUP BY organization_name, period_name ORDER BY period_name;
  • SELECT job_id, period_name, capacity_hrs, unassigned_hrs_s, ROUND(unassigned_hrs_s / NULLIF(capacity_hrs,0) * 100, 2) unassigned_pct FROM pji_dis_orgjob_v WHERE period_name = :period;
  • SELECT organization_name, SUM(available_hrs_bkt1_s) b1, SUM(available_hrs_bkt2_s) b2 FROM pji_dis_orgjob_v GROUP BY organization_name;

Given the obsolete status and the "not implemented" note, any query should first confirm object existence and data currency, and new reporting requirements should be evaluated against supported alternatives.