Search Results refund_prepayments
Overview
APPS.AR_OM_PREPAY_REFUND_PVT is a private (PVT-classified) PL/SQL package body in the Oracle E-Business Suite Receivables module that supports the refunding of prepayments captured against customer orders originating in Oracle Order Management. The package belongs to the family of AR prepayment APIs and provides a thin wrapper layer that extends the functionality of the core AR_PREPAYMENTS.Refund_Prepayment logic. Its defining characteristic is that it accepts an additional bank account identifier alongside the receipt method identifier, allowing the refund transaction to be directed to a specific bank account rather than relying on ambiguous or defaulted payment instrument data. The header comment (AROMRFNB.pls, version 115.3, dated 2004) and naming conventions confirm that this is an internal helper used by the Order Management integration with Receivables rather than a publicly callable API. It is a longstanding component whose behavior is consistent across the 12.1.1 and 12.2.2 releases.
Key Procedures and Functions
The package exposes a single documented procedure:
- REFUND_PREPAYMENT_WRAPPER — Described in the package header as functionally equivalent to AR_PREPAYMENTS.Refund_Prepayment, but with one additional parameter, p_bank_account_id. When this parameter and p_receipt_method_id both carry values, the procedure uses them to populate global variables internal to AR_PREPAYMENTS.Refund_Prepayment, thereby controlling the bank account and receipt method under which the refund is created. The wrapper therefore serves as an entry point that lets callers from the Order Management flow supply explicit payment-instrument information that the base refund routine does not otherwise accept. No other procedures or functions are documented in the excerpted body; the remainder of the specification consists of package global constants used for message levels (G_MSG_UERROR, G_MSG_ERROR, G_MSG_SUCCESS, and the debug severity levels), a G_PKG_NAME constant for error attribution, and a PG_DEBUG flag initialized from the AFLOG_ENABLED profile option to govern diagnostic logging.
Tables Accessed
The package operates against two Receivables tables, accessed through APPS synonyms:
- AR_CASH_RECEIPTS — The primary table for receipt and refund records. Refunding a prepayment results in the creation of a refund receipt, so this table is written when the refund transaction is generated and read when validation or lookup of existing receipt data is required.
- AR_RECEIVABLE_APPLICATIONS — Used to manage the application (and unapplication, where necessary) linkage between the prepayment and the refund. The wrapper, like the underlying AR_PREPAYMENTS logic, must adjust applied amounts so that the prepayment balance and the new refund are correctly reflected in Receivables.
The package is also referenced by one other package within the APPS schema, reflecting its role as a component of a larger prepayment-refund call chain rather than a standalone utility.
Usage Notes
Because this is a PVT-classified package, it is not intended for direct invocation by customers or extension developers; Oracle's documented public API for prepayment refunds remains AR_PREPAYMENTS.Refund_Prepayment. AR_OM_PREPAY_REFUND_PVT is typically reached through Order Management's prepayment processing path — for example, when a refund must be issued against an order-related prepayment and the specific bank account and receipt method are known at the point of the call. In practice, it is invoked by other PL/SQL packages in the Order Management/Receivables integration rather than from a form or a concurrent program directly. Callers must ensure that both the receipt method identifier and the bank account identifier are supplied and valid; when they are provided, the wrapper propagates them to the base refund routine's globals. Custom code should avoid calling this package directly and should instead use the supported AR_PREPAYMENTS API, since the wrapper's signature, internal globals, and behavior are subject to change without notice.
-
PACKAGE BODY: APPS.AR_OM_PREPAY_REFUND_PVT
12.1.1
-
PACKAGE BODY: APPS.AR_OM_PREPAY_REFUND_PVT
12.2.2
-
PACKAGE BODY: APPS.AR_PREPAYMENTS
12.1.1
-
PACKAGE BODY: APPS.AR_PREPAYMENTS
12.2.2
-
PACKAGE: APPS.AR_PREPAYMENTS
12.2.2
-
PACKAGE: APPS.AR_PREPAYMENTS
12.1.1
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on ARP_UTIL
12.1.1
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on ARP_UTIL
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on ARP_UTIL
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on ARP_UTIL
12.2.2
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_MESSAGE
12.2.2
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_MESSAGE
12.1.1
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_API
12.1.1
-
APPS.AR_OM_PREPAY_REFUND_PVT dependencies on FND_API
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on FND_API
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on FND_API
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on STANDARD
12.2.2
-
APPS.OE_PREPAYMENT_PVT dependencies on AR_PREPAYMENTS
12.1.1
-
APPS.OE_PREPAYMENT_PVT dependencies on AR_PREPAYMENTS
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on STANDARD
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on FND_API
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on FND_API
12.2.2
-
PACKAGE BODY: APPS.OE_PREPAYMENT_PVT
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on STANDARD
12.1.1
-
PACKAGE BODY: APPS.OE_PREPAYMENT_PVT
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on STANDARD
12.2.2
-
APPS.OE_PREPAYMENT_PVT dependencies on OE_DEBUG_PUB
12.1.1
-
APPS.OE_PREPAYMENT_PVT dependencies on OE_DEBUG_PUB
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on FND_MSG_PUB
12.2.2
-
APPS.AR_PREPAYMENTS dependencies on FND_MSG_PUB
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on AR_CASH_RECEIPTS
12.1.1
-
APPS.AR_PREPAYMENTS dependencies on AR_CASH_RECEIPTS
12.2.2