Results for “okl_transaction_type_name”

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

Overview

The view APPS.OKL_AR_CUST_TRX_LINES_L_V is a Receivables (AR) reporting construct used within the Oracle E-Business Suite ETRM (Enterprise Contracts / Lease Management) module. It presents a language-enabled, denormalized projection of Accounts Receivable customer transaction lines enriched with Oracle Lease Management contract attributes. The "_L_" naming convention indicates that one or more columns are language-sensitive, resolved at runtime using a session-bound language identifier surfaced as the LANGUAGE column through the OKL_LANGUAGE alias.

Functionally the view serves as a bridge between standard Receivables transaction data and lease/contract metadata maintained in the OKL schema family. Instead of forcing report authors and integration developers to reconstruct the join logic themselves, it exposes a curated flat result set that couples each AR customer transaction line with its originating lease event, agreement status, transaction type, stream type, and inventory organization. This makes it well suited to operational reporting on invoicing and receivables activity generated by lease contracts, and to interface programs that must reconcile AR lines back to their contractual origin.

Underlying Base Objects

The view is defined over two documented base objects, joined in the view text:

• AR_CUST_TRX_LINES_L_V — the standard Receivables customer transaction lines view, referenced with the alias ACTL. It supplies the core transaction line identity and language context.
• OKL_AR_INV_KHR_IA_REF_VL — an OKL (Lease Management) reference view, aliased OAIKA, which contributes the lease-specific descriptive attributes such as agreement status, contract status, stream type, transaction type name, line description, and inventory organization name.

The join predicate is documented as ACTL.TRX_LINE_ATTR14 = OAIKA.OKL_TXD_ID. This means the AR transaction line's descriptive flexfield attribute 14 (TRX_LINE_ATTR14) stores the lease transaction detail identifier that links the Receivables line back to its lease context. Both base objects are themselves views, so the lineage terminates in underlying APPLSYS/AR and OKL base tables rather than directly in tables, but the documented dependency is explicitly on these two views.

Key Columns

• EVENT_ID — identifier of the lease event associated with the transaction line, used to trace an AR line back to its originating contractual event.
• LINE_NUMBER — the Receivables transaction line number, preserving order and identity within the transaction.
• LEDGER_ID — the ledger context of the transaction, enabling set-of-books/ledger-based reporting.
• LANGUAGE (aliased from OKL_LANGUAGE) — the language in which language-sensitive attributes are rendered.
• OKL_CONTRACT_STATUS — status of the underlying lease contract.
• OKL_INV_AGRMNT_STATUS — status of the invoicing agreement; this is the column most commonly sought by users searching for invoicing-agreement status in lease invoicing workflows.
• OKL_STREAM_TYPE_NAME — descriptive name of the lease stream type (e.g., billing or revenue stream classification).
• OKL_TRANSACTION_TYPE_NAME — the lease transaction type name associated with the line.
• OKL_TRANS_LINE_DESCRIPTION — descriptive text for the lease transaction line.
• OKL_INVENTORY_ORG_NAME — name of the inventory organization linked to the leased asset, where applicable.

Common Use Cases and Queries

Typical scenarios include reconciling AR invoices to lease agreements, reporting on invoicing-agreement status by contract, and validating that lease-generated receivables carry the expected stream and transaction type classifications.

• Listing AR transaction lines with their lease agreement status for a ledger.
• Filtering lines by OKL_CONTRACT_STATUS or OKL_STREAM_TYPE_NAME for operational dashboards.
• Joining back to lease events via EVENT_ID for drill-down reporting.

Sample query:

SELECT event_id,
       line_number,
       ledger_id,
       okl_contract_status,
       okl_inv_agrmnt_status,
       okl_stream_type_name,
       okl_transaction_type_name,
       okl_inventory_org_name
FROM   apps.okl_ar_cust_trx_lines_l_v
WHERE  okl_inv_agrmnt_status = 'ACTIVE'
AND    ledger_id = :p_ledger_id
ORDER BY event_id, line_number;

Because the view inherits language handling from the AR base view, reports should confirm the effective LANGUAGE value when multi-language installations are in use.