Search Results pqyv_tbl_type




Overview

OKL_PQY_PVT is a private (PVT-classified) PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema, belonging to the Oracle Lease and Finance Management (OLFM/OKL) product family. The "PQY" token in the package name corresponds to product quality — that is, the quality characteristics, conditions, or qualification criteria that can be associated with leased or financed products within an OKL contract. The package provides the low-level, internal data-manipulation and validation logic that supports the public product-quality API surface, including the maintenance of product quality definitions and their versioned copies.

A defining characteristic of this package is its role in shadowing the public API layer. The header declares two PL/SQL record and collection types: pqy_rec_type (mirroring the OKL_PDT_QUALITYS base table) and pqyv_rec_type (mirroring the OKL_PDT_QUALITYS_V view). The user's search term, pqyv_tbl_type, is the associative-array (index-by BINARY_INTEGER) collection type built upon pqyv_rec_type, used to pass sets of product-quality records between the public API and this private implementation in bulk. Each attribute defaults to the OKC_API.G_MISS_* sentinels, which is the standard EBS convention for distinguishing "no value supplied" from NULL during row processing.

Key Procedures and Functions

The documented interface exposes 14 procedures/functions. In approximate order of the internal processing cycle:

  • QC — A quality-control/consistency check routine that verifies the integrity of the package's internal state or the record being processed.
  • CHANGE_VERSION — Creates a new version of an existing product-quality definition, supporting the date-effective versioning model of OKL_PDT_QUALITYS.
  • API_COPY — Copies one product-quality record (typically a version or template) into a new record, populating the pqyv_rec_type/pqy_rec_type structures.
  • INSERT_ROW — Performs the physical insert of a new product-quality row, including WHO columns (created_by, creation_date, last_updated_by, etc.).
  • LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) and, where applicable, validates the object_version_number for optimistic concurrency control.
  • UPDATE_ROW — Updates an existing product-quality row and increments the object_version_number.
  • DELETE_ROW — Removes a product-quality row, subject to referential and date-effective integrity rules.
  • VALIDATE_ROW — Applies business-rule validation to the supplied record before it is written, returning status/error information to the caller.
  • LOAD_SEED_ROW — Loads seed (predefined) product-quality data, used during installation or upgrade.

The remaining documented routines are internal helpers invoked by these entry points. Parameter signatures are not reproduced here; the record/collection types above form the primary interface contracts.

Tables Accessed

Two underlying objects are documented, referenced through APPS synonyms:

  • OKL_PDT_QUALITYS — The base table storing product-quality definitions. This is the target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW, and the source for QC and LOAD_SEED_ROW. Its column data types determine the field types of pqy_rec_type.
  • PLITBLM — The PL/SQL API helper table (used by the EBS PL/SQL-API infrastructure) to persist multi-row error and status messages generated during validation.

Note that OKL_PDT_QUALITYS_V, though referenced by the header records, is a view rather than a base table.

Usage Notes

As a private package, OKL_PQY_PVT is not intended for direct invocation by customers. It is called by the corresponding public OKL product-quality API and is referenced by 17 other packages across the OKL schema, forming the persistence backbone of that API. Typical invocation paths are: the OLFM product-quality setup/trading forms, concurrent programs that import or version product-quality data, and upgrade or seed-load routines that call LOAD_SEED_ROW. Customizations should target the public API; calling the private layer directly bypasses validation and versioning safeguards. The package is compiled AUTHID CURRENT_USER and, per its header, was last built at script version 120.2 (2006/12/07), indicating stable, mature code across both 12.1.1 and 12.2.2.