Search Results okl_rcpt_freight_lines_uv




Overview
Explore in AI Chat

Overview

OKL_RCPT_FREIGHT_LINES_UV is an APPS-owned database view in the Oracle E-Business Suite Leasing and Finance Management (OKL) product. Its stated purpose, per the ETRM metadata, is to fetch open invoices whose freight and charges remaining are greater than zero. The view therefore acts as a reporting and integration surface that isolates the freight and receivables-charges components of open (unpaid) customer invoices, rather than presenting the full invoice balance.

The name carries the conventional Oracle suffix _UV, denoting a user-facing view intended for query, reporting, and downstream consumption rather than for transactional update. It exposes a controlled projection over Oracle Receivables data that would otherwise require joins between payment schedules and customer transactions. This makes it relevant to reconciliation, collections, and receipt-application reporting within the leasing and finance domain.

Because the view filters on open status and on non-zero freight or charge remainders, it returns only the subset of invoices where these ancillary amounts are still outstanding. A user searching for invoice_line_number in connection with this object should note that the view does not derive a line number from the receivables line tables; it returns a literal NULL for that column.

Underlying Base Objects

The documented base objects referenced by the view are two synonyms: AR_PAYMENT_SCHEDULES_ALL and RA_CUSTOMER_TRX_ALL, both resolving in the APPS schema. AR_PAYMENT_SCHEDULES_ALL supplies installment-level payment scheduling data, including status, class, due dates, terms sequence, and the freight and receivables charge remaining balances. RA_CUSTOMER_TRX_ALL supplies invoice header attributes such as transaction number, customer transaction identifier, transaction date, organization identifier, currency code, and bill-to customer.

The join is a simple equality between AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_TRX_ID and RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID. The view is a UNION ALL of two select blocks, one for freight and one for charges, each applying the same header-level filters. No other base objects are documented in the ETRM metadata.

Key Columns

Common Use Cases and Queries

Typical uses include collections reporting on freight and charge balances, reconciliation between Receivables payment schedules and leasing receipts, and integration extracts feeding downstream freight settlement processes. The following query lists open freight and charge balances by invoice and operating unit.

  • SELECT invoice_number, invoice_id, line_type, org_id, currency_code, amount_due_remaining FROM okl_rcpt_freight_lines_uv WHERE org_id = :p_org_id ORDER BY invoice_number, line_type;
  • SELECT line_type, SUM(amount_due_remaining) FROM okl_rcpt_freight_lines_uv GROUP BY line_type;
  • SELECT * FROM okl_rcpt_freight_lines_uv WHERE invoice_number = :p_invoice_number;

Because INVOICE_LINE_NUMBER is always NULL, queries expecting a line-level identifier will not succeed through this view. Where line detail is required, the underlying Receivables line tables must be queried separately using INVOICE_ID as the join key. All access should be read-only, respecting the reporting intent of the view.