Search Results g_normal_qa




Overview

OKC_TERMS_QA_GRP is a PL/SQL package in the APPS schema that implements the quality assurance (QA) validation engine for Oracle E-Business Suite contracts and terms authoring, part of the Enterprise Contracts (OKC) module. Its role is to execute configurable validation rules against contract documents, terms, deliverables and related entities, recording the outcome of every rule evaluation as a structured error, warning or success record. The package therefore underpins the QA checking that contract administrators trigger before a contract is approved, signed or otherwise progressed through its lifecycle. It is classified as a GRP (group) package, meaning it exposes shared types, constants and helper logic consumed by other QA-enabled APIs rather than a single end-user transaction. ETRM 12.2.2 documentation records four procedures/functions and identifies the object as referenced by 17 other packages, confirming its position as a core dependency of the contracts validation framework.

Key Procedures and Functions

  • QA_DOC — The principal driver procedure. It performs QA validation for a document (contract, template usage or related business document), iterating the applicable QA rules and logging resulting validation messages into OKC_QA_ERRORS_T. The header comment in the source records that from release 11.5.10 onward it accepts an additional validation-level input parameter, and that a commit parameter defaults to FND_API.G_TRUE for backward compatibility, allowing callers to suppress committing when they wish to control the transaction. It returns a sequence identifier as an out parameter.
  • CHECK_TERMS — Evaluates the terms and conditions associated with a document against the configured QA rules, identifying missing, conflicting or non-conforming articles and clauses. Results are expressed through the package's QA result record structures.
  • QA result typing — The package declares qa_result_rec_type and qa_result_tbl_type, the canonical structures used to carry document type/id, sequence, error severity, QA code, message name, problem description, suggestion text and five generic reference columns. It also declares BUSDOCDATES_REC_TYPE and BUSDOCDATES_TBL_TYPE for deliverable due-date events.
  • Global constants — The user search term g_normal_qa resolves to G_NORMAL_QA CONSTANT VARCHAR2(30) := 'NORMAL', the QA type indicator for standard (non-amendment) validation. It is paired with G_AMEND_QA := 'AMEND' and the status constants G_QA_STS_SUCCESS ('S'), G_QA_STS_ERROR ('E') and G_QA_STS_WARNING ('W'). Callers pass these values to select the validation mode and to interpret returned status.

Tables Accessed

  • OKC_DOC_QA_LISTS — Defines which QA rules apply to a given document type; the driver reads this to build the rule set.
  • OKC_QA_ERRORS_T — The transaction table into which validation results are written, including severity, QA code and message name.
  • OKC_BUS_DOC_TYPES_B — Supplies business document type metadata used to resolve applicable rules.
  • OKC_DELIVERABLES — Provides deliverable definitions and due dates checked by QA rules.
  • OKC_TEMPLATE_USAGES — Links documents to the templates governing their terms.
  • FND_NEW_MESSAGES — Resolves message names to translatable message text for the logged results.
  • PLITBLM — The PL/SQL character table used for bulk message/parameter handling.

Usage Notes

OKC_TERMS_QA_GRP is normally invoked indirectly: the Contracts authoring forms and the contract approval workflow call the QA driver when a user requests validation, and concurrent programs may invoke it in batch for large rule sets. Custom code should call QA_DOC rather than manipulating OKC_QA_ERRORS_T directly, passing G_NORMAL_QA or G_AMEND_QA from this package to select the validation mode, and using the QA status constants to interpret outcomes. Because the object is referenced by 17 other packages, changes to its signature or global constants have wide impact and should be avoided. The header date (2006) and stub version (120.1) indicate the package is long stable; behaviour is consistent between 12.1.1 and 12.2.2.