Results for “okl_ptl_qualitys”

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

Overview

The OKL_PTL_QUALITYS table resides in the OKL schema and belongs to the Oracle E-Business Suite Leasing and Finance Management (OKL/ETRM) product family. It stores the template quality definitions that are consumed by the Product Template — Template Qualities functionality during product setup. In practice, each row represents a reusable "quality" (a scoring or classification attribute) that can be attached to a product template and, through that association, to the lease and finance contracts generated from the template.

In EBS 12.1.1 and 12.2.2, the OKL product model distinguishes between contract templates, product templates, and the qualities that parameterize them. OKL_PTL_QUALITYS holds the master list of those qualities. From a Data Vault modeling perspective, the FK topology (other tables referencing this table through PTQ_ID) suggests a hub-leaning classification: the table behaves primarily as a business entity hub, with descriptive and audit attributes acting as satellite-like payload. This classification is a heuristic modeling suggestion rather than a documented Oracle design decision.

Key Information Stored

The table exposes eleven documented columns. The most significant are:

• ID — Surrogate primary key (OKL_PTL_QUALITYS_PK) and backed by unique index OKL_PTL_QUALITYS_U1. This is the value propagated to child tables as PTQ_ID.
• NAME — Business-key candidate, enforced by unique index OKL_PTL_QUALITYS_U2. Identifies the quality in the user interface and in reporting.
• DESCRIPTION — Free-text explanation of the quality's purpose.
• FROM_DATE / TO_DATE — Effective-dating pair that governs when the quality is active for product setup.
• OBJECT_VERSION_NUMBER — Optimistic-locking column used by the OAF framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS "WHO" audit columns recording the user and timestamp of insertion and last change.

Together, ID (surrogate) and NAME (business key) provide the two unique access paths documented for this object.

Common Use Cases and Queries

Typical usage falls into three categories: product-setup validation, effective-date reporting, and quality-to-value resolution.

• Enumerating active qualities:

  SELECT id, name, description
  FROM   okl.okl_ptl_qualitys
  WHERE  TRUNC(SYSDATE) BETWEEN from_date AND NVL(to_date, SYSDATE)
  ORDER  BY name;

• Resolving qualities to their permitted values by joining through OKL_PTL_PTQ_VALS.PTQ_ID:

SELECT q.id, q.name, v.value
FROM   okl.okl_ptl_qualitys q,
       okl.okl_ptl_ptq_vals v
WHERE  q.id = v.ptq_id;

The same join against OKL_PTQ_VALUES supports reporting on the defined value set per quality. Because NAME is uniquely indexed, lookups by name are efficient; lookups by ID use the primary key. Effective-date filtering should always account for a NULL TO_DATE, which conventionally means an open-ended, still-active record.

Related Objects

Two documented foreign keys reference this table, and both are central to interpreting its data:

• OKL_PTL_PTQ_VALS — child table; column PTQ_ID references OKL_PTL_QUALITYS.ID. Holds the template-level quality values.
• OKL_PTQ_VALUES — child table; column PTQ_ID references OKL_PTL_QUALITYS.ID. Holds the master value list associated with each quality.

In addition, product-template setup forms and the OKL concurrent programs that generate contract templates read from this table indirectly via those children. DBAs should expect the standard OKL grants and synonyms, and treat OKL_PTL_QUALITYS as reference/master data that is rarely updated once templates are in production.