Search Results lock_pdt_quality_vals

Overview

The APPS.OKL_PDT_QUALITYS_PUB package body is a public API within the Oracle E-Business Suite Lease and Finance Management (formerly Oracle Lease Management) module. Its name encodes its purpose: PDT denotes product, QUALITYS denotes quality or quality-assurance specifications, and the PUB suffix identifies it as a public API built on the Oracle Application Object Library (AOL) API framework. The package serves as the transactional entry point for creating, maintaining, and validating the quality specifications associated with lease products, as well as the individual quality values that hang beneath each quality specification header.

In the leasing domain, a product must carry a set of quality or condition criteria that define acceptable characteristics of the asset being leased. The OKL_PDT_QUALITYS_PUB layer exposes this business functionality to callers through a supported, version-tolerant interface, delegating the actual data manipulation to the private implementation packages that follow the standard Oracle ETRM public/private (PUB/PVT) design pattern.

Key Procedures and Functions

The package body exposes twenty-three documented procedures and functions organized around two logical entities: the quality specification header and the quality values (detail lines) attached to it. The primary header-level operations are:

• CREATE_PDT_QUALITYS — Creates a new product quality specification record.
• UPDATE_PDT_QUALITYS — Modifies an existing quality specification.
• VALIDATE_PDT_QUALITYS — Performs validation of the quality specification data before or independent of persistence.
• LOCK_PDT_QUALITYS — Acquires a lock on the specification record to support concurrent-safe updates.
• DELETE_PDT_QUALITYS — Removes a quality specification.

The parallel set of detail-level operations governs the individual quality values belonging to a specification:

• CREATE_PDT_QUALITY_VALS — Creates quality value records for a specification.
• LOCK_PDT_QUALITY_VALS — Locks quality value records during update processing.
• UPDATE_PDT_QUALITY_VALS — Updates existing quality value records.
• DELETE_PDT_QUALITY_VALS — Deletes quality value records.
• VALIDATE_PDT_QUALITY_VALS — Validates quality value data.

Each entry is a thin wrapper that delegates to OKL_PDT_QUALITYS_PVT, OKL_PQY_PVT, or OKL_QVE_PVT, and uses FND_API for the standard p_init_msg_list, x_return_status, and x_msg_count/x_msg_data interface, with messages stored via FND_MSG_PUB and common validations routed through OKC_API.

Tables Accessed

The ETRM dependency metadata records a single table dependency, resolved through an APPS synonym: PLITBLM. This is the PL/SQL integer table type used as an internal bulk-processing collection and does not represent a business table. The actual persistence of quality specifications and values is encapsulated in the private packages (OKL_PDT_QUALITYS_PVT, OKL_PQY_PVT, OKL_QVE_PVT), which write to the OKL quality specification base tables. Callers should treat the public layer as the only supported access path and should not read or write those base tables directly.

Usage Notes

The package is invoked from the Lease Management product setup user interface, from concurrent programs that seed or migrate product quality data, and from custom extensions requiring programmatic maintenance of quality specifications. Standard practice is to call CREATE_, UPDATE_, or DELETE_ within a caller-controlled transaction, always checking x_return_status for FND_API.G_RET_STS_SUCCESS and iterating FND_MSG_PUB for error detail. Because the package is not referenced by any database object, it is a top-level entry point with no constraint or trigger dependencies. It is itself referenced by five other packages, confirming its role as a shared service in the OKL product-configuration stack. In EBS 12.1.1 and 12.2.2 the interface is unchanged; the online patching architecture of 12.2.2 requires only that dependent custom code be editioned consistently with the APPS edition in which these APIs are compiled.