Search Results create_fp_ent_rollup

Overview

PJI_PJP_PRG_PERF_ALL is an Oracle Projects (PJI) performance processing package owned by the APPS schema. It supports the Oracle E-Business Suite Project Performance and Funds Planning data model by orchestrating the rollup, proration, aggregation, and fact-loading of plan amounts and transactional balances into reporting fact tables. In the context of Oracle EBS 12.1.1 and 12.2.2, the package serves as the backend engine that transforms raw project budget, resource assignment, and transaction accumulation data into summarized performance facts used by Project Performance reporting, Funds Check, and related analytical dashboards.

The package header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the owner, which allows it to run under the security context of the calling session. The $Header comment indicates the released source version is 120.0.12020000.2 (dated 2012/07/18), consistent with the 12.1.3/12.2.x code line.

Key Procedures and Functions

The package exposes 28 documented procedures and functions. In terms of the searched term insert_into_fp_fact, the relevant procedure is:

• INSERT_INTO_FP_FACT — Inserts computed plan performance data into the Funds Planning (FP) fact table. It is one of the core data-loading steps that materialize rollup results into the reporting fact store.
• MERGE_INTO_FP_FACTS — Performs a merge (insert/update) of fact rows, complementing INSERT_INTO_FP_FACT for incremental loading.

Supporting rollup procedures include:

• CREATE_FP_ENT_ROLLUP — Creates the enterprise-level Funds Planning rollup.
• CREATE_FP_PA_PRI_ROLLUP — Creates the Projects/PA primary rollup.
• CREATE_FP_GL_PRI_ROLLUP — Creates the General Ledger primary rollup.
• CREATE_FP_ALL_T_PRI_ROLLUP — Creates the consolidated "all types" primary rollup, parameterized by calendar type (default 'G').

Proration procedures distribute plan amounts across periods: PRORATE_TO_ENT_PG_PJP1_D, PRORATE_TO_ENT_N_PJP1_D, PRORATE_TO_PAGL_PGE_PJP1_D, PRORATE_TO_PAGL_N_PJP1_D, and PRORATE_TO_ENT. Extraction and header maintenance are handled by EXTRACT_PLAN_AMTS_PRIRBS_GLC12, EXTRACT_DANGL_REVERSAL, POPULATE_RBS_HDR, UPDATE_WBS_HDR, and UPDATE_WBS_HDR_1. Additional procedures include GET_GLOBAL_EXCHANGE_RATES, REMAP_RBS_TXN_ACCUM_HDRS, UPDATE_BATCH_CONC_STATUS, AGGREGATE_FP_CUST_SLICES, ROLLUP_FPR_WBS, PURGE_PLAN_DATA, EXECUTE_ROLLUP_FPR_WBS, EXECUTE_AGGREGATE_PLAN_DATA, and GATHER_TEMP_STATS. Control-flow helpers include the function NEED_TO_RUN_STEP, and procedures REGISTER_STEP_COMPLETION and WRAPUP_PROCESS.

Tables Accessed

The package reads and writes several APPS-synonym tables central to Projects and Funds Planning:

• PA_BUDGET_LINES, PA_BUDGET_VERSIONS, PA_FIN_PLAN_TYPES_B — source plan and budget definitions.
• PA_PROJECTS_ALL, PA_PROJ_FP_OPTIONS, PA_PROJ_WORKPLAN_ATTR, PA_PROJ_ELEM_VER_STRUCTURE, PA_XBS_DENORM — project, workplan, and element structure metadata.
• PA_RESOURCE_ASSIGNMENTS, PA_RBS_PRJ_ASSIGNMENTS, PA_RBS_VERSIONS_B — resource breakdown structure and assignments.
• PJI_AC_AGGR_PJP1 — the transaction accumulation table used during aggregation.
• FND_CURRENCIES, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES — currency and profile option lookups that drive proration, exchange rates, and processing behavior.

Usage Notes

PJI_PJP_PRG_PERF_ALL is typically invoked from concurrent programs within the Oracle Projects performance processing flow. It is referenced by six other packages, indicating it functions as a shared processing layer rather than an entry-point API. The step-control procedures (NEED_TO_RUN_STEP, REGISTER_STEP_COMPLETION, WRAPUP_PROCESS) and UPDATE_BATCH_CONC_STATUS suggest it runs inside a multi-step batch pipeline where each phase checks completion status before executing. Custom extensions should generally not call the individual data-movement procedures directly; instead they should invoke the orchestrating procedures such as EXECUTE_ROLLUP_FPR_WBS and EXECUTE_AGGREGATE_PLAN_DATA, which manage worker IDs, partial mode, and upgrade flags. The INSERT_INTO_FP_FACT procedure, as the user's search term, is an internal step of this pipeline and should be treated as internal API in 12.1.1/12.2.2 releases.