Search Results apps_ts_nologging




Overview
Explore in AI Chat

Overview

The OKL_STREAM_TRX_DATA table is a core transactional data store within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a staging and logging repository for XML data exchanged with an external pricing engine during the processing of financial streams. Its primary role is to temporarily hold outbound XML requests sent to the pricing engine and the corresponding inbound XML responses received. The table is designed for transient data; once a transaction is complete, the associated data is purged. It is stored in the APPS_TS_NOLOGGING tablespace, indicating its operational nature where data recovery via redo logs is typically not required, prioritizing performance for high-volume, temporary data operations.

Key Information Stored

The table's structure is centered on managing the lifecycle of a pricing transaction. The ID column serves as the primary key. Critical transactional identifiers include TRANSACTION_NUMBER (a unique identifier for the transaction) and foreign key columns SIF_ID and SIR_ID, which link to the stream interface headers and returns, respectively. The core data payload is stored in Large Object (LOB) columns: OUT_XML (CLOB) for the data sent to the pricing engine, and IN_XML (CLOB) for the response received. Status tracking is facilitated through the STATUS and TRANSACTION_STATE columns. Additional context is provided by columns like KHR_ID (contract header ID), ORIG_KHR_ID, and user-entered COMMENTS.

Common Use Cases and Queries

This table is primarily accessed for debugging, auditing, and monitoring the integration with the external pricing engine. Common operational queries include investigating pending or failed transactions, reviewing the raw XML exchanged for specific contracts, or purging completed transactions. A typical query to examine active transactions for a specific contract would join to the interface headers table.

  • Sample Query: Find transactions for a specific contract (KHR_ID):
    SELECT std.TRANSACTION_NUMBER, std.STATUS, std.OUT_XML, std.IN_XML
    FROM OKL.OKL_STREAM_TRX_DATA std
    WHERE std.KHR_ID = <contract_id>
    ORDER BY std.ID DESC;
  • Sample Query: Monitor pending transactions:
    SELECT COUNT(*), STATUS
    FROM OKL.OKL_STREAM_TRX_DATA
    GROUP BY STATUS;

Related Objects

OKL_STREAM_TRX_DATA is integral to the OKL module's pricing integration framework. Its documented foreign key relationships establish clear data lineage.

  • OKL_STREAM_INTERFACES: The SIF_ID column in OKL_STREAM_TRX_DATA is a foreign key referencing this table, linking the transactional XML data to its originating stream interface header.
  • OKL_SIF_RETS: The SIR_ID column is a foreign key referencing this table, connecting the transaction data to the corresponding stream interface return records.

These relationships allow for comprehensive analysis by joining transactional XML data with its source interface metadata and processed return information.