Search Results cleared_base_amount

Overview

AP_CHECKS_V is a documented, VALID view owned by the APPS schema within the Oracle E-Business Suite Payables (AP) product module. It exposes payment and check information from the underlying AP_CHECKS entity, supplementing that core data with attributes drawn from bank account, supplier, address, payment document, and global setup sources. Unlike the base transactional table, the view presents a denormalized, reporting-friendly projection that joins payment header data to banking and payee context, making it suitable for both inquiry and integration purposes across Oracle EBS 12.1.1 and 12.2.2.

The view retains the payment record identity through ROW_ID (mapped from AP_CHECKS.ROWID) and CHECK_ID, while adding derived and joined attributes such as BANK_ACCOUNT_ID from CE_BANK_ACCOUNTS and PAYMENT_DOCUMENT_ID from CE_PAYMENT_DOCUMENTS. The presence of CONTROL_AMOUNT (aliased from AC.AMOUNT) indicates the view is consumed by payment control and reconciliation processes as well as ad hoc reporting.

Underlying Base Objects

Per the documented metadata, AP_CHECKS_V references the following base objects:

• Core payment objects: AP_CHECKS (synonym), AP_CHECKS_PKG, AP_AUTO_PAYMENT_PKG, AP_INVOICE_PAYMENTS_PKG.
• Supplier and party objects: AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS.
• Banking and cash management objects: CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, CE_BANK_BRANCHES_V, CE_PAYMENT_DOCUMENTS, CE_STATEMENT_HEADERS, CE_STATEMENT_LINES, CE_STATEMENT_RECONCILS_ALL.
• Setup and reference objects: AP_SYSTEM_PARAMETERS_ALL, AP_LOOKUP_CODES, FND_LOOKUPS, FND_DOCUMENT_SEQUENCES, FND_DOC_SEQUENCE_CATEGORIES, FND_GLOBAL, FND_TERRITORIES_VL, GL_DAILY_CONVERSION_TYPES, IBY_PAYMENT_METHODS_VL, IBY_PAYMENT_PROFILES.

The view text confirms a primary selection from AP_CHECKS (aliased AC) joined to CE_BANK_ACCOUNTS (aliased CBA) to supply BANK_ACCOUNT_ID, with PAYMENT_DOCUMENT_ID supplied by CE_PAYMENT_DOCUMENTS (aliased PD). Package references indicate the view participates in the payment creation, auto-payment, and invoice-payment application flows.

Key Columns

• Identity and control: ROW_ID, CHECK_ID, CHECK_NUMBER, CHECK_VOUCHER_NUM, DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE, DOC_CATEGORY_CODE.
• Amounts and currency: AMOUNT, CONTROL_AMOUNT, BASE_AMOUNT, CLEARED_AMOUNT, CLEARED_BASE_AMOUNT, CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE.
• Payment run context: CHECKRUN_ID, CHECKRUN_NAME, CHECK_DATE, FUTURE_PAY_DUE_DATE.
• Banking details: BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, BANK_NUM, PAYMENT_DOCUMENT_ID.
• Clearing and reconciliation: CLEARED_DATE, CLEARED_EXCHANGE_DATE, CLEARED_EXCHANGE_RATE, CLEARED_EXCHANGE_RATE_TYPE.
• Payee address: ADDRESS_LINE1 through ADDRESS_LINE4, ADDRESS_STYLE, CITY, COUNTY, COUNTRY. ADDRESS_STYLE defaults to 'DEFAULT' via NVL when unpopulated.
• Descriptive flexfields: ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15.
• Audit: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The view is typically used for payment registers, bank reconciliation extracts, check printing verification, and integration feeds to treasury or financial data warehouses.

Listing recent payments for a payee or bank account:

• SELECT check_id, check_number, check_date, amount, currency_code, bank_account_num FROM ap_checks_v WHERE bank_account_id = :p_bank_account_id AND check_date >= :p_from_date;

Reconciling cleared versus issued amounts:

• SELECT check_number, amount, cleared_amount, cleared_date FROM ap_checks_v WHERE cleared_date IS NULL AND check_date < SYSDATE - 30;

Extracting payment-run totals for a given run:

• SELECT checkrun_name, COUNT(*) payment_count, SUM(amount) total_amount FROM ap_checks_v WHERE checkrun_id = :p_checkrun_id GROUP BY checkrun_name;

Because the view draws on joined banking and party objects, queries should filter on indexed base columns such as CHECK_ID, CHECKRUN_ID, and BANK_ACCOUNT_ID to avoid full-scan overhead. The descriptive flexfield attributes and address columns make the view equally suitable for formatted output and for downstream document generation.