Search Results populate_global_variables

Overview

APPS.PSA_XFR_TO_GL_PKG is a PL/SQL package in Oracle E-Business Suite 12.1.1 and 12.2.2 that transfers subledger activity from the Receivables-family accounting modules into the Oracle General Ledger interface. It is part of the "PSA" (Public Sector/Receivables accounting) transfer layer whose header, PSAMFG2S.pls, indicates a maintenance lineage reaching back to 2006. The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the APPS schema, a characteristic that requires careful grant management when invoked from custom code.

The business function is to select accounting distributions that have not yet reached General Ledger, derive the entered debit and credit amounts for each line, populate the GL_INTERFACE table through helper procedures such as Upd_seg_in_gl_interface, and optionally reverse entries that were previously transferred in error. Standard concurrent programs and standard Receivables transfer logic invoke these entry points to move transaction, receipt, adjustment, and miscellaneous receipt balances in a controlled, date-bounded fashion.

Key Procedures and Functions

The package exposes twenty-two documented program units. The most significant are the transfer procedures, each of which accepts an error buffer, a return code, a set of books identifier, a GL date range (including the p_gl_date_from parameter the user searched for), a posted date, and, in some cases, a summarization flag or parent request identifier:

• TRANSFER_TO_GL — the primary entry point, transferring receivable-related distributions within a defined GL date range and accepting additional parameters for parent request and period status control.
• MFAR_TRX_TO_GL, MFAR_RCPT_TO_GL, MFAR_ADJ_TO_GL — move multi-fund (MFAR) transactions, receipts, and adjustments respectively to General Ledger.
• MISC_RCT_TO_GL — transfers miscellaneous receipt activity.
• POPULATE_GLOBAL_VARIABLES — establishes session-level values referenced by the transfer routines.
• UPD_SEG_IN_GL_INTERFACE — updates accounting flexfield segments on rows already staged in the GL interface.
• REVERSE_CORE_ENTRIES_IF_ANY — reverses core entries previously passed to GL, returning an error message where applicable.
• CLEAR_REVERSAL_LINES — removes reversal rows from the interface.
• GET_ENTERED_DR_RCT, GET_ENTERED_CR_RCT, GET_ENTERED_DR_CRM, GET_ENTERED_CR_CRM, GET_ENTERED_DR_ADJ, GET_ENTERED_CR_ADJ, GET_ENTERED_DR_RCT_CLEAR, GET_ENTERED_CR_RCT_CLEAR — calculation functions returning the entered debit or credit amount for receipts, credit memos, adjustments, and cleared receipts, incorporating discount and unearned discount factors.
• GET_ADJ_CCID, GET_MISC_ARD_ID, GET_ADJ_ARD_ID — lookup functions resolving code combination identifiers and distribution identifiers.

Tables Accessed

The package reads and writes Receivables base and interface tables through APPS synonyms. Distribution and adjustment sources include AR_DISTRIBUTIONS, AR_DISTRIBUTIONS_ALL, AR_ADJUSTMENTS, and AR_ADJUSTMENTS_ALL. Receipt data is drawn from AR_CASH_RECEIPTS, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY, and AR_CASH_RECEIPT_HISTORY_ALL, while AR_RECEIVABLE_APPLICATIONS and AR_MISC_CASH_DISTRIBUTIONS / AR_MISC_CASH_DISTRIBUTIONS_ALL provide application and miscellaneous receipt detail. AR_SYSTEM_PARAMETERS supplies ledger and defaulting context. FND_APPLICATION, FND_NEW_MESSAGES, and FND_RESPONSIBILITY support application identification, message lookup, and responsibility context.

Usage Notes

The package is invoked from Oracle Receivables transfer and multi-fund accounting concurrent programs, from Receivables forms during posting operations, and from custom code that must move subledger balances to GL within a specified date range using p_gl_date_from and p_gl_date_to. Because the package runs under CURRENT_USER privileges, custom callers must ensure the invoking schema holds the necessary grants on the underlying AR tables. One other package references this package, indicating it is itself embedded in a wider transfer dependency chain. Modifications to GL interface segments should always follow the documented helper procedures rather than direct DML.