Results for “ptv_id”

50+ results




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

Overview

The OKL_PTL_PTQ_VALS table resides in the OKL schema, which supports the Oracle Leasing and Finance Management (OKL) module within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as a template-level association table that links product templates (via OKL_PDT_TEMPLATES) to the specific template qualities (via OKL_PTL_QUALITYS) and the acceptable or applicable quality values (via OKL_PTQ_VALUES) that apply to a given template.

In functional terms, this is a configuration or setup table. When leasing and finance users define a product template, they must delimit which qualities (attributes such as asset type, financing category, term parameters, and similar characteristics) apply to that template, and which permitted values satisfy those qualities. OKL_PTL_PTQ_VALS records each valid combination. The result controls downstream validation of contract and quote entry, restricts lookup lists presented to users, and enforces consistency between template definition and transaction data capture.

From a heuristic Data Vault modeling perspective, the metadata suggests classification as a link table. It bridges three parent entities — product templates, template qualities, and quality values — through a set of foreign key relationships, and it declares business-key uniqueness over the combination of PTL_ID and PTQ_ID rather than over each parent individually.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

  • ID — the surrogate primary key, enforced by OKL_PTL_PTQ_VALS_PK and the unique index OKL_PTL_PTQ_VALS_U1. It provides a stable technical identifier for each association row.
  • PTL_ID — the foreign key to OKL_PDT_TEMPLATES, identifying the product template to which the quality-and-value assignment belongs.
  • PTQ_ID — the foreign key to OKL_PTL_QUALITYS, identifying the specific template quality being configured.
  • PTV_ID — the foreign key to OKL_PTQ_VALUES, identifying the permitted quality value associated with the quality and template.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle AOL/ADF framework to detect concurrent updates.
  • FROM_DATE and TO_DATE — date-effective columns that define the validity window of the association.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns capturing creation and modification metadata for governance and reconciliation.

Business-key candidacy is documented through two unique indexes: OKL_PTL_PTQ_VALS_U1 on ID (surrogate), and OKL_PTL_PTQ_VALS_U2 on the composite (PTL_ID, PTQ_ID), which enforces that a given quality may appear at most once per template while allowing multiple permitted values to be expressed through PTV_ID.

Common Use Cases and Queries

Typical applications include configuration completeness reporting, template migration and cloning, and troubleshooting of value-list behavior at contract entry. A standard join pattern retrieves the template, quality, and value descriptions for review:

  • Reporting: select template name, quality name, and value description by joining OKL_PDT_TEMPLATES on PTL_ID, OKL_PTL_QUALITYS on PTQ_ID, and OKL_PTQ_VALUES on PTV_ID to produce an effective configuration matrix.
  • Gap analysis: identify templates with no rows in OKL_PTL_PTQ_VALS to detect incomplete setup before deployment.
  • Duplicate detection: query GROUP BY PTL_ID, PTQ_ID HAVING COUNT(*) > 1 to confirm composite uniqueness has not been violated by uncontrolled data loads.
  • Date-effectivity filtering: restrict results using FROM_DATE and TO_DATE to return only currently active assignments.
  • Change audit: use CREATION_DATE and LAST_UPDATE_DATE to track configuration drift between environments.

Related Objects

The following objects are most directly related through documented foreign keys and indexing:

  • OKL_PDT_TEMPLATES — parent template table; joined on PTL_ID = OKL_PDT_TEMPLATES.ID.
  • OKL_PTL_QUALITYS — parent quality table; joined on PTQ_ID = OKL_PTL_QUALITYS.ID.
  • OKL_PTQ_VALUES — parent value table; joined on PTV_ID = OKL_PTQ_VALUES.ID.
  • OKL_PTL_PTQ_VALS_PK / _U1 / _U2 — primary key and unique index constraints that govern row identity and business-key integrity.
  • Contract and quote configuration tables within OKL that consume template quality and value assignments indirectly when validating transaction entries.