Search Results ap_pay_in_full_pkg




Overview

APPS.AP_PAY_IN_FULL_PKG is a server-side PL/SQL package within the Oracle E-Business Suite Payables (AP) module. Its central business function is to support the "Pay in Full" payment model, whereby an invoice is selected for payment in its entirety rather than through partial or installment-based disbursement. The package encapsulates the logic required to identify invoices eligible for full payment, evaluate whether discounts remain available, determine the appropriate check or payment amount, and construct the corresponding payment records. It is classified as an "OTHER" API within the ETRM repository, indicating it is an internal utility package rather than a formally published public API. The package is owned by the APPS schema and holds a VALID status in both Release 12.1.1 and 12.2.2. Its dependencies span core Payables transaction tables and setup tables, reflecting its role in the payment creation lifecycle.

Key Procedures and Functions

The package body exposes four documented procedures and functions, each aligned to a discrete step in the full-payment workflow:

  • AP_LOCK_INVOICES — Acquires the necessary locks on invoice records prior to payment processing, ensuring that concurrent activity does not corrupt the payment selection state.
  • AP_DISCOUNT_AVAILABLE — Evaluates whether an eligible discount can still be taken on the invoice at the time of payment, based on the invoice and payment schedule terms.
  • AP_GET_CHECK_AMOUNT — Derives the payment (check) amount to be disbursed for the invoice being paid in full, reconciling invoice amounts and applicable adjustments.
  • AP_CREATE_PAYMENTS — Creates the payment records that represent the full settlement of the selected invoices.

Detailed parameter signatures are not defined in the documented metadata; only the procedure and function names and their functional intent are recorded.

Tables Accessed

The package reads and writes a broad set of Payables tables through APPS synonyms. Invoice and schedule data are drawn from AP_INVOICES, AP_INVOICES_ALL, AP_INVOICES_S, AP_PAYMENT_SCHEDULES, and AP_PAYMENT_SCHEDULES_ALL, which together define the amounts and due terms driving full payment. Supplier identity and remittance information come from AP_SUPPLIERS and AP_SUPPLIER_SITES. Distribution and line detail are read from AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_DISTRIBUTIONS_ALL, and AP_INVOICE_LINES_ALL. Payment history and linkage records are handled through AP_INVOICE_PAYMENTS_ALL and AP_INVOICE_PAYMENTS_S. Interest calculations reference AP_INTEREST_PERIODS, while AP_SYSTEM_PARAMETERS and FND_DOCUMENT_SEQUENCES supply system-level defaults and document numbering for payment creation.

Usage Notes

AP_PAY_IN_FULL_PKG is referenced by AP_PAY_SINGLE_INVOICE_PKG, indicating that it is invoked as part of the broader single-invoice payment processing pathway rather than called directly by end users. It is typically triggered from Payables payment forms or from concurrent payment processing programs that perform full settlement of selected invoices. Custom extensions requiring pay-in-full behavior should treat this package as a dependent internal utility and call the higher-level AP_PAY_SINGLE_INVOICE_PKG entry point rather than AP_PAY_IN_FULL_PKG directly. Because it manipulates invoice locks and creates payment rows, any invocation must be performed within the standard Payables transaction and validation framework.