Search Results okl_stream_interfaces




Overview
Explore in AI Chat

Overview

The OKL_STREAM_INTERFACES table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to serve as the interface and staging table for contract header-level details during the process of external pricing. This table acts as the central repository for incoming pricing data from external systems before it is validated, processed, and integrated into the core leasing contracts within the application. It is fundamental to the external pricing integration workflow, ensuring that complex financial calculations for leases and other financing agreements can be sourced from specialized third-party pricing engines.

Key Information Stored

The table stores metadata and identifiers that link external pricing data to internal contract structures. Based on the provided ETRM metadata, the most critical columns include the primary key ID and the unique key combination of KHR_ID and TRANSACTION_NUMBER. The KHR_ID is a foreign key that links directly to the OKL_K_HEADERS table, which is the master table for all lease contracts. This linkage is essential for associating the external pricing results with the correct contract. The TRANSACTION_NUMBER likely serves to uniquely identify a specific pricing request or batch for a given contract, allowing for versioning or multiple pricing scenarios. The table's structure, as indicated by its foreign key relationships, is designed to be a parent table for more granular pricing data stored in related interface tables.

Common Use Cases and Queries

The primary use case revolves around troubleshooting and reporting on the status of external pricing integrations. Common queries involve identifying pricing data for a specific contract, checking for unprocessed interface records, or validating data integrity before processing. For instance, to find all external pricing interface records for a specific contract number, one would typically join from OKL_K_HEADERS (using the contract number) to OKL_STREAM_INTERFACES (using KHR_ID). A sample pattern for such a diagnostic query is:

  • SELECT khr.contract_number, sif.id, sif.transaction_number, sif.creation_date FROM okl_k_headers khr, okl_stream_interfaces sif WHERE khr.id = sif.khr_id AND khr.contract_number = '<CONTRACT_NUMBER>';

Another critical scenario is data purging or archival of processed interface records, which requires understanding the relationships with all child tables (e.g., OKL_SIF_LINES, OKL_SIF_FEES) to maintain referential integrity.

Related Objects

OKL_STREAM_INTERFACES sits at the center of a dedicated schema for external pricing interface data. As per the documented foreign keys, it has a direct parent relationship with the core contract table, OKL_K_HEADERS. It is the primary parent table for several child tables that hold detailed pricing components, including:

  • OKL_SIF_LINES: Likely holds individual payment stream lines (e.g., rent, residual).
  • OKL_SIF_FEES: Stores fee-related pricing data.
  • OKL_SIF_YIELDS: Holds calculated yield or rate information.
  • OKL_SIF_STREAM_TYPES: Probably defines types for the streams.
  • OKL_STREAM_TRX_DATA and OKL_SIF_TRX_PARMS: Likely contain transactional parameters and additional data for the pricing transaction.

This network of tables collectively manages the complete dataset required to pass a fully priced contract structure from an external system into Oracle Leasing.