Search Results okl_strm_g_origination_process

Overview

APPS.OKL_BPD_VAR_INT_PROCESS_UV is a reporting and diagnostic view in the Oracle E-Business Suite Lease and Finance Management (OKL) module. It exposes the processing state of "variable interest" (VAR_INT) interface records in relation to a lease contract, presenting each variable interest interface request alongside its parent and child stream interface rows. The view is primarily used to monitor batch processing outcomes for variable interest calculations—such as rate adjustments, interest accruals, and stream regeneration—that are submitted through the Lease Management concurrent programs.

The object carries the "_UV" suffix, indicating it is a user view (user-facing, read-only), and it is owned by the APPS schema. In an EBS 12.1.1 or 12.2.2 environment, it functions purely as a query object: no DML is supported against it, and it is typically consumed by Oracle Reports, OAF pages, BI Publisher extracts, or ad hoc SQL used by support and implementation teams. Because the parent interface table records a TRANSACTION_NUMBER, this view is directly relevant to users searching on that attribute, as it surfaces both parent and child transaction numbers side by side.

Underlying Base Objects

The view is defined over four documented base objects:

• OKL_VAR_INT_PROCESS_B (synonym) – the driving table, aliased VIP. It holds the variable interest process records, including CONTRACT_NUMBER, REQUEST_ID, PARENT_TRX_ID, and CHILD_TRX_ID.
• OKL_STREAM_INTERFACES (synonym) – joined twice, aliased SIF1 (parent) and SIF2 (child). SIF1 is joined on SIF1.TRANSACTION_NUMBER = VIP.PARENT_TRX_ID; SIF2 is outer-joined on SIF2.TRANSACTION_NUMBER (+) = VIP.CHILD_TRX_ID, making the child side optional.
• OKC_K_HEADERS_B (synonym) – the contract header table, aliased CHR, joined on CHR.CONTRACT_NUMBER = VIP.CONTRACT_NUMBER. It supplies the contract status code (STS_CODE), authoring organization (AUTHORING_ORG_ID), and contract ID.
• OKL_ACCOUNTING_UTIL (package) – a PL/SQL package invoked three times per row through GET_LOOKUP_MEANING to translate lookup codes (OKL_SIF_STATUS, OKL_STRM_G_ORIGINATION_PROCESS) into descriptive meanings.

Because the view calls a PL/SQL function for every returned row, query performance is sensitive to the number of qualifying records; filtering by CONTRACT_NUMBER or REQUEST_ID is advisable.

Key Columns

• CONTRACT_NUMBER – the lease contract to which the variable interest process belongs.
• REQUEST_ID – the concurrent request that generated the interface processing records; useful for tracing batch runs.
• CONTRACT_STATUS – the status code of the contract from OKC_K_HEADERS_B.
• PARENT_TRANSACTION_NUMBER / CHILD_TRANSACTION_NUMBER – transaction numbers from the parent and child OKL_STREAM_INTERFACES rows; the child values are null when no child row exists.
• PARENT_SIF_ID / CHILD_SIF_ID – primary key identifiers of the respective stream interface rows.
• PARENT_SIS_CODE / CHILD_SIS_CODE – interface status codes, decoded into PARENT_STATUS and CHILD_STATUS via OKL_SIF_STATUS.
• PARENT_ORP_CODE / CHILD_ORP_CODE – originating process codes, decoded into PARENT_ORIGINATING_PROCESS and CHILD_ORIGINATING_PROCESS.
• PARENT_DATE_PROCESSED / CHILD_DATE_PROCESSED – timestamps indicating when each interface row was processed.
• PARENT_LOG_FILE / CHILD_LOG_FILE – log file references supporting error investigation.
• ORG_ID / CONTRACT_ID – the authoring organization and internal contract identifier from OKC_K_HEADERS_B.

Common Use Cases and Queries

Typical scenarios include verifying whether a variable interest batch completed successfully, comparing parent and child stream interface status, and diagnosing failures by reviewing the associated log files. A representative query filtering by contract and transaction number follows:

SELECT contract_number,
       request_id,
       parent_transaction_number,
       parent_status,
       child_transaction_number,
       child_status,
       parent_date_processed,
       child_date_processed
FROM   apps.okl_bpd_var_int_process_uv
WHERE  contract_number = :p_contract_number
ORDER BY request_id, parent_transaction_number;

To locate a specific transaction, the view can be queried on either the parent or child column:

SELECT contract_number, request_id,
       parent_transaction_number, child_transaction_number
FROM   apps.okl_bpd_var_int_process_uv
WHERE  parent_transaction_number = :p_trx_number
OR     child_transaction_number  = :p_trx_number;

Because the child side is an outer join, records with CHILD_TRANSACTION_NUMBER IS NULL identify parent interfaces that did not generate a child stream, which is often a key diagnostic indicator. The view should always be queried with the APPS schema prefix or a synonym, and results are best restricted by CONTRACT_NUMBER or REQUEST_ID to minimize the overhead of the OKL_ACCOUNTING_UTIL lookup calls.