Search Results ar_ta_remit_hist_all

Overview

AR_TA_REMIT_HIST_ALL is a Receivables module table that stores the application details of all Receipts and Receipt lines processed by the Oracle Cash Engine (Cash Management remittance processing). When receipts are submitted through AutoLockbox, manual remittance batches, or the Cash Engine's receipt application workflows, the resulting application records are captured in this history table. It functions as a persistent ledger of how cash was applied against customer transactions, providing a stable, queryable record separate from the live application tables.

Based on the foreign key structure mined from the table definition, the object exhibits a satellite-leaning Data Vault classification. Its single documented foreign key to HZ_CUST_ACCOUNTS, combined with a single-column surrogate primary key on HISTORY_LINE_ID, suggests this table behaves primarily as a descriptive detail store (satellite) hanging off a customer hub. In Data Vault modeling terms, one might model it as a satellite keyed to the customer hub, with HISTORY_LINE_ID serving as a degenerate or surrogate identifier.

Under Oracle EBS 12.1.1 / 12.2.2, the table is documented as "Not implemented in this database" in the ETRM reference, meaning it is not seeded or populated by default and is typically instantiated only when the Cash Engine remittance history feature is configured or exercised.

Key Information Stored

Because the table captures receipt and receipt-line application details, the most significant columns include:

• HISTORY_LINE_ID — The surrogate primary key (AR_TA_REMIT_HIST_PK), uniquely identifying each history line.
• CUSTOMER_ID — Foreign key to HZ_CUST_ACCOUNTS, linking the remittance history record to the paying customer.
• Receipt identifier and receipt number columns, tying the record back to the originating cash receipt.
• Receipt line and application reference columns, describing which transaction the receipt was applied to.
• Application amount, currency, and exchange rate columns capturing the value applied.
• Remittance batch and deposit reference columns identifying the bank and deposit context.
• Application date, GL date, and status columns reflecting posting state and timing.

The documented surrogate primary key is HISTORY_LINE_ID. CUSTOMER_ID is the principle documented business-key candidate via its foreign key relationship to HZ_CUST_ACCOUNTS; additional business keys (receipt number, batch name) are typically combined with HISTORY_LINE_ID to form unique composite identifiers in practice.

Common Use Cases and Queries

Typical scenarios include auditing cash application history, reconciling Cash Engine output, and reporting on applied receipts by customer. A representative query joining to the customer hub is:

• SELECT h.history_line_id, h.customer_id, c.account_number
  FROM ar_ta_remit_hist_all h, hz_cust_accounts c
  WHERE h.customer_id = c.cust_account_id;
• Aggregating applied amounts by customer or remittance batch for month-end cash reporting.
• Tracing a specific receipt or receipt line backward through the Cash Engine's processing history for dispute or reconciliation purposes.

Related Objects

The most significant related objects include:

• HZ_CUST_ACCOUNTS — joined via AR_TA_REMIT_HIST_ALL.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID; the sole documented foreign key.
• AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY_ALL — source receipt records from which remittance history is derived.
• AR_RECEIVABLE_APPLICATIONS_ALL — holds the live application detail that this history table mirrors.
• AR_BATCHES_ALL — remittance and lockbox batch context.
• AR_TA_REMIT_HIST related views or synonyms exposing the same data.

These objects together allow consultants to reconstruct the full cash application lifecycle across the Cash Engine.