Search Results year_end_rollover




Overview
Explore in AI Chat

Overview

PA_YEAR_END_ROLLOVER_PKG is the Oracle Projects (PA) PL/SQL package responsible for executing the Year End Budget Rollover process in Oracle E-Business Suite 12.1.1 and 12.2.2. At fiscal year end, baselined project budgets and their associated budgetary control balances must be carried forward so that commitments, encumbrances, and funds checking remain valid in the new budgetary period. This package performs that carry-forward, moving prior-year baseline amounts into a new working budget version, rebuilding budgetary control (BC) balances, and refreshing the budget summary account lines used by the account-level validation and funds check logic. The package is owned by APPS and is classified as OTHER in the ETRM repository. Its header comment (revision 120.13) indicates it has been a long-standing component of the projects budgeting infrastructure, and the source contains a debug flag driven by the PA_DEBUG_MODE profile option together with a LOG_MESSAGE helper that writes through pa_debug to the FND logging framework.

Key Procedures and Functions

Eight procedures and functions are documented for this package. Their responsibilities are as follows:

  • YEAR_END_ROLLOVER — The main driver procedure. It coordinates the entire rollover run, determining which budget versions are eligible, invoking the working budget creation and balance-building steps, and returning a completion status to the caller.
  • GET_PERIOD_DETAILS — Resolves the period name and start/end dates for the target rollover period, used to stamp the rolled-forward budget lines and balances with correct GL period context.
  • UPD_INS_BUDGET_LINE — Inserts or updates individual budget lines for the new working budget version as amounts are carried forward from the prior baselined version.
  • CREATE_WORKING_BUDGET — Creates the working budget version that receives the rolled amounts, and drives creation of the budget summary account (BC) balances prerequisite to account-level validation and funds check display.
  • YEAR_END_ROLLOVER_LOG — Writes informational and error messages generated during the rollover into the logging tables for later review.
  • IS_YR_END_ROLLOVER_RUNNING — A concurrency guard that detects whether a rollover is already in progress, preventing overlapping runs that would corrupt balances.
  • UPD_YR_END_ROLLOVER_FLAG_TO_P — Sets the year-end rollover flag to its "P" (processing) state at the start of a run.
  • UPD_YR_END_ROLLOVER_FLAG_TO_E — Sets the year-end rollover flag to its "E" (ended/error) state at completion, indicating the run has finished.

Tables Accessed

The package reads and writes project budgeting, commitment, and GL reference data through APPS synonyms. PA_BUDGET_VERSIONS stores the source and target budget versions and their rollover flags; PA_BC_BALANCES and PA_BC_COMMITMENTS hold the budgetary control balances and commitments rebuilt by the Create_bc_balances logic. PA_PROJECTS_ALL, PA_TASKS, PA_RESOURCE_ASSIGNMENTS, and PA_RESOURCE_LIST_MEMBERS supply the project, task, and resource structure against which budget lines are created. PA_BUDGET_TYPES and PA_BUDGET_ENTRY_METHODS define the budget type and entry method governing the rollover. GL tables — GL_CODE_COMBINATIONS, GL_PERIODS, GL_PERIOD_STATUSES, and GL_ENCUMBRANCE_TYPES — provide the accounting flexfield, period, and encumbrance context. FND_CONCURRENT_REQUESTS captures the concurrent request ID for the run, while FND_NEW_MESSAGES supports message lookup for validation and error reporting.

Usage Notes

This package is normally invoked from the Year End Budget Rollover concurrent program in Oracle Projects, which drives YEAR_END_ROLLOVER and reports results into the concurrent manager log. Budgetary control forms and funds check logic indirectly depend on the BC balances it builds, which is why the source explicitly reintroduces summary-account construction for the working budget so that account-level validation and funds check failures display correctly. Because IS_YR_END_ROLLOVER_RUNNING acts as a guard and the P/E flags bracket processing, runs should be scheduled in a single-threaded manner at fiscal year end and never interrupted mid-run. Custom code should call the packaged procedure rather than the underlying tables, and the PA_DEBUG_MODE profile option can be enabled for detailed pa_debug tracing during troubleshooting. Only one other package references it, so it is best treated as a scheduled, self-contained utility rather than a general-purpose API.