Search Results discount_amt
Overview
AR_TA_VRH_MTRX_V is a reporting view in the Oracle Receivables (AR) module that consolidates matched transaction and remittance history data produced by the AutoCash / Cash Engine matching process. Its name reflects its purpose: "TA" (Transaction Application / Trade Application), "VRH" (Remittance History), and "MTRX" (Match Matrix). The view is designed to present the results of remittance matching — including any discount taken, unearned discount, and the discount basis applied — in a form suitable for reconciliation, reporting, and downstream integration. It surfaces the discount decision logic executed by the Cash Engine against a payment schedule, which is why a search for "discount_amt" leads here.
The view is defined with a join to AR_PAYMENT_SCHEDULES using an outer-join condition (MATCHED_TRX_ID = CUSTOMER_TRX_ID(+)), meaning matched transactions are returned even where no corresponding payment schedule row exists. It filters specifically to rows created by the Cash Engine (CREATED_FROM = 'CASH_ENGINE') and to a single historical record type (RECORD_TYPE = 6). This narrow filtering makes AR_TA_VRH_MTRX_V a targeted diagnostic and reconciliation object rather than a general purpose receivables view.
Underlying Base Objects
The view is defined over two documented base tables:
- AR_TA_REMIT_HIST (aliased RH) — the remittance history table that records each matching event and its associated discount parameters. This is the driving table.
- AR_PAYMENT_SCHEDULES (aliased PS) — the payment schedule table supplying the due date and installment status for the matched transaction.
The ETRM metadata excerpt does not document the owner schema or other referenced objects, and lists no additional base objects. Note that the record set is restricted by CREATED_FROM and RECORD_TYPE, so the view exposes only a subset of the underlying remittance history. The ETRM excerpt also states the view is "Not implemented in this database," indicating it may be present in specific environments only.
Key Columns
- BATCH_NAME, CHECK_NUMBER — identifiers of the remittance batch and check from which the match originated.
- CASH_RECEIPT_ID — the cash receipt that funded the application.
- HISTORY_LINE_ID — the primary remittance history line identifier.
- MATCHED_TRX_NUMBER, MATCHED_TRX_TYPE — the transaction number and type that were matched.
- DUE_DATE, STATUS — from AR_PAYMENT_SCHEDULES; the installment due date and current status.
- APPLICATION_STATUS — status of the application of the receipt.
- AMOUNT — the transaction amount being considered for application.
- DISCOUNT_BASIS_USED, DISCOUNT_DATE_BASIS_USED — the discount calculation basis and date basis elected during matching.
- DISCOUNT_DATE_USED — the effective date applied when testing discount eligibility.
- UNEARNED_DISCOUNT — portion of the discount earned but not yet taken, carried forward.
- FULL_DISCOUNT_FLAG — indicates whether the full discount was earned.
- DISCOUNT_GRACE_DAYS_USED — grace days consumed in the discount test.
- AMOUNT_APPLIED — NVL-wrapped applied amount (0 when null).
- DISCOUNT_AMT — NVL-wrapped discount amount actually taken; the column most relevant to a "discount_amt" search.
Common Use Cases and Queries
Typical scenarios include reconciling discount amounts captured by the Cash Engine, auditing why a discount was or was not granted, and validating unearned discount carry-forward against the payment schedule.
Sample query listing discounts taken per matched transaction:
- SELECT BATCH_NAME, CHECK_NUMBER, MATCHED_TRX_NUMBER, DUE_DATE, STATUS, DISCOUNT_BASIS_USED, DISCOUNT_DATE_USED, AMOUNT_APPLIED, DISCOUNT_AMT FROM AR_TA_VRH_MTRX_V WHERE DISCOUNT_AMT > 0 ORDER BY BATCH_NAME, MATCHED_TRX_NUMBER;
To isolate transactions where a discount was available but not fully applied, filter on UNEARNED_DISCOUNT or FULL_DISCOUNT_FLAG. Because the view restricts output to CREATED_FROM = 'CASH_ENGINE' and RECORD_TYPE = 6, results reflect only automated Cash Engine matching activity, which should be accounted for when comparing against manual applications in AR_TA_REMIT_HIST.
-
View: AR_TA_VRH_MTRX_V
12.2.2
product: AR - Receivables , implementation_dba_data: Not implemented in this database ,
-
View: AR_TA_VRH_MTRX_V
12.1.1
product: AR - Receivables , implementation_dba_data: Not implemented in this database ,
-
View: AR_TA_REMIT_HIST
12.1.1
product: AR - Receivables , description: SINGLE_ORG view , implementation_dba_data: Not implemented in this database ,
-
View: AR_TA_REMIT_HIST
12.2.2
product: AR - Receivables , description: SINGLE_ORG view , implementation_dba_data: Not implemented in this database ,
-
View: AR_TA_ESS_LINE_V
12.1.1
product: AR - Receivables , implementation_dba_data: Not implemented in this database ,
-
View: AR_TA_ESS_LINE_V
12.2.2
product: AR - Receivables , implementation_dba_data: Not implemented in this database ,
-
PACKAGE: APPS.ONT_OEXPRPRD_XMLP_PKG
12.2.2
-
PACKAGE: APPS.ONT_OEXPRPRD_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.ONT_OEXPRPRD_XMLP_PKG
12.2.2
-
PACKAGE BODY: APPS.ONT_OEXPRPRD_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.FII_AP_INV_LINES_F_C
12.1.1
-
APPS.FII_AP_INV_LINES_F_C dependencies on EDW_LOG
12.1.1
-
APPS.FII_AP_INV_LINES_F_C dependencies on FII_UTIL
12.1.1