Search Results period_month




Overview
Explore in AI Chat

Overview

APPS.PA_REP_UTIL_ORGVW_GE_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that presents organization-level utilization and capacity data aggregated by global week. It is a Global Expenditure (GE) variant, meaning it exposes expenditure organization information aligned to the Global Week calendar rather than a project-specific or project expenditure organization calendar. The view is classified as an internal Oracle object; Oracle Corporation does not support direct application-data access through it except from standard Oracle Applications programs, as noted in the ETRM metadata. Consequently, it is best treated as a read-only reporting surface consumed by Oracle-delivered utilization reports, dashboards, and integration extracts rather than as a transactional interface.

The view is particularly relevant to users searching for period_month, which is one of its exposed columns. Alongside PERIOD_YEAR, the PERIOD_MONTH column lets consumers pivot global-week utilization data into calendar-month reporting buckets, a common requirement when reconciling weekly timecard or summary balance data against monthly management reporting cycles.

Underlying Base Objects

The view is defined over a set of documented dependencies that combine organizational, security, lookup, and summarized balance data. The referenced objects are HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) and HR_ORG_UNITS_NO_JOIN (VIEW), which supply organization identifiers and language-specific organization names; HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE), which supply global calendar derivation and organization security enforcement respectively; PA_LOOKUPS (VIEW), which resolves balance type names and codes; PA_OBJECTS (SYNONYM), which provides object-type context; and PA_SUMM_BALANCES (SYNONYM), which is the principal fact source for total hours and capacity. The package PA_REP_UTIL_GLOB supplies the summarized logic that reconciles summarized balances into the weekly organization rollup. The view is not referenced by any other database object, confirming its role as a terminal reporting layer. Because HR_SECURITY participates, rows returned are filtered by the organization security profile of the querying user.

Key Columns

  • EXPENDITURE_ORGANIZATION_ID (NUMBER) — internal identifier of the expenditure organization; the primary grouping key used in joins to HR organization tables.
  • EXPENDITURE_ORGANIZATION_NAME (VARCHAR2, 240) — language-specific organization name sourced from the TL table, honoring the session's language.
  • EXP_END_DATE (DATE) — the global week ending date, the time-dimension anchor for the row.
  • PERIOD_MONTH (NUMBER) — the calendar month to which the global week belongs; used to aggregate weekly data into monthly reporting periods.
  • PERIOD_YEAR (NUMBER) — the calendar year to which the global week belongs; pairs with PERIOD_MONTH for period filtering.
  • BALANCE_TYPE_NAME (VARCHAR2, 80) and BALANCE_TYPE_CODE (VARCHAR2, 30) — name and code of the summarized balance type, resolved through PA_LOOKUPS, distinguishing measures such as utilization or available capacity.
  • TOTAL_HOURS (NUMBER) — total hours recorded for the organization in the week.
  • CAPACITY (NUMBER) — organization capacity after accounting for reduced capacity, enabling utilization ratio calculations.

Common Use Cases and Queries

The view is typically queried to build weekly and monthly utilization reporting by expenditure organization. A typical query selects all columns as documented, filtered by year and month:

SELECT EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_NAME,
       EXP_END_DATE, PERIOD_MONTH, PERIOD_YEAR,
       BALANCE_TYPE_NAME, BALANCE_TYPE_CODE, TOTAL_HOURS, CAPACITY
FROM   APPS.PA_REP_UTIL_ORGVW_GE_V
WHERE  PERIOD_YEAR = :p_year
AND    PERIOD_MONTH = :p_month;

To compute a monthly utilization ratio, aggregate TOTAL_HOURS against CAPACITY per organization:

SELECT EXPENDITURE_ORGANIZATION_ID,
       SUM(TOTAL_HOURS) total_hours,
       SUM(CAPACITY)    capacity
FROM   APPS.PA_REP_UTIL_ORGVW_GE_V
WHERE  PERIOD_YEAR = :p_year
AND    PERIOD_MONTH = :p_month
GROUP  BY EXPENDITURE_ORGANIZATION_ID;

Because the object is Oracle-internal, custom code should consume it only for read-only reporting, and secure access should be granted through a custom APPS-privileged wrapper rather than direct schema grants.