Search Results is_yr_end_rollover_running




Overview
Explore in AI Chat

Overview

PA_YEAR_END_ROLLOVER_PKG is an Oracle EBS Projects (PA) schema package owned by APPS that supports the year-end budget rollover process. In project-centric organizations, budgets are typically defined by fiscal year, and at the close of a fiscal year the balances, resource assignments, and budget lines associated with an expiring budget version must be carried forward into a new or working budget version for the subsequent year. This package automates that carry-forward logic, ensuring continuity of project budget data across fiscal boundaries without requiring manual re-entry of budget lines.

The package is classified as OTHER within the ETRM registry, indicating that it is not a publicly documented extension API but rather an internal utility invoked by Oracle-provided concurrent programs and by other PA packages. The metadata confirms it is a valid, non-invalidated object in the APPS schema, which means it participates in standard EBS patching and dependency tracking.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within the package. These are described below by purpose only; parameter signatures are not published in the metadata and should be confirmed against the deployed source.

  • YEAR_END_ROLLOVER — The primary driver routine that orchestrates the rollover of budget data from the ending fiscal year into the target year. It typically coordinates period selection, budget line creation, and status flag updates.
  • GET_PERIOD_DETAILS — Resolves the GL period information (period names, start and end dates, period statuses) required to identify the source and destination accounting periods for the rollover.
  • UPD_INS_BUDGET_LINE — Performs the insert or update of individual budget lines in the target budget version, forming the core data transformation step.
  • CREATE_WORKING_BUDGET — Creates the working budget version that will receive the rolled-forward amounts, establishing the destination container for the process.
  • YEAR_END_ROLLOVER_LOG — Writes diagnostic and progress messages, typically using FND_NEW_MESSAGES, so the concurrent request log and output file reflect the outcome of the rollover.
  • IS_YR_END_ROLLOVER_RUNNING — A validation function that determines whether a rollover is already in progress, preventing concurrent or duplicate executions.
  • UPD_YR_END_ROLLOVER_FLAG_TO_P — Sets the year-end rollover flag to the "processed" or pending state.
  • UPD_YR_END_ROLLOVER_FLAG_TO_E — Sets the year-end rollover flag to the "error" or completed state, allowing the process to signal a terminal status.

Tables Accessed

The package reads and writes several core PA and GL tables. Budget-related tables — PA_BUDGET_TYPES, PA_BUDGET_VERSIONS, PA_BUDGET_ENTRY_METHODS — define what is being rolled and how budgets are entered. PA_PROJECTS_ALL, PA_TASKS, PA_RESOURCE_ASSIGNMENTS, and PA_RESOURCE_LIST_MEMBERS supply the project, task, and resource context for each budget line. GL_PERIODS, GL_PERIOD_STATUSES, GL_SETS_OF_BOOKS, and GL_CODE_COMBINATIONS resolve the accounting period and chart-of-accounts information. PA_ORGANIZATIONS_V is used for organization validation, while PA_BC_BALANCES and PA_BC_COMMITMENTS hold the budgetary control balances and commitments that may also be rolled. FND_CONCURRENT_REQUESTS is queried to associate the run with its concurrent request ID, and FND_NEW_MESSAGES is used for logging. GL_ENCUMBRANCE_TYPES is referenced for encumbrance-related processing.

Usage Notes

PA_YEAR_END_ROLLOVER_PKG is referenced by PA_BUDGET_FUND_PKG and by itself, confirming that it is invoked programmatically rather than through a standalone form. In practice it is executed by an Oracle-provided concurrent program for year-end budget rollover, scheduled at fiscal year end by the project accounting administrator. Because the package references FND_CONCURRENT_REQUESTS and FND_NEW_MESSAGES, it is designed to run in a concurrent manager context and produce a request log. Custom code should not invoke this package directly; instead, use the supported concurrent program submission path. The IS_YR_END_ROLLOVER_RUNNING function provides the concurrency guard that prevents overlapping runs, and the flag-update routines (UPD_YR_END_ROLLOVER_FLAG_TO_P and _E) provide restartability and error visibility.