Search Results get_sla_notupgraded_flag

Overview

The APPS.PSA_BC_XLA_PVT package is a private PL/SQL package within the Oracle E-Business Suite Public Sector Applications (PSA) module, specifically supporting Budgetary Control (BC) integration with the Subledger Accounting (SLA) engine. Its primary business function is to invoke the SLA accounting engine for budgetary control transactions generated by the BCPSA subsystem. The package acts as an internal bridge between budgetary control event creation and the generation of corresponding subledger accounting entries, ensuring that commitment, obligation, and reservation events are properly translated into accounting events within the SLA framework. As a private (PVT classification) package, it is not intended to be called directly by external applications or end users, but rather serves as an internal implementation component invoked by other PSA budgetary control packages.

Key Procedures and Functions

• BUDGETARY_CONTROL — This is the principal procedure of the package. It invokes the SLA accounting engine for BCPSA, with the documented pre-requisite that events must first be created in the PSA_BC_XLA_EVENTS_GT global temporary table. It accepts parameters including an initialization message list flag, a commit flag, an application identifier, a budgetary control mode (supporting values Check, Reserve, partial, and Force pass), an override flag, user and responsibility identifiers, and returns status indicators, message count and data, a status code, and a packet identifier. This procedure is central to driving the SLA processing pipeline for budgetary control transactions.
• GET_SLA_NOTUPGRADED_FLAG — A private function that returns a flag indicating whether SLA has not yet been upgraded for the relevant context. Per the documented source, it has no pre-requisites. This function is the object targeted by the search term "get_sla_notupgraded_flag," and it is used internally to determine upgrade state during budgetary control processing, allowing the package to branch between legacy and upgraded SLA processing paths.
• PSA_XLA_ERROR — A procedure involved in handling and recording accounting errors generated during SLA processing. It interacts with the various error-tracking tables listed below to capture and persist failure conditions encountered during the accounting event lifecycle.

Tables Accessed

The package reads and writes a broad set of tables, primarily through APPS synonyms:

• PSA_BC_XLA_EVENTS_GT, PSA_BC_ALLOC_GT, PSA_OPTION_DETAILS_GT, XLA_ACCT_PROG_DOCS_GT, XLA_ACCT_PROG_EVENTS_GT — global temporary tables used as staging and program-level data stores during accounting event and document processing.
• XLA_ACCOUNTING_ERRORS, PSA_XLA_ACCOUNTING_ERRORS, PSA_XLA_ACCOUNTING_ERRORS_S, PSA_BC_ACCOUNTING_ERRORS — error repositories used to capture and surface accounting failures during SLA invocation.
• AP_INVOICE_DISTRIBUTIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_REQ_DISTRIBUTIONS_ALL — distribution-level source tables that provide the transactional detail for budgetary control checks, reservations, and obligation events.
• GL_LEDGERS, FND_PROFILE_OPTION_VALUES, FND_NEW_MESSAGES — configuration and reference tables providing ledger context, profile option values, and message retrieval for user-facing errors.

Usage Notes

As a private package, PSA_BC_XLA_PVT is not directly invoked through EBS forms, concurrent programs, or external custom code. It is referenced by five other packages according to the ETRM metadata, meaning it is invoked internally by the PSA budgetary control processing stack. Administrators and developers encountering errors related to this package typically do so indirectly, when budgetary control transactions (such as funds checks, reservations, or purchase order encumbrances) fail during SLA accounting generation. The presence of the GET_SLA_NOTUPGRADED_FLAG function indicates the package supports both pre-upgrade and post-upgrade SLA processing paths, making it relevant during EBS upgrade troubleshooting. Diagnostic analysis should focus on the associated error tables, particularly XLA_ACCOUNTING_ERRORS and PSA_XLA_ACCOUNTING_ERRORS, to identify the root cause of SLA processing failures.