Search Results derive_perf_rbs_parameters

Overview

APPS.PJI_REP_UTIL is a utility package within the Oracle E-Business Suite Projects Intelligence (PJI) reporting schema, the analytic foundation used by Project Management and Project Financial Management for cross-business reporting and OLAP-style aggregation. Its documented API classification is UTIL, confirming that it serves as a shared library of common services rather than a business transaction API. The package centralizes the derivation of reporting context — default periods, calendars, currencies, plan versions, resource breakdown structures, and project attributes — that the PJI reporting stack requires before executing fact-based reports. It also underpins denormalized structures such as PJI_XBS_DENORM and the OLAP WBS hierarchy caches that accelerate performance of the Projects reporting views and dashboards. In Oracle EBS 12.1.1 and 12.2.2, the package remains a core component of the PJI reporting framework, referenced by ten other packages across measure, rollup, drilldown, and default-parameter processing.

Key Procedures and Functions

The package exposes 71 documented procedures and functions, of which the reported representative subset illustrates its responsibilities across four functional areas:

• Denormalization management: OLAP_DENORM_CREATE builds the denormalized structures that support reporting queries against project and task hierarchies.
• Diagnostics and eventing: ADD_MESSAGE provides standardized error/message handling; LOG_STRUCT_CHANGE_EVENT records structural changes for reporting lineage.
• Cache population: POPULATE_WBS_HIERARCHY_CACHE and POPULATE_WP_PLAN_VERS_CACHE prebuild the WBS and workplan plan-version hierarchies used by reports to avoid runtime recursion.
• Rollup and derivation logic: DERIVE_PRG_ROLLUP_FLAG, DERIVE_PERF_PRG_ROLLUP_FLAG, DERIVE_FACTORBY, DERIVE_PROJECT_ATTRIBUTES, GET_VERSION_TYPE, and DERIVE_DEFAULT_PLAN_VERSIONS establish progress, performance, factor, and version semantics.
• Default context resolution: GET_DEFAULT_PERIOD_NAME, GET_DEFAULT_CALENDAR_TYPE, DERIVE_DEFAULT_CALENDAR_INFO, DERIVE_DEFAULT_CURRENCY_INFO, and DERIVE_PERF_CURRENCY_INFO resolve period and currency defaults for reporting parameters.
• Baseline and cost retrieval: GET_TASK_BASELINE_COST and GET_TASK_LATEST_PUBLISHED_COST return task-level cost values for comparative reporting.
• RBS parameters: DERIVE_DEFAULT_RBS_PARAMETERS and DERIVE_PERF_RBS_PARAMETERS produce resource breakdown structure parameters for standard and performance reporting modes.

Tables Accessed

The package reads and writes through APPS synonyms. Configuration and definition sources include PA_PROJECTS_ALL (project master), PA_STRUCTURE_TYPES (work breakdown structures), PA_PROJ_FP_OPTIONS (forecast/plan options), PA_PROJ_ELEMENT_VERSIONS (structure versioning), PA_BUDGET_VERSIONS, PA_PERIODS_ALL, GL_PERIOD_STATUSES (calendar and period state), PA_IMPLEMENTATIONS and PA_IMPLEMENTATIONS_ALL (multi-organization/implementation ownership), PA_OBJECT_RELATIONSHIPS, and PA_PERIODS_ALL. Reporting and denormalized structures include PJI_FP_XBS_ACCUM_F (forecast accumulations), PJI_XBS_DENORM, PA_OLAP_WBS_HEADER, and PA_OLAP_XBS_DENORM_TMP. PA_PJI_PROJ_EVENTS_LOG supports structural change event tracking. These accesses reflect the package's dual role: reading setup and transactional metadata, and writing/refreshing denormalized reporting artifacts.

Usage Notes

PJI_REP_UTIL is generally not called directly by end users. It is invoked indirectly by concurrent reporting programs, the Projects reporting UI, and the other PJI packages listed as callers, including PA_RP_UTIL, PJI_FM_XBS_ACCUM_MAINT, PJI_MAP_ROWSET_MEASURE, PJI_PJP_SUM_ROLLUP, PJI_REP_DFLT_DRILLDOWN_TXN, PJI_REP_MEASURE_UTIL, PJI_REP_PRF_DFLT_PARAMS, PJI_REP_VP_UTILS, PJI_REP_WP_DFLT_PARAMS, and PJI_VP_REP_DFLT_PARAMS. Typical invocation occurs during execution of PJI reports, dashboard rendering, and maintenance jobs that rebuild denormalized and cache tables. Because the package touches denormalized structures, it is best invoked within scheduled maintenance windows or as part of the standard PJI reporting cycle rather than from ad hoc custom code. Any customization referencing this package should follow the same locking and commit conventions used by the standard PJI reporting framework, and version-specific behavior differences between 12.1.1 and 12.2.2 should be validated against the installed patch level before reuse.