Search Results get_cash_defaults

Overview

APPS.AR_RECEIPT_LIB_PVT is the private implementation body of the Oracle Receivables receipt library. It supplies the core PL/SQL routines that the public Receipt API (AR_RECEIPT_API_PUB) and related Receivables interfaces rely on to construct, default, validate, and persist cash receipt information. The package is classified as PVT in the ETRM documentation, meaning it is an internal support package and is not intended as a directly callable public API. Its logic encapsulates the defaulting rules that determine how receipt attributes are populated from customer, transaction, bank, and receipt method sources when a user enters a receipt in the Receivables window or when receipt data is imported through the AutoLockbox, receipt migration, or Receipt API processes.

The header reflects a long-lived code line (ARXPRELB.pls, version 120.92.12020000.6, dated 2013), and the body contains extensive global cache declarations and record types, such as Site_Use_Cache_Rec_Type and Exchange_Rate_Cache, indicating a memory-caching design intended to reduce repeated lookups of customer sites, currencies, exchange rates, receipt methods, tax codes, and remittance references during high-volume receipt entry. This caching is particularly important for performance when processing large receipt batches.

Key Procedures and Functions

The documented procedures and functions divide into several functional groups that together implement receipt defaulting, ID derivation, and validation:

• GET_MISC_DEFAULTS and DEFAULT_MISC_IDS — Return default values for miscellaneous receipts and derive the associated miscellaneous receipt identifiers. These routines are the target of the search term "get_misc_defaults," which users typically encounter when troubleshooting defaulting behavior in miscellaneous receipt entry.
• GET_CASH_DEFAULTS and DEFAULT_CASH_IDS — Derive default cash receipt attributes and the primary cash receipt identifiers used when creating a new receipt.
• DEFAULT_CASH_RECEIPT_ID — Establishes the default cash receipt identifier for the receipt record.
• DEFAULT_APPLN_IDS and DEFAULT_APPLICATION_INFO — Default application-related identifiers and populate application context information for the receipt.
• DERIVE_UNAPP_IDS, DEFAULT_UNAPP_INFO, and DEFAULT_UNAPP_ON_AC_ACT_INFO — Derive and default unapplied receipt information, including on-account activity details.
• DEFAULT_REVERSE_INFO and DERIVE_REVERSE_IDS — Default reversal information and derive the identifiers needed to reverse a receipt.
• DEFAULT_ON_AC_APP_INFO and DERIVE_UNAPP_ON_AC_IDS — Default on-account application information and derive related unapplied identifiers.
• DERIVE_OTHERACCOUNT_IDS, DERIVE_ACTIVITY_UNAPP_IDS — Derive identifiers for other-account and activity-based unapplied transactions.
• GET_DOC_SEQ — Obtain the document sequence value required for receipt numbering.
• DERIVE_CUST_INFO_FROM_TRX — Derive customer information from the originating transaction, supporting receipt entry against a specific invoice.
• DEFAULT_DESC_FLEXFIELD and VALIDATE_DESC_FLEXFIELD — Default and validate the descriptive flexfield segments attached to the receipt.

Tables Accessed

The package reads and writes the principal Receivables and shared reference tables that supply defaulting and validation data. AR_CASH_RECEIPTS stores the receipt records; AR_PAYMENT_SCHEDULES holds installment and application information; AR_RECEIPT_CLASSES and AR_RECEIPT_METHODS define valid receipt classifications and payment methods, with AR_RECEIPT_METHOD_ACCOUNTS_ALL supplying method-to-account mappings. CE_BANK_ACCOUNTS provides bank account data, while HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, and HZ_PARTY_SITES (the TCA uptake objects, referenced in the Site_Use_Cache_Rec_Type record) supply customer, party, and site-use information. FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES provide currency and exchange rate definitions, and RA_CUSTOMER_TRX supplies transaction data for deriving customer information. AP_INVOICES and AP_CHECKS are referenced to support integration scenarios involving payments and refunds. The ETRM metadata records APPS synonyms for these objects, confirming standard operating unit and multi-org access through the APPS schema.

Usage Notes

AR_RECEIPT_LIB_PVT is invoked indirectly rather than directly. The Receivables Receipts window (ARXRWMAI), the AutoLockbox concurrent program, and the public AR_RECEIPT_API_PUB package all delegate defaulting and derivation logic to this package when a receipt is created, applied, unapplied, reversed, or updated. The ETRM metadata notes that it is referenced by 11 other packages, confirming its role as a foundational dependency within the Receivables receipt code family.

Because the package is marked PVT and is not documented as a public API, customizations and extensions should generally avoid calling it directly; supported integration should use AR_RECEIPT_API_PUB or the documented Receipt API instead. When diagnosing defaulting issues — such as why a miscellaneous receipt defaulted a particular receipt method, activity, or customer — the routines GET_MISC_DEFAULTS and DEFAULT_MISC_IDS are the relevant entry points in the cached defaulting flow. Performance tuning considerations include the package's 1,000-entry cache declarations, which persist for the duration of a session and can materially affect throughput during bulk receipt processing. The package is delivered identically in EBS 12.1.1 and 12.2.2, with the 12.2 online patching edition retaining the same ARXPRELB.pls lineage.