Search Results create_events_and_fundscheck
Overview
PA_BUDGET_FUND_PKG is a PL/SQL package body in the Oracle EBS Projects (PA) module that performs budgetary control and funds checking against project budgets. Its primary purpose, as stated in the header, is to verify whether a funds check is required for a given budget version and, when required, to call the appropriate General Ledger (GL) and/or budgetary control (BC) funds check procedures for each account summary line. The package therefore acts as the bridge between project budget maintenance and the funds reservation/validation logic, ensuring that expenditures and commitments are evaluated against available project funding.
The package supports multiple calling modes — notably CHECK_FUNDS, CHECK_BASELINE, and RESERVE_BASELINE — and returns a dual budgetary control flag indicating whether dual budget control is active. In Release 12 it was extended to integrate with the new PA budgetary control architecture through PA_BC_PACKETS and PA_BC_BALANCES, handling packet status updates, draft budget version cleanup, and event-driven funds checking. The final header revision (120.33) dates from December 2007.
Key Procedures and Functions
- CHECK_OR_RESERVE_FUNDS — Core entry point that determines whether a funds check or a reserve operation is required and orchestrates calls to GL and budgetary control routines.
- GET_BUDGET_CTRL_OPTIONS — Retrieves the budgetary control configuration options applicable to the budget/project context.
- UPD_BDGT_ACCT_BAL — Updates budget account balances following a funds check operation.
- UPD_BDGT_ACCT_BAL_NO_FCK — Updates budget account balances without performing a funds check.
- IS_BDGT_INTG_ENABLED — Indicates whether budget integration is enabled.
- COPY_BUDGETARY_CONTROLS — Copies budgetary control settings, typically between budget versions or projects.
- RELEASE_BC_LOCK — Releases a budgetary control lock held on budget data.
- IS_PA_BC_ENABLED — Determines whether PA budgetary control is enabled for the applicable context.
- IS_BUDGET_LOCKED — Reports whether a budget is currently locked.
- CREATE_EVENTS_AND_FUNDSCHECK — Creates budgetary control events and performs the associated funds check.
- GET_PREVIOUS_BVID — Returns the previous budget version identifier, used in baseline comparison logic.
- UNBURDENED_CDL_EXISTS — Checks for the existence of unbundered cost distribution lines.
Private helpers include Update_bc_packets_fail, Update_bc_packets_pass, ADD_MESSAGE, LOG_MESSAGE, and DELETE_DRAFT_BC_PACKETS, which manage packet status ('R' reject, 'T' fatal, 'A' pass) and messaging.
Tables Accessed
The package reads and writes PA_BUDGET_VERSIONS, PA_BUDGET_ACCT_LINES, PA_BUDGET_LINES, PA_BUDGET_TYPES, and PA_BUDGET_ENTRY_METHODS to resolve budget definitions and account summary amounts. Budgetary control configuration is read from PA_BUDGETARY_CONTROL_OPTIONS. Balance and packet data are managed through PA_BC_BALANCES and PA_BC_PACKETS, with GL_BC_PACKETS used for GL-side packet integration. GL_PERIOD_STATUSES supports the closed-period validation cursor, while GL_CODE_COMBINATIONS, GL_JE_CATEGORIES, and GL_JE_SOURCES provide accounting and journal classification context. IGC_CC_INTERFACE and PA_COST_DISTRIBUTION_LINES_ALL support cost distribution and interface processing.
Usage Notes
The package is typically invoked from budget entry and baseline forms when a user checks, reserves, or validates funds. It is also callable from concurrent programs and custom PL/SQL that need to drive funds checking or budgetary control processing. Because it manipulates packet status and account balances, it should be executed within the standard PA budgetary control transaction flow rather than ad hoc. It is referenced by thirteen other packages, confirming its role as a shared funds-check utility. The autonomous packet-failure update procedure allows status recording to persist independently of the main transaction. Customizations should respect existing locks, period-close validations, and the IS_PA_BC_ENABLED gate before assuming PA budgetary control behavior.
-
PACKAGE BODY: APPS.PA_BUDGET_FUND_PKG
12.1.1
-
PACKAGE BODY: APPS.PA_BUDGET_FUND_PKG
12.2.2
-
PACKAGE: APPS.PA_BUDGET_FUND_PKG
12.2.2
-
PACKAGE: APPS.PA_BUDGET_FUND_PKG
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on PSA_BC_XLA_PUB
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on PSA_BC_XLA_PUB
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on PSA_BC_XLA_EVENTS_GT
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on PSA_BC_XLA_EVENTS_GT
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on PA_MOAC_UTILS
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on PA_MOAC_UTILS
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on XLA_EVENTS
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on XLA_EVENTS
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on PA_YEAR_END_ROLLOVER_PKG
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on PA_YEAR_END_ROLLOVER_PKG
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on DUAL
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on DUAL
12.1.1
-
APPS.PA_BUDGET_FUND_PKG dependencies on FND_API
12.2.2
-
APPS.PA_BUDGET_FUND_PKG dependencies on FND_API
12.1.1