Results for “ptl_id”

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

Overview

OKL_PDT_PQYS is a table in the OKL (Leasing and Finance Management) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. Its documented description is "Association of qualities with product." Functionally, the table serves as the junction that links product templates to the qualities defined for a product, enabling a leasing product to carry a configurable set of quality attributes that drive pricing, qualification rules, and downstream contract generation.

The metadata notes a unique constraint OKL_PDT_PQYS_U2 on (PTL_ID, PQY_ID), meaning a given product template can be associated with a given quality only once. From a Data Vault modeling perspective, the mined classification is satellite-leaning, which suggests this object is best treated as an attribute-bearing structure attached to a parent product/template hub rather than a pure many-to-many link. The documented schema for 12.2.2 lists 11 columns under owner OKL.

Key Information Stored

The table stores the association between a product template and a product quality, together with standard EBS audit and concurrency columns. The most significant columns are:

• ID — surrogate primary key, enforced by OKL_PDT_PQYS_PK and also indexed by OKL_PDT_PQYS_U1. This is the internal identifier referenced by dependent child rows.
• PTL_ID — foreign key to OKL_PDT_TEMPLATES, identifying the product template to which the quality association belongs. Together with PQY_ID it forms the business-key candidate OKL_PDT_PQYS_U2.
• PQY_ID — foreign key to OKL_PDT_QUALITYS, identifying the quality attached to the template.
• FROM_DATE and TO_DATE — effective dating for the association, supporting date-tracked or versioned quality assignments.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "Who" audit columns maintained by Oracle Application Object Library.

The surrogate ID is distinct from the business key (PTL_ID, PQY_ID), so integrations should resolve records via the unique pair rather than assuming ID values are portable across environments.

Common Use Cases and Queries

Typical usage includes validating which qualities are configured for a given product template, reporting the full set of qualities available for a leasing product, and reconciling associations against effective dates. A representative query joining template and quality descriptions is:

• SELECT p.ID, p.PTL_ID, p.PQY_ID, p.FROM_DATE, p.TO_DATE FROM OKL_PDT_PQYS p WHERE p.PTL_ID = :template_id;
• SELECT p.* FROM OKL_PDT_PQYS p JOIN OKL_PDT_QUALITYS q ON p.PQY_ID = q.ID WHERE TRUNC(SYSDATE) BETWEEN p.FROM_DATE AND NVL(p.TO_DATE, SYSDATE);
• Retrieving dependent quality values: SELECT v.* FROM OKL_PDT_PQY_VALS v WHERE v.PDQ_ID = :pdq_id;

These patterns support product configuration audits, effective-date validation, and data migration verification between 12.1.1 and 12.2.2 environments.

Related Objects

The following objects are most closely tied to OKL_PDT_PQYS:

• OKL_PDT_TEMPLATES — parent table; joined via OKL_PDT_PQYS.PTL_ID = OKL_PDT_TEMPLATES.ID.
• OKL_PDT_QUALITYS — quality definition table; joined via OKL_PDT_PQYS.PQY_ID = OKL_PDT_QUALITYS.ID.
• OKL_PDT_PQY_VALS — child table holding quality values; references this table through OKL_PDT_PQY_VALS.PDQ_ID = OKL_PDT_PQYS.ID.
• Supporting constraints OKL_PDT_PQYS_PK, OKL_PDT_PQYS_U1, and OKL_PDT_PQYS_U2, which enforce identity and uniqueness on ID and (PTL_ID, PQY_ID).

Together these objects form the product-quality configuration cluster within OKL, with OKL_PDT_PQYS acting as the central association point between templates, qualities, and their assigned values.