Results for “okl_provisions_v”

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

Overview

OKL_PROVISIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. Its documented purpose is to expose loss provision definitions used by the leasing application. In leasing operations, a loss provision represents an anticipated credit loss or impairment associated with a contract, and the accounting configuration attached to that provision determines which General Ledger accounts are debited and credited when the provision is applied, adjusted, or reversed.

The view is defined as a thin projection over the OKL_PROVISIONS base entity. It does not perform joins, aggregation, or filtering; instead it renames the ROWID pseudo-column to ROW_ID and surfaces every attribute of the underlying record, including the four accounting flexfield identifiers that drive provisioning entries. This makes the view a stable, read-only access point for reporting tools, concurrent programs, and external integrations that need provision setup data without touching the base table directly. Because it is a simple view, it inherits the base object's row-level security behavior and reflects committed data at query time.

Underlying Base Objects

The documented dependency for OKL_PROVISIONS_V is a single referenced object: the synonym OKL_PROVISIONS. The synonym resolves to the OKL_PROVISIONS table in the APPS schema (or the corresponding product schema in a given installation). The view text confirms a one-to-one relationship — every row in the view corresponds to exactly one row in the base table, with no DISTINCT, WHERE, GROUP BY, or set operators applied.

Because the view is defined over a synonym rather than directly over the table, it is portable across environments where the physical table owner differs. Two synthetic columns are introduced by the view definition: ROW_ID, derived from the base table's ROWID, and the remaining columns, which map straight through from OKL_PROVISIONS by name. Standard EBS audit columns are preserved without transformation, so downstream consumers can rely on CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN exactly as stored.

Key Columns

• ID – Primary identifier of the provision record.
• NAME / DESCRIPTION – User-facing identification of the loss provision.
• APP_DEBIT_CCID / APP_CREDIT_CCID – Accounting flexfield combination identifiers for the debit and credit sides of the provision application entry. APP_DEBIT_CCID is the column most frequently referenced when diagnosing provision accounting; it is a CODE_COMBINATION_ID foreign key to GL_CODE_COMBINATIONS.
• REV_DEBIT_CCID / REV_CREDIT_CCID – Corresponding debit and credit accounts used when the provision is reversed, allowing asymmetrical reversal accounting.
• SET_OF_BOOKS_ID – The ledger (set of books) under which the provision accounting is valid.
• OBJECT_VERSION_NUMBER – Optimistic locking token used by the leasing forms and APIs.
• VERSION, FROM_DATE, TO_DATE – Effective-dating and versioning attributes governing when the provision definition is active.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments for customer-specific extensions.
• ROW_ID – Row identifier projected from the base table ROWID for update-safe access.

Common Use Cases and Queries

Typical usage includes validating provision accounting setup before period close, reconciling provisioning entries against GL balances, and extracting provision definitions for data warehousing. A frequent diagnostic query resolves the application debit account for each provision:

• SELECT p.ID, p.NAME, p.APP_DEBIT_CCID, gcc.concatenated_segments debit_account FROM okl_provisions_v p, gl_code_combinations_kfv gcc WHERE p.app_debit_ccid = gcc.code_combination_id AND p.set_of_books_id = :ledger_id;
• SELECT ID, NAME, APP_DEBIT_CCID, APP_CREDIT_CCID, REV_DEBIT_CCID, REV_CREDIT_CCID FROM okl_provisions_v WHERE FROM_DATE <= SYSDATE AND NVL(TO_DATE, SYSDATE) >= SYSDATE;
• SELECT ID, NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM okl_provisions_v ORDER BY LAST_UPDATE_DATE DESC;

Because the view exposes CODE_COMBINATION_ID values rather than account strings, joins to GL_CODE_COMBINATIONS_KFV or FND_FLEX_VALUES are required for human-readable output. Integration programs should treat the view as read-only and perform DML through the leasing APIs that maintain OKL_PROVISIONS.