Results for “is_payment_matured”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_CHECKS_PKG is a core Oracle Payables (AP) package in the APPS schema that encapsulates persistence and business logic for payment records stored in the AP_CHECKS and AP_CHECKS_ALL tables. In Oracle EBS 12.1.1 and 12.2.2, payments may be created as either manual or automatic payments, and each is physically represented as a "check" row regardless of the disbursement method (check, wire, ACH, or electronic funds transfer). AP_CHECKS_PKG serves as the programmatic interface for creating, maintaining, and querying these records, and it exposes utility routines used by other Payables objects to determine invoice payment maturity, accounting status, and posting status.

The package is classified as OTHER in the ETRM repository for 12.2.2, meaning it is not a formally published open API but is nevertheless a stable, widely referenced internal package. It is validated in both release levels and is referenced by four other database objects, most notably the AP_CHECKS_V view and the AP_PAY_SINGLE_INVOICE_PKG and AP_PMT_CALLOUT_PKG packages. This dependency footprint confirms that the package sits at the centre of the payment data model and is invoked whenever payment rows are inserted or maintained.

Key Procedures and Functions

The ETRM documentation registers nine callable units within AP_CHECKS_PKG. The four base persistence routines follow the standard Oracle Forms-generated table handler pattern: INSERT_ROW, LOCK_ROW, UPDATE_ROW, and DELETE_ROW. INSERT_ROW creates a new payment record; LOCK_ROW performs a SELECT FOR UPDATE to serialize concurrent access; UPDATE_ROW modifies an existing payment; and DELETE_ROW removes a payment row. These routines are typically invoked from the Payables payment forms and from the package's own internal transaction sequences rather than by external callers.

• GET_INVOICES_PAID — Returns the invoices settled by a given payment, resolving data across AP_INVOICE_PAYMENTS and AP_INVOICE_PAYMENTS_ALL.
• IS_MATURITY_ACCOUNTED — Reports whether the accounting entries for a payment's maturity event have been generated, supporting accounting validation and close activities.
• IS_PAYMENT_MATURED — Determines whether a payment has reached its maturity date and is therefore eligible for clearing or reconciliation processing.
• GET_POSTING_STATUS — Returns the posting status of a payment so callers can determine whether it has been transferred to the General Ledger.
• SUBSCRIBE_TO_PAYMENT_EVENT — Registers a subscription to a payment-related business event via the Oracle Workflow Business Event System, enabling downstream consumers (such as AP_PMT_CALLOUT_PKG) to react to payment creation or status changes.

Tables Accessed

The package reads and writes the AP_CHECKS and AP_CHECKS_ALL tables, which hold the payment header information; AP_CHECKS_ALL is the multi-org–enabled variant and is the primary source for queries. AP_INVOICES and AP_INVOICE_PAYMENTS (together with AP_INVOICE_PAYMENTS_ALL) provide the invoice-side linkage that GET_INVOICES_PAID resolves. AP_PAYMENT_HISTORY stores the audit trail of payment status transitions, while AP_PRODUCT_REGISTRATIONS and AP_SYSTEM_PARAMETERS supply configuration and option data. Supplier and address information is drawn from AP_SUPPLIER_SITES and HZ_LOCATIONS, and territory descriptions come from FND_TERRITORIES and FND_TERRITORIES_TL. All tables are accessed through APPS synonyms.

Usage Notes

AP_CHECKS_PKG is invoked primarily from the Oracle Payables payment workbench forms (APXPAYWI and related forms) during manual payment entry, payment formatting, and void/reissue processing. Concurrent programs such as Payment Process Request (PPR) and the Payment Formatting Program call it indirectly via AP_PMT_CALLOUT_PKG. Because it is classified as OTHER and not as a published open interface, custom code should avoid direct calls to its DML routines; instead, customers should use documented APIs such as AP_PAYMENT_UTIL_PKG or ap_pay_single_invoice_pkg. Where read-only information is required, GET_INVOICES_PAID, IS_PAYMENT_MATURED, and GET_POSTING_STATUS are frequently referenced from custom reports and reconciliation scripts. The dependency on AP_CHECKS_V makes the package sensitive to column changes in AP_CHECKS_ALL, so patches to Payables should be regression-tested against any custom objects referencing this package.