Search Results reserve_baseline

Overview

PA_BUDGET_FUND_PKG is a PL/SQL package owned by the APPS schema in Oracle EBS Projects (PA). It encapsulates the core budgetary control and funds checking logic used by Oracle Projects to validate, reserve, and release project funds against budgeted amounts. The package forms part of the budgetary control infrastructure that enforces spending limits on projects and award-funded expenditures, ensuring that commitments, actuals, and encumbrances do not exceed authorized budget balances. It operates in close coordination with Oracle General Ledger budgetary control functionality, as evidenced by its references to GL budgetary control tables such as GL_BC_PACKETS and GL_JE_CATEGORIES, and with the Grants Accounting (IGC) module through the IGC_CC_INTERFACE table.

The package is classified as an "OTHER" API within the ETRM metadata for release 12.2.2, meaning it is an internal supporting package rather than a public, formally documented API. It is nonetheless a foundational dependency for numerous Projects packages, and is itself referenced by thirteen other packages, including PA_BUDGET_PUB, PA_BUDGET_PVT, PA_FUNDS_CONTROL_PKG, and PA_YEAR_END_ROLLOVER_PKG.

Key Procedures and Functions

The package exposes twelve documented procedures and functions. Their names indicate the following responsibilities:

• CHECK_OR_RESERVE_FUNDS — The central funds-checking routine; validates available budget and either confirms availability or places a reservation against project funds.
• GET_BUDGET_CTRL_OPTIONS — Retrieves budgetary control configuration options governing how funds checks are performed.
• UPD_BDGT_ACCT_BAL — Updates budget account balances, typically after funds consumption or release.
• UPD_BDGT_ACCT_BAL_NO_FCK — Performs the same balance update but without invoking a funds check, used in controlled circumstances.
• IS_BDGT_INTG_ENABLED — Returns whether budget integration is enabled for the relevant context.
• COPY_BUDGETARY_CONTROLS — Copies budgetary control settings between budget versions or project structures.
• RELEASE_BC_LOCK — Releases a budgetary control lock, allowing concurrent processing to proceed.
• IS_PA_BC_ENABLED — Indicates whether Projects budgetary control is active.
• IS_BUDGET_LOCKED — Determines whether the subject budget is locked against modification.
• CREATE_EVENTS_AND_FUNDSCHECK — Creates budgetary control events and executes a funds check in a single operation.
• GET_PREVIOUS_BVID — Retrieves the previous budget version identifier, supporting version comparison and rollover logic.
• UNBURDENED_CDL_EXISTS — Checks existence of unbundened cost distribution lines relevant to funds calculations.

Tables Accessed

Via APPS synonyms, the package reads and writes project budget structures including PA_BUDGET_VERSIONS, PA_BUDGET_LINES, PA_BUDGET_TYPES, PA_BUDGET_ACCT_LINES, PA_BUDGET_ENTRY_METHODS, and PA_BUDGETARY_CONTROL_OPTIONS. Balance and packet data are maintained through PA_BC_BALANCES and PA_BC_PACKETS. General Ledger integration relies on GL_BC_PACKETS, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_PERIOD_STATUSES, and GL_CODE_COMBINATIONS. Cost data flows from PA_COST_DISTRIBUTION_LINES_ALL, while grants-related activity is captured through IGC_CC_INTERFACE.

Usage Notes

Because PA_BUDGET_FUND_PKG is an internal package, it is not intended for direct invocation from custom code. It is called by Projects budget forms, by concurrent programs such as year-end rollover (PA_YEAR_END_ROLLOVER_PKG), and by the public budget APIs (PA_BUDGET_PUB, PA_BUDGET_PVT). Customizations requiring funds checking should call the supported public APIs, which delegate to this package. Customers upgrading between 12.1.1 and 12.2.2 should treat the package as a version-sensitive internal dependency, validating any extensions that reference it after patching.