Results for “ap_checks_pkg”

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

Overview

The APPS.AP_CHECKS_PKG package body encapsulates the core data-access and business logic that Oracle Payables applies to payment records stored in the AP_CHECKS and AP_CHECKS_ALL tables. In Oracle E-Business Suite 12.1.1 and 12.2.2, a "check" is the internal representation of any disbursement document — a printed cheque, an electronic funds transfer, a wire, or a clearing payment. This package provides the Application Programming Interface used by the Payables payment workbench, the payment batch programs, and dependent modules such as reconciliation and positive pay to insert, lock, update, and delete those disbursement rows, and to answer domain questions about their state.

The package is classified as OTHER, meaning it is a support package rather than a formally published Open Interface. It is marked VALID in the APPS schema and is referenced by four other database packages, confirming its role as a foundational dependency in the Payables object hierarchy. It is not itself referenced externally as an inbound interface, so it should be treated as internal to the Payables application layer.

Key Procedures and Functions

The documented API exposes nine procedures and functions:

• INSERT_ROW — Creates a new disbursement record in the check tables, applying the standard column defaults and audit attributes required by the Payables data model.
• LOCK_ROW — Obtains a selective lock on an existing check row so that concurrent updates cannot corrupt payment state.
• UPDATE_ROW — Persists modifications to an existing disbursement record, including status changes, amounts, and clearing information.
• DELETE_ROW — Removes a disbursement record when a payment is voided, cancelled, or reversed before settlement.
• GET_INVOICES_PAID — Returns the invoices that a given payment disbursed, joining the check to the invoice-payment association tables.
• IS_MATURITY_ACCOUNTED — Determines whether the accounting entries for a maturing payment have already been generated, used to prevent double accounting.
• IS_PAYMENT_MATURED — Evaluates whether a payment has reached its maturity (value) date and is therefore eligible for accounting and reconciliation.
• GET_POSTING_STATUS — Reports the posting status of the payment, indicating whether it has been transferred to General Ledger.
• SUBSCRIBE_TO_PAYMENT_EVENT — Registers a subscription to the payment business event, supporting the Payables event-based integration model.

Parameter lists are intentionally omitted; callers should reference the live package specification, as signatures vary by patch level.

Tables Accessed

The package reads and writes the core disbursement tables AP_CHECKS and AP_CHECKS_ALL, the latter being the partitioned, multi-org-enabled base table. It queries AP_INVOICES, AP_INVOICE_PAYMENTS, and AP_INVOICE_PAYMENTS_ALL to resolve which invoices a payment settled. AP_PAYMENT_HISTORY records the lifecycle audit trail of each payment. AP_SYSTEM_PARAMETERS supplies accounting and payment configuration defaults. AP_PRODUCT_REGISTRATIONS is read for licensing checks. Supplier and location context are drawn from AP_SUPPLIER_SITES, HZ_LOCATIONS, and FND_TERRITORIES/FND_TERRITORIES_TL. The package also calls AP_RECONCILIATION_PKG, AP_AC_TABLE_HANDLER_PKG, APP_EXCEPTION, and FND_MESSAGE for reconciliation, accounting, error handling, and messaging.

Usage Notes

AP_CHECKS_PKG is invoked indirectly by the Payables Payment Workbench form and by concurrent programs such as Payment Batch, Payment Process Request, and Positive Pay. Custom extensions should not call the low-level row procedures directly, because they bypass validation and event publication; instead, use documented public APIs. When troubleshooting payment accounting or reconciliation discrepancies, IS_MATURITY_ACCOUNTED, IS_PAYMENT_MATURED, and GET_POSTING_STATUS are the appropriate investigative entry points.