Search Results sgn_code




Overview
Explore in AI Chat

Overview

OKL_STREAMS_H is a history table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, holding streams history details. Streams in OKL represent the scheduled cash flows, payment structures, and contractual financial events associated with a lease or loan contract. The history table preserves prior or versioned snapshots of stream records, enabling audit trails, point-in-time reconstruction, and change tracking across the contract lifecycle.

The table resides in the OKL schema and is valid in both EBS 12.1.1 and 12.2.2. The documented physical schema contains 29 columns, with the primary key OKL_STREAMS_H_PK defined on (ID, MAJOR_VERSION). A secondary unique index, STMH_STM_UK, is defined on (MAJOR_VERSION, KHR_ID, KLE_ID, TRANSACTION_NUMBER, STY_ID). Under the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as standalone; that classification is a modeling suggestion, indicating the table functions largely independently within the mined FK graph rather than serving as a canonical hub, link, or satellite in a Data Vault sense. Its MAJOR_VERSION column nonetheless gives it a versioned, history-satellite character over stream data.

Key Information Stored

The most significant columns fall into identity, linkage, and audit groups:

  • ID — Surrogate identifier for the stream record; combines with MAJOR_VERSION in the primary key OKL_STREAMS_H_PK.
  • MAJOR_VERSION — Version discriminator that, together with ID, uniquely identifies a historical row and forms part of the business-key candidate STMH_STM_UK.
  • KHR_ID — Foreign key to OKL_PRTFL_CNTRCTS_B, linking the stream history row to its parent contract in the portfolio.
  • KLE_ID — Reference to the lease or contract line/entity context for the stream.
  • TRANSACTION_NUMBER — Transaction identifier that, with the other business key columns, supports uniqueness in STMH_STM_UK.
  • STY_ID — Stream type reference that categorizes the stream (for example, payment, billing, or accrual schedules); part of the unique business key.
  • STM_ID — Identifier of the corresponding current stream record, allowing history rows to be mapped back to their live source.
  • SOURCE_ID / SOURCE_TABLE / TRX_ID / LINK_HIST_STREAM_ID — Traceability columns identifying the originating record, table, transaction, and linked historical stream.
  • SGN_CODE / SAY_CODE — Sign and code attributes governing the directional and classification semantics of the stream amount.
  • ACTIVE_YN — Active flag indicating whether the historical row is current.
  • DATE_CURRENT, DATE_WORKING, DATE_HISTORY — Date context columns marking when the stream was current, when it was effective, and when it was historized.
  • PURPOSE_CODE — Classifies the purpose of the stream history entry.
  • OBJECT_VERSION_NUMBER — Optimistic locking version used by the ORM framework.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE capture who and which concurrent program created or modified the row.

Common Use Cases and Queries

Typical uses include reconstructing the stream schedule for a contract as of a specific date, auditing changes to stream definitions, and reconciling current streams against their historical versions. A representative query joins history to the contract and the current stream:

  • Retrieve latest history for a contract: SELECT h.ID, h.MAJOR_VERSION, h.STY_ID, h.ACTIVE_YN, h.DATE_HISTORY FROM OKL_STREAMS_H h WHERE h.KHR_ID = :contract_id ORDER BY h.MAJOR_VERSION DESC;
  • Compare current and historical streams: join OKL_STREAMS_H to the current OKL_STREAMS table on STM_ID = ID to identify changed stream types or amounts.
  • Historical as-of reporting: filter on DATE_HISTORY and DATE_CURRENT to present the schedule in effect at a chosen reporting date.
  • Audit reporting: group by LAST_UPDATED_BY, CREATION_DATE, and PROGRAM_ID to trace which process versioned the stream.
  • Source tracing: use SOURCE_TABLE, SOURCE_ID, and TRX_ID to follow a history row back to the originating transaction.

Related Objects

  • OKL_PRTFL_CNTRCTS_B — Parent contract table; joined via OKL_STREAMS_H.KHR_ID = KHR_ID.
  • OKL_STREAMS — The current (non-history) stream table, related through STM_ID and the shared ID/MAJOR_VERSION pattern.
  • OKL_STREAM_TYPES / STY_ID reference — Table supplying stream type definitions for STY_ID.
  • OKL_K_LEASES / KLE_ID reference — Lease/line entity source for KLE_ID.
  • OKL_TRX_* transaction tables — Traceability targets for TRX_ID and SOURCE_TABLE.
  • OKL_STREAMS_H_PK / STMH_STM_UK — Primary and unique indexes enforcing identity and business-key uniqueness.
  • OKL Lease Management APIs — Public APIs that generate and version stream records, writing history rows into this table.