Search Results child_log_file

Overview

OKL_BPD_VAR_INT_PROCESS_UV is an APPS-owned, VALID database view in the Oracle Leasing and Finance Management (OKL) module. It is documented under the title "Variable Interest Process" and is classified as a reporting and diagnostic view rather than a transactional entity. Its purpose is to present the outcome of variable interest processing runs in a readable, fully resolved form, pairing each parent stream interface transaction with its optional child transaction. Because the view already joins the interface records to their originating contract header and decodes several coded columns into descriptive lookup meanings, it can be queried directly for report development, reconciliation of variable interest processing, and troubleshooting of stream interface activity without requiring the caller to reconstruct the join logic manually.

The view is available in both Oracle EBS 12.1.1 and 12.2.2. In the 12.2.2 ETRM metadata the underlying objects are identified as synonyms: OKC_K_HEADERS_B, OKL_STREAM_INTERFACES, and OKL_VAR_INT_PROCESS_B, along with the package OKL_ACCOUNTING_UTIL.

Underlying Base Objects

The view is defined across four documented base objects:

• OKL_VAR_INT_PROCESS_B (synonym) — the driver table, supplying the contract number, request identifier, parent transaction ID, and child transaction ID that anchor the query.
• OKL_STREAM_INTERFACES (synonym) — referenced twice, once as SIF1 for the parent stream interface record and once as SIF2 for the child. The parent is joined via SIF1.TRANSACTION_NUMBER = VIP.PARENT_TRX_ID; the child is joined by the outer join condition SIF2.TRANSACTION_NUMBER (+) = VIP.CHILD_TRX_ID, meaning a row is still returned when no child transaction exists.
• OKC_K_HEADERS_B (synonym) — joined on CHR.CONTRACT_NUMBER = VIP.CONTRACT_NUMBER to supply the contract status and the authoring organization and contract identifiers.
• OKL_ACCOUNTING_UTIL (package) — invoked through GET_LOOKUP_MEANING to translate SIS_CODE (against lookup type OKL_SIF_STATUS) and ORP_CODE (against lookup type OKL_STRM_G_ORIGINATION_PROCESS) into their display meanings.

Key Columns

The view exposes identifying, status, and audit columns for both parent and child records. The contract identifiers (CONTRACT_NUMBER, CONTRACT_ID, ORG_ID, CONTRACT_STATUS) describe the lease being processed. The parent side includes PARENT_TRANSACTION_NUMBER, PARENT_SIF_ID, PARENT_SIS_CODE, PARENT_STATUS, PARENT_ORP_CODE, PARENT_ORIGINATING_PROCESS, PARENT_DATE_PROCESSED, and PARENT_LOG_FILE. The child side mirrors these as CHILD_TRANSACTION_NUMBER, CHILD_SIF_ID, CHILD_SIS_CODE, CHILD_STATUS, CHILD_ORP_CODE, CHILD_ORIGINATING_PROCESS, CHILD_DATE_PROCESSED, and CHILD_LOG_FILE.

The PARENT_ORP_CODE column is of particular interest to users searching on the originating process attribute. It carries the raw ORP (originating process) code from the parent stream interface record, while PARENT_ORIGINATING_PROCESS provides the decoded lookup meaning from OKL_STRM_G_ORIGINATION_PROCESS. The same pairing exists on the child side through CHILD_ORP_CODE and CHILD_ORIGINATING_PROCESS. PARENT_SIS_CODE and CHILD_SIS_CODE hold the stream interface status codes, decoded into PARENT_STATUS and CHILD_STATUS. REQUEST_ID identifies the concurrent request that generated the processing run, and the LOG_FILE columns point to the relevant log output.

Common Use Cases and Queries

Typical uses include reconciling variable interest processing output by contract, confirming whether a child transaction was created for a given parent, and reviewing status and log information after a processing run. The following query demonstrates filtering on the originating process code:

• SELECT contract_number, parent_transaction_number, parent_originating_process, parent_status, child_transaction_number, child_status FROM okl_bpd_var_int_process_uv WHERE parent_orp_code = :orp_code;
• SELECT request_id, contract_number, parent_transaction_number, parent_date_processed FROM okl_bpd_var_int_process_uv WHERE request_id = :request_id ORDER BY contract_number;
• SELECT contract_number, parent_sif_id, child_sif_id, parent_log_file FROM okl_bpd_var_int_process_uv WHERE child_sif_id IS NULL; — rows where no child interface record was produced, since the child join is an outer join.

Because the column set is pre-joined and pre-decoded, the view is well suited to ad hoc reporting and to feeds into custom concurrent programs, though it should be used strictly for read-only purposes and not treated as a source of record for transactional updates.