Results for “pqy_id”

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

Overview

The view APPS.OKL_PDT_PQYS_UV is a denormalized reporting construct within the Oracle Lease and Finance Management (OKL) product family. Its name reflects its lineage: "PDT" denotes product, "PQYS" identifies the product quality associations, "UV" indicates a user-facing view. The view joins the product quality definition table to the product-to-quality association table, presenting a flattened, unambiguous record of which qualities are attached to which products in the lease and finance product catalog.

Because the underlying association table stores only surrogate foreign keys, the raw table is not directly useful for ad-hoc reporting. OKL_PDT_PQYS_UV resolves those keys into descriptive attributes such as quality name, description, and effective date range, making it suitable for BI Publisher reports, OAF-based inquiry pages, and integration extracts that must surface human-readable product quality information without embedding the join logic in each consumer. The view carries no updateable semantics and is intended strictly for read access.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms in the ETRM 12.2.2 metadata:

• OKL_PDT_PQYS (aliased PDQ) — the product quality association table, supplying the association record identifier (ID), the product template identifier (PTL_ID), the quality identifier (PQY_ID), and the row version number.
• OKL_PDT_QUALITYS (aliased PQY) — the product quality definition table, supplying the quality name, description, and the from/to date bounds that define its effective period.

The two objects are joined with an inner join on PQY.ID = PDQ.PQY_ID. This means the view returns only association rows whose referenced quality definition still exists; orphaned associations are silently filtered out. Both base objects reside in the APPS schema and are exposed to the view under the same schema, so no cross-schema grants are required for querying.

Key Columns

• ID (PDQ.ID) — the unique identifier of the product-to-quality association record. This is the primary handle for the association itself, distinct from either the product or the quality.
• PTL_ID (PDQ.PTL_ID) — the product template identifier. This is the column matched by the search term "ptl_id" and links the association to a specific product definition in the lease catalog.
• PQY_ID (PDQ.PQY_ID) — the surrogate key resolving to the quality definition, also matching PQY.ID in the join.
• PQY_NAME and PQY_DESCRIPTION — the descriptive text of the quality, used in reports instead of the opaque numeric key.
• FROM_DATE / TO_DATE — the effective date range of the quality definition, supporting date-sensitive reporting.
• OBJECT_VERSION_NUMBER — the optimistic locking column propagated from the association table, useful for detecting stale extracts.

Common Use Cases and Queries

The most frequent use is listing the qualities attached to a product, filtered by PTL_ID:

• SELECT p.ptl_id, p.pqy_name, p.pqy_description, p.from_date, p.to_date FROM okl_pdt_pqys_uv p WHERE p.ptl_id = :product_template_id;
• Detecting associations whose effective window has expired: SELECT * FROM okl_pdt_pqys_uv WHERE to_date < SYSDATE;
• Feeding integration extracts that must distribute product quality attributes to downstream pricing or contract engines, selecting PTL_ID, PQY_NAME, and OBJECT_VERSION_NUMBER for change detection.

Because the view joins two APPS objects with no bind-parameter protection, callers should always filter on PTL_ID or ID to avoid full scans of the quality association table.