Search Results okl_sif_stream_types_v




Overview
Explore in AI Chat

Overview

The OKL_SIF_STREAM_TYPES_V view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 belongs to the OKL - Lease and Finance Management product family, commonly referred to as Oracle Lease Management (OLM). The view is owned by the APPS schema and is documented with a status of VALID. Its stated purpose is to expose the stream types generated for a lease or finance transaction originating from an external pricing engine. In practice, the view serves as a reporting and integration surface over the underlying staging table that captures pricing engine output before it is consumed by downstream lease authoring, booking, or accounting processes.

Because the view is a thin projection over a single base table, it provides read-only, denormalized access to records used during the pricing interface workflow. Consultants and developers query this view when validating that pricing results have been correctly imported, when reconciling stream definitions against booked contracts, or when building outbound extracts for reporting tools such as Oracle BI Publisher or custom concurrent programs.

Underlying Base Objects

The view is defined exclusively over the base object OKL_SIF_STREAM_TYPES, referenced through a SYNONYM in the APPS schema. This base table stores stream type records produced by the SIF (Stream Interface File / external pricing interface) process. The view contains no joins, unions, or aggregations; it is a straight SELECT projecting every column of the base table, with ROWID aliased as ROW_ID.

The alias SITB is used for the base table in the defining query. Because the view maps one-to-one with the base table, all DML against the underlying table is reflected immediately, and no materialized or cached data is involved. The view therefore inherits the base table's partitioning, indexing, and security characteristics.

Key Columns

  • ID — Primary identifier of the stream type record (surrogate key from the base table).
  • ROW_ID — The ROWID of the base table row, useful for identified-row updates and duplicate detection.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OLM framework to detect concurrent updates.
  • SIF_ID — Foreign key to the SIF header record, tying the stream type to a specific pricing engine interface run or transaction.
  • STY_ID — Identifier of the stream type definition; relates to the stream type setup used to classify cash flows (for example, rent, residual, or fee streams).
  • SIL_ID — The identifier most commonly searched by users ("sil_id"). It links the stream type record to the associated stream interface line or stream item, connecting pricing output to the corresponding contract-level stream.
  • SFE_ID — Identifier of the stream, fee, or element to which the type applies within the pricing structure.
  • PRICING_NAME — Descriptive name assigned by the external pricing engine, used for human-readable identification during reconciliation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking record provenance and modification history.

Common Use Cases and Queries

Typical use cases include verifying that pricing engine output loaded correctly, tracing a given SIL_ID to its stream type, and auditing recently created records. A representative query follows:

SELECT id,
       sif_id,
       sty_id,
       sil_id,
       sfe_id,
       pricing_name,
       creation_date
FROM   apps.okl_sif_stream_types_v
WHERE  sil_id = :p_sil_id;

To audit records loaded for a specific interface run:

SELECT sil_id,
       pricing_name,
       last_update_date
FROM   apps.okl_sif_stream_types_v
WHERE  sif_id = :p_sif_id
ORDER BY sil_id;

Because the view exposes the base table's ROWID and OBJECT_VERSION_NUMBER, it is also suitable as a data source for OAF-based pages, correction scripts, and integration extracts that must respect optimistic locking. Queries should always be schema-qualified with APPS. and respect the standard OLM responsibility-based security, since the view itself applies no row-level filtering.