Search Results populate_in_bulk




Overview
Explore in AI Chat

Overview

PA_FP_ROLLUP_TMP_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Project Billing / Project Foundation family of packages, as indicated by the PA_FP prefix (FP denotes "Foundation Project" style utilities used within the Project Accounting application). The package provides the programmatic logic that populates and maintains the temporary rollup structures used during project forecasting, budgeting, and resource planning operations.

The central purpose of the package is to stage aggregated project data into the temporary table PA_FP_ROLLUP_TMP and its companion sequence PA_FP_ROLLUP_TMP_S before that data is consumed by downstream reporting, budgeting, or budgeting-rollup processes. By working against temporary staging tables, the package isolates intermediate calculations from the permanent Project Accounting tables, reducing contention and allowing bulk processing of large project hierarchies.

The package is classified as OTHER in the ETRM repository, meaning it is not a documented public API with a published contract. It is therefore an internal implementation package, VALID in the APPS schema, and it is not referenced by any other database object, nor is it referenced by any other package.

Key Procedures and Functions

The ETRM metadata documents two procedures in this package body:

  • POPULATE_IN_BULK — Loads rollup data into the temporary table PA_FP_ROLLUP_TMP in a set-based bulk operation. This procedure is the primary entry point for loading large volumes of project rollup rows, typically flushing the temporary table and re-populating it from the budget and resource assignment sources in a single pass.
  • POPULATE_IN_MATRIX — Loads rollup data using a matrix-style access pattern, commonly used where the rollup must be populated across a two-dimensional arrangement of project and resource or period dimensions rather than a flat bulk set. This variant is intended for cases where the rollup structure is organized by intersecting dimensions.

Parameter lists are not exposed in the ETRM metadata and are deliberately not reproduced here.

Tables Accessed

The package accesses the following documented tables and objects through APPS synonyms:

  • PA_FP_ROLLUP_TMP — the primary temporary staging table into which the populate procedures write rolled-up project data.
  • PA_FP_ROLLUP_TMP_S — the companion sequence used to generate surrogate keys for rows inserted into PA_FP_ROLLUP_TMP.
  • PA_BUDGET_LINES — the source of budget line amounts and quantities that are aggregated during the rollup.
  • PA_RESOURCE_ASSIGNMENTS — supplies the resource assignment detail that is rolled up alongside budget information.
  • DUAL — the standard Oracle single-row utility, used for control queries and sequence lookups.
  • PLITBLM — an Oracle-supplied table used internally by PL/SQL for boolean and other internal datatype handling.

Additional package dependencies include FND_API, FND_MSG_PUB, FND_PROFILE, PA_DEBUG, PA_FP_CONSTANTS_PKG, and PA_FP_WEBADI_PKG, indicating that the package uses the standard EBS API error-handling and message stack, profile options, the Project Accounting debug facility, the FP constants package, and the WebADI integration package.

Usage Notes

Because the package is classified as OTHER and is not referenced by any other database object, it is not intended for direct invocation by customer extensions. It is normally called internally by Project Accounting rollup and forecasting flows, including those driven from the Project Budgeting and Project Forecasting forms and their associated concurrent programs. The use of FND_API, FND_MSG_PUB, and PA_DEBUG indicates that errors are reported through the standard EBS message stack and that diagnostic output can be enabled through the Project Accounting debug profile. Customers should treat PA_FP_ROLLUP_TMP_PKG as an internal implementation detail of the Project Foundation rollup process and should not build custom code against it; any required extension should instead target the documented public APIs of the Project Accounting product family.