Search Results pa_rep_util_summ0_tmp

Overview

PA_SUMMARIZE_FORECAST_UTIL_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle Projects forecast utilization reporting process. Its role is to stage summarized forecast utilization data into temporary reporting tables before the Project Utilization Report is formatted and displayed. The package operates on forecast balances, using the balance type PA_REP_UTIL_GLOB.G_BAL_TYPE_C.G_FORECAST_C, and derives its behavior from the shared runtime state held in the PA_REP_UTIL_GLOB package, including forecast start and end dates, utilization option details, implementation options, profile options, and period information.

The package is classified as a private API (PVT), meaning it is not intended for direct invocation by external code or custom extensions. It is consumed internally by the utilization reporting framework, and the ETRM metadata records it as referenced by one other package. Its design mirrors the broader Oracle Projects pattern of separating public reporting drivers from private data-staging and summarization logic.

Key Procedures and Functions

The package exposes eight documented procedures. The primary entry point is SUMMARIZE_FORECAST_UTIL, which orchestrates the summarization of forecast utilization data. Based on the utilization option flags retrieved from PA_REP_UTIL_GLOB.G_util_option_details — specifically pa_period_flag, gl_period_flag, and global_exp_period_flag — the driver determines which period-based or global-expenditure-based staging path to execute.

Six procedures perform the actual inserts into the temporary reporting tables, each corresponding to a distinct combination of period and expenditure basis:

• INSERT_FCST_INTO_TMP_PA — stages forecast data keyed to PA (Project Accounting) periods.
• INSERT_FCST_INTO_TMP_GL — stages forecast data keyed to GL periods.
• INSERT_FCST_INTO_TMP_GE — stages forecast data keyed to global expenditure periods.
• INSERT_FCST_INTO_TMP_PAGL — stages forecast data combining the PA and GL period bases.
• INSERT_FCST_INTO_TMP_PAGE — stages forecast data combining the PA and global expenditure bases.
• INSERT_FCST_INTO_TMP_GLGE — stages forecast data combining the GL and global expenditure bases.
• INSERT_FCST_INTO_TMP_PAGLGE — stages forecast data combining all three period bases (PA, GL, and global expenditure).

This combinatorial structure allows the same summarization logic to serve every supported utilization option configuration without duplicating the driver.

Tables Accessed

The package reads configuration and setup data and writes summarized results to reporting temporary tables. Among the documented tables:

• PA_REP_UTIL_SUMM0_TMP and PA_REP_UTIL_SUMM00_TMP — the temporary staging tables that receive the summarized forecast utilization rows. The user's search term pa_rep_util_summ0_tmp corresponds directly to this staging family, which is populated by this package and consumed downstream by the utilization report.
• PA_UTILIZATION_OPTIONS and PA_UTILIZATION_OPTIONS_ALL — supply the period-flag and forecast-through-date options that drive branching in SUMMARIZE_FORECAST_UTIL.
• PA_IMPLEMENTATIONS — provides organization ID and PA period type used for context and period resolution.
• GL_PERIODS — used to resolve GL and PA period set names and period types for date-to-period mapping.
• PA_FORECAST_ITEMS and PA_FORECAST_ITEM_DETAILS — the source of forecast item and forecast detail amounts that are summarized.
• PA_AMOUNT_TYPES_B — supplies amount type definitions used to interpret forecast amounts.
• PLITBLM — the standard Oracle Applications PL/SQL index-by table type used for in-memory processing arrays.

Usage Notes

This package is invoked indirectly through the Project Utilization Report flow rather than by direct user action. When a user submits the utilization report for forecast amounts, the reporting framework initializes PA_REP_UTIL_GLOB with the selected utilization options, implementation details, and profile values, then calls SUMMARIZE_FORECAST_UTIL to populate the temporary tables. The report then queries PA_REP_UTIL_SUMM0_TMP (or its variants) to produce output.

Because the package depends on global state established by PA_REP_UTIL_GLOB, it cannot be reliably called standalone from custom code. Developers troubleshooting utilization report performance or missing forecast rows should trace calls through the parent reporting package and inspect the PA_REP_UTIL_SUMM0_TMP staging table contents after submission. The header comment referencing PARRFCVB.pls and the noship designation confirm this is a standard shipped Oracle Projects file; it should not be modified, and any extensions should use supported public APIs or the utilization report's standard submission path instead.