Search Results lock_pdt_qualitys

Overview

OKL_PDT_QUALITYS_PVT is a private PL/SQL API package within the Oracle E-Business Suite (EBS) Lease Management (OKL) module, part of the larger Oracle Contracts family. The package encapsulates the business logic required to manage "quality" attributes and their associated values for lease product lines and related pricing structures. In the OKL data model, quality records (PQY) represent qualifiers or quality characteristics tied to a product or pricing entity, while quality values (QVE) represent the individual value instances associated with those quality definitions. This package provides the private implementation layer that supports the public quality management APIs exposed elsewhere in the OKL schema.

The package is classified as PVT (private), meaning it is intended for internal consumption by other Oracle Lease Management packages rather than being a directly callable public API for external integrations. It is declared with AUTHID CURRENT_USER, so it executes with the privileges of the invoking session rather than the definer, a standard convention for EBS private APIs that rely on APPS schema synonyms and row-level security established by the calling context.

Global constants such as G_PKG_NAME, G_APP_NAME, and standard error tokens (SQLERRM, SQLCODE) follow Oracle's unified error-handling pattern for contract APIs, enabling consistent message propagation through the OKC_API messaging framework. A dedicated exception, G_EXCEPTION_HALT_VALIDATION, allows validation logic to short-circuit processing when critical data errors are detected.

Key Procedures and Functions

The package exposes twenty-three documented procedures and functions. The core record-management procedures operate on the pqyv_rec_type and qvev_tbl_type structures:

• CREATE_PDT_QUALITYS — Inserts a new quality record together with its associated quality values, accepting an input record and value table and returning the persisted records.
• UPDATE_PDT_QUALITYS — Modifies an existing quality record and its dependent value rows.
• VALIDATE_PDT_QUALITYS — Performs business-rule validation on a quality record prior to persistence, raising the halt-validation exception when errors are found.
• LOCK_PDT_QUALITYS — Acquires a row-level lock on the quality record, typically used in concurrent modification scenarios to prevent lost updates.
• DELETE_PDT_QUALITYS — Removes a quality record and optionally its related value rows.

A parallel set of procedures manages the value-level entity:

• CREATE_PDT_QUALITY_VALS — Inserts individual quality value rows associated with a parent quality record.
• UPDATE_PDT_QUALITY_VALS — Updates existing quality value rows.
• DELETE_PDT_QUALITY_VALS — Deletes quality value rows.
• LOCK_PDT_QUALITY_VALS — Locks value rows for consistent concurrent processing.
• VALIDATE_PDT_QUALITY_VALS — Validates value data against defined rules before commit.

The remaining documented procedures support the same object hierarchy, handling subtype conversions between okl_pqy_pvt and okl_qve_pvt record definitions and standard API plumbing (API version checks, message list initialization, and return status handling).

Tables Accessed

The package operates against two documented database objects, reached through APPS synonyms:

• OKL_PQY_VALUES — The primary transactional table storing quality value records. All create, update, delete, lock, and validate operations ultimately read from or write to this table.
• PLITBLM — A standard Oracle Application Object Library (FND) message-handling table used by the API messaging framework to store and retrieve translatable error and warning messages during exception processing.

Reads against OKL_PQY_VALUES are performed during validation and locking, while inserts, updates, and deletes occur during the corresponding CRUD procedures. PLITBLM is accessed indirectly through the messaging utilities invoked when errors are logged.

Usage Notes

As a private package, OKL_PDT_QUALITYS_PVT is not intended for direct invocation by end users or external systems. It is referenced by two other packages within the OKL schema, which act as public wrappers and orchestrate calls during lease product and pricing configuration. Typical invocation paths include:

• Oracle Forms — OKL product definition and pricing setup forms call the public wrapper APIs, which in turn delegate to this private package for validation and DML.
• Concurrent programs — Batch processes that mass-maintain quality attributes for lease products rely on the same underlying logic.
• Custom extensions — Customers extending Oracle Lease Management should call only the documented public APIs; direct reliance on this PVT package is unsupported and subject to change between releases such as 12.1.1 and 12.2.2.

Developers should note the use of NOCOPY OUT parameters for status and message data, and should honor the standard x_return_status contract (typically OKC_API.G_RET_STS_SUCCESS, ERROR, or UNEXPECTED_ERROR) when interpreting results from wrapper calls.