Search Results invoice_due_date




Overview
Explore in AI Chat

Overview

OKL_RCPT_FREIGHT_LINES_UV is an APPS-owned union view in Oracle E-Business Suite that surfaces open receivables balances attributable specifically to freight charges and receivables charges on customer invoices. Rather than presenting full invoice lines, the view exposes header-level receivables data from AR, tagged with a LINE_TYPE discriminator of either 'FREIGHT' or 'CHARGES'. It is typically consumed by Oracle Lease Management (OKL) and related receipt/collections flows where freight and charge recoveries must be reported or reconciled separately from standard invoice line amounts.

The view returns one row per qualifying payment schedule, meaning a single invoice may appear multiple times where it carries both freight and charge balances or multiple open schedules. It is read-only and intended primarily for inquiry, reporting, and integration rather than transactional processing.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through public synonyms:

  • AR_PAYMENT_SCHEDULES_ALL — supplies the due date, terms sequence, amount due original, and the freight_remaining and receivables_charges_remaining balances that drive the row selection.
  • RA_CUSTOMER_TRX_ALL — supplies invoice header attributes including transaction number, transaction ID, transaction date, operating unit, currency, and bill-to customer.

The two are joined on customer_trx_id. Union branches filter on pay_sch.status = 'OP' and pay_sch.class = 'INV', so only open invoice-class schedules qualify. The FREIGHT branch requires freight_remaining > 0; the CHARGES branch requires receivables_charges_remaining > 0.

Key Columns

  • INVOICE_NUMBER / INVOICE_ID — transaction number and customer_trx_id from the invoice header.
  • INVOICE_LINE_ID / INVOICE_LINE_NUMBER — deliberately returned as NULL; the view is header/schedule-level, not line-level.
  • INVOICE_DATE — the transaction date (trx_date) of the invoice.
  • INVOICE_DUE_DATE — the payment schedule due_date, the column most relevant to the user's search term. This is the scheduled due date of the open schedule carrying the freight or charge balance.
  • TERMS_SEQUENCE_NUMBER — payment term installment sequence associated with that schedule.
  • ORG_ID — operating unit, required for multi-org security in reporting.
  • CURRENCY_CODE — invoice currency.
  • LINE_TYPE — 'FREIGHT' or 'CHARGES', indicating which union branch produced the row.
  • BILL_TO_CUSTOMER_ID — customer on the invoice.
  • AMOUNT_DUE_ORIGINAL — original scheduled amount for the payment schedule.
  • AMOUNT_DUE_REMAINING — scalar subquery summing freight_remaining or receivables_charges_remaining across all schedules for the invoice, giving the total outstanding for that category.

Common Use Cases and Queries

Typical uses include aging freight and charge recoveries, feeding collections worklists, and reconciling lease receipts against outstanding freight.

Aging report by due date:

  • SELECT invoice_number, invoice_due_date, line_type, currency_code, amount_due_remaining FROM okl_rcpt_freight_lines_uv WHERE org_id = :p_org AND invoice_due_date < SYSDATE ORDER BY invoice_due_date;

Freight balances only:

  • SELECT invoice_number, invoice_due_date, amount_due_remaining FROM okl_rcpt_freight_lines_uv WHERE line_type = 'FREIGHT' AND org_id = :p_org;

Charge balances only:

  • SELECT invoice_number, invoice_due_date, amount_due_remaining FROM okl_rcpt_freight_lines_uv WHERE line_type = 'CHARGES';

Because no invoice_line_id is returned, line-level drill-down requires joining back to RA_CUSTOMER_TRX_LINES_ALL using invoice_id.