Search Results ap_history_checks_all




Overview
Explore in AI Chat

Overview

The AP_HISTORY_CHECKS_ALL table is a core data retention object within the Oracle E-Business Suite Payables (AP) module for versions 12.1.1 and 12.2.2. It serves as a historical summary repository for payment records, specifically checks and electronic payments, after the detailed transactional data has been purged from the active tables. Its primary role is to preserve essential audit and reconciliation information following the execution of the Payables purge process. This allows organizations to maintain a compliant record of payments for closed accounting periods while managing the growth of operational tables. As an "ALL" table, it is multi-organization enabled, storing data for all operating units accessible to a responsibility.

Key Information Stored

The table stores summarized attributes of purged payments. Key columns, as indicated by its foreign key relationships, include CHECK_ID (the primary key), PAYMENT_ID, and PURGE_NAME, which links the record to the specific purge job that created it. Financial details are captured through columns such as CHECK_NUMBER, CURRENCY_CODE, and CHECK_AMOUNT. The table also retains critical banking information via BANK_ACCOUNT_ID and CE_BANK_ACCT_USE_ID, linking to the bank account and its usage context. Other significant columns typically include PAYMENT_DATE, VENDOR_ID, STATUS, and DOC_SEQUENCE_ID for document sequencing. This condensed dataset provides a permanent record of the payment's key characteristics.

Common Use Cases and Queries

The primary use case is historical reporting and audit inquiry for payments that are no longer present in the active AP_CHECKS_ALL table. Common queries involve tracing payment history by vendor, bank account, or within a date range post-purge. For instance, to retrieve a summary of all purged checks for a specific vendor, one might use a query such as:

  • SELECT check_number, check_amount, currency_code, payment_date FROM ap_history_checks_all WHERE vendor_id = <VENDOR_ID> AND org_id = <ORG_ID>;

Another critical use is reconciliation with bank statements, where the historical check data can be joined to the AP_HISTORY_INV_PAYMENTS_ALL table to see which purged invoices were settled by a purged payment. Reporting on purge effectiveness, by analyzing the volume and value of records moved to history tables for a given PURGE_NAME, is also a standard administrative task.

Related Objects

AP_HISTORY_CHECKS_ALL has integral relationships with several other EBS objects. Its primary foreign key relationship is with AP_HISTORY_INV_PAYMENTS_ALL, which holds the detailed links between purged payments and their associated invoices. It references master data tables including AP_BANK_ACCOUNTS_ALL (bank account details), CE_BANK_ACCT_USES_ALL (bank account usage), FND_CURRENCIES, and FND_DOCUMENT_SEQUENCES. The FINANCIALS_PURGES table provides metadata about the purge process itself. For active payment data, the corresponding operational table is AP_CHECKS_ALL. These relationships ensure referential integrity is maintained even after data archival.