Search Results okl_ptq_values_v




Overview
Explore in AI Chat

Overview

The view OKL_PTQ_VALUES_V belongs to the OKL (Leasing and Finance Management) product family within Oracle E-Business Suite, and resides in the APPS schema with a status of VALID. It exposes the values that are attached to Template Qualities, which are used during Product Setup in the Product Template – Template Qualities flow. In practical terms, this view is the reporting and integration entry point for the list of permissible or configured quality values that drive leasing product configuration.

Because it is a view rather than a base table, OKL_PTQ_VALUES_V provides a stable, read-oriented interface onto the underlying storage for template quality values. It is principally used by Product Template – Template Qualities during Product Setup, and it is equally suitable for ad hoc reporting, data extraction, and interface development where downstream systems need to consume the configured quality values without directly querying the base table. Its reliance on ROWID and its exposure of standard WHO audit columns make it consistent with other descriptive/validation views in the OKL module.

Underlying Base Objects

The documented base object referenced by this view is OKL_PTQ_VALUES, which is exposed to the view through a synonym. The view text is a straightforward projection over that object:

  • The FROM clause selects from OKL_PTQ_VALUES, aliased as PTVB.
  • Every column in the view is drawn directly from the base object; no joins, aggregations, or computed expressions are present.
  • The column list is a one-to-one mapping of the base table's columns to view columns, with the addition of the ROWID (aliased as ROW_ID) to provide a unique row identifier.

Consequently, the view behaves as a thin, pass-through layer. There is no denormalization or filtering logic in the view definition, so row counts and business meaning mirror the underlying OKL_PTQ_VALUES records exactly. Any customization or data correction should be applied to the base table, because the view cannot be modified directly in a supported manner.

Key Columns

  • ROW_ID – The ROWID of the underlying base row, exposed as a unique identifier for the record. Useful for de-duplication and precise row targeting.
  • ID – The primary key of the PTQ value record.
  • OBJECT_VERSION_NUMBER – Optimistic locking / version control column used by the framework to detect concurrent updates.
  • PTQ_ID – Foreign key to the parent Template Quality record. This is the critical join column that links a value back to the quality it belongs to; joins are typically made to the Template Quality base object via this column.
  • VALUE – The actual value assigned to the Template Quality. This is the principal business attribute carried by the view.
  • DESCRIPTION – Descriptive text associated with the value.
  • FROM_DATE / TO_DATE – Date-range columns that define the effective period for the value.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns recording who created and last changed the row and when.

Common Use Cases and Queries

Typical uses include validating product setup data, extracting configured quality values for a migration or integration, and reporting on the values available for a given template quality. A common pattern is to retrieve all values for a specific quality using PTQ_ID:

  • SELECT id, ptq_id, value, description, from_date, to_date FROM apps.okl_ptq_values_v WHERE ptq_id = :p_ptq_id;
  • SELECT value, description FROM apps.okl_ptq_values_v WHERE ptq_id = :p_ptq_id AND (to_date IS NULL OR to_date >= SYSDATE);
  • SELECT ptq_id, COUNT(*) FROM apps.okl_ptq_values_v GROUP BY ptq_id;

When joining to the parent Template Quality, use PTQ_ID as the link key and qualify the view with the APPS schema prefix. Because the view performs no filtering, callers are responsible for applying effective-date and status conditions appropriate to their reporting requirement.