Search Results okl_streams_v




Overview
Explore in AI Chat

Overview

OKL_STREAMS_V is a view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, delivered as part of the OKL — Leasing and Finance Management product family. The view holds the payment header details for lease and finance transactions. In the ETRM data model, a "stream" represents a discrete set of financial movements — payments, billings, or cash flows — associated with a contract, and the stream header is the parent record that groups those movements. OKL_STREAMS_V exposes that header-level information in a flattened, query-friendly form.

From a reporting and integration standpoint, the view provides a stable, read-only projection over the base stream table, making it suitable for concurrent programs, Oracle Reports, BI Publisher data templates, OAF-based inquiry pages, and third-party integrations that need to read lease payment stream headers without navigating the full normalized structure. Because the view is defined as a simple projection with no joins or filters, it preserves the row cardinality of the underlying table and inherits its transactional semantics.

Underlying Base Objects

The view is defined over a single documented base object: OKL_STREAMS, referenced in the source metadata as a synonym owned by APPS. The view text performs a direct column-by-column selection from OKL_STREAMS (aliased STMB), including the ROWID projected as ROW_ID to support row-level addressing by Oracle Forms and other tools that require a unique row identifier. No additional tables are joined, and no WHERE clause is applied, so the view returns every row present in OKL_STREAMS, including inactive streams.

Columns STY_ID, KLE_ID, and KHR_ID are foreign key references into other OKL entities (stream type, lease/contract, and related header structures), but these are exposed as raw identifiers rather than resolved descriptions. Consumers requiring descriptive attributes must join outward to the corresponding OKL lookup and entity tables. The presence of SOURCE_ID, SOURCE_TABLE, and TRX_ID indicates that streams carry origin-tracking information linking them back to the transaction or document that generated them.

Key Columns

  • ID / STM_ID — Primary and stream identifiers for the header record; STM_ID is typically the functional key used in downstream joins.
  • TRANSACTION_NUMBER — The user-visible document or transaction number associated with the stream.
  • PURPOSE_CODE — Classifies the business purpose of the stream (the specific attribute surfaced in the user's search). This is the primary discriminator for filtering streams by intent, such as term-related versus ancillary payment flows. Reporting queries seeking a particular category of payment stream should filter on this column.
  • SGN_CODE, SAY_CODE, STY_ID — Sign, activity/type code, and stream type identifier; together these drive how the stream is classified and signed in financial calculations.
  • KLE_ID, KHR_ID — Identifiers linking the stream to its lease/contract and related header context.
  • ACTIVE_YN — Indicates whether the stream is currently active; essential for point-in-time reporting.
  • DATE_CURRENT, DATE_WORKING, DATE_HISTORY — Stream lifecycle dates supporting current, working, and historical views of the record.
  • SOURCE_ID, SOURCE_TABLE, TRX_ID, LINK_HIST_STREAM_ID — Provenance and lineage columns identifying the originating transaction and any historical stream linkage.
  • Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the concurrent program audit columns (PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE), plus OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Typical scenarios include listing active payment streams for a contract, isolating streams by purpose for reconciliation, and feeding lease cash-flow extracts into downstream reporting. A representative query filtering on the searched attribute is:

SELECT transaction_number, purpose_code, sty_id, kle_id, sgn_code, active_yn, date_current
FROM apps.okl_streams_v
WHERE purpose_code = :p_purpose_code
AND active_yn = 'Y';

To retrieve all streams belonging to a specific lease, query by KLE_ID; to trace origin, select SOURCE_TABLE, SOURCE_ID, and TRX_ID. Because the view is unfiltered, always apply predicates such as ACTIVE_YN or date ranges to bound result sets. Underlying DML is not supported through this view in standard practice; inserts and updates should target OKL_STREAMS through the supported OKL APIs to preserve validation and versioning behavior.