Results for “okl_streams_pk”

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

Overview

OKL_STREAMS is a core transaction table within the Oracle Leasing and Finance Management (OKL) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The table holds the payment header details for lease and finance contracts, functioning as the orchestrating header record for a stream of scheduled payment, billing, or cash-flow activity. Each row represents one payment stream attached to a contract, and the table ties together the contract header, the contract line, and the stream type definition that governs how the stream behaves.

The ETRM documentation classifies this table by heuristic as satellite-leaning within a Data Vault model. This is consistent with its structure: OKL_STREAMS carries descriptive and state attributes (dates, status codes, source tracking, audit columns) around a business key, rather than serving as a pure hub of business entities or a pure link between hubs. The uniqueness constraint OKL_STM_U3, composed of STY_ID, KHR_ID, TRANSACTION_NUMBER, and KLE_ID, reinforces that the table describes one stream per contract/line/type/transaction combination.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• ID — the surrogate primary key (OKL_STREAMS_PK) and the column referenced by dependent tables.
• KHR_ID — foreign key to OKL_K_HEADERS, identifying the contract header to which the payment stream belongs.
• KLE_ID — foreign key to OKL_K_LINES, identifying the specific contract line for the stream.
• STY_ID — foreign key to OKL_STRM_TYPE_B, the stream type definition controlling stream behavior and grouping.
• TRANSACTION_NUMBER — the business-facing transaction identifier, part of the OKL_STM_U3 unique index.
• STM_ID — a stream identifier used for lineage or source-stream linkage within the contract structure.
• SGN_CODE — sign code indicating the direction (positive/negative) of the payment stream.
• SAY_CODE — a status or system action code governing the stream's lifecycle state.
• ACTIVE_YN — flag indicating whether the stream is currently active.
• DATE_CURRENT, DATE_WORKING, DATE_HISTORY — the effective, working, and historical date reference points that drive stream scheduling and versioning.
• PURPOSE_CODE — classifies the business purpose of the stream.
• SOURCE_ID, SOURCE_TABLE, TRX_ID — source-tracking columns identifying the originating transaction and table.
• PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic-locking columns.
• LINK_HIST_STREAM_ID — links the stream to its historical stream record for version tracking.

The surrogate key ID is distinct from the business-key candidate captured by OKL_STM_U1 (ID) and the composite OKL_STM_U3 (STY_ID, KHR_ID, TRANSACTION_NUMBER, KLE_ID); the latter is the true business identifier for a stream.

Common Use Cases and Queries

Typical usage centers on reconstructing a contract's payment schedule, reporting active streams by type, and reconciling streams to their contract header and line. A common reporting query joins OKL_STREAMS to OKL_K_HEADERS and OKL_STRM_TYPE_B:

SELECT s.ID, s.TRANSACTION_NUMBER, s.SGN_CODE, s.ACTIVE_YN, t.STY_CODE, h.CONTRACT_NUMBER FROM OKL.OKL_STREAMS s, OKL.OKL_K_HEADERS h, OKL.OKL_STRM_TYPE_B t WHERE s.KHR_ID = h.ID AND s.STY_ID = t.ID AND s.ACTIVE_YN = 'Y';

Analysts also filter by DATE_CURRENT or DATE_WORKING to isolate the currently effective schedule, and use SOURCE_TABLE/SOURCE_ID/TRX_ID to trace streams back to their originating transaction. Because OKL_POOL_CONTENTS and OKL_STRM_ELEMENTS reference STM_ID, streams frequently act as the anchor for pool participation and element-level detail reporting.

Related Objects

• OKL_K_HEADERS — joined on OKL_STREAMS.KHR_ID = OKL_K_HEADERS.ID; the parent contract header.
• OKL_K_LINES — joined on OKL_STREAMS.KLE_ID = OKL_K_LINES.ID; the contract line.
• OKL_STRM_TYPE_B — joined on OKL_STREAMS.STY_ID = OKL_STRM_TYPE_B.ID; the stream type definition.
• OKL_STRM_ELEMENTS — child table referencing OKL_STRM_ELEMENTS.STM_ID = OKL_STREAMS.ID; holds stream element detail.
• OKL_POOL_CONTENTS — child table referencing OKL_POOL_CONTENTS.STM_ID = OKL_STREAMS.ID; links streams to pools.

These relationships confirm OKL_STREAMS as the central payment-header hub for contract-level stream data within the OKL module.