Search Results okl_ptl_qualitys_v




Overview
Explore in AI Chat

Overview

OKL_PTL_QUALITYS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL product family (Leasing and Finance Management). In ETRM terminology, the object is classified as a VIEW with an effective status of VALID, meaning it is a supported, queryable database object maintained by the application rather than a transient or obsolete construct. Its documented purpose is to expose the set of Template Qualities associated with Product Template setup. Within the leasing product configuration model, product templates define the reusable attributes that drive how contracts, assets, and financing terms are created and processed; the qualities attached to a template represent the qualifying characteristics that can be referenced during product setup and rule evaluation.

Because the view is defined in the APPS schema and is conventionally granted to reporting and integration responsibilities, it functions as the read-oriented interface through which external reports, concurrent programs, and interfaces access template quality data without touching the underlying transactional table directly. This isolation is significant in a 12.1.1 or 12.2.2 environment, where direct DML against base application tables is unsupported and where the APPS synonyms and grants determine visibility for customizations and third-party tooling.

Underlying Base Objects

The view is defined over a single documented base object: OKL_PTL_QUALITYS, referenced through the APPS synonym. The projection is a straightforward, unfiltered selection of columns from that table, with the base table's ROWID exposed as ROW_ID. There is no join, aggregation, or filter in the documented view text, which means the view is effectively a column-renaming and access-isolation layer rather than a denormalized reporting construct.

Consequently, every row returned by the view corresponds one-to-one with a row in OKL_PTL_QUALITYS. Any row-level security, multi-org behavior, or date-based filtering must be applied by the consuming query, since the view itself imposes none. Implementers should note that the referenced base object is recorded as a synonym, and that object versioning and audit columns are carried through unchanged from the source table.

Key Columns

  • ROW_ID — the ROWID of the underlying OKL_PTL_QUALITYS row, useful for high-performance direct row access.
  • ID — the primary identifier of the template quality record.
  • OBJECT_VERSION_NUMBER — the optimistic locking version number used by the EBS framework to detect concurrent updates.
  • NAME — the descriptive name of the template quality.
  • DESCRIPTION — free-text detail describing the quality.
  • FROM_DATE / TO_DATE — the effective date range governing when the quality is active and valid for use.
  • CREATED_BY, CREATION_DATE — standard audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change, its timestamp, and the login session that performed it.

Common Use Cases and Queries

Typical scenarios include validating that a template quality is currently effective, reconciling configured qualities against requirements, and feeding quality definitions into downstream interfaces. A current-effective query filters on the date range as follows:

  • SELECT id, name, description, from_date, to_date FROM apps.okl_ptl_qualitys_v WHERE TRUNC(SYSDATE) BETWEEN from_date AND NVL(to_date, TRUNC(SYSDATE));
  • SELECT id, name FROM apps.okl_ptl_qualitys_v ORDER BY name; — a simple reference listing for setup validation.
  • SELECT name, last_updated_by, last_update_date FROM apps.okl_ptl_qualitys_v WHERE last_update_date >= :p_since; — an incremental audit extract.

Because the view applies no filtering, the FROM_DATE and TO_DATE predicates must be supplied explicitly whenever only active qualities are relevant.