Search Results okl_sif_rets_v




Overview
Explore in AI Chat

Overview

OKL_SIF_RETS_V is a VALID Oracle E-Business Suite view owned by the APPS schema and defined within the OKL – Leasing and Finance Management product family. Its documented purpose is to hold the header details for the data returned by the external pricing engine. In the Oracle Leasing and Finance Management (OKL) flow, pricing and yield calculations are frequently delegated to an external pricing or "stream interface" engine; the results of that call are staged and subsequently consumed by ETRM processes. OKL_SIF_RETS_V presents the header-level portion of those returned results, while a companion structure holds the associated stream or detail lines.

Because the object is a view rather than a table, it is not a storage container but a presentation layer exposing a curated set of columns to reporting tools, concurrent programs, and integration code. The suffix "_V" and the "_SIF_" naming convention indicate the "Stream Interface" family of objects used to bridge ETRM with the external pricing engine. The view is available in both Oracle EBS 12.1.1 and 12.2.2, and the documented metadata reflects the ETRM 12.2.2 dictionary.

Underlying Base Objects

The documented base object referenced by OKL_SIF_RETS_V is OKL_SIF_RETS, exposed in the view definition as a SYNONYM. The view is a straightforward single-source SELECT from that synonym, aliased as SIRB, and performs no joins, unions, or aggregations. Consequently the view is updatable/insertable in the same manner as the underlying synonym, and it functions as an interface access point rather than a derived or computed result set. The ROWID of the base row is projected as ROW_ID, which allows consumers to identify and lock individual base records. Applications should treat OKL_SIF_RETS as the authoritative base table and OKL_SIF_RETS_V as the supported read interface over it.

Key Columns

Common Use Cases and Queries

Typical uses include troubleshooting external pricing calls, reconciling engine results against ETRM contracts, and building custom reports. A basic inspection query follows:

  • SELECT transaction_number, srt_code, yield_name, effective_pre_tax_yield, implicit_interest_rate, date_processed FROM apps.okl_sif_rets_v WHERE transaction_number = :p_txn;
  • SELECT id, transaction_number, request_id, program_id, date_processed FROM apps.okl_sif_rets_v WHERE date_processed >= :p_from_date ORDER BY date_processed;
  • SELECT transaction_number, stream_interface_attribute01, stream_interface_attribute02 FROM apps.okl_sif_rets_v WHERE srt_code = :p_srt_code;

These queries support yield analysis, concurrency diagnostics via REQUEST_ID, and validation that the external pricing engine populated the expected header fields.