Search Results pa_ppr_smart_slice_pvt




Overview
Explore in AI Chat

Overview

PA_PPR_SMART_SLICE_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that supports the Smart Slice functionality within Oracle Project Portfolio Analysis (PPR). Smart Slices are generated database slices that persist a pre-computed, queryable projection of project financial plan data so that reporting, analysis, and downstream calculation processes can retrieve summarized plan figures efficiently rather than recomputing them from base plan and transaction tables on demand.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoker rather than the definer. This is a deliberate security posture for a private (_PVT) package: it is intended to be called only from within the APPS schema by other PL/SQL constructs, and not to be granted directly to end users or external schemas. The naming convention (_PVT) and the ETRM API classification of "PVT" confirm that this is an internal helper package rather than a published public API.

Key Procedures and Functions

The package header exposes two documented procedures.

  • MAINTAIN_SMART_SLICE — The core worker procedure. Its purpose is to create, refresh, or reconcile the smart slice records for a given planning context. The parameter set identifies the version and element scope of the operation (resource breakdown structure version, planning version, WBS element, RBS element, WBS version), the record type, the calendar type, and flags such as the program rollup flag. It also exposes a commit flag, an optional fact slice identifier, and the standard concurrent-style OUT parameters x_msg_count, x_msg_data, and x_return_status for error and status communication to the calling process. The use of collection parameters (table-of-number types) indicates that the procedure can process multiple plan versions in a single invocation.
  • PPR_LOG — A diagnostic logging utility that writes messages at a specified log level. It is used throughout the package for instrumentation and troubleshooting, and its behavior is governed by package globals such as G_LOG_LEVEL, G_DEBUG_MODE, and G_PACKAGE_NAME.

Tables Accessed

The package references the following tables through APPS synonyms:

  • PA_BUDGET_VERSIONS — Budget and planning version definitions, used to resolve the version context for the slice.
  • PA_PROJECTS_ALL — Project master records, used to identify the projects within scope.
  • PA_PROJ_ELEMENT_VERSIONS — Versioned project structure elements, providing the WBS/RBS element hierarchy data on which slices are built.
  • PA_PROJ_FP_OPTIONS — Financial plan options controlling how plan amounts are calculated and displayed.
  • PLITBLM — The standard Oracle Projects temporary numeric table used for processing collections of IDs in bulk operations.

Usage Notes

Because this is a private package with no dependent public packages recorded, it is not intended as an integration point for custom code. It is typically invoked indirectly from Oracle Projects forms and concurrent programs that maintain Project Portfolio Analysis smart slices — for example, when a user regenerates or refreshes a smart slice from the PPR user interface, or when a scheduled concurrent request rebuilds slice data for one or more plan versions. In 12.1.1 and 12.2.2 the package is shipped as part of the standard APPS codebase, and its behavior is driven by the passed version, element, and record type parameters together with the commit and fact slice flags. Customizations should avoid calling the package directly; where slice maintenance must be triggered programmatically, the supported public APIs and concurrent programs should be used instead.