Search Results derive_reverse_ids

Overview

APPS.AR_RECEIPT_LIB_PVT is an internal (private) PL/SQL library package in the Oracle E-Business Suite Receivables module. It supplies the shared defaulting, derivation, and validation logic that underpins the public Receivables receipt APIs, most notably AR_RECEIPT_API_PUB, which is the supported entry point most commonly associated with the search term "AR_RECEIPT_API_PUB." Where AR_RECEIPT_API_PUB exposes the callable interface for creating, applying, unapplying, reversing, and managing cash receipts, AR_RECEIPT_LIB_PVT performs the supporting computational work: resolving default values, deriving internal identifiers for applications and unapplications, and constructing the descriptive flexfield data that the public API ultimately persists.

The package is classified as a PVT (private) API, meaning Oracle does not document it as a supported integration interface. It resides in the APPS schema and carries a VALID status. It is referenced by eleven other packages and itself references AR_RECEIPT_API_PUB, indicating a cooperating relationship within the Receivables receipt-processing stack rather than a standalone utility.

Key Procedures and Functions

The documented 29 procedures and functions form a cohesive set of defaulting and derivation routines:

• GET_CASH_DEFAULTS, DEFAULT_CASH_IDS, DEFAULT_CASH_RECEIPT_ID — establish default cash receipt attributes and identifiers, including the cash receipt ID assigned during receipt creation.
• DEFAULT_APPLN_IDS, DERIVE_UNAPP_IDS, DEFAULT_UNAPP_INFO — derive and default the identifiers and attributes required when a receipt is applied or unapplied against transactions.
• DEFAULT_REVERSE_INFO, DERIVE_REVERSE_IDS — resolve the values needed to reverse a receipt or its applications.
• DEFAULT_ON_AC_APP_INFO, DERIVE_UNAPP_ON_AC_IDS, DEFAULT_UNAPP_ON_AC_ACT_INFO, DERIVE_ACTIVITY_UNAPP_IDS — handle on-account application and unapplication scenarios, including activity-based unapplication derivation.
• DERIVE_OTHERACCOUNT_IDS — derive identifiers for receipts applied to accounts other than the primary customer account.
• GET_DOC_SEQ — retrieve document sequence values for receipt numbering.
• DERIVE_CUST_INFO_FROM_TRX — derive customer information from the transaction being applied.
• VALIDATE_DESC_FLEXFIELD, DEFAULT_DESC_FLEXFIELD — validate and default the descriptive flexfield segments carried on the receipt.
• DEFAULT_MISC_IDS, GET_MISC_DEFAULTS — supply default values for miscellaneous receipt processing.
• DEFAULT_APPLICATION_INFO — populate the standard application context information used across the preceding routines.

Tables Accessed

The package reads and writes across the Receivables and shared reference schema via APPS synonyms. It works with AR_CASH_RECEIPTS, AR_PAYMENT_SCHEDULES, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, and AR_RECEIPT_METHOD_ACCOUNTS_ALL to default receipt attributes, methods, and remittance accounts. Customer data is sourced from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, and HZ_PARTY_SITES, while RA_CUSTOMER_TRX supplies transaction context for applications. Currency and conversion information comes from FND_CURRENCIES, FND_CURRENCIES_VL, and GL_DAILY_CONVERSION_TYPES; banking data from CE_BANK_ACCOUNTS and IBY_EXT_BANK_ACCOUNTS_V. AP_INVOICES and AP_CHECKS support payment-related scenarios.

Usage Notes

AR_RECEIPT_LIB_PVT is not invoked directly by end users or external integrations. It is called by AR_RECEIPT_API_PUB and related public packages—including AR_CM_API_PUB, AR_CM_APPLICATION_PUB, AR_AUTOREC_API, AR_PREPAYMENTS, AR_PREPAYMENTS_PUB, AR_RAAPI_UTIL, AR_RECEIPT_VAL_PVT, PA_AR_ADV_RECEIPT, and ARP_PROCESS_MISC_RECEIPTS—during standard receipt entry, application, unapplication, reversal, miscellaneous receipt, and prepayment processing. It executes whenever these public APIs run, whether from the Receivables forms, concurrent programs, or custom code that calls AR_RECEIPT_API_PUB. Customizations should target the public API; direct calls to this private library package are unsupported and may be affected by patches or upgrades in both 12.1.1 and 12.2.2.