Results for “okl_provisions_u2”

12 results




Overview
Explore in AI Chat

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

Overview

OKL_PROVISIONS is a table in the OKL (Leasing and Finance Management) schema of Oracle E-Business Suite, holding loss provision definitions used in lease and finance contract accounting. Loss provisions represent anticipated credit losses or reserves associated with contract portfolios, and this table stores the accounting configuration that governs how those provisions are recognized — most notably the debit and credit accounts applied to the asset and revenue sides of the provision entries. The object resides in the OKL schema, is marked VALID, and is documented with 33 columns in the ETRM 12.2.2 physical schema; the same definition applies to 12.1.1 deployments of the ETRM/OKL module.

From a Data Vault modeling perspective, the mined foreign-key structure classifies OKL_PROVISIONS as hub-leaning. This is a heuristic suggestion rather than a physical implementation detail: the table behaves as a reference or master entity whose primary key is referenced by dependent transactional tables, rather than as a pure transactional link or descriptive satellite.

Key Information Stored

The table is anchored by two documented unique indexes. OKL_PROVISIONS_PK on ID is the surrogate primary key; OKL_PROVISIONS_U1 also enforces uniqueness on ID. The business-key candidate is OKL_PROVISIONS_U2 on the combination of NAME and VERSION, meaning a provision definition is uniquely identified by its name and its version number — supporting versioned, effective-dated configuration.

The most significant columns include:

  • ID — Surrogate primary key, referenced by dependent contract tables via PVN_ID.
  • NAME — Business identifier of the provision definition; first element of the unique key.
  • VERSION — Version number of the definition; second element of the unique key.
  • DESCRIPTION — Free-text description of the provision.
  • SET_OF_BOOKS_ID — Ledger context in which the provision is defined and posted.
  • APP_DEBIT_CCID and APP_CREDIT_CCID — Debit and credit accounting flexfield (code combination) identifiers for the asset/application side entries.
  • REV_DEBIT_CCID and REV_CREDIT_CCID — Debit and credit code combinations for the revenue side entries.
  • FROM_DATE and TO_DATE — Effective start and end dates of the provision definition.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM framework.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — DFF-enabled descriptive flexfield segment storage.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The primary retrieval pattern resolves a provision identifier to its accounting configuration for a given ledger. Because contract tables carry PVN_ID, a typical join returns the applicable provision accounts alongside contract data:

  • Provision lookup by ID or name/version: SELECT id, name, version, set_of_books_id, from_date, to_date FROM okl_provisions WHERE name = :name AND version = :version;
  • Effective-dated resolution: filter with WHERE from_date <= :as_of AND NVL(to_date, :as_of) >= :as_of to find the provision in force at a point in time.
  • Contract-to-provision reporting: SELECT c.id, p.name, p.app_debit_ccid, p.rev_debit_ccid FROM okl_trx_contracts c, okl_provisions p WHERE c.pvn_id = p.id;
  • Account validation: join the four CCID columns to the accounting flexfield combinations to confirm provision postings map to valid accounts within the ledger.
  • Version comparison: compare successive VERSION rows for a NAME to audit changes in provision accounts or effective dates.
  • DFF extraction: query ATTRIBUTE_CATEGORY with ATTRIBUTE1–15 for client-specific reporting extensions.

Related Objects

The documented foreign-key relationships show that OKL_PROVISIONS is referenced by the contract tables, with PVN_ID acting as the foreign-key column:

  • OKL_TRX_CONTRACTS — References OKL_PROVISIONS via OKL_TRX_CONTRACTS.PVN_ID.
  • OKL_TRX_CONTRACTS_ALL — The _ALL variant of the contract table, referencing OKL_PROVISIONS via OKL_TRX_CONTRACTS_ALL.PVN_ID.
  • Accounting flexfield combinations — The APP_DEBIT_CCID, APP_CREDIT_CCID, REV_DEBIT_CCID and REV_CREDIT_CCID columns resolve to code combinations validated against the ledger identified by SET_OF_BOOKS_ID.
  • OKL provisioning and accounting APIs — Provision definitions are consumed by OKL contract accounting routines when generating provision journal entries and accrual adjustments.

Because OKL_PROVISIONS acts as a hub-like reference for contract provisioning, any change to its account mappings or effective dates propagates directly to the derived provision balances reported against OKL_TRX_CONTRACTS and OKL_TRX_CONTRACTS_ALL.