Search Results check_voucher_number

Overview

APFV_AP_PAYMENTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered in FND Design Data under the identifier SQLAP.APFV_AP_PAYMENTS. Its documented status is VALID across EBS 12.1.1 and 12.2.2. The view presents payment records — disbursements issued to a supplier — in a flattened, denormalized form suitable for reporting and downstream integration. Rather than exposing the internal foreign-key structure of the Payables transaction tables, it resolves supplier, bank, currency, clearing, and withholding attributes into a single queryable surface.

Because it is a BIS view, APFV_AP_PAYMENTS is intended primarily for read-only reporting, ad hoc inquiry, and extract-based integration. Concurrent programs, Oracle Business Intelligence Publisher reports, and custom operational reports frequently select from it rather than from the base Payables entities, avoiding the multi-table joins otherwise required to reconstruct a payment record.

Underlying Base Objects

The documented referenced base object for this view is AP_CHECKS, accessed through a synonym in the APPS schema. AP_CHECKS is the core Payables table that stores payment documents — issued checks, electronic funds transfers, wire payments, and clearing transactions — keyed by CHECK_ID. The view projects the majority of its columns from that single table, which explains the presence of the CHECK_ID and CHECK_NUMBER columns and the payment-oriented naming convention throughout the column list.

Supplier identifying information (VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, and the address and bank account attributes) is surfaced as already-resolved values. The catalogued column set includes descriptive suffixes such as _LA:PAYMENT_TYPE_DESCR, _LA:PAYMENT_STATUS_DESCR, and _LA:PAYMENT_METHOD_DESCR, indicating lookup-code translation is layered into the view definition.

Key Columns

• CHECK_ID — Number(15); the primary key of the underlying payment record and the join key to AP_CHECKS.
• CHECK_NUMBER — Number(15); the printed payment document number. The queried term check_voucher_number corresponds to the view column CHECK_VOUCHER_NUMBER, a Number(16) attribute carried alongside CHECK_NUMBER for voucher reconciliation.
• AMOUNT, CURRENCY_CODE, FUNCTIONAL_AMOUNT — Entered and functional payment values, with CURRENCY_EXCHANGE_RATE, CURRENCY_EXCHANGE_DATE, and CURRENCY_EXCHANGE_RATE_TYPE describing the conversion.
• CHECK_DATE, FUTURE_PAY_DUE_DATE, TREASURY_PAYMENT_DATE — Payment, scheduling, and treasury dates.
• PAYMENT_TYPE, PAYMENT_STATUS, PAYMENT_METHOD — Flags plus translated _LA descriptive counterparts.
• BANK_ACCOUNT_NAME, VENDOR_BANK_ACCOUNT_NUMBER, VENDOR_BANK_ACCOUNT_TYPE, CHECKRUN_NAME — Disbursement channel and payment batch context.
• CLEARED_AMOUNT, CLEARED_DATE, CLEARED_FUNCTIONAL_AMOUNT, CLEARED_CHARGES_AMOUNT, CLEARED_ERROR_AMOUNT — Bank reconciliation outcome values.
• VOID_DATE, STOP_PAYMENT_RECORDED_DATE, STOP_PAYMENT_RELEASED_DATE — Lifecycle and exception timestamps.

Common Use Cases and Queries

Typical consumption includes payment registers, cash-requirement analysis, cleared-versus-issued reconciliation, void and stop-payment exception reports, and supplier-level disbursement extracts.

SELECT check_id,
       check_number,
       check_voucher_number,
       check_date,
       amount,
       currency_code,
       payment_status,
       vendor_name,
       bank_account_name
FROM   apps.apfv_ap_payments
WHERE  check_date BETWEEN :p_start_date AND :p_end_date
ORDER  BY check_date, check_number;

Joining results to AP_INVOICE_PAYMENTS on CHECK_ID links each disbursement back to the invoices it settled, enabling payment-to-invoice reconciliation using CHECK_VOUCHER_NUMBER as a cross-reference. Queries should be constrained by date or vendor, as the view spans all payment history and is not indexed independently.