Search Results ar_ll_lines_groups_v




Overview
Explore in AI Chat

Overview

AR_LL_LINES_GROUPS_V is a Receivables (AR) view owned by the APPS schema that exposes line-level and group-level detail used by the Line-Level Cash Application feature in Oracle E-Business Suite. Line-Level Cash Application allows a receipt to be applied against individual transaction lines (and their associated tax lines) rather than against an invoice header in aggregate. The view consolidates the activity detail records that store the applied amounts, discounts, and tax amounts for each receipt line, and joins them to the customer transaction lines they settle.

Because the view flattens and normalizes the underlying application detail across receipt lines, invoice lines, and tax lines, it is the natural reporting source for questions about how a given cash receipt was distributed across the lines of one or more transactions. It is read-only by design; it is not intended for direct DML but for queries, reports, and integration extracts that require line-level application granularity. Its status is VALID in both 12.1.1 and 12.2.2, and its structure is consistent across those releases.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • AR_ACTIVITY_DETAILS — the primary driver, aliased as LL. It stores the line-level cash application records: the receipt, the transaction line, the allocated amount, tax, discounts, and descriptive attributes.
  • RA_CUSTOMER_TRX_LINES — aliased as LINE for the invoice line being applied to, and referenced again through an inline aggregate subquery aliased as TAX that sums tax-line balances grouped by transaction and linked line.

A UNION combines the per-line detail with a summarized grouping of the same activity details (aggregated by receipt, with CUSTOMER_TRX_LINE_ID set to 0), which produces the group-level rows. In the line branch, the query restricts to LINE_TYPE = 'LINE', excludes APPLY_TO values of 'FREIGHT' and 'CHARGES', limits SOURCE_TABLE to 'RA', and requires CURRENT_ACTIVITY_FLAG to be 'Y'. The tax balance is attached through an outer join on the tax subquery.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling receipts to invoice lines, reporting unapplied or partially applied lines, and auditing line-level application detail for cash application troubleshooting.

List line-level applications for a receipt:

  • SELECT CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, LINE_NUMBER, AMOUNT, TAX, AMOUNT_APPLIED, LINE_BALANCE, TAX_BALANCE FROM AR_LL_LINES_GROUPS_V WHERE CASH_RECEIPT_ID = :receipt_id ORDER BY CUSTOMER_TRX_LINE_ID;

Identify lines with a remaining balance after application:

  • SELECT CASH_RECEIPT_ID, CUSTOMER_TRX_ID, LINE_NUMBER, LINE_BALANCE + NVL(TAX_BALANCE,0) BALANCE_DUE FROM AR_LL_LINES_GROUPS_V WHERE CUSTOMER_TRX_LINE_ID > 0 AND NVL(LINE_BALANCE,0) + NVL(TAX_BALANCE,0) > 0;

Aggregate applied amounts by transaction:

  • SELECT CUSTOMER_TRX_ID, SUM(AMOUNT_APPLIED) TOTAL_APPLIED FROM AR_LL_LINES_GROUPS_V WHERE CUSTOMER_TRX_LINE_ID > 0 GROUP BY CUSTOMER_TRX_ID;

Because the view restricts APPLY_TO and SOURCE_TABLE and relies on the CURRENT_ACTIVITY_FLAG, queries return only current, RA-sourced line applications, making it suitable for point-in-time reconciliation without additional filtering.