Results for “late_charge_ass_yn”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKL_BPD_LEASING_PAYMENT_TRX_V view resides in the APPS schema and is owned by the Oracle Lease and Finance Management (OKL) module. It is a denormalized reporting view designed to expose leasing payment transaction data spanning lease contracts, consolidated billing headers and lines, consolidated streams, receivables invoices, and customer master records. Its principal role is to support Business Process Definition (BPD) reporting and integration scenarios where leasing payment schedules must be reconciled with their originating lease contracts and corresponding Oracle Receivables transactions.

The view joins Receivables payment schedules (AR_PAYMENT_SCHEDULES_ALL) to the OKL consolidated AR stream and line tables, thereby enabling users to trace a receivables invoice back to the lease contract, contract line, and stream that generated it. Customer identification flows through the Trading Community Architecture (TCA) via HZ_CUST_ACCOUNTS and HZ_PARTIES, while contract header information is retrieved from OKC_K_HEADERS_ALL_B. Stream type and invoice line type descriptions are resolved through the corresponding _B/_TL translation pairs.

Underlying Base Objects

The view is defined over eleven documented base objects, all referenced through APPS synonyms:

  • AR_PAYMENT_SCHEDULES_ALL — supplies receivables invoice number, transaction date, due dates, amount due original, amount due remaining, class, and status.
  • OKL_CNSLD_AR_STRMS_B — the consolidated AR stream, providing contract ID, contract line ID, stream ID, stream type ID, tax amount, receivables invoice ID, and late charge flag.
  • OKL_CNSLD_AR_LINES_B — consolidated AR line, supplying line sequence number, line type, and invoice line type ID.
  • OKL_CNSLD_AR_HDRS_B — consolidated AR header, providing currency, invoice date, consolidated invoice number, customer ID, and legal entity ID.
  • OKL_STRM_TYPE_B and OKL_STRM_TYPE_TL — stream type definition and translated name.
  • OKL_INVC_LINE_TYPES_B and OKL_INVC_LINE_TYPES_TL — invoice line type definition and translated name.
  • OKC_K_HEADERS_ALL_B — lease contract header, supplying the contract number.
  • HZ_CUST_ACCOUNTS and HZ_PARTIES — customer account number and party name.

The view applies an outer join to the invoice line type tables (denoted by (+)) and restricts to PS.CLASS IN ('INV','CM'), so only invoice and credit memo payment schedules are returned. The stream type translation is filtered by the session language (USERENV('LANG')).

Key Columns

Common Use Cases and Queries

The view is typically used to reconcile lease billing streams with receivable transactions, investigate outstanding lease receivables, and feed downstream reports on lease payment activity. A representative query returning all leasing payment transactions for a contract is shown below:

SELECT contract_number,
       consolidated_invoice_number,
       receivables_invoice_number,
       trx_date,
       due_date,
       customer_name,
       amount_due_original,
       amount_due_remaining,
       status
FROM   apps.okl_bpd_leasing_payment_trx_v
WHERE  contract_number = :p_contract_number
ORDER  BY trx_date;

To aggregate open balances by stream type, the view can be grouped as follows:

SELECT stream_name,
       SUM(amount_due_remaining) open_balance
FROM   apps.okl_bpd_leasing_payment_trx_v
WHERE  status != 'CLOSED'
GROUP  BY stream_name;

Because the view is read-only and built entirely from base transactional and setup tables, it carries no special privileges beyond SELECT granted to appropriate reporting responsibilities. Confirming details of the stream and line type translations requires the correct session language, and any direct query should therefore be executed under a user whose LANG environment setting matches the stored OKL_STRM_TYPE_TL and OKL_INVC_LINE_TYPES_TL rows.