Search Results pa_bc_commitments_s

Overview

PA_SWEEPER is an Oracle Projects (PA) package body in the APPS schema that supports the commitments and budgetary control (BC) infrastructure of Oracle E-Business Suite. Its central responsibility is to reconcile and refresh actual and encumbrance balances that underpin funds checking against project budgets. Within the funds control model, commitments are captured in the PA_BC_COMMITMENTS tables and summarized into balance rows; the sweeper periodically reads those commitments, computes the appropriate balance movements, and writes updated balance records. In this sense the package acts as the bridge between transactional commitment detail and the aggregated balances used to determine whether sufficient funds exist before an expenditure is approved. It also participates in period-related processing, deriving the begin and end dates that govern which budgetary periods are in scope for a given sweep. The package depends on a broad set of Projects and common EBS utilities, including PA_FUNDS_CONTROL_UTILS, PA_FCK_UTIL, FND_API, FND_GLOBAL, FND_MSG_PUB, FND_PROFILE, and PA_DEBUG, indicating that it honors the standard API error-handling, multi-org, and debug conventions used throughout Oracle Projects.

Key Procedures and Functions

• GETBCBALSTARTDATE — Returns the starting date that defines the window of budgetary control balances to be processed during a sweep operation. It allows the sweeper to establish the lower bound of the period range over which commitment and balance data is evaluated.
• GETBCBALENDDATE — Returns the corresponding ending date for the budgetary control balance window. Together with GETBCBALSTARTDATE, it frames the period interval used when selecting and updating balances.
• UPDATE_ACT_ENC_BALANCE — Performs the core update of actual and encumbrance balance amounts. This procedure is the substantive workhorse of the package, applying computed commitment or expenditure movements to the stored balance records so that funds availability reflects current activity.

The ETRM metadata documents three procedures for this package. No parameter lists are asserted here; the descriptions above reflect documented purpose only.

Tables Accessed

The package reads and writes the core budgetary control tables. PA_BC_COMMITMENTS_ALL holds commitment header/detail information in a multi-org context, while PA_BC_COMMITMENTS_S is its security (org-striped) counterpart — directly relevant to the searched term pa_bc_commitments_s. PA_BC_BALANCES stores the budget balances that are updated by UPDATE_ACT_ENC_BALANCE. PA_BC_PACKETS and PA_BC_PACKETS_HIST represent the packet structures and their history used in funds checking and commitment processing. PA_BUDGET_VERSIONS and PA_BUDGET_ENTRY_METHODS provide the budget version and data-entry configuration that determine how balances are interpreted. PA_PERIODS_ALL and GL_PERIOD_STATUSES supply the accounting period calendar and open/closed period status used to bound processing (via GETBCBALSTARTDATE and GETBCBALENDDATE). PA_PROJECTS_ALL supplies project attributes, and XLA_EVENTS links the sweeper to subledger accounting events where commitments generate accounting entries. DUAL, PLITBLM, and V$SESSION are infrastructure references.

Usage Notes

PA_SWEEPER is not referenced by any database object according to the documentation, meaning it is not called from other stored PL/SQL units but is invoked as a top-level driver — typically from a concurrent program, a scheduled request, or via direct custom invocation. It is normally executed when commitment or actual/encumbrance balances must be re-swept, such as after commitment transactions post, at period boundaries, or during funds-control reconciliation. Because it operates on multi-org data through the _ALL and _S tables, callers must ensure the correct operating unit and security context are set. The presence of FND_MSG_PUB and PA_DEBUG indicates that errors are surfaced through the standard message stack, so callers should check the returned API status and review the message stack after execution. In Oracle EBS 12.1.1 and 12.2.2 the package remains VALID and is treated as a supporting utility rather than a published public API, so custom code should replicate the framework’s invocation context rather than extend the package directly.