Results for “cleared_charges_amount”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_CHECKS_ALL is the core Oracle Payables table that stores supplier payment data recorded against an operating unit. It is the authoritative record for every payment document generated by the Payables module, whether issued as a printed check, an electronic funds transfer, a wire, or a payment card transaction. Each row corresponds to a single payment instruction that has been formatted and confirmed by the payment process, capturing the monetary amount, the bank account, the supplier, the payment method, and the full lifecycle status of the document.

Because payment processing touches purchasing, cash management, treasury, and general ledger, AP_CHECKS_ALL functions as a central integration point. The metadata records a heuristic Data Vault classification of hub, reflecting its role as the anchor entity keyed by the surrogate identifier CHECK_ID, around which numerous descriptive satellites and transactional links revolve.

Key Information Stored

AP_CHECKS_ALL contains 156 documented columns in release 12.2.2. The table is owned by the AP schema and is secured by the primary key AP_CHECKS_PK on CHECK_ID, with additional unique indexes AP_CHECKS_U1 (CHECK_ID) and AP_CHECKS_U3 (DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE) serving as business-key candidates.

• CHECK_ID – surrogate primary key and the column used by all downstream foreign keys.
• CHECK_NUMBER and VOID_CHECK_NUMBER / VOID_CHECK_ID – the printed document number and its voiding counterpart.
• DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE – the document sequence assignment, an auditable business key enforced by AP_CHECKS_U3.
• AMOUNT, BASE_AMOUNT, EXCHANGE_RATE, EXCHANGE_RATE_TYPE – the payment value in the entered and functional currencies, plus conversion detail.
• CHECK_DATE, ACTUAL_VALUE_DATE, ANTICIPATED_VALUE_DATE, FUTURE_PAY_DUE_DATE – the accounting and treasury dates that drive disbursement timing.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_SITE_CODE – supplier identification inherited from PO_VENDORS and PO_VENDOR_SITES_ALL.
• BANK_ACCOUNT_ID, EXTERNAL_BANK_ACCOUNT_ID, CE_BANK_ACCT_USE_ID – the internal and supplier bank accounts used for disbursement.
• CHECK_STOCK_ID and CHECK_FORMAT_ID – the physical check stock and print format applied.
• STATUS_LOOKUP_CODE, POSITIVE_PAY_STATUS_CODE, WITHHOLDING_STATUS_LOOKUP_CODE – lifecycle and compliance state.
• CLEARED_DATE, CLEARED_AMOUNT, CLEARED_EXCHANGE_RATE – bank reconciliation outcome.
• PAYMENT_METHOD_CODE, PAYMENT_TYPE_FLAG, PAYMENT_ID, PAYMENT_INSTRUCTION_ID – the payment instrument and its instruction record.
• ORG_ID, LEGAL_ENTITY_ID, CURRENCY_CODE – operating unit, legal entity, and currency context.

Common Use Cases and Queries

Typical reporting scenarios include payment register extracts, outstanding check listings, void and stop-payment analysis, and bank reconciliation feeds. A standard query joining the payment to its supplier and invoices is shown below.

• Payment register: SELECT c.check_number, c.check_date, c.amount, c.currency_code, c.status_lookup_code FROM ap_checks_all c WHERE c.org_id = :org_id AND c.check_date BETWEEN :from_date AND :to_date ORDER BY c.check_date, c.check_number;
• Supplier payment detail: join AP_CHECKS_ALL to PO_VENDORS on VENDOR_ID and to AP_INVOICE_PAYMENTS_ALL on CHECK_ID to reconcile payments to invoices.
• Uncleared disbursements: filter on CLEARED_DATE IS NULL and STATUS_LOOKUP_CODE to identify outstanding items feeding cash management.
• Treasury reporting: aggregate AMOUNT and BASE_AMOUNT by CURRENCY_CODE, LEGAL_ENTITY_ID, and TREASURY_PAY_DATE for cash forecasting.
• Document sequence audit: query DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE to verify gapless sequential numbering, a statutory requirement in many jurisdictions.
• Positive pay: extract CHECK_NUMBER, CHECK_DATE, and AMOUNT where POSITIVE_PAY_STATUS_CODE is set, feeding bank transmission files.

Related Objects

• AP_INVOICE_PAYMENTS_ALL – joins on CHECK_ID; links each payment to the invoices it settles.
• AP_PAYMENT_HISTORY_ALL – joins on CHECK_ID; retains historical payment records including voids.
• AP_SELECTED_INVOICE_CHECKS_ALL – joins on CHECK_ID; staging detail from payment batch selection.
• AP_INV_SELECTION_CRITERIA_ALL – referenced via CHECKRUN_ID and CHECKRUN_NAME, defining the payment batch.
• PO_VENDORS and PO_VENDOR_SITES_ALL – referenced via VENDOR_ID and VENDOR_SITE_ID for supplier identity.
• CE_BANK_ACCT_USES_ALL and AP_BANK_ACCOUNTS_ALL – referenced via CE_BANK_ACCT_USE_ID and BANK_ACCOUNT_ID for disbursement accounts.
• IBY_PAY_INSTRUCTIONS_ALL – referenced via PAYMENT_INSTRUCTION_ID in the Oracle Payments integration.
• AP_CHECK_STOCKS_ALL and AP_CHECK_FORMATS – referenced via CHECK_STOCK_ID and CHECK_FORMAT_ID for document generation.
• FND_DOCUMENT_SEQUENCES and AP_DOC_SEQUENCE_AUDIT – referenced via DOC_SEQUENCE_ID for sequence control.
• FV_REFUNDS_VOIDS_ALL – joins on CHECK_ID, connecting treasury refund and void processing.