Search Results ap_invoice_payments_all

Overview

The AP_INVOICE_PAYMENTS_ALL table is a core transaction table within the Oracle E-Business Suite Payables module (AP). It serves as the central repository for all records of payments made against supplier invoices, including checks, electronic funds transfers, wire transfers, and clearing transactions. Its primary role is to establish and maintain the critical link between an invoice, its payment schedule, and the actual payment instrument (e.g., a check). This table is fundamental for tracking payment history, reconciling bank statements, and supporting the accounting events that generate journal entries for payment-related transactions in General Ledger. As an "ALL" table, it is multi-organization enabled, storing data for all operating units accessible to a responsibility based on the security profile.

Key Information Stored

The table's structure captures the essential attributes of a payment application. Its primary key is INVOICE_PAYMENT_ID, a unique system-generated identifier. Critical foreign key columns define its relationships: INVOICE_ID links to AP_INVOICES_ALL, CHECK_ID links to AP_CHECKS_ALL (or equivalent payment documents), and PAYMENT_NUM along with INVOICE_ID links to AP_PAYMENT_SCHEDULES_ALL. The SET_OF_BOOKS_ID column anchors the payment to a specific ledger. Key transactional columns include the PAYMENT_AMOUNT, which records the amount applied from the payment to the specific invoice line or schedule, and columns for managing cross-currency payments such as EXCHANGE_RATE and EXCHANGE_RATE_TYPE. The ACCOUNTING_EVENT_ID links to the GL transfer process, and columns like INVOICING_PARTY_ID and INVOICING_PARTY_SITE_ID reference the Trading Community Architecture (TCA) model for the paying entity.

Common Use Cases and Queries

This table is central to payment inquiry, reconciliation, and audit reporting. Common operational queries involve tracing payment history for a specific invoice or identifying all invoices paid by a specific check. For example, to retrieve detailed payment application records for an invoice, a typical SQL pattern joins AP_INVOICE_PAYMENTS_ALL with AP_CHECKS_ALL and AP_INVOICES_ALL. During bank reconciliation, queries often join this table to AP_CHECKS_ALL and the reconciliation tables to match cleared items. For accounting analysis, joins to AP_ACCOUNTING_EVENTS_ALL and GL_JE_LINES are used to trace the journal entries sourced from payments. Reporting on payment performance, such as the average time to pay, requires correlating payment dates from this table with invoice dates.

Related Objects

AP_INVOICE_PAYMENTS_ALL has extensive relationships within the Payables and integrated modules. Primary parent tables include AP_INVOICES_ALL, AP_PAYMENT_SCHEDULES_ALL, and AP_CHECKS_ALL. Key child tables, which store detailed distributions, are AP_PAYMENT_DISTRIBUTIONS_ALL and AP_PAYMENT_HIST_DISTS. For accounting, it links to AP_ACCOUNTING_EVENTS_ALL. The table also interfaces with other financial products: FV_BD_CONTROLS (Bills Discounting), FV_TREASURY_CONFIRMATIONS_ALL, and PA_COST_DISTRIBUTION_LINES_ALL (Projects). For localized tax functionality, such as Indian Tax Deducted at Source (TDS), it is referenced by JAI_AP_TDS_INV_PAYMENTS and related tables. Its relationship with HZ_PARTIES and HZ_PARTY_SITES aligns the payment data with the unified TCA customer and supplier model.