Results for “okl_pqy_values_v”

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

Overview

OKL_PQY_VALUES_V is a reporting and integration view in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, owned by the APPS schema. It exposes values that are attached to Product Qualities and is used by the Product – Quality Value setup flow during Product configuration. In functional terms, Product Qualities define the attributes and constraints that govern how lease and finance products behave, and the quality values captured through this view represent the specific permitted or assigned values bound to those qualities. The view therefore serves as a read layer over the quality-value setup data, allowing product definition screens, validation logic, concurrent programs, and external integrations to reference quality values consistently.

Because it is a view rather than a base table, OKL_PQY_VALUES_V does not introduce additional transactional storage. Instead, it presents a controlled projection of the underlying data, retaining surrogate keys and audit columns while shielding consumers from any physical differences in the base object. This makes it a stable, query-friendly interface for reporting on product quality configuration.

Underlying Base Objects

The view is defined over a single documented base object, available in the APPS schema through the synonym OKL_PQY_VALUES. The view text selects directly from this base table, aliasing it as QVEB, and maps each base column to a same-named view column. No joins, unions, or aggregations are applied, so the view is a straightforward column projection rather than a denormalized or transformed dataset.

Each row in OKL_PQY_VALUES corresponds to one quality value record associated with a Product Quality (PQY_ID). The view therefore inherits a one-to-one relationship with the underlying table: every row exposed by the view maps to exactly one row in OKL_PQY_VALUES, identified by the ROWID passed through as ROW_ID and by the primary key ID. Filtering, sorting, and validation applied against the view operate directly against the base table's data, and the view reflects commit-time visibility in the normal Oracle read-consistency model.

Key Columns

• ROW_ID – The base table ROWID, useful for set-based operations and row identification.
• ID – The unique surrogate key identifying each quality value record.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the EBS framework to detect concurrent updates.
• PQY_ID – Foreign key to the parent Product Quality, establishing the relationship between a quality and its assigned values.
• VALUE – The actual quality value captured for the parent quality.
• DESCRIPTION – Descriptive text explaining or qualifying the value.
• FROM_DATE / TO_DATE – Effective date range controlling when the value is valid.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns recording who created and last modified the record and when.

Common Use Cases and Queries

Typical uses include reporting on the values configured for a given product quality, verifying effective-dated setup before product activation, and supporting integrations that need to synchronize or validate quality values with external systems.

SELECT id, pqy_id, value, description, from_date, to_date
FROM   apps.okl_pqy_values_v
WHERE  pqy_id = :p_pqy_id
ORDER  BY value;

To restrict results to currently effective values:

SELECT pqy_id, value, description
FROM   apps.okl_pqy_values_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(from_date, SYSDATE)
                          AND NVL(to_date, SYSDATE);

Audit-oriented queries can join the view back to the parent quality definition using PQY_ID to produce a complete product quality configuration report.