Search Results g_bal_type_c

Overview

PA_REP_UTIL_GLOB is a global utility package in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and holding VALID status in both Oracle EBS 12.1.1 and 12.2.2. The package functions as the central configuration and parameter repository for the Project Resource Utilization reporting framework. Its primary business purpose is to resolve the reporting options, period identifiers, amount type identifiers, and organizational parameters that drive the utilization reports consumed by project managers, resource managers, and financial analysts. Rather than embedding those values individually in each dependent object, the utilization reporting architecture consolidates them in PA_REP_UTIL_GLOB, which is referenced by thirty-eight other packages and numerous views.

The package embodies the period-type, balance-type, and organizational logic required to reconcile actual and forecast utilization figures across three distinct source ledgers: Oracle Projects (PA), Oracle General Ledger (GL), and Grants/other external integrations (GE). This three-way alignment is reflected in the naming of the dependent views, each of which exists in a _PA, _GL, or _GE variant.

Key Procedures and Functions

The documented interface contains fifty-five procedures and functions, grouped by purpose:

• Parameter retrieval: GET_UTIL_AC_PARM and GET_UTIL_FC_PARM return actual and forecast utilization parameters respectively; GET_UTIL_PRC_SWITCH returns processing switches that govern report behaviour.
• Period resolution: GET_EFFECTIVE_START_PERIOD_NUM identifies the starting period for a utilization run; SETU3PERIODTYPE, SETU3PERIODNAME, SETU3QTRORMONNUM, SETU3YEARNUM, and SETU3EFFPERIODNUM set and derive period classification values used throughout the reporting cycle.
• Period type by ledger: GETPERIODTYPEGL, GETPERIODTYPEPA, and GETPERIODTYPEGE return the period type appropriate to the General Ledger, Projects, and Grants sources respectively.
• Amount and balance classification: GETBALTYPEACTUALS and GETBALTYPEFORECAST return the balance type identifiers applied to actual and forecast data.
• Caching: INITIALIZE_UTIL_CACHE and INITIALIZE_AMT_TYPE_ID_CACHE populate session-level caches for utilization settings and amount type identifiers, avoiding repeated table lookups during high-volume reporting.
• Session and scope setters: SETU3PERSONID, SETU3GEENDDATE, and SETU1SHOWPRCTGBY establish the reporting person, end date for Grants data, and percentage display option.
• Scope resolution: GETOBJECTTYPEORG returns the object type and organization context for the current run.

Tables Accessed

PA_REP_UTIL_GLOB reads from GL_PERIODS and GL_SETS_OF_BOOKS to resolve accounting calendar periods and ledger context, and from GL_DATE_PERIOD_MAP for date-to-period conversion. PA_AMOUNT_TYPES_B supplies the amount type definitions used by the amount type cache and balance type functions. PA_IMPLEMENTATIONS provides implementation-level options that control utilization reporting behaviour. PA_UTILIZATION_OPTIONS holds the setup values returned by the parameter functions. PA_ORG_HIERARCHY_DENORM supplies the denormalized organization hierarchy used by GETOBJECTTYPEORG. All access is performed through APPS synonyms; the metadata does not indicate that the package writes to these tables.

Usage Notes

PA_REP_UTIL_GLOB is not an end-user API and is not invoked directly from Oracle Forms or concurrent program parameters. It is called internally by the Project Resource Utilization report suite, including PA_REPORT_UTIL, PA_REP_UTIL_SCREEN, PA_REP_UTIL_SETUP, PA_REP_UTILS_SUMM_PKG, and the summarization private packages PA_SUMMARIZE_ACTUAL_UTIL_PVT, PA_SUMMARIZE_FORECAST_UTIL_PVT, and PA_SUMMARIZE_ORG_ROLLUP_PVT. It additionally underpins the PA_REP_UTIL_*_V view family covering resource, organization, and organization-with-task reporting structures. Customizations that alter utilization reporting behaviour should treat these procedures as the supported tuning surface, while recognizing that direct modification of the package body is not supported and that any extension must account for the shared caching semantics established by INITIALIZE_UTIL_CACHE.