Results for “pqy_name”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.OKL_PDT_PQYS_UV is a reporting and integration view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL / ETRM) module. It exposes the association between a Product Quality (PQY) definition and the product or product-template records that consume it. Because the view joins the PQY master records in OKL_PDT_QUALITYS to the association rows in OKL_PDT_PQYS, it allows downstream inquiries, reports, and interfaces to retrieve the quality name, description, validity dates, and parent product reference through a single SELECT without navigating the underlying foreign-key relationship manually.

The view is commonly surfaced in the Product Information / Quality setup areas of Lease Management and is exposed for ad hoc reporting, OA Framework/Discoverer queries, and integration extracts. The "_UV" suffix denotes a user/validation view, indicating a denormalized read-only projection rather than a base table.

Underlying Base Objects

The view is defined over two synonyms that resolve to base objects:

  • OKL_PDT_QUALITYS (PQY) — the quality master table holding the quality definition.
  • OKL_PDT_PQYS (PDQ) — the association table linking a quality to a product template line.

The join is PQY.ID = PDQ.PQY_ID, making OKL_PDT_PQYS the driving link and OKL_PDT_QUALITYS the lookup. Both objects are referenced as synonyms owned by APPS, so the view inherits the standard EBS APPS synonyms and privileges.

Key Columns

  • ID — from PDQ.ID; the primary key of the association row.
  • PTL_ID — from PDQ.PTL_ID; the parent product template line identifier.
  • PQY_ID — from PQY.ID; the identifier of the quality master record.
  • PQY_NAME — from PQY.NAME; the user-facing quality name. This is the most frequently searched attribute (the term "pqy_name") and the primary descriptor returned by the view.
  • PQY_DESCRIPTION — from PQY.DESCRIPTION; the long description of the quality.
  • FROM_DATE / TO_DATE — from PQY.FROM_DATE / PQY.TO_DATE; the effective/expiry window of the quality definition.
  • OBJECT_VERSION_NUMBER — from PDQ.OBJECT_VERSION_NUMBER; the OVN used for optimistic locking on the association record.

Common Use Cases and Queries

The view is used to list all qualities attached to a given product template line, to look up a quality by name, and to extract quality assignments for integration or reconciliation. A typical query filtering on the quality name is:

SELECT id, ptl_id, pqy_id, pqy_name, pqy_description, from_date, to_date FROM apps.okl_pdt_pqys_uv WHERE pqy_name = :p_name;

To retrieve all qualities for a specific parent line:

SELECT pqy_name, pqy_description, from_date, to_date FROM apps.okl_pdt_pqys_uv WHERE ptl_id = :p_ptl_id ORDER BY pqy_name;

To check currently effective qualities, constrain on the date columns:

SELECT pqy_name FROM apps.okl_pdt_pqys_uv WHERE TRUNC(SYSDATE) BETWEEN from_date AND to_date;

Because the view is read-only and aggregates only the documented columns, it is safe for concurrent reporting and does not carry the OVN of the quality master. Joins back to OKL_PDT_QUALITYS or OKL_PDT_PQYS are required when additional master attributes or update operations are needed.