Search Results get_destination_function

Overview

AP_PAYMENT_UTIL_PKG is a utility package in the APPS schema of Oracle E-Business Suite that supports the Oracle Payables payment processing framework. It provides shared helper routines used by the payment selection, payment building, and payment formatting components of Payables, including the Payment Workbench and the payment batch concurrent programs. The package encapsulates common lookups — such as legal entity names, operating unit names, payer defaults, and count queries against selected, unselected, and rejected payment schedules — that would otherwise be duplicated across payment-related packages. It is classified in ETRM as an OTHER API, meaning it is not a formally published public interface but is nevertheless referenced by multiple standard EBS packages and is therefore significant when analyzing payment behavior, troubleshooting selection anomalies, or extending payment functionality.

Key Procedures and Functions

The 28 documented procedures and functions fall into several functional groups. Name lookup routines include GET_LE_NAME and GET_OU_NAME, which resolve legal entity and operating unit identifiers to descriptive names, and GET_IBY_PAYER_DEFAULTS, which retrieves default payer attributes from the IBY (Oracle Payments) payer configuration. Count routines support payment batch validation and diagnostics: GET_PI_COUNT returns the count of payment instructions; GET_SELECTED_PS_COUNT, GET_UNSEL_PS_COUNT, and GET_REJECTED_PS_COUNT return counts of selected, unselected, and rejected payment schedules; GET_PS_UR_COUNT and GET_UNSEL_REASON_COUNT break down unselected schedules and their reasons; and GET_MISSING_RATES_PS_COUNT identifies schedules lacking currency conversion rates. Financial calculation routines include GET_INTEREST_DUE, GET_INTEREST_PAID, GET_INTEREST_INV, GET_GAIN_LOSS_AMOUNT, and GET_INTEREST_RATE, which support interest and gain/loss determination on overdue payments. Status and control routines include GET_PAYMENT_STATUS_FLAG, GET_PSR_STATUS, GET_DESTINATION_FUNCTION, and GET_ACTION_FUNCTION, while ACTION_SWITCHER acts as a dispatcher that routes processing to the appropriate action function based on the requested operation.

Tables Accessed

The package reads and writes a broad set of Payables tables through APPS synonyms. Invoice-related tables include AP_INVOICES_ALL, AP_INVOICE_PAYMENTS_ALL, AP_INVOICE_RELATIONSHIPS, and AP_PAYMENT_SCHEDULES_ALL, reflecting its role in counting and evaluating invoices and scheduled payments. Payment selection data is drawn from AP_INV_SELECTION_CRITERIA_ALL, AP_SELECTED_INVOICES, AP_SELECTED_INVOICES_ALL, and AP_UNSELECTED_INVOICES_ALL — the core tables that track which invoices were selected or excluded during a payment batch. Payment instructions and checks are represented by AP_CHECKS_ALL, with configuration supplied by AP_PAYMENT_TEMPLATES and AP_SYSTEM_PARAMETERS_ALL. Grouping and interest logic reference AP_CURRENCY_GROUP, AP_LE_GROUP, AP_OU_GROUP, and AP_INTEREST_PERIODS. These accesses support both transactional processing and the diagnostic counts returned by the utility functions.

Usage Notes

AP_PAYMENT_UTIL_PKG is invoked indirectly rather than by end users directly. It is referenced by AP_AUTOSELECT_PKG (invoice auto-selection), AP_DOCUMENTS_PAYABLE, AP_PERIOD_CLOSE_PKG (period close validation), IBY_PAYMENT_MANAGER_PKG (the Oracle Payments payment manager), and IBY_UTILITY_PVT. In practice, its routines are exercised whenever a payment batch is selected, built, or formatted, and when the Payment Workbench displays counts and status for selected, unselected, and rejected payment schedules. Customizations and diagnostics should call these procedures only through the documented callers where possible, since the package is not a published API. Developers extending payment behavior in 12.1.1 or 12.2.2 should treat AP_PAYMENT_UTIL_PKG as an internal dependency and verify behavior after patches, as the package body may change without notice between releases.