Search Results execute_qa_check_list

Overview

OKC_QA_CHECK_PUB is the public API wrapper for the Oracle Contracts quality assurance (QA) check list subsystem within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its principal purpose is to expose a stable, externally callable entry point for the execution of a quality assurance check list against a contract. The package body analyzed here carries the header identifier OKCPQACB.pls 120.0, dated 2005/05/25, indicating that the logic has been stable across the 11i and R12 code lines, including the 12.1.1 and 12.2.2 releases.

The business function addressed by this package is the systematic verification of contractual terms against predefined quality criteria. Contract administrators and quality reviewers invoke check lists to validate that negotiated agreements satisfy internal quality gates before approval, signature, or downstream fulfillment. The public package acts as a thin façade: it performs API housekeeping, fires user hooks, and then delegates to OKC_QA_CHECK_PVT, the private implementation package where the substantive processing resides.

Key Procedures and Functions

The package body exposes a single documented procedure:

• EXECUTE_QA_CHECK_LIST — Executes a specified quality assurance check list for a given contract. The procedure accepts an API version, initialization flag, check list identifier, contract header identifier, and an override flag, and returns standard EBS API outputs (return status, message count, message data, and a message table). Its implementation follows the canonical Oracle EBS API pattern: it calls OKC_API.START_ACTIVITY to initialize the API context, invokes okc_util.call_user_hook with the 'B' (before) phase, delegates to OKC_QA_CHECK_PVT.execute_qa_check_list, then invokes the user hook again for the 'A' (after) phase. Return status values are propagated through the standard G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR constants, with exceptions raised via G_EXCEPTION_ERROR and G_EXCEPTION_UNEXPECTED_ERROR. Because the procedure is defined in the _PUB package, the parameters and body remain contractually stable between patch levels.

Tables Accessed

The ETRM metadata for this object lists no directly referenced tables through APPS synonyms. All data access is concentrated in the private package OKC_QA_CHECK_PVT and in the OKC schema's underlying check list and contract tables (for example, the QA check list definition and result tables whose identifiers are passed in as p_qcl_id and p_chr_id). Because the public body only orchestrates API plumbing, hooks, and delegation, any direct DML against QA check list headers, lines, and results occurs in the private layer. Consumers should treat the public surface as an abstraction over those tables rather than attempting to query them directly.

Usage Notes

OKC_QA_CHECK_LIST is typically invoked from Oracle Contracts forms when a user selects and runs a check list against a contract, and from custom PL/SQL that needs to programmatically trigger QA validation. The ETRM metadata records that the package is referenced by nine other database objects, confirming its role as a shared dependency within the OKC module. Callers must supply a valid API version and initialize the message list when required, and must inspect x_return_status together with the returned message table rather than relying on exceptions alone. Because the procedure honors AFLOG_ENABLED via the l_debug flag and participates in the OKC user hook framework, customizations should be placed in the supported hook points ('B' and 'A') instead of modifying the package body. The p_override_flag allows callers to bypass failing checks under controlled authorization, so its use should be restricted and audited in production environments.