Search Results cleared_error_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
- PAYMENT_DOCUMENT_ID (NUMBER(15)) — Primary identifier of the payment document; the join key back to AP_CHECKS and to downstream payment-related tables.
- AMOUNT and FUNCTIONAL_AMOUNT — The entered and functional (ledger) amounts of the disbursement.
- PAYMENT_DOCUMENT_DATE, PAYMENT_DOCUMENT_NUMBER, PAYMENT_TYPE, and PAYMENT_STATUS — Identify the document, its date, its payment method class, and its current lifecycle state.
- CLEARED_AMOUNT, CLEARED_DATE, and CLEARED_FUNCTIONAL_AMOUNT — The amount of the payment that has been reconciled against the bank statement, the clearing date, and its functional equivalent.
- CLEARED_CHARGES_AMOUNT — The bank charges element associated with the cleared portion of the payment. This is the column targeted by the search term "cleared_charges_amount"; it isolates charges rather than the principal disbursement, which is essential for bank charge analysis and cash reconciliation.
- CLEARED_CHARGES_FUNCTIONAL_AMT and CLEARED_ERROR_AMOUNT / CLEARED_ERROR_FUNCTIONAL_AMT — Functional-currency charges and any clearing error amounts recorded during reconciliation.
- CLEARED_CURRENCY_EXCH_RATE, CLEARED_CURRENCY_EXCH_DATE, and CLEARED_CRNCY_EXCH_RATE_TYPE — The exchange rate context applied at clearing time; the parallel CURRENCY_EXCHANGE_* columns record the rate at payment creation.
- VOID_DATE, STOP_PAYMENT_RECORDED_DATE, STOP_PAYMENT_RELEASED_DATE, and the associated user IDs — Void and stop-payment audit columns.
- USSGL_TRANSACTION_CODE, TRANSFER_PRIORITY, STAMP_DUTY_AMOUNT, and STAMP_DUTY_FUNCTIONAL_AMOUNT — Supporting attributes for governmental accounting and payment processing.
- Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) — Audit trail 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.
-
VIEW: APPS.APBV_AP_PAYMENTS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APBV_AP_PAYMENTS, object_name:APBV_AP_PAYMENTS, status:VALID,
-
VIEW: AP.AP_CHECKS_ALL#
12.2.2
-
VIEW: APPS.APBV_AP_PAYMENTS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APBV_AP_PAYMENTS, object_name:APBV_AP_PAYMENTS, status:VALID,
-
View: AP_CHECKS_ALL_MRC_V
12.1.1
product: AP - Payables , description: MULTI-ORG MRC view , implementation_dba_data: Not implemented in this database ,
-
View: AP_CHECKS_ALL_MRC_V
12.2.2
product: AP - Payables , description: MULTI-ORG MRC view , implementation_dba_data: Not implemented in this database ,
-
VIEW: APPS.APFV_AP_PAYMENTS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_AP_PAYMENTS, object_name:APFV_AP_PAYMENTS, status:VALID,
-
VIEW: APPS.APFV_AP_PAYMENTS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_AP_PAYMENTS, object_name:APFV_AP_PAYMENTS, status:VALID,
-
View: AP_CHECKS_MRC_V
12.1.1
product: AP - Payables , description: SINGLE-ORG MRC view , implementation_dba_data: Not implemented in this database ,
-
View: APBV_AP_PAYMENTS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APBV_AP_PAYMENTS, object_name:APBV_AP_PAYMENTS, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APBV_AP_PAYMENTS ,
-
View: APBV_AP_PAYMENTS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APBV_AP_PAYMENTS, object_name:APBV_AP_PAYMENTS, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APBV_AP_PAYMENTS ,
-
View: AP_CHECKS_MRC_V
12.2.2
product: AP - Payables , description: SINGLE-ORG MRC view , implementation_dba_data: Not implemented in this database ,
-
View: APFV_AP_PAYMENTS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_AP_PAYMENTS, object_name:APFV_AP_PAYMENTS, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APFV_AP_PAYMENTS ,
-
View: APFV_AP_PAYMENTS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_AP_PAYMENTS, object_name:APFV_AP_PAYMENTS, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APFV_AP_PAYMENTS ,
-
VIEW: AP.AP_CHECKS_ALL#
12.2.2
owner:AP, object_type:VIEW, object_name:AP_CHECKS_ALL#, status:VALID,
-
APPS.AP_RECONCILIATION_PKG SQL Statements
12.1.1
-
APPS.AP_RECONCILIATION_PKG SQL Statements
12.2.2
-
TABLE: AP.AP_CHECKS_ALL
12.2.2
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_CHECKS_ALL, object_name:AP_CHECKS_ALL, status:VALID,
-
TABLE: AP.AP_CHECKS_ALL
12.1.1
owner:AP, object_type:TABLE, fnd_design_data:SQLAP.AP_CHECKS_ALL, object_name:AP_CHECKS_ALL, status:VALID,
-
APPS.AP_CHECKS_PKG SQL Statements
12.2.2
-
APPS.AP_CHECKS_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AP_RECONCILIATION_PKG
12.1.1
-
PACKAGE BODY: APPS.AP_RECONCILIATION_PKG
12.2.2
-
APPS.AP_RECONCILIATION_PKG dependencies on AP_CHECKS
12.1.1
-
APPS.AP_RECONCILIATION_PKG dependencies on AP_CHECKS_ALL
12.2.2
-
APPS.AP_RECONCILIATION_PKG dependencies on AP_CHECKS
12.2.2
-
PACKAGE BODY: APPS.AP_CHECKS_PKG
12.1.1
-
PACKAGE BODY: APPS.AP_CHECKS_PKG
12.2.2
-
eTRM - SQLAP Tables and Views
12.2.2
description: Set Distribution Table. ,
-
eTRM - SQLAP Tables and Views
12.1.1
description: Set Distribution Table. ,