Search Results ap_payment_hist_dists_n1




Overview

AP.AP_PAYMENT_HIST_DISTS is a transaction-table within the Oracle E-Business Suite Payables (AP) module that stores payment distribution lines generated by the Payables accounting process. The table is populated during the pre-processing phase of the accounting extract, which is triggered when a Payables user launches the create accounting program. Each row represents a single distribution of a payment accounting event, capturing how a payment amount is allocated across invoice distributions, currencies, and functional amounts for subledger accounting and general ledger transfer.

The table was introduced as the child of AP.AP_PAYMENT_HIST (APH). Where each row in APH represents a payment accounting event, AP_PAYMENT_HIST_DISTS holds the many distribution rows that belong to that event. This parent-child construct allows a single payment accounting event to be decomposed into multiple accounting lines — for example, across invoice distributions, withheld amounts, or bank-currency versus functional-currency components.

Mined from its foreign-key structure, the table leans toward a satellite classification in a Data Vault model. It describes the descriptive and quantitative attributes of a payment accounting event (the parent hub/link), rather than acting as a standalone hub or as a pure association link. This classification is heuristic and intended as a modeling suggestion; in EBS-native terms the table functions as a detail/child table to APH.

Key Information Stored

The surrogate primary key is PAYMENT_HIST_DIST_ID, a NUMBER(15) column. This is also the business-key candidate in the sense that it is enforced by the unique index AP_PAYMENT_HIST_DISTS_U1, the only unique index documented on the table.

The table carries standard EBS Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus concurrent-program context columns (PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_LOGIN_ID, PROGRAM_UPDATE_DATE). The documented physical schema at 12.2.2 lists 36 columns in total, stored in the APPS_TS_TX_DATA tablespace with PCT Free 10.

Common Use Cases and Queries

Typical uses include reconciliations between payments and their accounting distributions, verification of multi-currency payment accounting, and audit of reversal handling. A common pattern joins distributions to the parent history table and to the invoice payment:

  • Trace a payment accounting event: join AP_PAYMENT_HIST_DISTS.PAYMENT_HISTORY_ID to AP.AP_PAYMENT_HIST and aggregate by ACCOUNTING_EVENT_ID.
  • Reconcile invoice payments: join INVOICE_PAYMENT_ID to AP_INVOICE_PAYMENTS_ALL to compare AMOUNT against the recorded payment.
  • Currency analysis: compare AMOUNT, BANK_CURR_AMOUNT, and CLEARED_BASE_AMOUNT to detect rounding or exchange-rate differences.
  • Reversal reporting: filter on REVERSAL_FLAG and trace REVERSED_PAY_HIST_DIST_ID to the original row.
  • Upgrade validation: filter on HISTORICAL_FLAG to separate legacy-converted distributions from newly created ones.

A representative query retrieves distributions for a given payment history with their invoice payment context:

  • SELECT d.PAYMENT_HIST_DIST_ID, d.PAY_DIST_LOOKUP_CODE, d.AMOUNT, d.BANK_CURR_AMOUNT, d.CLEARED_BASE_AMOUNT, ip.INVOICE_PAYMENT_ID
  • FROM AP.AP_PAYMENT_HIST_DISTS d, AP.AP_INVOICE_PAYMENTS_ALL ip
  • WHERE d.INVOICE_PAYMENT_ID = ip.INVOICE_PAYMENT_ID
  • AND d.PAYMENT_HISTORY_ID = :history_id;

Indexes AP_PAYMENT_HIST_DISTS_N1 through N5 support lookups by PAYMENT_HISTORY_ID, INVOICE_DISTRIBUTION_ID, ACCOUNTING_EVENT_ID, PA_ADDITION_FLAG, and INVOICE_PAYMENT_ID respectively, which reflect the dominant reporting access paths.

Related Objects

  • AP.AP_PAYMENT_HIST — parent table of payment accounting events; join on AP_PAYMENT_HIST_DISTS.PAYMENT_HISTORY_ID = AP_PAYMENT_HIST.PAYMENT_HISTORY_ID.
  • AP.AP_INVOICE_PAYMENTS_ALL — documented foreign-key target via INVOICE_PAYMENT_ID.
  • AP.AP_INVOICE_DISTRIBUTIONS_ALL — referenced through INVOICE_DISTRIBUTION_ID for the underlying invoice distribution detail.
  • XLA accounting events / AP subledger accounting views — related through ACCOUNTING_EVENT_ID.
  • AP.AP_PAYMENT_SCHEDULES_ALL — supplies invoice payment schedule context for the distributions.
  • AP.AP_INVOICES_ALL — reachable via invoice payment and distribution joins for invoice-level reporting.
  • Payables Create Accounting concurrent program — the process that populates this table.
  • GL_JE_LINES / GL transfer views — consume the resulting accounting entries derived from these distributions.