Search Results disable_mfar




Overview
Explore in AI Chat

Overview

PSA_IMPLEMENTATION is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It resides in the Public Sector / Grants Accounting (PSA) product family and forms part of the underlying infrastructure that supports the Multi-Fund Accounts Receivable (MFAR) feature set. Its principal business purpose is to record and expose implementation-level configuration state—specifically, whether Multi-Fund Accounts Receivable processing has been enabled for a given operating unit or implementation context. Rather than performing transactional accounting itself, the package acts as a control and status repository that other PSA components query before executing MFAR-specific logic. The dependency listing confirms that PSA_IMPLEMENTATION is referenced by PSA_AR_GL_POST_PKG, PSA_MF_CREATE_DISTRIBUTIONS, and by itself, and that it in turn references the STANDARD package under the SYS schema. This places the package near the base of the MFAR dependency hierarchy, where its configuration decisions propagate upward into receivables posting and distribution creation routines. The object is reported as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, and it is classified as OTHER rather than as a public or private API.

Key Procedures and Functions

Three documented procedures/functions are exposed by the package:

  • GET — Retrieves implementation status or configuration information for the caller. It is the read-side entry point that other PSA packages use to determine the current MFAR setting before branching into enablement-specific processing.
  • ENABLE_MFAR — Sets the implementation state so that Multi-Fund Accounts Receivable processing is active. Invoking this procedure flips the control flag consumed by downstream receivables and distribution packages.
  • DISABLE_MFAR — Reverses the action of ENABLE_MFAR, marking Multi-Fund Accounts Receivable as inactive so that standard (non-MFAR) processing paths are taken by dependent code.

No parameter lists are documented in the available metadata, so signatures should be confirmed directly against the package specification in the target environment before use.

Tables Accessed

The package reads and writes the table PSA_IMPLEMENTATION_ALL. The "_ALL" suffix indicates that the table is not org-striped at the database level; instead, it is expected to be filtered by operating unit or implementation context within the query logic. This table stores the implementation flags and related configuration rows that the GET, ENABLE_MFAR, and DISABLE_MFAR procedures manipulate. Access occurs through APPS synonyms, consistent with standard EBS coding practice.

Usage Notes

PSA_IMPLEMENTATION is not typically invoked directly by end users. It is called programmatically by other PSA packages such as PSA_AR_GL_POST_PKG and PSA_MF_CREATE_DISTRIBUTIONS, which query the implementation status before deciding whether to apply MFAR accounting distributions. Administrators normally toggle MFAR behavior through the corresponding setup forms or concurrent program parameters rather than by executing ENABLE_MFAR or DISABLE_MFAR manually. Custom code should treat the package as an internal dependency and, where possible, obtain MFAR status through supported forms or APIs instead of calling these procedures directly. Because the package is heavily referenced, any modification to its behavior carries downstream risk to receivables posting and distribution creation.