Search Results msg_tbl_type

Overview

OKC_QA_CHECK_PVT is a private PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module. It supports the Quality Assurance check list processing framework that governs validation and business-rule enforcement on contract and sub-class records. The package belongs to the OKC_QA_CHECK family of objects and is classified as a PVT package, meaning its interfaces are intended for internal consumption by other OKC packages rather than directly by forms or external integrations.

The central role of OKC_QA_CHECK_PVT is to execute configured QA check lists against contract entities. QA check lists allow implementers to associate a series of validation processes with a contract class, subclass, or operation. Each process is defined in the OKC_PROCESS_DEFS_V view and points to a package and procedure that performs the actual validation. OKC_QA_CHECK_PVT drives those processes and collects the resulting messages.

A distinguishing feature of the package is its internal message architecture. It declares a record type (qa_msg_rec_type) capturing severity, process name, description, package name, procedure name, error status, and a data payload, together with a collection type (qa_msg_tbl_type) indexed by binary integer. The subtype msg_tbl_type used throughout the package is an alias for that collection, which is why the term appears prominently in searches. A public global, pub_qa_msg_tbl, exposes the accumulated messages to callers.

Key Procedures and Functions

The documented interface of the package consists of one procedure:

• EXECUTE_QA_CHECK_LIST — The driver routine that runs a QA check list for a given contract context. It resolves the processes associated with the applicable class or subclass, invokes each referenced validation procedure, and accumulates results into the public message table. Severity values are derived from OKC_QA_LIST_PROCESSES_V, and error status flags are set per process so callers can determine whether the overall check succeeded or produced warnings and errors.

The package also declares a number of global message constants that mirror those in OKC_API, including G_NO_PARENT_RECORD, G_FORM_UNABLE_TO_RESERVE_REC, G_REQUIRED_VALUE, G_INVALID_VALUE, and various token placeholders such as G_COL_NAME_TOKEN and G_PARENT_TABLE_TOKEN. These constants are used to build consistent, translatable error messages when a QA check fails.

Tables Accessed

The package reads and writes the following documented objects:

• OKC_QA_CHECK_LISTS_B — Stores the QA check list definitions that drive execution.
• OKC_QA_LIST_PROCESSES — Associates check lists with individual validation processes and supplies the severity attribute returned in messages.
• OKC_CLASS_OPERATIONS, OKC_OPERATIONS_B, OKC_SUBCLASSES_B, and OKC_K_HEADERS_B — Provide the class, subclass, operation, and contract header context used to resolve which check list applies to the record under validation.
• DBMS_SQL and PLITBLM — Utility packages used for dynamic SQL and PL/SQL table manipulation supporting generic process execution and message handling.

Usage Notes

OKC_QA_CHECK_PVT is referenced by eleven other packages, confirming its role as a shared internal service within the Contracts quality-assurance layer. It is typically invoked indirectly: contract maintenance forms and contract API processing call higher-level OKC packages, which in turn call EXECUTE_QA_CHECK_LIST when a record is saved, validated, or transitioned through an operation. Custom code should avoid calling this private package directly; the supported approach is to invoke the public OKC_API or OKC_QA_CHECK entry points that internally delegate to this package. Because a single execution can return multiple messages, callers must inspect the full contents of the returned message table rather than assuming a single error.