Search Results line_balance




Overview
Explore in AI Chat

Overview

APPS.AR_LL_FREIGHT_CHARGES_V is an Oracle E-Business Suite view, owned by the APPS schema, that consolidates freight and charges activity associated with cash receipts and their corresponding customer transaction lines. The view is defined in the Oracle Receivables module and is available in both EBS 12.1.1 and 12.2.2. Its primary purpose is to present aggregated freight and charges amounts at the level of a cash receipt, a customer transaction, and the apply-to relationship between them.

The view is particularly relevant to users searching for the freight_amount column, since FREIGHT_AMOUNT is one of the principal measures exposed. Because the underlying definition aggregates data from AR_ACTIVITY_DETAILS and RA_CUSTOMER_TRX_LINES, the view is best understood as a reporting and integration aid rather than a transactional entity. It shields downstream reports, forms, and interfaces from the denormalized detail stored in the activity table, returning one summarized row per cash receipt and customer transaction combination for lines whose line type is FREIGHT or CHARGES.

Underlying Base Objects

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

  • AR_ACTIVITY_DETAILS (SYNONYM) — aliased as ll in the view text. This table supplies the receipt-level activity measures, including allocated_receipt_amount, freight, charges, freight_discount, comments, source_table, current_activity_flag, and auditing columns such as creation_date, created_by, last_update_date, and last_update_login.
  • RA_CUSTOMER_TRX_LINES (SYNONYM) — aliased as line. This table provides the transaction line context: customer_trx_line_id, customer_trx_id, line_number, line_type, and amount_due_remaining (exposed as line_balance).

The join between the two objects is on customer_trx_line_id. The view restricts the result set to lines where line_type is 'FREIGHT' or 'CHARGES', where nvl(ll.source_table, 'RA') = 'RA', and where nvl(ll.current_activity_flag, 'Y') = 'Y'. It then groups by cash_receipt_id, customer_trx_id, and apply_to, applying aggregate functions such as SUM, MIN, and MAX across the remaining columns.

Key Columns

  • FREIGHT_AMOUNT — the summed freight value from AR_ACTIVITY_DETAILS, the column most commonly searched by users.
  • CHARGES_AMOUNT — the summed charges value from the same source.
  • AMOUNT — a decoded measure returning the freight value for FREIGHT lines and the charges value for CHARGES lines.
  • ALLOCATED_RECEIPT_AMOUNT — the summed receipt amount allocated to the associated activity.
  • CASH_RECEIPT_ID — the receipt identifier used as a grouping key.
  • CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID / LINE_NUMBER — transaction and line identifiers; the line identifiers are minimized during aggregation.
  • APPLY_TO — the apply-to indicator from AR_ACTIVITY_DETAILS, converted to character and included in the group-by clause.
  • LINE_DISCOUNT — the summed freight_discount value.
  • LINE_BALANCE — the summed amount_due_remaining from RA_CUSTOMER_TRX_LINES.
  • OBJECT_VERSION_NUMBER, CREATED_BY_MODULE, COMMENTS, and audit columns — carried through for concurrency control and traceability.

Common Use Cases and Queries

Typical usage centers on reconciling freight and charges against receipts and transactions, and on supplying summarized freight values to custom reports or interfaces. A representative query retrieving freight and charges for a given receipt is:

SELECT cash_receipt_id,
       customer_trx_id,
       apply_to,
       freight_amount,
       charges_amount,
       allocated_receipt_amount,
       line_balance
FROM   apps.ar_ll_freight_charges_v
WHERE  cash_receipt_id = :p_cash_receipt_id;

To review freight activity for a specific transaction line set, query by customer_trx_id and order by line_number. Because the view aggregates, filters on non-grouped attributes should be applied with care, and joins back to RA_CUSTOMER_TRX_ALL or AR_CASH_RECEIPTS_ALL are commonly added to obtain customer or receipt metadata. The view's reliance on current_activity_flag and source_table means it reflects only current, Receivables-sourced activity, which is an important consideration when reconciling against historical or foreign-source data.