Search Results apfv_ap_payments

Overview

APFV_AP_PAYMENTS is a business view owned by the APPS schema in Oracle E-Business Suite, classified under the AP – Payables product. In both Release 12.1.1 and 12.2.2 it is reported by ETRM as VALID and is described simply as a "Business view." Functionally, it presents payment (check) information in a flattened, reporting-friendly form: rather than requiring the caller to join AP_CHECKS to lookups, vendor sites, and bank account tables, the view exposes a single row per payment with descriptive payment type, status, and method columns already resolved. The view exposes a defined column list including CHECK_ID, BANK_ACCOUNT_NAME, AMOUNT, CURRENCY_CODE, CHECK_DATE, CHECK_NUMBER, CHECK_VOUCHER_NUMBER, CHECKRUN_NAME, PAYMENT_TYPE, PAYMENT_STATUS, PAYMENT_METHOD, VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, ADDRESS_LINE_1, and ADDRESS_LINE_2. Because it carries vendor name and address attributes alongside payment attributes, it is frequently used as a source for payment registers, vendor remittance reporting, and downstream integration extracts that require both payment and payee context in one query, a role that remains consistent across the 12.1.1 and 12.2.2 code lines.

Underlying Base Objects

According to the documented view metadata for 12.2.2, APFV_AP_PAYMENTS is defined over a single referenced base object: the AP_CHECKS synonym (owner APPS). The view text confirms this, selecting exclusively from AP_CHECKS, aliased as CH, and terminating with the WITH READ ONLY clause, which enforces that the view cannot be used for DML. Key projected columns are the check identity and payment attributes (CHECK_ID, AMOUNT, CURRENCY_CODE, CHECK_DATE, CHECK_NUMBER, CHECK_VOUCHER_NUM, CHECKRUN_NAME, PAYMENT_TYPE_FLAG, STATUS_LOOKUP_CODE, PAYMENT_METHOD_LOOKUP_CODE), clearing and bank data (CLEARED_AMOUNT, CLEARED_DATE, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, CE_BANK_ACCT_USE_ID, EXTERNAL_BANK_ACCOUNT_ID), exchange and base amount information, and vendor identity and address columns (VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, ADDRESS_LINE1 through ADDRESS_LINE3, CITY, STATE, ZIP, COUNTRY, VENDOR_SITE_CODE). The view also embeds descriptive-flex and DBI internal markers in its select list. Although the extract lists only AP_CHECKS as the referenced object, users should treat the view as a denormalized presentation layer over the AP payments schema rather than as an independent data source.

Key Columns

• CHECK_ID – Primary identifier of the payment row in AP_CHECKS; the join key to payment distributions and invoice linkage.
• AMOUNT, CURRENCY_CODE, CHECK_DATE, CHECK_NUMBER – Core payment attributes used in registers and reconciliation.
• PAYMENT_TYPE, PAYMENT_STATUS, PAYMENT_METHOD – Descriptive columns resolving the underlying lookup codes into displayable values.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_SITE_CODE – Payee identity, supporting vendor-level aggregation.
• ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, CITY, STATE, ZIP, COUNTRY – Vendor site address columns, the attributes most relevant when a user searches for vendor postal code information, since ZIP and the address lines together form the postal address of the payee site.
• CLEARED_AMOUNT, CLEARED_DATE, VOID_DATE, STOPPED_AT – Payment lifecycle and bank reconciliation state.

Common Use Cases and Queries

The view supports payment register reporting, remittance advice generation, vendor payment analysis, and extracts feeding external treasury or bank reconciliation systems. Because it is read-only, it is used exclusively for queries. A typical query filtered on postal code information is:

SELECT check_id, check_number, check_date, vendor_name, vendor_site_code, address_line_1, city, state, zip, country, amount, currency_code FROM apps.apfv_ap_payments WHERE zip = :postal_code ORDER BY check_date DESC;

Vendor-level summaries are equally common:

SELECT vendor_id, vendor_name, currency_code, SUM(amount) total_paid FROM apps.apfv_ap_payments WHERE check_date BETWEEN :from_date AND :to_date GROUP BY vendor_id, vendor_name, currency_code;

Where additional detail is required — payment distributions, invoice lines, or bank account definitions — the view is joined back to AP_CHECKS and its related AP tables on CHECK_ID.