Search Results stream_type_purpose




Overview
Explore in AI Chat

Overview

APPS.OKL_TRX_LINE_UV is a union view in the Oracle E-Business Suite (EBS) Lease and Finance Management (formerly Oracle Lease Management, OKL) module, part of the Enterprise Transaction/Contract Management (ETRM) schema. It presents a consolidated, transaction-level list of lease contract line items, merging two distinct sources of line data: contract stream lines and asset-level lines associated with lease transactions. The view is intended to serve as a unified read-only reporting and integration surface, presenting line amounts, currencies, and descriptive attributes in a single, denormalized row set. Because it exposes a resolved stream type purpose via a lookup-meaning function call, it is particularly useful where downstream consumers must display human-readable classifications rather than raw lookup codes.

Underlying Base Objects

The view is defined over the following documented base objects:

The contract-line branch is the only branch carrying stream type data; the asset branch returns NULL for STREAM_TYPE and STREAM_TYPE_PURPOSE, reflecting its distinct purpose and column availability.

Key Columns

  • ID — Line identifier (OTCL.ID or ASL.ID).
  • LINE_NUMBER — Line sequence number.
  • DESCRIPTION — Line description (line text for contract lines, manufacturer name for asset lines).
  • AMOUNT — Line amount (OTCL.AMOUNT or ASL.MATCH_AMOUNT).
  • CURRENCY_CODE — Currency of the line.
  • STREAM_TYPE — Stream type name from OKL_STRM_TYPE_V; NULL for asset lines.
  • STREAM_TYPE_PURPOSE — Lookup meaning derived from OKL_STREAM_TYPE_PURPOSE; NULL for asset lines. This is the column corresponding to the stream_type_purpose search term.
  • TRANSACTION_ID — Parent transaction reference (OTCL.TCN_ID or ASL.TAS_ID).
  • SOURCE_TABLE — Literal identifying the originating table ('OKL_TXL_CNTRCT_LNS' or 'OKL_TXL_ASSETS_B'), enabling provenance tracking.
  • KHR_ID — Knowledge/contract header reference (OTCL.KHR_ID or ASL.DNZ_KHR_ID).

Common Use Cases and Queries

Typical scenarios include reconciling transaction lines across sources, reporting by stream type purpose, and filtering lines to a specific transaction or contract header. The SOURCE_TABLE literal supports branching logic where consumers must distinguish line origins.

Query a single transaction:

SELECT ID, LINE_NUMBER, DESCRIPTION, AMOUNT, CURRENCY_CODE,
       STREAM_TYPE, STREAM_TYPE_PURPOSE, SOURCE_TABLE
FROM   APPS.OKL_TRX_LINE_UV
WHERE  TRANSACTION_ID = :p_transaction_id
ORDER BY SOURCE_TABLE, LINE_NUMBER;

Report by stream type purpose:

SELECT STREAM_TYPE_PURPOSE, COUNT(*) line_count, SUM(AMOUNT) total_amount
FROM   APPS.OKL_TRX_LINE_UV
WHERE  SOURCE_TABLE = 'OKL_TXL_CNTRCT_LNS'
GROUP BY STREAM_TYPE_PURPOSE;

Filter by contract header:

SELECT ID, LINE_NUMBER, AMOUNT, CURRENCY_CODE, STREAM_TYPE
FROM   APPS.OKL_TRX_LINE_UV
WHERE  KHR_ID = :p_khr_id;

Note that the union imposes NULL stream columns for asset lines; queries relying on STREAM_TYPE_PURPOSE should constrain SOURCE_TABLE accordingly to avoid unintended exclusion of rows.