Results for “org_util_calc_method”

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

Overview

APPS.PJI_DIS_ORG_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Enterprise Project and Portfolio Management (PPM) product family, specifically the Project Resource Management / utilization reporting area delivered by the PJI (Project Intelligence) schema. In EBS 12.1.1 and 12.2.2 the view exposes organization-level utilization and capacity facts for a given expenditure organization, period, quarter, and year. It is designed to surface pre-aggregated resource management metrics — assigned, billable, confirmed, provisional, training, unassigned, and reduced-capacity hours — together with the calculated utilization method codes that govern how those percentages are derived.

Because utilization calculations in EBS are governed by administration parameters (for example, the organization utilization calculation method and the resource utilization calculation method), the view is the natural join point between fact data and the configuration lookup that determines how utilization is computed. This makes it a common target for custom OTBI/BIP reporting, extracts to external HR or finance warehouses, and reconciliation diagnostics when displayed utilization figures appear inconsistent with capacity planning expectations.

Underlying Base Objects

The documented view text joins several base and materialized objects:

• PJI_RM_ORG_F_MV — the organization resource management fact materialized view supplying capacity, total, missing, billable, confirmed, provisional, training, unassigned, and reduce-capacity hours (both actuals and summarized variants), plus period type, calendar type, time ID, expenditure org ID, and utilization methods.
• PJI_PMV_ORG_DIM_TMP and PJI_PMV_ORGZ_DIM_TMP — temporary organization dimension staging objects used during concurrent processing.
• PJI_ORG_DENORM — a denormalized organization view/object providing organization and sub-organization identifiers and levels.
• HR_ALL_ORGANIZATION_UNITS_TL (aliased hou1 and hou2) — the HR organization translation table, supplying organization and sub-organization display names.
• PJI_TIME_MV — the time dimension materialized view providing period, quarter, and year attributes and date boundaries.
• PJI_ORG_EXTR_INFO — organization extraction information.
• Inline functions: a scalar subquery calling pji_utils.get_parameter('LAST_FM_EXTR_DATE') to return the last fact extraction date as a Julian number, and additional inline subqueries exposing func2.org_util_calc_method and func3.res_util_calc_method.

No referenced base tables are separately documented in the ETRM metadata, so the view should be treated as a dependent reporting layer over the PJI materialized views and HR organization tables above.

Key Columns

• CAPACITY_HRS, TOTAL_HRS_A, MISSING_HRS_A — capacity, total effort, and unaccounted (missing) hours for the actual period.
• BILL_HRS_A, BILL_WTD_ORG_HRS_A, BILL_WTD_RES_HRS_A — billable hours and weighted organization-level / resource-level billable hours.
• CONF_* and PROV_* families — confirmed and provisional hours (S-suffixed, summarized), including weighted and billable variants and over-commitment columns.
• TRAINING_HRS_A/S, UNASSIGNED_HRS_A/S, REDUCE_CAPACITY_HRS_A/S — non-productive and capacity-reduction categories.
• AVAILABLE_HRS_BKT1–BKT5_S and AVAILABLE_RES_COUNT_BKT1–BKT5_S — availability split across five time buckets, with corresponding available resource counts.
• TOTAL_RES_COUNT — total number of resources contributing to the organization.
• PERIOD_NAME, QUARTER_NAME, YEAR, PERIOD_START_DATE, PERIOD_END_DATE (plus quarter/year dates) — time dimension attributes.
• ORGANIZATION_ID, SUB_ORGANIZATION_ID, ORGANIZATION_NAME, SUB_ORGANIZATION_NAME, ORGANIZATION_LEVEL, SUB_ORGANIZATION_LEVEL, EXPENDITURE_ORG_ID — organization and reporting-entity context.
• org_util_calc_method, res_util_calc_method — the administration-controlled method codes that drive how organization and resource utilization are calculated; these directly answer the search term org_util_calc_method.

Common Use Cases and Queries

Typical scenarios include utilization dashboards, capacity-vs-billable reconciliation, and verification of the calculation method in effect for a given organization and period.

• Reporting organization utilization hours for a period:

  SELECT organization_name, period_name, capacity_hrs, bill_hrs_a, bill_wtd_org_hrs_a, org_util_calc_method FROM apps.pji_dis_org_v WHERE period_name = :p_period;

• Comparing confirmed versus provisional commitment:

  SELECT organization_id, period_name, conf_hrs_s, prov_hrs_s, conf_overcom_hrs_s, prov_overcom_hrs_s FROM apps.pji_dis_org_v ORDER BY period_name;

• Auditing which calculation method applies:

  SELECT organization_name, period_name, res_util_calc_method, org_util_calc_method FROM apps.pji_dis_org_v WHERE organization_id = :p_org_id;

• Extracting availability by bucket for workforce planning, selecting AVAILABLE_HRS_BKT1–BKT5_S and AVAILABLE_RES_COUNT_BKT1–BKT5_S.

Because the view depends on materialized views and extraction parameters, results reflect the last refresh of the PJI fact data; consumers should confirm the most recent LAST_FM_EXTR_DATE extraction before relying on figures for period close or audit purposes.