Search Results link_fee_asset




Overview
Explore in AI Chat

Overview

The view APPS.OKL_CS_PAYMENT_SUMMARY_UV is an Oracle E-Business Suite (EBS) reporting object that belongs to the Enterprise Contracts / Oracle Lease and Finance Management (OKL) module and is exposed through the ETRM (Enterprise Transaction and Reporting Model) layer. In EBS 12.1.1 and 12.2.2, this object presents a consolidated summary of payment streams associated with contracts and contract lines, aggregating stream type, contract header, status, stream amount, and currency. Its primary role is to serve as a unified, query-friendly source of payment and stream information for reporting, integration, and downstream processing, particularly where the amount to be paid for a given stream depends on the contract and the associated line or asset.

The view is defined as a UNION of two SELECT branches, which indicates that it deliberately merges two populations of records: streams that have no associated contract line key (KLE_ID is null), and streams that are linked to a specific contract line and line style. This design supports both header-level and line-level payment summaries in a single result set.

Underlying Base Objects

The documented base objects referenced by the view are: FND_GLOBAL (package), FND_LOOKUPS (view), OKC_K_HEADERS_B (synonym), OKC_K_LINES_V (view), OKC_LINE_STYLES_V (view), OKL_CS_LC_CONTRACT_PVT (package), OKL_STREAMS (synonym), OKL_STRM_TYPE_B (synonym), and OKL_STRM_TYPE_TL (synonym).

The OKL_STREAMS entity supplies the core payment stream rows, joined to OKL_STRM_TYPE_B and OKL_STRM_TYPE_TL to obtain stream type identifiers and language-translated names. OKC_K_HEADERS_B provides the contract header (contract number and currency code). The view uses the OKL_CS_LC_CONTRACT_PVT package, specifically the get_total_stream_amount function, to compute the stream amount dynamically by contract (KHR_ID), optional line ID (KLE_ID), and stream type (STY_ID). FND_LOOKUPS is joined on lookup type 'OKL_STREAM_ACTIVITY' to translate the status code (say_code) into a status meaning. In the second branch, OKC_K_LINES_V and OKC_LINE_STYLES_V are joined via an outer join to resolve the contract line name and line type code (LTY_CODE).

Key Columns

  • STM_ID — identifier of the payment stream row.
  • KHR_ID — contract header identifier linking the stream to its contract.
  • STREAM_TYPE / STY_ID — the stream type name and identifier.
  • ASSET_NUMBER — derived from KLE.NAME for line types such as FREE_FORM1, LINK_SERV_ASSET, and LINK_FEE_ASSET; null in the header-only branch.
  • KLE_ID — contract line identifier, present only in the line-level branch.
  • CONTRACT_NUMBER / CURRENCY_CODE — from the contract header.
  • LINE_TYPE / LINE_TYPE_CODE — the line style name and code (LSE.NAME, LSE.LTY_CODE).
  • STATUS_CODE / STATUS — the raw stream activity code and its FND_LOOKUPS meaning.
  • AMOUNT — the total stream amount returned by okl_cs_lc_contract_pvt.get_total_stream_amount.

Common Use Cases and Queries

This view is typically used to report billable streams and their payment amounts per contract and per linked asset, and to reconcile stream activity. A user searching for "link_serv_asset" is likely targeting the LINE_TYPE_CODE 'LINK_SERV_ASSET' branch, which surfaces service asset lines with their asset numbers and amounts.

A representative query is:

  • SELECT contract_number, stream_type, asset_number, line_type, status, amount, currency_code FROM apps.okl_cs_payment_summary_uv WHERE line_type_code = 'LINK_SERV_ASSET' AND contract_number = :p_contract;
  • SELECT contract_number, SUM(amount) total_amount FROM apps.okl_cs_payment_summary_uv GROUP BY contract_number;
  • SELECT * FROM apps.okl_cs_payment_summary_uv WHERE kle_id IS NULL;

These queries illustrate header-level aggregation, line-level filtering by line style, and separation of header-only streams, respectively.