Results for “okl_k_control”

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

Overview

OKL_K_CONTROL is a control table owned by the OKL schema within the Oracle Leasing and Finance Management (OKL) module. Its documented purpose is narrow and operationally significant: it stores the earliest next billing date for each contract. Rather than deriving the next billing date repeatedly at runtime, the billing engine consults this table to determine, per contract, the soonest date on which a billing event is due. This makes OKL_K_CONTROL a scheduling and control artifact rather than a transactional ledger.

Under the heuristic Data Vault classification mined from its foreign key structure, OKL_K_CONTROL is modelled as a standalone object. It carries a single foreign key association to OKL_PRTFL_CNTRCTS_B, meaning it is not itself a hub, link, or satellite in the strict sense, but rather a supporting control structure keyed to a portfolio contract record. The scheduling semantics — one earliest billing date per contract — suggest a satellite-style relationship to the contract, with KHR_ID acting as the driving identifier.

Key Information Stored

The documented physical structure contains 10 columns in ETRM 12.2.2. The most important are:

• KHR_ID — the contract identifier and foreign key to OKL_PRTFL_CNTRCTS_B; this is the business key that ties each control row to its parent lease or loan contract.
• EARLIEST_STRM_BILL_DATE — the earliest next billing date for the contract, and the sole functional payload of the table. All billing stream scheduling logic in the OKL module ultimately reads or refreshes this value.
• CREATED_BY, CREATION_DATE — Who-Columns that record the original insert of the control row, typically populated by a concurrent billing program rather than a user.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Who-Columns capturing the most recent refresh of EARLIEST_STRM_BILL_DATE.
• REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the batch job that last updated the row, which is critical for diagnosing stale or missing billing dates.

The WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) follow the standard Oracle EBS audit convention used across the OKL schema. No distinct surrogate primary key beyond KHR_ID is documented in the metadata, and no unique index columns are enumerated; KHR_ID functions as both the primary identification and the join column to the contract table.

Common Use Cases and Queries

The principal use case is billing cycle monitoring. Lease administrators and finance analysts frequently need to identify contracts whose next billing date has passed or is imminent, indicating a missed or pending billing run.

SELECT c.contract_number, k.earliest_strm_bill_date
FROM   okl_k_control k, okl_prtfl_cntrcts_b c
WHERE  k.khr_id = c.id
AND    k.earliest_strm_bill_date <= SYSDATE;

Second, the table supports reconciliation of billing program output. Because REQUEST_ID and PROGRAM_ID are retained, DBAs can trace which concurrent request last recalculated a contract's earliest billing date and verify completeness of a billing run.

SELECT request_id, program_id, COUNT(*)
FROM   okl_k_control
WHERE  program_update_date >= TRUNC(SYSDATE)
GROUP BY request_id, program_id;

Third, the table underpins aging and forecasting reports. Aggregating earliest_strm_bill_date by period supports expected billing volume projections. Finally, it is a diagnostic target when contracts fail to bill: a missing or stale row here is a common root cause, so support teams query by khr_id to confirm that a control record exists and reflects the correct date.

Related Objects

• OKL_PRTFL_CNTRCTS_B — The primary parent table; joined via OKL_K_CONTROL.KHR_ID = OKL_PRTFL_CNTRCTS_B.ID. This is the only documented foreign key relationship.
• OKL_PRTFL_CNTRCTS_TL — Provides contract descriptive and name translations for reporting output joined through the base contract record.
• OKL_STRM_BILL_SCHEDULES — Billing stream schedule detail from which the earliest streaming bill date is typically derived and then summarized into OKL_K_CONTROL.
• OKL_TRX_BILLING — Actual billing transaction lines; used to compare predicted versus billed dates per contract.
• FND_CONCURRENT_REQUESTS — Resolves REQUEST_ID and PROGRAM_ID to the concurrent program run that last refreshed the control row.
• FND_USER — Resolves LAST_UPDATED_BY and CREATED_BY to a user identity for audit reporting.

Because OKL_K_CONTROL is a lightweight control table, its dependencies are concentrated around the billing and contract schemas rather than spread across the application. Direct DML should be avoided; the table is maintained by OKL concurrent billing programs, and manual updates risk corrupting the billing schedule for the affected contract.