Search Results psa_funds_checker_pkg




Overview
Explore in AI Chat

Overview

PSA_FUNDS_CHECKER_PKG is the online funds checker for Oracle Public Sector Advanced Features within Oracle E-Business Suite. It enforces budgetary control by providing a uniform interface through which subledgers and General Ledger can check and reserve funds. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than its owner, which is significant for a budgetary control module where ledger and responsibility security must be respected.

The package header carries the source control identifier $Header: psafbcfs.pls 120.25.12020000.1 2012/06/26 13:06:57 appldev ship $, and is registered in ETRM as product PSA (Public Sector Advanced Features), lifecycle active, compatibility S, with the business entity category GL_BC_PACKETS. The package is referenced by 14 other packages, confirming its role as a shared budgetary control service rather than an isolated utility.

Key Procedures and Functions

ETRM documents 13 procedures and functions. The following are the principal entries directly relevant to funds checking and the sync_xla_errors search term:

  • GLXFCK — The main Funds Check API for any process requiring funds check and/or funds reservation. It returns TRUE on success and FALSE otherwise, accepting parameters for ledger, packet, mode, override, concurrent flag, user and responsibility identifiers for override, and a calling-program flag identifying whether Funds Checker was invoked from the SLA validation routine. It returns a funds check return code for the packet in process.
  • GL_CONFIRM_OVERRIDE — Confirms an override action initiated when funds reservation fails, aligning with the p_override and user/responsibility parameters on GLXFCK.
  • GLXFPP — Related funds check processing routine operating in the same budgetary control family as GLXFCK.
  • GLXFMA — Additional funds check routine documented within the package.
  • GLSIBC and GLSFBC — Budgetary control initialisation and finalisation counterparts, bracketing the funds check cycle.
  • BUDGETARY_CONTROL — The general budgetary control entry point.
  • BC_OPTIMIZER and BC_PURGE_HIST — Budgetary control maintenance routines, the latter purging historical budgetary control data.
  • POPULATE_GROUP_ID — Populates grouping identifiers used to associate related funds check records.
  • GET_DEBUG — Returns the debug state used for diagnostic logging within the package.
  • SYNC_XLA_ERRORS — Synchronises Subledger Accounting error information. This is the routine matched by the user's search term. It works with the PSA_XLA_*_LOGS tables to reconcile subledger accounting errors against the funds checker's own logging structures.

Tables Accessed

The package accesses the following via APPS synonyms:

Usage Notes

PSA_FUNDS_CHECKER_PKG is invoked online through Public Sector Advanced Features forms and from concurrent programs, and it is called programmatically by subledgers and General Ledger when an online funds check or reservation is required. The p_conc_flag parameter distinguishes concurrent invocation from online invocation, and p_calling_prog_flag identifies calls originating from the SLA validation routine.

Because GLXFCK is a public, active API with compatibility S, custom code may call it to enforce budgetary control against a GL_BC_PACKETS packet. Overrides require appropriate user and responsibility context, and GL_CONFIRM_OVERRIDE should be used to finalise an override when funds reservation fails. SYNC_XLA_ERRORS is relevant where Subledger Accounting error records require reconciliation with the PSA logging tables; it should be invoked as part of error resolution rather than routine transaction processing. Debug behaviour can be inspected through GET_DEBUG.