Search Results update_qa_check_list

Overview

OKC_QA_CHECK_LIST_PVT is a private PL/SQL package body in the Oracle E-Business Suite Contracts (OKC) module, owned by the APPS schema. Its classification as a PVT (private) API indicates that it is intended for internal consumption within the OKC quality assurance framework rather than as a directly callable public interface. The package provides a thin wrapper layer over the underlying entity-handling package OKC_QCL_PVT, exposing a consistent set of transactional operations for two distinct business entities: QA check lists and QA processes, along with their associated parameters (QA parms).

The primary business purpose of this package is to centralize the create, update, delete, lock, and validate operations for quality assurance configuration data used by Oracle Quality and Contracts. By delegating actual DML to OKC_QCL_PVT, the package maintains a layered architecture in which validation, message handling, and record locking are consistently applied. The header comment ($Header: OKCCQCLB.pls 120.0 2005/05/25) confirms the source file is OKCCQCLB.pls, which places this code squarely within the OKC module's QA check list generation code family.

Key Procedures and Functions

The package exposes 16 documented procedures and functions, organized into logical groupings:

• Check List Operations: CREATE_QA_CHECK_LIST, UPDATE_QA_CHECK_LIST, DELETE_QA_CHECK_LIST, LOCK_QA_CHECK_LIST, and VALIDATE_QA_CHECK_LIST manage the lifecycle of QA check list definitions.
• Process Operations: CREATE_QA_PROCESS, UPDATE_QA_PROCESS, DELETE_QA_PROCESS, LOCK_QA_PROCESS, and VALIDATE_QA_PROCESS perform the equivalent lifecycle operations for QA processes.
• Parameter Operations: CREATE_QA_PARM, UPDATE_QA_PARM, DELETE_QA_PARM, LOCK_QA_PARM, and VALIDATE_QA_PARM manage QA parameter records.
• Language Support: ADD_LANGUAGE supports multilingual (MLS) installation for translated QA data.

Where the ETRM excerpt provides detail, the check list procedures accept a standard API signature containing p_api_version, p_init_msg_list, x_return_status, x_msg_count, x_msg_data, and a qclv_rec_type record. In each case, the wrapper delegates to the corresponding insert_row, update_row, or delete_row procedure in OKC_QCL_PVT. The LOCK and VALIDATE procedures follow the same delegation model. Notably, the searched term delete_qa_process corresponds to the DELETE_QA_PROCESS procedure, which mirrors DELETE_QA_CHECK_LIST and routes the deletion to the underlying entity package.

Tables Accessed

The ETRM metadata lists no directly referenced tables for this package. This is expected given that the package is a wrapper: all physical DML against the QA check list, QA process, and QA parameter tables is performed by OKC_QCL_PVT and the base entity handling routines. Any base tables (for example, the OKC QA check list and QA process tables) are reached indirectly through the underlying package and its APPS synonyms. Consequently, this package should be treated as a pass-through interface rather than a data-access layer.

Usage Notes

Because OKC_QA_CHECK_LIST_PVT is classified as a private API, it is not typically invoked directly by external custom code. The package is referenced by one other package within the OKC module, indicating a controlled internal call graph. In practice, the procedures are reached from the QA check list and QA process user interfaces in Oracle Contracts and Oracle Quality, from concurrent programs that generate or maintain QA configuration, and from other OKC packages that require a validated, message-aware entry point for check list and process maintenance. Developers extending QA functionality in EBS 12.1.1 or 12.2.2 should call the corresponding public APIs rather than this private wrapper, and must always honor the standard API conventions (initializing message lists, checking x_return_status, and retrieving messages via x_msg_count and x_msg_data).