Search Results lin_balance

Overview

APPS.AR_LL_SUMMARY_V is an Oracle E-Business Suite Receivables (AR) reporting and integration view that consolidates activity-level detail from AR_ACTIVITY_DETAILS into a summarized, transaction-oriented format. Its central purpose is to aggregate "line-level" (LL) accounting and allocation figures — amounts, tax, freight, charges, discounts, and remaining balances — grouped by cash receipt and customer transaction. The name reflects its origin in the AR activity/allocation engine (the LL prefix), which links cash receipts to transactions through the AR_ACTIVITY_DETAILS table.

The view exposes a single row per unique combination of CASH_RECEIPT_ID and CUSTOMER_TRX_ID, rolling up multiple activity rows using SUM and MAX aggregates. Because it exposes ALLOCATED_RECEIPT_AMOUNT as a first-class column, it is a common target when users search for how an applied receipt amount against a given transaction is stored and reported. In practice, the view supports reconciliation reporting, cash application analysis, and downstream integration extracts where a compact, aggregated receipt-to-transaction picture is required.

Underlying Base Objects

The view is defined over two documented base objects:

• AR_ACTIVITY_DETAILS (accessed via synonym) — the core allocation/activity table. In the view text it is aliased ll and supplies ALLOCATED_RECEIPT_AMOUNT, line/tax/freight/charge amounts, discounts, comments, module, version, and audit columns.
• RA_CUSTOMER_TRX_LINES (accessed via synonym) — aliased ctl for the transaction line, joined via ctl.customer_trx_line_id = ll.customer_trx_line_id.

The view is built as a UNION ALL of multiple activity branches (a line branch, and additional branches such as tax, freight, and charges), then wrapped by an outer aggregation query. Within the first branch, a secondary inline subquery over RA_CUSTOMER_TRX_LINES (aliased ctltax) rolls up TAX line type rows, grouped by link_to_cust_trx_line_id, to obtain tax balances. The join is made outer ((+)) and is filtered by nvl(ll.source_table,'RA') = 'RA' and nvl(ll.CURRENT_ACTIVITY_FLAG,'Y') = 'Y'. Audit columns are reduced with MAX, while monetary and balance columns are reduced with SUM, producing the summarized grain.

Key Columns

• CASH_RECEIPT_ID — the receipt; part of the grouping key.
• CUSTOMER_TRX_ID — the transaction being applied; part of the grouping key.
• ALLOCATED_RECEIPT_AMOUNT — summed allocated receipt amount, the primary measure users search on.
• LINE, TAX, FREIGHT, CHARGES — summed component amounts.
• LIN_DISCOUNT, TAX_DISCOUNT, FRT_DISCOUNT — summed discount amounts.
• LIN_BALANCE, TAX_BALANCE, FRT_BALANCE, CHG_BALANCE — remaining balances (from amount_due_remaining).
• COMMENTS, CREATED_BY_MODULE, OBJECT_VERSION_NUMBER — descriptive/technical attributes (MAX).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — audit columns (MAX).

Common Use Cases and Queries

Typical uses include receipt-to-transaction reconciliation, cash application reporting, and integration extracts. A representative query retrieving allocated amounts for a receipt is:

• SELECT cash_receipt_id, customer_trx_id, allocated_receipt_amount, lin_balance, tax_balance FROM apps.ar_ll_summary_v WHERE cash_receipt_id = :receipt_id;
• Aggregating applied amounts per transaction: SELECT customer_trx_id, SUM(allocated_receipt_amount) FROM apps.ar_ll_summary_v GROUP BY customer_trx_id;
• Identifying open balances: SELECT * FROM apps.ar_ll_summary_v WHERE lin_balance > 0 OR tax_balance > 0;

Because the view is granted to APPS and used in reporting, queries should be schema-qualified and filter on indexed identifiers (CASH_RECEIPT_ID, CUSTOMER_TRX_ID) to constrain the underlying union and aggregation cost.