Results for “okl_generate_streams_uv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_GENERATE_STREAMS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the OKL – Leasing and Finance Management module. Its purpose is to expose the relationship between a contract header and the stream interface records that were generated against it, including the corresponding report (reporting) stream interface record where one exists. The view derives its name from the "Generate Streams" process within Leasing and Finance Management, which builds the stream interface rows that feed downstream accounting and reporting logic. Because it joins a contract to both its primary stream interface row and a secondary "report" stream interface row, the view is primarily a diagnostic and inquiry artifact: it allows users to confirm which contract and transaction number produced a given stream interface, and to compare the status of the stream interface against the status of its associated report record. The user keyword "report_status" maps directly to the REPORT_STATUS column returned by this view, which is the lookup meaning of the report stream interface's status code (SIFB2.SIS_CODE), resolved through the OKL_SIF_STATUS lookup type.

Underlying Base Objects

The documented referenced base objects are OKC_K_HEADERS_B (SYNONYM), OKL_ACCOUNTING_UTIL (PACKAGE), and OKL_STREAM_INTERFACES (SYNONYM). The FROM clause joins OKC_K_HEADERS_B KHRB (the contract headers table, aliased KHRB) to OKL_STREAM_INTERFACES SIFB on KHRB.ID = SIFB.KHR_ID, and then outer-joins OKL_STREAM_INTERFACES a second time as SIFB2 on SIFB.ID = SIFB2.SIF_ID (+). The final predicate, SIFB.SIF_ID IS NULL, is a restrictive filter on the primary stream interface alias. The package OKL_ACCOUNTING_UTIL is not joined as a table; it is invoked as OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING to translate stored lookup codes (for OKL_SIF_STATUS and OKL_STRM_G_ORIGINATION_PROCESS) into human-readable meanings. OKL_STREAM_INTERFACES is the core OKL table holding stream interface records, including SIF_ID, KHR_ID, TRANSACTION_NUMBER, SIS_CODE, ORP_CODE, PURPOSE_CODE, DATE_PROCESSED, LOG_FILE, and the STREAM_INTERFACE_ATTRIBUTE01 through 15 flex columns.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER – Identifiers taken from OKC_K_HEADERS_B (KHRB.ID, KHRB.CONTRACT_NUMBER), tying each row to a leasing contract.
• TRANSACTION_NUMBER – Transaction number of the primary stream interface row (SIFB.TRANSACTION_NUMBER).
• REPORT_TRANSACTION_NUMBER – Transaction number of the related report stream interface row (SIFB2.TRANSACTION_NUMBER).
• SIF_ID – Primary key of the stream interface record (SIFB.ID), also the join key to the report record.
• STATUS – Lookup meaning of the primary record's status code SIFB.SIS_CODE via OKL_SIF_STATUS.
• REPORT_STATUS – Lookup meaning of the report record's status code SIFB2.SIS_CODE via OKL_SIF_STATUS; this is the column most relevant to the "report_status" search.
• REP_SIS_CODE – Raw status code of the report stream interface row.
• ORIGINATING_PROCESS – Lookup meaning of SIFB.ORP_CODE via OKL_STRM_G_ORIGINATION_PROCESS.
• PURPOSE_CODE, DATE_PROCESSED, LOG_FILE – Purpose classification, processing date, and log file reference for the primary stream interface.
• STREAM_INTERFACE_ATTRIBUTE01–15 – Descriptive flexfield-style attribute columns carried from SIFB.

Common Use Cases and Queries

Typical usage is troubleshooting stream generation and reporting status. To identify contracts whose report stream failed or remains unprocessed, query REPORT_STATUS:

SELECT CONTRACT_NUMBER, TRANSACTION_NUMBER, REPORT_TRANSACTION_NUMBER, STATUS, REPORT_STATUS FROM APPS.OKL_GENERATE_STREAMS_UV WHERE REPORT_STATUS IS NOT NULL AND STATUS <> REPORT_STATUS;

To trace a single contract, filter on CONTRACT_NUMBER:

SELECT SIF_ID, TRANSACTION_NUMBER, REPORT_TRANSACTION_NUMBER, ORIGINATING_PROCESS, DATE_PROCESSED FROM APPS.OKL_GENERATE_STREAMS_UV WHERE CONTRACT_NUMBER = :p_contract_number;

Because STATUS and REPORT_STATUS are resolved by OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING, results are already returned as descriptive lookup meanings, which makes the view convenient for BI Publisher reports and concurrent-program diagnostics without additional lookup joins.