Search Results tax_balance




Overview
Explore in AI Chat

Overview

AR_LL_SUMMARY_V is an Oracle Receivables (AR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide a "Summary for Line-Level Cash Application." The view aggregates transactional data captured during the application of cash receipts against customer transaction lines, consolidating allocation amounts and remaining balances at the grain of a cash receipt and customer transaction pair (CASH_RECEIPT_ID, CUSTOMER_TRX_ID).

Functionally, it rolls up line-level cash application activity into a single summarized row per receipt/transaction combination. It is not a base table but a read-only query object intended for reporting, inquiry, and integration scenarios where a consolidated picture of applied amounts and outstanding balances—including tax—is required without traversing detail tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both exposed in the APPS schema as synonyms:

  • AR_ACTIVITY_DETAILS (SYNONYM) — the line-level cash application detail source (aliased LL in the view text), supplying allocated receipt amounts, discounts, comments, and audit columns.
  • RA_CUSTOMER_TRX_LINES (SYNONYM) — the customer transaction lines table (aliased CTL), joined to activity details on CUSTOMER_TRX_LINE_ID. The view additionally derives tax balances through an inline aggregate subquery (aliased CTLTAX) over RA_CUSTOMER_TRX_LINES filtered to LINE_TYPE = 'TAX', grouped by LINK_TO_CUST_TRX_LINE_ID.

The join structure uses a standard line-type filter (CTL.LINE_TYPE = 'LINE') plus an outer join to the tax subquery, incorporating a documented defect fix (BUG FIX 5503852) in the tax aggregation logic. Because the view aggregates with SUM and MAX over this joined set, it presents one summarized row per CASH_RECEIPT_ID / CUSTOMER_TRX_ID pair.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling applied receipt amounts to transaction balances, reporting tax still outstanding on a transaction, and feeding downstream integrations that require summarized application data.

  • Retrieving tax balance for a specific transaction: SELECT CUSTOMER_TRX_ID, TAX_BALANCE, TAX, TAX_DISCOUNT FROM AR_LL_SUMMARY_V WHERE CUSTOMER_TRX_ID = :trx_id;
  • Listing summary balances for a receipt: SELECT CASH_RECEIPT_ID, CUSTOMER_TRX_ID, ALLOCATED_RECEIPT_AMOUNT, LIN_BALANCE, TAX_BALANCE FROM AR_LL_SUMMARY_V WHERE CASH_RECEIPT_ID = :receipt_id;
  • Identifying transactions with remaining tax: SELECT CUSTOMER_TRX_ID, TAX_BALANCE FROM AR_LL_SUMMARY_V WHERE TAX_BALANCE > 0;

Because aggregation is performed within the view, queries should apply filters on the grouping keys or exposed summary columns rather than attempting to re-aggregate component detail. This view is best used for summarized reporting and should not be treated as a substitute for line-level detail views when drill-down is required.