Search Results generate_distributions

Overview

PSA_MF_MISC_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports miscellaneous cash receipt processing within the Public Sector/Projects accounting and Receivables integration flow. Its primary responsibility is the creation and regeneration of accounting distributions for miscellaneous cash receipts. The package bridges Oracle Receivables (AR) cash receipt history with the PSA miscellaneous distribution staging structures, ensuring that receipt activity recorded in AR is correctly translated into GL-ready distribution lines. Because it operates on the intersection of receipt lifecycle events and distribution generation, it functions as a supporting engine for the Receivables-to-General-Ledger accounting pipeline rather than a user-facing interface. The package body carries a header identifying version 120.14, last modified in September 2006, and declares global variables for cash receipt, set of books, and run identifiers, along with standard FND logging level constants and a log path. The package is referenced by one other package, indicating it is an internal building block consumed by higher-level PSA processing routines.

Key Procedures and Functions

The package defines several functions. The primary documented callable is GENERATE_DISTRIBUTIONS, which drives the creation of distribution records for a given cash receipt. It accepts a cash receipt identifier, a set of books identifier, a run identifier, an output error message, an optional report-only flag, and the standard concurrent program error buffer and return code outputs. Its internal cursor c_crh_status reads the status and reversal relationships of cash receipt history rows, while cursor c_match_ccid joins PSA_MF_MISC_DIST_ALL against AR_MISC_CASH_DISTRIBUTIONS to reconcile miscellaneous distribution identifiers with code combinations.

Of particular relevance to the search term, CREATE_DISTRIBUTIONS is a function that links a cash receipt history record to a distribution action. It receives a mode parameter, a status value, a cash receipt history identifier, plus the standard error buffer, return code, and error message outputs, and returns a Boolean result. It is closely associated with the local helper MISC_RCT_CHANGED, which evaluates whether a miscellaneous receipt has changed and therefore warrants regeneration. Together these routines govern when distributions must be created versus preserved.

Tables Accessed

The package reads and writes several Receivables and PSA tables. AR_CASH_RECEIPTS and AR_CASH_RECEIPTS_ALL provide the header-level receipt attributes, including the cash receipt identifier and status. AR_CASH_RECEIPT_HISTORY supplies the lifecycle status transitions, reversal indicators, and prior-status references used to detect changes and drive distribution generation. AR_MISC_CASH_DISTRIBUTIONS stores the actual miscellaneous cash distribution lines and their code combinations, which the package matches against the PSA staging table. AR_RECEIPT_METHODS and AR_RECEIPT_METHOD_ACCOUNTS define the receipt method and its associated accounting flexfield defaults, ensuring distributions inherit the correct accounts. PSA_MF_MISC_DIST_ALL is the PSA staging table that holds candidate miscellaneous distributions keyed by reference values, and it is the principal target of the match and creation logic.

Usage Notes

PSA_MF_MISC_PKG is not typically invoked directly by end users. It is called from concurrent programs, higher-level PSA packages, and potentially from form-based logic that triggers distribution generation after a miscellaneous receipt is created, updated, or reversed. Because the principal routines follow the standard concurrent program signature — error buffer, return code, and output message parameters — they are well suited to submission as concurrent requests or as callable units from a request set. Callers pass the receipt identifier, set of books identifier, and run identifier, and may use the report-only mode to preview distributions without committing them. FND logging constants are declared so that the package can emit statement, procedure, event, exception, error, and unexpected level messages for diagnostics. Because the code dates from the 12.1.1/12.2.2-era codebase, customizations should treat it as an internal, version-coupled dependency and avoid modifying its behavior directly; instead, extensions should wrap or supersede it where supported.