Search Results okl_var_int_process_b_u1

Overview

OKL.OKL_VAR_INT_PROCESS_B is a transaction-processing table in the Oracle E-Business Suite ETRM (Enterprise Trading and Risk Management) module, owned by the OKL schema. As its name indicates, it tracks the "Variable Interest Rate Process" — the batch workflow that recalculates or rebooks leases and contracts subject to variable (floating) interest terms. The table records the linkage between a parent "Super Trump" transaction and its child transaction created during the rebooking operation, together with the contract number, rebook status, and the concurrent manager context under which the process was executed.

Physically, the table resides on the APPS_TS_TX_DATA tablespace with PCT_FREE 10, and its unique index OKL_VAR_INT_PROCESS_B_U1 on the ID column is stored on APPS_TS_TX_IDX. The primary key constraint OKL_VAR_INT_PROCESS_B_PK is defined on ID. Under the heuristic Data Vault classification derived from the FK structure, this object is modeled as standalone — it does not participate in a documented hub-link-satellite chain and should be treated as an independent process-log entity rather than a core master or relationship table.

Key Information Stored

The table contains 33 documented columns. The most operationally significant are:

• ID (NUMBER) — surrogate primary key; enforced by OKL_VAR_INT_PROCESS_B_PK and the unique index OKL_VAR_INT_PROCESS_B_U1. It is the sole documented business-key candidate.
• OBJECT_VERSION_NUMBER (NUMBER) — optimistic locking column used to serialize record updates.
• PARENT_TRX_ID (NUMBER) — transaction number of the original Super Trump transaction.
• CHILD_TRX_ID (NUMBER) — transaction number of the child Super Trump transaction created by the variable interest rebooking.
• CONTRACT_NUMBER (VARCHAR2 120) — the contract being processed.
• REBOOK_STATUS (VARCHAR2 2000) — contract status captured during the process.
• STATUS (VARCHAR2 200) — transaction status of the process record.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — concurrent manager columns identifying the batch request that generated the row.
• ORG_ID (NUMBER 15) — operating unit identifier, enabling multi-org reporting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 (VARCHAR2 450 each) — descriptive flexfield storage.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on reconciliation and process monitoring of variable interest rebooking runs. A frequent pattern joins parent and child transactions through the TRX identifiers, restricting by operating unit:

• Process audit: SELECT contract_number, status, rebook_status FROM okl.okl_var_int_process_b WHERE request_id = :p_request_id;
• Reconciliation: locate rows where PARENT_TRX_ID and CHILD_TRX_ID pairs are incomplete or where STATUS is not in the expected completion set.
• Concurrent manager drill-down: join REQUEST_ID to FND_CONCURRENT_REQUESTS to attribute each row to its submitting program and completion timestamp.
• Multi-org reporting: aggregate by ORG_ID to compare rebooking volumes across operating units.
• Flexfield reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 for locally configured tracking attributes.

Related Objects

Because the model is classified standalone, the table is referenced primarily through logical, not enforced, joins. The most significant related objects are:

• OKL_TRX_TYPES / OKL_TRX_HEADERS_B — join PARENT_TRX_ID and CHILD_TRX_ID to the transaction header ID to resolve Super Trump records.
• OKL_CONTRACTS / OKL_K_HEADERS — joined via CONTRACT_NUMBER to the originating lease or contract.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for concurrent program context.
• FND_APPLICATION — joined on PROGRAM_APPLICATION_ID.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_ID.
• HR_OPERATING_UNITS — joined on ORG_ID for operating unit names.

Subsequent or dependent OKL processing tables that consume CHILD_TRX_ID complete the logical dependency chain for downstream rebooking steps.