Search Results extended_amount




Overview
Explore in AI Chat

Overview

APPS.AR_INVOICE_TOTALS_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module that consolidates invoice line amounts into summary totals per transaction. It categorizes amounts into tax, freight, and other line components using the LINE_TYPE discriminator found on receivable transaction lines. The view is defined only over transactions whose complete flag is set and whose transaction type is configured with a primary printing option, which restricts the result set to finalized, printable invoices.

Because it aggregates at the CUSTOMER_TRX_ID level, the view is typically consumed in reporting, dashboards, and downstream integrations that require header-level financial totals without traversing the line detail. The line_type column that a user searches for is the central pivot of the view's DECODE logic, determining whether a given line's extended amount is attributed to tax, freight, or ordinary line amounts.

Underlying Base Objects

The view is defined over three base objects, each referenced through an APPS synonym in the 12.2.2 metadata:

The three objects are joined on CUSTOMER_TRX_ID and CUST_TRX_TYPE_ID, and the header rows are further constrained by TRX.COMPLETE_FLAG = 'Y' and TYPES.DEFAULT_PRINTING_OPTION = 'PRI'.

Key Columns

  • CUSTOMER_TRX_ID — the transaction identifier and the sole grouping key, linking each result row to its invoice header.
  • TOTAL_TAX_AMOUNT — the sum of EXTENDED_AMOUNT across lines where LINE_TYPE = 'TAX'.
  • TOTAL_FREIGHT_AMOUNT — the sum of EXTENDED_AMOUNT across lines where LINE_TYPE = 'FREIGHT'.
  • TOTAL_LINE_AMOUNT — the sum of EXTENDED_AMOUNT for lines that are neither FREIGHT nor TAX, representing the core item line total.
  • TOTAL_AMOUNT — the sum of all EXTENDED_AMOUNT values across every line, i.e., the aggregate transaction extended amount.

Note that LINE_TYPE itself is not projected as a column; it is used internally within DECODE expressions to partition the amounts.

Common Use Cases and Queries

Typical usage includes reconciling invoice headers against their line detail, building AR reporting extracts, and validating printing eligibility. A representative query retrieving totals for a single transaction is:

  • SELECT customer_trx_id, total_line_amount, total_tax_amount, total_freight_amount, total_amount FROM apps.ar_invoice_totals_v WHERE customer_trx_id = :trx_id;

To compare the view's tax total against an independently computed line-level tax amount:

  • SELECT t.customer_trx_id, t.total_tax_amount, SUM(l.extended_amount) line_tax FROM apps.ar_invoice_totals_v t, apps.ra_customer_trx_lines l WHERE t.customer_trx_id = l.customer_trx_id AND l.line_type = 'TAX' GROUP BY t.customer_trx_id, t.total_tax_amount;

Because the view filters on COMPLETE_FLAG and DEFAULT_PRINTING_OPTION = 'PRI', results exclude incomplete transactions and transaction types not marked for primary printing, which should be accounted for when reconciling against AR aging or standard receipt-based reports.