Results for “okl_products”

50+ results




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

Overview

OKL_PRODUCTS is the master definition table for leasing and finance products within the Oracle E-Business Suite Leasing and Finance Management module (OKL). Each row represents a financing product that governs the financial treatment applied to a contract, including the accounting, pricing, term, and quoting behavior associated with that product. In Oracle EBS 12.1.1 and 12.2.2, product definition is a prerequisite for originating contracts and quotes, since the product supplies the default financial treatment, rate factor sets, charge setups, and term templates that drive downstream processing.

The table resides in the OKL schema and is documented as VALID in ETRM 12.2.2 with 33 columns. In Data Vault modeling terms, OKL_PRODUCTS is heuristically classified as a hub: it is the central business entity identified by a stable surrogate key (ID), referenced by numerous satellite-style and transactional tables through foreign keys. This classification is offered as a modeling suggestion rather than a mandated design.

Key Information Stored

The table separates its surrogate identifier from its business keys, a standard EBS pattern:

  • ID — surrogate primary key, enforced by the OKL_PRODUCTS_PK constraint and the unique index OKL_PRODUCTS_U1. This is the value propagated to all child tables.
  • NAME and VERSION — the composite business key, enforced by the unique index OKL_PRODUCTS_U2 (NAME, VERSION). Product versioning permits multiple iterations of a definition while retaining distinct identities.
  • AES_ID — foreign key to OKL_AE_TMPT_SETS_ALL, linking the product to its accounting event template set that determines financial treatment.
  • PTL_ID — foreign key to OKL_PDT_TEMPLATES, tying the product to the template from which it was generated.
  • REPORTING_PDT_ID — self-referencing foreign key to OKL_PRODUCTS, used to relate a product to a reporting-level product.
  • LEGACY_PRODUCT_YN — flag identifying products carried over from prior releases or external systems.
  • PRODUCT_STATUS_CODE — controls whether the product is active and therefore selectable in transactional and quoting flows.
  • DESCRIPTION — free-text explanation of the product.
  • FROM_DATE and TO_DATE — effective-dating bounds for the product definition.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework.
  • ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 — the DESCRIPTIVE flexfield and its value columns, available for client-specific extensions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO-column audit trail.

Common Use Cases and Queries

Reporting and integration scenarios typically resolve the product NAME from the surrogate ID carried on contracts or quotes. A representative join returns the product context for a transaction:

  • Selecting active products for a validation list: SELECT id, name, version FROM okl_products WHERE product_status_code = 'ACTIVE' (adjust the status value to site-configured lookup values).
  • Resolving product names for contracts: SELECT c.contract_number, p.name, p.version FROM okl_trx_contracts c, okl_products p WHERE c.pdt_id = p.id.
  • Auditing changes by extracting WHO columns across last_update_date ranges.
  • Identifying legacy products for migration or cleanup using legacy_product_yn.
  • Verifying effective-dating windows via from_date and to_date.
  • Extracting flexfield metadata through attribute_category and the attribute columns.

Because the table is a hub, most analytic queries treat it as the dimension that anchors fact-style transactional tables such as OKL_TRX_CONTRACTS_ALL and OKL_TRX_QUOTES_ALL_B.

Related Objects

The documented foreign keys establish OKL_PRODUCTS as a highly referenced parent. The most significant related objects include:

  • OKL_TRX_CONTRACTS_ALL and OKL_TRX_CONTRACTS — join on PDT_ID = OKL_PRODUCTS.ID; the primary transaction records using the product.
  • OKL_TRX_QUOTES_ALL_B and OKL_TRX_QUOTES_B — join on PDT_ID; quote origination referencing the product.
  • OKL_FE_EO_TERMS_ALL_B — join on PRODUCT_ID; end-of-term (EO) option terms per product.
  • OKL_LS_RT_FCTR_SETS_B — join on PDT_ID; rate factor sets applied to the product.
  • OKL_LTE_CHRG_SETUPS — join on PDT_ID; charge setup definitions for the product.
  • OKL_PDT_OPTS and OKL_PDT_PQY_VALS — join on PDT_ID; product options and pricing quantity values.
  • OKL_TBC_DEFINITIONS — join on PDT_ID; terms and conditions definitions.
  • OKL_SUBSIDY_CRITERIA — join on PRODUCT_ID; subsidy eligibility rules.
  • OKL_AE_TMPT_SETS_ALL — referenced via AES_ID; accounting event template sets defining financial treatment.
  • OKL_PDT_TEMPLATES — referenced via PTL_ID; the template used to instantiate the product.
  • OKL_PRD_PRICE_TMPLS — join on PDT_ID; pricing templates for the product.
  • OKL_PRODUCTS — self-reference via REPORTING_PDT_ID to ID for reporting hierarchies.

Together these relationships confirm OKL_PRODUCTS as the foundational hub from which leasing contracts, quotes, term definitions, pricing, and accounting treatment are derived.