Search Results g_qa_sts_warning

Overview

OKC_TERMS_QA_GRP is a group-type PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, belonging to the Enterprise Contracts / Terms and Conditions (ETRM) schema owned by the APPS database user. The package implements quality assurance (QA) processing for contract Terms and Conditions authored through Oracle Contracts. Its central role is to validate the structure, completeness, and correctness of terms and conditions entered against a contract or template, and to surface validation failures back to the calling layer through the standard FND message and return-status framework.

The source header indicates the package has been in continuous use since at least the 11i/12.0 era (version 120.5, with a change log entry dated 2008). It is a private, internal API classified as a GRP package, meaning it is not intended as a public extension point but is invoked by other EBS modules. The constants block establishes the full set of FND_API global message tokens — including G_UNABLE_TO_RESERVE_REC, G_RECORD_DELETED, G_RECORD_CHANGED, G_REQUIRED_VALUE, and G_INVALID_VALUE — plus the standard return-status codes G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR. It is this QA-oriented framework that underlies the g_qa_sts_error status value surfaced during terms QA processing.

Key Procedures and Functions

• QA_DOC — The principal driver for the terms QA process. It orchestrates the evaluation of a contract document or template against its assigned QA lists and terms requirements, determines pass/fail outcomes, and loads QA validation errors into the OKC_QA_ERRORS_T staging table. The g_qa_sts_error return status is generated by this routine when one or more terms validations fail.
• CHECK_TERMS — A sub-validator invoked from QA_DOC that inspects individual terms and conditions structures, verifying required values, valid values, and referential integrity against the term definitions in effect for the document. It contributes the per-term diagnostics that ultimately roll up to the QA error status.

The metadata documents four procedures/functions in total; only these two are named in the excerpt. Both are internal to the package's QA group and return FND_API standard status values (success, error, unexpected error).

Tables Accessed

• OKC_DOC_QA_LISTS — Defines the QA checklists assigned to document types; read to determine which QA criteria apply.
• OKC_QA_ERRORS_T — The QA error staging table; written with validation failures that populate the g_qa_sts_error result.
• OKC_DELIVERABLES — Contract deliverables associated with the terms being validated; read for completeness checks.
• OKC_TEMPLATE_USAGES — Indicates which templates are in use and their applicability; read to scope QA to the correct template set.
• OKC_BUS_DOC_TYPES_B — Business document type definitions; read to resolve QA policy per document type.
• FND_NEW_MESSAGES — FND message repository; read to load the localized message text emitted with QA errors.
• PLITBLM — PL/SQL internal table type used for bulk error/message collection.

Usage Notes

OKC_TERMS_QA_GRP is invoked from the Oracle Contracts forms and concurrent programs during terms authoring and template validation. It is referenced by 17 other packages in the ETRM schema, most of which call it through the QA group's public entry point to drive bulk QA. Because it is a GRP package and relies on FND messages, callers must initialize FND message and global contexts before invocation. The g_qa_sts_error identifier is the status emitted when QA validation fails; developers tracing that token should look first at OKC_QA_ERRORS_T rows produced by QA_DOC. Direct custom calls are not supported; use the Contracts public APIs instead.