Search Results cleanup_fp_rmap_fpr
Overview
APPS.PJI_FM_PLAN_MAINT_PVT is a private (PVT) PL/SQL package in the Oracle EBS Projects (PA/PJI) schema that supports the maintenance and staging of financial plan data used by Project Resource Management and Project Financial Management. Its core responsibility is the extraction and preparation of plan amounts, effort, and version data from source planning structures into the fact tables and denormalized structures that drive financial plan rollups, RBS-based reporting, and slicing. The package is part of the extract-and-rollup infrastructure that moves plan information from RBS (Resource Breakdown Structure) planning constructs into the financial plan fact and resource map tables.
The package is classified as PVT, meaning it is an internal API not intended for direct customer invocation. It is referenced by four other packages within the EBS codebase, indicating that it functions as a shared implementation layer for higher-level public APIs and concurrent programs that manage financial plan versions and plan amounts. The header identifies the file as PJIPP02S.pls and carries a version stamp from the 12.0.0 development line, consistent with its presence in both 12.1.1 and 12.2.2 releases.
Key Procedures and Functions
- VALIDATE_SET_PR_PARAMS — Validates input parameters relating to RBS version and plan type within a given context ('RBS' or 'PLANTYPE'), returning row counts and status to the caller.
- OBTAIN_RELEASE_LOCKS — Manages locking for extract operations, taking a context and lock mode to coordinate concurrency during plan maintenance.
- EXTRACT_FIN_PLAN_VERS_BULK — Bulk extraction of financial plan versions, optionally scoped to primary ('PRI') or secondary ('SEC') slices.
- EXTRACT_FIN_PLAN_VERSIONS — Extracts specific financial plan versions, accepting a nested-table collection of version IDs and a slice type.
- EXTRACT_PLAN_AMOUNTS_PRIRBS — Extracts plan amounts for the primary RBS.
- EXTRACT_PLAN_AMTS_PRIRBS_GLC12 — Extracts primary RBS plan amounts for the GLC12 (ledger/currency) processing path, with a pull-dangling flag controlling whether reversal computation is performed.
- EXTRACT_PLAN_AMTS_SECRBS_GLC12 — The secondary RBS counterpart of the preceding procedure, with the same pull-dangling flag semantics. This is the procedure most closely associated with the user's search term.
- EXTRACT_DANGL_REVERSAL — Handles extraction of dangling reversal entries produced when the pull-dangling flag is enabled.
- EXTRACT_ACTUALS — Extracts actual cost data for comparison against planned amounts.
- PROCESS_PENDING_PLAN_UPDATES — Applies queued or pending updates to plan data.
- RETRIEVE_OVERRIDDEN_WP_ETC — Retrieves workplan elements that carry overridden ETC (estimate-to-complete) values.
- EXTRACT_PLAN_ETC_PRIRBS — Extracts ETC values for the primary RBS.
- DELETE_PLAN_LINES — Removes plan lines as part of maintenance or refresh operations.
- CREATE_WBSRLP — Creates WBS-to-RLP (resource list/plan) relationships.
- ROLLUP_FPR_RBS and ROLLUP_FPR_RBS_T_SLICE — Perform rollups of financial plan resources by RBS, with a time-slice variant.
- INSERT_INTO_FP_FACT and MERGE_INTO_FP_FACT — Insert or merge plan rows into the financial plan fact table.
- CLEANUP_FP_RMAP_FPR and GET_FP_ROW_IDS — Clean up stale resource map rows and retrieve financial plan row identifiers.
Tables Accessed
The package reads and writes through APPS synonyms across planning, RBS, and parallel-processing tables. Planning and version data is sourced from PA_BUDGET_LINES, PA_BUDGET_VERSIONS, and PA_PROJ_ELEMENT_VERSIONS. RBS structures are held in PA_RBS_DENORM, PA_RBS_PRJ_ASSIGNMENTS, PA_RBS_TXN_ACCUM_MAP, and PA_RBS_VERSIONS_B. Project and resource context comes from PA_PROJECTS_ALL, PA_RESOURCE_ASSIGNMENTS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_FP_OPTIONS, and PA_FIN_PLAN_TYPES_B. Parallel processing is coordinated through AD_PARALLEL_UPDATES, AD_PARALLEL_UPDATE_UNITS, and AD_PARALLEL_WORKERS, enabling large plan extractions to be distributed across workers.
Usage Notes
As a PVT package, PJI_FM_PLAN_MAINT_PVT is not exposed to end users or directly callable from standard forms. It is invoked by the EBS financial plan extraction and rollup framework, including the concurrent programs that generate and refresh financial plan versions and their associated amounts. The GLC12 extraction procedures are typically reached through the plan version generation process, where the pull-dangling flag defaults to 'Y' so that reversal amounts are computed during extraction. Custom development should avoid direct use of this package; supported integration points are the public PA APIs. DBAs troubleshooting plan extraction issues may trace into this package's procedures to follow the flow from version extraction through amount staging, fact-table merge, and RBS rollup.
-
PACKAGE: APPS.PJI_FM_PLAN_MAINT_PVT
12.1.1
-
PACKAGE: APPS.PJI_FM_PLAN_MAINT_PVT
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_T_PVT dependencies on PJI_FP_RMAP_FPR_T
12.1.1
-
APPS.PJI_FM_PLAN_MAINT_PVT dependencies on PJI_FP_RMAP_FPR
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_T_PVT dependencies on PJI_FP_RMAP_FPR_T
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_PVT dependencies on PJI_FP_RMAP_FPR
12.1.1
-
PACKAGE BODY: APPS.PJI_FM_PLAN_MAINT_T_PVT
12.2.2
-
PACKAGE BODY: APPS.PJI_FM_PLAN_MAINT_T_PVT
12.1.1
-
PACKAGE BODY: APPS.PJI_FM_PLAN_MAINT_PVT
12.1.1
-
APPS.PJI_FM_PLAN_MAINT_PVT dependencies on FND_MSG_PUB
12.1.1
-
PACKAGE BODY: APPS.PJI_FM_PLAN_MAINT_PVT
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_T_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.PJI_FM_PLAN_MAINT_T_PVT dependencies on FND_MSG_PUB
12.1.1