Search Results cleared_functional_amount




Overview

APBV_AP_PAYMENTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. Its FND Design Data identifier is SQLAP.APBV_AP_PAYMENTS, and it is shipped with a status of VALID across the 12.1.1 and 12.2.2 releases. The view presents payment records — disbursements issued to a supplier — in a denormalized, reporting-friendly form. Rather than requiring report authors and integrators to join the transactional payment tables directly, APBV_AP_PAYMENTS surfaces the payment document, its status, its cleared position, and its currency conversion attributes in a single object. This design makes it a natural source for payables dashboards, cash-management extracts, reconciliation reports, and interface programs that must read payment and clearing information without navigating the full Oracle Payments data model.

Underlying Base Objects

The documented metadata for this view identifies a single referenced base object: AP_CHECKS, accessed through a synonym in the APPS schema. AP_CHECKS is the core payables table that stores payment documents — checks, electronic payments, and wire transfers — along with their amounts, dates, statuses, and clearing details. APBV_AP_PAYMENTS therefore acts as a curated projection over AP_CHECKS, exposing the payment-level attributes most commonly consumed by reporting and integration processes while hiding the internal surrogate keys, auditable columns, and bank-account linkage that are rarely needed outside the application's own forms and concurrent programs.

Key Columns

Common Use Cases and Queries

Typical scenarios include bank reconciliation reporting, analysis of bank charges against cleared payments, identification of unreconciled payments, and extraction of payment data for external cash-management systems. A representative query isolating cleared charges is:

SELECT payment_document_id, payment_document_number, payment_document_date, payment_status, cleared_amount, cleared_date, cleared_charges_amount FROM apps.apbv_ap_payments WHERE cleared_charges_amount > 0;

An unreconciled payments query would filter on CLEARED_DATE IS NULL while restricting PAYMENT_STATUS to issued values. Because the view is a simple projection over AP_CHECKS, such queries benefit from the index structures on the base table and remain stable across the 12.1.1 and 12.2.2 releases.