Search Results psa_mf_error_log_s

Overview

PSA_MFAR_RECEIPTS is an Oracle EBS PL/SQL package body owned by the APPS schema, classified as OTHER within the ETRM repository. It forms part of the Public Sector Applications (PSA) "MFAR" (Modified Accrual / Fund Accounting for Receipts) subsystem, which governs the distribution and reconciliation of cash receipt activity against accounts receivable and customer transaction data. Its core business purpose is to construct, adjust, and purge the accounting distribution records that link Oracle Receivables receipt activity to PSA fund-accounting balances.

The package is documented as VALID and is referenced by two other packages, indicating it is a supporting component called by higher-level MFAR processing rather than a top-level entry point. Its design integrates tightly with the PSA_MFAR_RECEIPTS and PSA_MFAR_RECEIPTS_COVER_PKG packages, and it draws utility services from PSA_MFAR_UTILS, PSA_UTILS, and FND_LOG/FND_MESSAGE for error handling and messaging. The dependency graph confirms direct dependencies on core Receivables and customer transaction tables, alongside PSA-specific distribution and error-logging objects such as PSA_MF_ERROR_LOG_S, PSA_MF_RCT_DIST_ALL, and PSA_MF_TRX_DIST_ALL.

Key Procedures and Functions

ETRM documents four procedures or functions within this package body:

• CREATE_DISTRIBUTIONS — The principal routine, responsible for generating the distribution records that represent receipt and transaction accounting. It derives distribution lines by reconciling receipt data against receivable applications and customer transaction lines, then persists them to the PSA_MF_RCT_DIST_ALL and PSA_MF_TRX_DIST_ALL tables.
• INCLUDE_MANUAL_LINE — Handles manual distribution lines entered by users, integrating user-specified accounting into the generated distribution set so that manual adjustments are treated consistently with system-generated lines.
• INCLUDE_IMPORTED_LINE — Incorporates imported distribution lines originating from external or batch sources, ensuring imported activity is merged into the MFAR receipt distributions processed by the package.
• PURGE_ORPHAN_DISTRIBUTIONS — Removes distribution records that no longer have a corresponding valid parent receipt or transaction, maintaining referential integrity across the MFAR distribution tables.

No parameter lists are documented in the available metadata; only the purposes above should be assumed.

Tables Accessed

The package reads and writes a defined set of Receivables and PSA tables through APPS synonyms. Receipt-side tables include AR_CASH_RECEIPTS_ALL (receipt header data), AR_CASH_RECEIPT_HISTORY_ALL (receipt status history), AR_RECEIVABLE_APPLICATIONS and AR_RECEIVABLE_APPLICATIONS_ALL (application of receipts to transactions), and AR_SYSTEM_PARAMETERS (Receivables setup defaults). Transaction-side tables include RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST, and RA_CUST_TRX_LINE_GL_DIST_ALL, which supply invoice and line-level accounting distributions. RA_TERMS_B provides payment term definitions, and GL_SETS_OF_BOOKS supplies ledger context for distribution accounting. PSA-specific tables include PSA_MF_RCT_DIST_ALL and PSA_MF_TRX_DIST_ALL (target distribution stores) and PSA_MF_ERROR_LOG_S (sequence-backed error logging). PSA_MF_BALANCES_VIEW supplies fund-accounting balance data, and FND_CURRENCY, ARP_GLOBAL, and OE_PROFILE provide currency and profile option context.

Usage Notes

PSA_MFAR_RECEIPTS is not intended for direct end-user invocation. It is typically called from PSA_MFAR_RECEIPTS and PSA_MFAR_RECEIPTS_COVER_PKG during receipt processing or reconciliation workflows, and may be exposed through concurrent programs or Public Sector forms that generate and maintain MFAR distributions. Because the package is referenced by two other database objects and references no external objects beyond its documented dependencies, customizations should call it only through those higher-level entry points. Error conditions are expected to be written to PSA_MF_ERROR_LOG_S and surfaced via FND_LOG and FND_MESSAGE, so consumers should inspect the error log after batch execution.