Results for “k_line_code”

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

Overview

OKL_LINE_STREAMS_UV is a consolidated reporting view owned by the APPS schema within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It presents contractual line-level payment streams together with their associated stream elements, exposing a flattened, denormalized projection that joins contract headers, contract lines, line styles, items, stream types, and individual cash flow elements. The view is a UNION ALL query, combining two distinct stream derivation paths: one bound to the contract line itself and a second path for streams sourced through related line items. Because the view spans both OKC (Contracts Core) and OKL (Leasing) base objects, it is a primary integration and reporting surface for lease accounting, revenue recognition, and cash flow analysis.

The view derives its significance from the fact that lease payment schedules in EBS are stored as hierarchical stream definitions, not as simple flat rows. Streams represent the recurring or one-time financial flows attached to a contract line, and stream elements represent the dated amounts that belong to a specific stream. OKL_LINE_STREAMS_UV collapses this hierarchy into a single row per stream element, which makes it practical for ad hoc queries, discoverer-style reports, and downstream interfaces to sub-ledger or treasury systems.

Underlying Base Objects

The ETRM metadata lists the following referenced objects, all accessed through APPS synonyms in a standard 12.1.1 / 12.2.2 environment:

• OKC_K_HEADERS_B — the base contract header table, supplying CONTRACT_ID and CONTRACT_NUMBER.
• OKC_K_LINES_B and OKC_K_LINES_TL — the base and translated contract line tables, supplying LINE_ID and the line description.
• OKC_LINE_STYLES_B — the line style table, filtered to LTY_CODE = 'FEE'.
• OKC_K_ITEMS — the contract line item table, used to associate each physical line with one or more item definitions, including the "K line" item (STYA).
• OKL_STRM_TYPE_B, OKL_STRM_TYPE_TL (aliased STYB/STYT and separately STYA) — the stream type base and translated tables, providing the stream name, short description, and stream type purpose code.
• OKL_STREAMS — the stream header table, providing the activity code, transaction number, and purpose code.
• OKL_STRM_ELEMENTS — the stream element detail table, providing STREAM_ELEMENT_DATE and AMOUNT.
• OKL_ACCOUNTING_UTIL — a PL/SQL package whose GET_LOOKUP_MEANING function decodes lookup codes for stream type purpose, stream activity, and stream general purpose.
• OKX_SYSTEM_ITEMS_V — referenced for item validation and the "K line" name mapping.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER — the contract header identifier and user-visible number.
• LINE_ID — the unique identifier of the contract line to which the stream belongs.
• K_LINE_NAME — the descriptive name of the "K line" item associated with the contract line. This is the column behind the common search term "k_line_name" and the primary label for the stream's originating line.
• K_LINE_CODE — the line style code, typically 'FEE' given the filter applied in the view.
• NAME — the translated name of the stream type (from OKL_STRM_TYPE_TL).
• STREAM_TYPE_PURPOSE_CODE / STREAM_TYPE_PURPOSE — the raw code and its decoded lookup meaning describing the stream's role (for example, payment, billing, or financing).
• STREAM_ELEMENT_DATE / AMOUNT — the effective date and monetary value of each individual stream element, which together form the cash flow schedule.
• ACTIVITY_CODE / ACTIVITY — the stream activity code and its decoded lookup meaning.
• TRANSACTION_NUMBER — the transaction number associated with the stream.
• PURPOSE_CODE / PURPOSE — the general purpose code and its decoded meaning.
• SHORT_DESCRIPTION — a short descriptive text for the stream type.

Common Use Cases and Queries

Typical scenarios include extracting the full scheduled cash flow for a lease contract, reconciling stream amounts against accounting entries, and building dashboards that surface "K line" names alongside their periodic payment amounts. The following query retrieves the payment schedule for a specific contract:

• SELECT contract_number, line_id, k_line_name, name, stream_element_date, amount FROM apps.okl_line_streams_uv WHERE contract_number = :p_contract_number ORDER BY line_id, stream_element_date;
• SELECT k_line_name, activity, SUM(amount) FROM apps.okl_line_streams_uv WHERE stream_element_date BETWEEN :start_date AND :end_date GROUP BY k_line_name, activity;
• SELECT DISTINCT k_line_name, k_line_code, name, stream_type_purpose FROM apps.okl_line_streams_uv WHERE contract_id = :p_contract_id;

Because the view is a UNION ALL, deduplication at the query level may be required when item-based and line-based stream derivations overlap. Performance is generally acceptable when filtering by CONTRACT_ID or CONTRACT_NUMBER, since these columns anchor the join to the contract header.