Search Results okl_var_int_process_b_pk

Overview

OKL_VAR_INT_PROCESS_B is a transactional table in the OKL (Leasing and Finance Management) module of Oracle E-Business Suite, holding records for the Variable Interest Rate Process. It tracks transactions where lease or loan contracts are subject to variable interest rate adjustments, capturing both the parent transaction (typically the original contract) and the child transaction (typically the rebooked or repriced contract) generated during processing. The table is central to interest-rate rebooking workflows for variable-rate instruments.

The owner schema is OKL and the object status is VALID in both 12.1.1 and 12.2.2. It carries 33 documented columns in the ETRM 12.2.2 physical schema. Based on the heuristic Data Vault classification derived from FK structure, the table is modeled as a standalone object — it is not directly linked by foreign keys to other tables within the OKL schema, though it logically relates to contract and transaction data via its own business columns.

Key Information Stored

The primary key is ID, defined by the constraint OKL_VAR_INT_PROCESS_B_PK and mirrored in the unique index OKL_VAR_INT_PROCESS_B_U1. Because ID also serves as the unique business-key candidate, it functions as both the surrogate and the de facto business identifier. Other significant columns include:

• PARENT_TRX_ID — identifier of the originating contract transaction, typically the pre-adjustment record.
• CHILD_TRX_ID — identifier of the resulting transaction produced by the variable interest process (e.g., a rebooked contract).
• CONTRACT_NUMBER — the human-readable contract identifier affected by the rate adjustment.
• REBOOK_STATUS — state flag indicating where the processing stands in the rebook lifecycle.
• STATUS — overall process status of the variable interest record.
• REQUEST_ID — the concurrent request that generated the record, enabling traceability via FND_CONCURRENT_REQUESTS.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — identify the concurrent program responsible for the row.
• PROGRAM_UPDATE_DATE — timestamp of the last program-driven update.
• ORG_ID — operating unit, supporting multi-org reporting.
• OBJECT_VERSION_NUMBER — optimistic locking for concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns for audit and date-tracked reporting.

Common Use Cases and Queries

Typical scenarios include auditing variable-rate rebookings, reconciling parent-to-child contract transformations, and diagnosing failed or pending concurrent processes. A common query joins the process table to the audit columns and concurrent request metadata:

• Identify all rebooked contracts: SELECT CONTRACT_NUMBER, PARENT_TRX_ID, CHILD_TRX_ID, REBOOK_STATUS FROM OKL_VAR_INT_PROCESS_B WHERE REBOOK_STATUS = 'COMPLETE';
• Trace a specific run: SELECT * FROM OKL_VAR_INT_PROCESS_B WHERE REQUEST_ID = :req_id;
• Dashboard for pending work: filter on STATUS and REBOOK_STATUS for open items.
• Audit who changed rows: order by LAST_UPDATE_DATE and group by LAST_UPDATED_BY.

Related Objects

Although the heuristic classification indicates no direct FK links, the table integrates with the following OKL objects:

• OKL_TRX_CONTRACTS_B / _TL — joined on CONTRACT_NUMBER or transaction ID to resolve contract detail.
• OKL_TRX_HEADERS / OKL_TRX_LINES — parent/child transaction identifiers resolve here.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for program and completion status.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID.
• OKL_INTEREST_RATES — the rate source driving variable interest recalculation.
• HR_OPERATING_UNITS — joined on ORG_ID for multi-org reporting.