Results for “qve_id”

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

Overview

OKL_PDT_PQY_VALS is a transactional association table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. As its documented description states, the table binds Quality Values to a lease product, effectively acting as a cross-reference that defines which pricing or product quality characteristics apply to a given product configuration. In the leasing lifecycle, quality values are used to capture product attributes, rating factors, or scored characteristics that influence pricing, approval, and product eligibility. OKL_PDT_PQY_VALS therefore sits at the intersection of the product definition and the quality value master data, forming a many-to-many resolution between products and their applicable quality values, scoped by the product quality header.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This is appropriate: the table contains no descriptive master attributes of its own beyond association metadata and effective-dating columns; its purpose is to relate OKL_PRODUCTS, OKL_PDT_PQYS, and OKL_PQY_VALUES. A Data Vault implementation would treat it as a link table between those hubs, with the associated date and audit columns carried as link metadata.

Key Information Stored

The table is documented with twelve columns. The most significant are listed below.

• ID — surrogate primary key, enforced by constraint OKL_PDT_PQY_VALS_PK and reinforced by unique index OKL_PDT_PQY_VALS_U1. It uniquely identifies each product-to-quality-value association row.
• PDQ_ID — foreign key to OKL_PDT_PQYS, identifying the product quality header to which this value association belongs.
• PDT_ID — foreign key to OKL_PRODUCTS, identifying the lease product being configured.
• QVE_ID — foreign key to OKL_PQY_VALUES, identifying the specific quality value assigned.
• FROM_DATE / TO_DATE — effective-dating columns defining the validity window of the association.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework and EBS APIs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing the creation and last-modification audit trail.

In addition to the primary key, unique index OKL_PDT_PQY_VALS_U2 on (PDQ_ID, PDT_ID) is a business-key candidate, indicating that a given product may appear only once under a given product quality header. The other unique index, OKL_PDT_PQY_VALS_U1, corresponds to the surrogate ID and is documented as part of the PQV_POT_UK key definition.

Common Use Cases and Queries

Typical reporting scenarios include extracting all quality values configured for a product, validating that a product has no duplicate quality associations, and joining to the value master to retrieve descriptions for pricing or approval analysis. A representative query joining the three parent tables is:

• SELECT p.pdt_id, p.product_name, q.qve_id, pv.value_description FROM okl_pdt_pqy_vals v, okl_products p, okl_pqy_values pv WHERE v.pdt_id = p.pdt_id AND v.qve_id = pv.qve_id;
• Effectivity checks filter on FROM_DATE and TO_DATE to return only associations active at a given date.
• Duplicate or integrity checks use the PDQ_ID and PDT_ID combination, consistent with the U2 unique index, to detect data issues prior to migration or setup validation.
• Audit reporting relies on LAST_UPDATED_BY and LAST_UPDATE_DATE to trace configuration changes for compliance and change-control purposes.

Related Objects

The most significant related objects are the foreign-key parents and any views or APIs that externalize this association.

• OKL_PRODUCTS — parent of PDT_ID; holds the lease product master record.
• OKL_PDT_PQYS — parent of PDQ_ID; the product quality header grouping the values.
• OKL_PQY_VALUES — parent of QVE_ID; the quality value master that supplies individual values.
• OKL_PRODUCTS public views and product setup APIs consume rows from this table when rendering the Product Quality Values region.
• OKL_PDT_PQY_VALS_PK, OKL_PDT_PQY_VALS_U1, OKL_PDT_PQY_VALS_U2 — primary and unique constraints that enforce row identity and the (PDQ_ID, PDT_ID) business rule.