Search Results psa_ar_gl_interface




Overview
Explore in AI Chat

Overview

PSA_AR_GL_INTERFACE is an Oracle Application Object Library (AOL) PL/SQL package owned by the APPS schema. It belongs to the Public Sector Applications (PSA) product family — historically the Grants Accounting and Fund Accounting modules — where it supports the flow of receivables and cash activity between Oracle Receivables (AR) and Oracle General Ledger (GL). The package header carries the RCS identifier PSAARTCS.pls 120.6, indicating a mature, Release 12-level object maintained through the standard EBS file/patch cycle, and it is declared AUTHID CURRENT_USER so that runtime privileges are evaluated against the invoking schema rather than the APPS owner.

Its functional remit is narrow and specialized: it deals with "transaction codes" used to classify AR transactions for downstream GL posting under multi-fund accounting rules (MFAR). Because the package name combines the AR and GL interface naming conventions, it is best understood as a supporting utility within the PSA integration layer rather than a general-purpose AR or GL API.

Key Procedures and Functions

  • RESET_TRANSACTION_CODES — a procedure that resets or re-derives transaction code assignments for a given posting control context. It returns status through an error buffer and a return code, and accepts a posting control identifier (p_pstctrl_id) that scopes the operation to a specific posting run. It is the primary maintenance entry point of the package and would typically be used when transaction coding must be rebuilt after corrections, reversals, or re-runs.
  • IS_MFAR_TRANSACTION — a function returning a VARCHAR2 indicator that determines whether a document belongs to the MFAR (multi-fund accounting) transaction stream. It takes a document identifier and a set of books identifier, and is designed as a boolean-style test callable from SQL or PL/SQL to drive conditional logic in surrounding integration code.

No other subprograms are documented in the package specification; the specification exposes only these two entry points.

Tables Accessed

  • AR_CASH_RECEIPTS — read to identify receipt activity associated with the transaction or posting control being processed.
  • AR_RECEIVABLE_APPLICATIONS — read to resolve how receipts are applied against transactions, which is fundamental to fund-level classification.
  • AR_SYSTEM_PARAMETERS — read to obtain AR setup and defaulting values that influence transaction-code derivation and MFAR determination.
  • GL_INTERFACE — the GL open interface table; the package interacts with it as part of posting-line preparation or correction for accounting entries.
  • PSA_IMPLEMENTATION_ALL — the PSA implementation/options table, used to confirm whether the relevant PSA and MFAR features are enabled for the operating unit.

Usage Notes

PSA_AR_GL_INTERFACE is not exposed as a user-facing form or concurrent program in its own right. It is invoked programmatically — from other PSA packages, from AR/GL posting logic, or from custom extensions — when transaction codes must be refreshed or when code needs to test whether a document is MFAR-relevant. The ETRM metadata records that the package is referenced by one other package in the APPS schema, confirming it operates as a subordinate utility rather than a top-level driver. Because the header retains an AUTHID CURRENT_USER declaration and the $Header comment reflects an older file revision, implementations upgrading from 12.1.1 to 12.2.2 should treat the package as release-stable but product-version sensitive, and should always pass valid posting control and set of books identifiers when calling it.