Search Results payment_history_id




Overview
Explore in AI Chat

Overview

The AP_PAYMENT_HISTORY_ALL table is a core transactional table within the Oracle E-Business Suite Payables module (AP). It serves as the system of record for tracking the complete lifecycle and financial reconciliation history of payments issued. Its primary role is to maintain an immutable audit trail that captures the maturity and reconciliation status changes for payments, such as checks, electronic funds transfers, and wire payments. This history is critical for financial reporting, audit compliance, and troubleshooting payment-related accounting entries. As an "ALL" table, it is multi-org enabled, storing data for all operating units configured within the instance, with access typically controlled by the MO: Security Profile responsibility.

Key Information Stored

The table's structure is designed to log discrete events in a payment's lifecycle. The primary key, PAYMENT_HISTORY_ID, uniquely identifies each historical entry. Two critical foreign key relationships define its core purpose. The CHECK_ID column links each history record to its parent payment in the AP_CHECKS_ALL table. The ACCOUNTING_EVENT_ID column links the history entry to the corresponding accounting event in the AP_ACCOUNTING_EVENTS_ALL table, creating a direct tie to the General Ledger. While the provided metadata does not list all columns, typical data stored includes timestamps for status changes (e.g., printed, reconciled, voided), the payment status at that point, reconciliation references like bank statement information, and identifiers for the reconciliation batch. The self-referential foreign key on PAYMENT_HISTORY_ID suggests a potential hierarchical relationship between history entries, possibly for correcting or reversing prior history records.

Common Use Cases and Queries

This table is essential for reconciliation reporting and payment lifecycle audits. A common use case is generating a report of all payments that reached a specific status within a date range, such as identifying checks cleared by the bank. Analysts also query it to trace the accounting events generated for a particular payment or to diagnose discrepancies between Payables and bank statement balances. A typical query pattern joins AP_PAYMENT_HISTORY_ALL to AP_CHECKS_ALL and AP_ACCOUNTING_EVENTS_ALL to get a complete picture.

  • Sample Query: To find the reconciliation history for a specific check number: SELECT aph.* FROM ap_payment_history_all aph, ap_checks_all ac WHERE aph.check_id = ac.check_id AND ac.check_number = '12345' ORDER BY aph.creation_date;
  • Reporting Use Case: Reconciling the Payables payments register to the bank statement by joining history records with a status of 'RECONCILED' to bank statement lines.

Related Objects

AP_PAYMENT_HISTORY_ALL is centrally connected to other key Payables and accounting tables. Its primary relationship is with the AP_CHECKS_ALL table, which holds the master payment record. It is also intrinsically linked to the AP_ACCOUNTING_EVENTS_ALL table, which triggers the creation of accounting entries in GL. For reporting, standard Oracle Payables views such as AP_CHECKS_ALL_V may aggregate data from this history table. Key APIs, particularly those related to payment confirmation, reconciliation, and voiding processes (e.g., AP_PAYMENT_UTILITY_PKG), will insert records into this table to document each procedural step.