Search Results history_line_id




Overview
Explore in AI Chat

Overview

AR_TA_VRH_DEDU_V is a Receivables (AR) reporting view that consolidates data from the Trade Management / Advanced Receivables remittance history and payment schedules model. Its central purpose is to expose the remittance workflow events handled by the Cash Engine so that deduction, chargeback, and adjustment transactions generated automatically can be reviewed alongside their originating bank remittance attributes. The view joins remittance history records to the newly created transaction and its payment schedule, thereby presenting both the transaction identifier (such as a transaction number) and financial measures such as original amount and remaining balance. The name and prefix indicate a Trade/AR remittance history ("VRH") deduction ("DEDU") view, and the WHERE clause filter on CREATED_FROM = 'CASH_ENGINE' combined with RECORD_TYPE = 7 restricts the output to rows generated by the Cash Engine processing deduction-type records.

Underlying Base Objects

The view is defined over three base objects:

  • AR_TA_REMIT_HIST — the remittance history table (aliased RH), which supplies the batch name, check number, history line identifiers, new transaction type, promotion number, adjustment identifier, application status, and the created-from / record-type discriminator columns.
  • AR_PAYMENT_SCHEDULES — the payment schedules table (aliased PS), which supplies the original amount due and the remaining balance due for the new transaction, along with its status.
  • RA_CUSTOMER_TRX — the customer transactions table (aliased CT), which supplies the transaction number of the new transaction.

The join predicate links RH.NEW_TRX_ID to both CT.CUSTOMER_TRX_ID and PS.CUSTOMER_TRX_ID, so a row appears only when the remittance history record's resulting transaction exists in both the transaction and payment schedule tables. Because the metadata indicates the object is "Not implemented in this database" and that no base objects are formally documented in the ETRM 12.2.2 metadata, the relationships described above are derived directly from the view text rather than from documented dependency registrations.

Key Columns

  • BATCH_NAME — the remittance batch into which the source payment was grouped.
  • CHECK_NUMBER — the instrument associated with the remittance.
  • HISTORY_LINE_ID — the unique identifier of the remittance history line; the primary key of the row in the remittance history table.
  • PARENT_HISTORY_LINE_ID — the identifier of the parent history line, allowing reconstruction of multi-step remittance processing chains.
  • NEW_TRX_TYPE — the transaction type of the transaction created as a result of the remittance event.
  • PROMOTION_NUMBER and ADJUSTMENT_ID — references to the promotion and adjustment used when generating the deduction.
  • TRX_NUMBER — the transaction number of the newly created customer transaction.
  • ORIGINAL_AMOUNT / BALANCE_DUE — original amount due and remaining open balance from the payment schedule.
  • STATUS — the payment schedule status of the new transaction.
  • APPLICATION_STATUS — the remittance history application status.

Common Use Cases and Queries

Typical use cases include reconciling Cash Engine deductions, tracing a remittance batch to the transactions it generated, and auditing adjustments applied during automatic receipt application.

SELECT batch_name, check_number, history_line_id,
       parent_history_line_id, trx_number,
       original_amount, balance_due, status
FROM   ar_ta_vrh_dedu_v
WHERE  history_line_id = :history_line_id;

The history_line_id search term reflects the most common access pattern: retrieving a specific remittance event and its created transaction. Queries can also aggregate by batch to compare total deduction amounts against applied receipts.