Results for “amount_adjusted”

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

Overview

AR_TRX_SUMMARY_HIST is an Oracle Receivables (AR) history table that records every modification performed on transactions where that modification affects the data stored in the Receivables summary tables. In Oracle EBS 12.1.1 and 12.2.2, summary tables such as AR_SUMMARY_TEMP and the customer balance summary structures are maintained incrementally rather than recomputed in full, and this history table provides the audit trail behind those incremental changes. Each row represents a captured event — an adjustment, an update to an amount due, a change in dispute status, or a scheduling revision — that altered the summarized position of a transaction.

Under the heuristic Data Vault classification derived from its foreign key structure, AR_TRX_SUMMARY_HIST is best modeled as a link table. It sits at the intersection of several business entities — customer accounts, customer site uses, transactions, receipts, payment schedules, and knowledge-base history records — and carries the transactional context of the change. Modeling it as a link rather than a satellite reflects its role in connecting business keys across domains while recording the event that joined them.

Key Information Stored

The table is documented with 22 columns. The most significant are summarized below.

• HISTORY_ID — surrogate primary key, enforced by the unique index AR_TRX_SUMMARY_HIST_U1. This is the business-key candidate and the single-column unique identifier for each history record.
• CUSTOMER_TRX_ID — identifies the transaction whose summary data was modified; the principal join to AR_CUSTOMER_TRX_ALL.
• CASH_RECEIPT_ID and PAYMENT_SCHEDULE_ID — identify the receipt and installment schedule affected by the change.
• PREVIOUS_HISTORY_ID — self-referencing pointer that chains successive modifications to the same transaction, enabling chronological reconstruction.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, AMOUNT_ADJUSTED, and AMOUNT_IN_DISPUTE — the monetary values before and after the change, which drive summary recalculation.
• CURRENCY_CODE and TRX_DATE — currency context and transaction date for the affected record.
• DUE_DATE — the due date associated with the affected payment schedule.
• CUSTOMER_ID and SITE_USE_ID — foreign keys to HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL respectively, providing the customer and site context.
• EVENT_NAME — the named event that triggered the history record.
• COMPLETE_FLAG and INSTALLMENTS — status and installment indicators describing the nature of the modification.
• LAST_UPDATE_DATE, CREATED_BY and the standard WHO columns — audit metadata recording who performed the change and when.

Common Use Cases and Queries

Typical applications include reconciling summary balances back to source transactions, investigating why a customer balance changed on a given date, and auditing adjustments against disputed amounts.

To trace the full change history for a transaction:

• SELECT history_id, previous_history_id, event_name, amount_due_original, amount_due_remaining, amount_adjusted, last_update_date FROM ar.ar_trx_summary_hist WHERE customer_trx_id = :p_trx_id ORDER BY history_id;

To identify all modifications for a customer within a period:

• SELECT h.history_id, h.customer_trx_id, h.event_name, h.amount_due_remaining FROM ar.ar_trx_summary_hist h WHERE h.customer_id = :p_customer_id AND h.trx_date BETWEEN :p_from AND :p_to;

To locate entries contributing to disputed balances, filter on AMOUNT_IN_DISPUTE > 0. Because the table records only changes that affect summary data, it is well suited to incremental reporting and to diagnosing summary-vs-detail mismatches.

Related Objects

• HZ_CUST_ACCOUNTS — joined via AR_TRX_SUMMARY_HIST.CUSTOMER_ID.
• HZ_CUST_SITE_USES_ALL — joined via AR_TRX_SUMMARY_HIST.SITE_USE_ID.
• CS_KB_HISTORIES_B — joined via AR_TRX_SUMMARY_HIST.HISTORY_ID.
• AR_CUSTOMER_TRX_ALL — primary transaction table referenced through CUSTOMER_TRX_ID.
• AR_CASH_RECEIPTS_ALL — receipt details referenced through CASH_RECEIPT_ID.
• AR_PAYMENT_SCHEDULES_ALL — installment and due-date data referenced through PAYMENT_SCHEDULE_ID.
• AR_SUMMARY_TEMP and related summary tables — the structures whose changes this table records.

The self-referencing relationship on PREVIOUS_HISTORY_ID should also be treated as a related object, since it drives chronological reconstruction of transaction modifications.