Search Results okc_qa_check_pvt




Overview
Explore in AI Chat

Overview

OKC_QA_CHECK_PVT is a private (PVT) PL/SQL package body in the APPS schema of Oracle E-Business Suite, part of the Oracle Contracts (OKC) module and the broader Enterprise Contracts / ETRM (Enterprise Transaction and Reference Management) technology stack. In EBS 12.1.1 and 12.2.2 this package implements the internal programming logic that drives Quality Assurance (QA) check list processing against contract documents. Its role is to evaluate configurable QA check lists — question-and-answer validations, compliance rules, and prerequisite conditions — against a contract header or line before that contract may advance to the next stage of its lifecycle. Because the package is classified as a private API, it is not intended for direct customer invocation; the public contract APIs (notably OKC_API) call into it to enforce governance rules as contracts are authored, approved, and submitted. The body is registered as VALID in the data dictionary and depends heavily on shared EBS infrastructure packages, including FND_API, FND_MSG_PUB, FND_LOG, and FND_PROFILE, which supply the standard error-handling, message-stack, debug-logging, and profile-option conventions used throughout ETRM development.

Key Procedures and Functions

The documented interface exposes a single public entry point:

  • EXECUTE_QA_CHECK_LIST — The core routine that evaluates a QA check list in the context of a specific contract. It reads the configured check list and its associated processes and parameters, dynamically assembles the required checks, executes them, and returns results to the calling contract operation. The routine relies on DBMS_SQL together with PLITBLM for dynamic SQL construction — a pattern used when the set of check expressions is data-driven and cannot be resolved at compile time.

Although only EXECUTE_QA_CHECK_LIST is documented as a formal entry point, ETRM metadata records the body as self-referential (OKC_QA_CHECK_PVT references OKC_QA_CHECK_PVT), indicating internal helper routines are declared and invoked within the same package. All error reporting is channelled through FND_API and FND_MSG_PUB; diagnostic output is emitted through FND_LOG when logging is enabled via FND_PROFILE.

Tables Accessed

The package operates against the following documented tables and views (accessed through APPS synonyms):

DBMS_SQL and PLITBLM are Oracle-supplied packages, not application tables, and are consumed for dynamic SQL parsing, binding, and execution.

Usage Notes

OKC_QA_CHECK_PVT is invoked indirectly. The standard path is through OKC_API during contract authoring, validation, or workflow-driven approval, where the QA result determines whether the contract may proceed. ETRM metadata records the package as referenced by eleven other database objects, confirming that it is a shared internal service rather than a standalone entry point. Debug tracing is governed by the FND profile options that enable FND_LOG output; because FND_MSG_PUB is used, all exceptions surface to the caller as standard EBS API messages. Custom code should never call OKC_QA_CHECK_PVT directly — the supported approach is to use the public OKC_API routines, which enforce the correct calling sequence, context initialisation, and commit handling. Because the package uses DBMS_SQL, care must be taken with respect to shared pool usage and cursor management in high-volume batch processing.