Search Results validate_severity

Overview

OKC_QLP_PVT is a private PL/SQL package body in the APPS schema that implements the validation and persistence logic for QA List Process records in Oracle E-Business Suite Contracts (OKC). It operates on the qlpv_rec_type record structure, which corresponds to the OKC_QA_LIST_PROCESSES entity — the association between QA check lists and the processes by which those check lists are applied to contract documents. The package is classified as PVT (private), meaning it is an internal implementation unit that is not intended as a public integration API; it is consumed by the public OKC API layer and by other private packages that delegate list-process maintenance to it.

The body defines a standard set of error tokens and constants, including G_NO_PARENT_RECORD, G_UNEXPECTED_ERROR, G_VALUE_NOT_UNIQUE, and the G_EXCEPTION_HALT_VALIDATION exception, which is raised to short-circuit validation once a fatal error has been recorded. Return status is reported through OKC_API.G_RET_STS_SUCCESS and the companion error status constants, and debug output is gated on the AFLOG_ENABLED profile option.

Key Procedures and Functions

• VALIDATE_ROW / Validate_Attributes — Central validation entry point for an OKC_QA_LIST_PROCESSES record. It drives required-value, foreign-key, uniqueness, and parent-record checks, accumulating messages through OKC_API.set_message and returning the aggregated status.
• QC — Performs the individual validation steps that back the overall validate routine, including the documented validate_qcl_id routine that confirms the QCL_ID is populated and that a matching row exists in OKC_QA_CHECK_LISTS_B.
• INSERT_ROW — Creates a new QA list process record after validation succeeds.
• UPDATE_ROW — Applies changes to an existing QA list process record.
• DELETE_ROW — Removes a QA list process record.
• LOCK_ROW — Obtains a row-level lock prior to update or delete to enforce concurrency control.
• API_COPY — Copies list-process records, supporting cloning scenarios at the API layer.
• CHANGE_VERSION — Manages the version attribute of the entity, supporting the Contracts versioning model.

The user search term validate_severity has no documented counterpart in this package's published interface; severity handling is not part of the OKC_QLP_PVT procedure list, and the search should be directed to the QA validation or message-framework packages.

Tables Accessed

• OKC_QA_CHECK_LISTS_B — Read to enforce the foreign key on QCL_ID, verifying that the referenced check list definition exists.
• OKC_QA_LIST_PROCESSES — The primary entity table maintained by this package; insert, update, delete, lock, and validation operations all target this table (via the OKC_QA_LIST_PROCESSES_V view where applicable).
• OKC_PROCESS_DEFS_B — Read to resolve and validate the process definition referenced by the list-process record.
• PLITBLM — The EBS message repository, accessed indirectly through OKC_API.set_message for token substitution and message text retrieval.

Usage Notes

OKC_QLP_PVT is invoked indirectly rather than called directly by end users. Its typical call paths are the Contracts QA setup forms and the OKC public API layer, which route insert, update, delete, and validate requests into the corresponding private routines. Because the package is classified PVT and is referenced by two other packages, customizations should not call it directly; instead, use the supported public OKC APIs that encapsulate this logic. Developers reviewing validation failures should note that the package raises G_EXCEPTION_HALT_VALIDATION on the first fatal error, so only one message may be surfaced per call. The header revision ($Header: OKCSQLPB.pls 120.0 2005/05/25) indicates a stable, long-lived implementation carried forward across 12.1.1 and 12.2.2 with no functional change to this body.