Search Results okc_qa_check_list_pvt




Overview
Explore in AI Chat

Overview

The APPS.OKC_QA_CHECK_LIST_PVT package is a private PL/SQL API within the Oracle E-Business Suite Contract Lifecycle Management (OKC) module. It provides the internal implementation layer for managing Quality Assurance (QA) check lists associated with contracts, contract templates, and contract deliverables. In the Oracle EBS architecture, packages classified as "PVT" (private) are not intended for direct invocation by external callers; instead, they are wrapped by a corresponding public package — in this case OKC_QA_CHECK_LIST_PUB — which exposes supported entry points while the _PVT package handles the underlying business logic, validation, concurrency locking, and persistence operations.

The package supports the definition and maintenance of QA check lists and the individual QA processes and QA parameters that comprise a check list. These constructs allow organizations to define structured quality verification steps that must be completed against contract terms, ensuring consistency in contract authoring and compliance workflows.

Key Procedures and Functions

The package exposes sixteen documented procedures, organized into three functional groupings.

Parameter lists are not documented in the ETRM metadata and should not be assumed; developers must inspect the package specification for current signatures.

Tables Accessed

The ETRM metadata does not enumerate specific base tables for this package. However, the dependency listing confirms that OKC_QA_CHECK_LIST_PVT invokes sibling packages OKC_QCL_PVT, OKC_QLP_PVT, and OKC_QPP_PVT (QA check list, QA process, and QA parameter private packages, respectively), as well as the general OKC_API utility package. The actual DML against OKC QA tables (such as OKC_QA_CHECK_LISTS_B/TL and their process and parameter child tables) is delegated to those helper packages rather than performed directly here. This layered design centralizes table access and preserves consistency across QA-related APIs.

Usage Notes

Because this is a _PVT package, it is not a supported integration point. External callers should use OKC_QA_CHECK_LIST_PUB, which delegates to this package. The dependency metadata confirms that OKC_QA_CHECK_LIST_PUB references this package, and that OKC_QA_CHECK_LIST_PVT is referenced by exactly one other package. Typical invocation paths include the Contract Terms and QA setup forms within the Contracts (OKC) responsibility, concurrent programs that seed or migrate QA check list data, and custom extensions that have been granted explicit access. Direct calls bypass the public API contract and risk breaking with patches. All calls must honor the LOCK/VALIDATE sequencing to avoid concurrency errors and referential integrity violations.