Search Results insert_deliverables_qa_checks

Overview

OKC_REP_QA_CHECK_PVT is a private PL/SQL package in the Oracle Contracts (OKC) module of Oracle E-Business Suite, used within the repository (OKC_REP) subsystem. Its business function is to execute quality assurance (QA) checks against contract terms and deliverables that were authored or generated from the contract repository templates. In the Oracle Contracts architecture, contract terms are assembled into structured term groups, and each term group may be subject to configured QA rules defined in the QA list lookups and QA group definitions. The package provides the runtime engine that evaluates those rules, reports success, error, or warning statuses, and persists findings such as deliverables QA checks.

The $Header line (OKCVREPQACHKS.pls 120.0.12000000.1) indicates a 12.0-series source file, which is consistent with the file also running under 12.1.1 and 12.2.2 since the Contracts QA framework was carried forward largely unchanged. The package is classified as PVT, meaning it is not intended for direct customer invocation; it is called by other OKC APIs and forms.

Key Procedures and Functions

The package exposes two documented entry points:

• PERFORM_CONTRACT_QA_CHECK — Runs the QA check rules over a contract's terms. Based on the package constants, it evaluates rules against the OKC_TERM_QA_LIST lookup and the term QA group (OKC_TERMS_QA_GRP), returning statuses of success, error, or warning (G_QA_STS_SUCCESS, G_QA_STS_ERROR, G_QA_STS_WARNING). The package standardizes error signalling using FND_API constants such as G_RET_STS_ERROR and G_UNEXPECTED_ERROR, with the standard ERROR_MESSAGE and ERROR_CODE tokens for exception propagation.
• INSERT_DELIVERABLES_QA_CHECKS — Creates or records QA check results specifically for contract deliverables, writing into the deliverables QA structures. This supports validation that deliverable definitions (dates, quantities, parties, contacts) comply with configured business rules before the contract is finalized.

A business-event table type, EVENT_TBL_TYPE, is declared as OKC_TERMS_QA_GRP.BUSDOCDATES_TBL_TYPE, allowing multiple contract business document dates to be passed into a check in a single call. Module-level globals G_PKG_NAME, G_APP_NAME, and G_MODULE provide consistent logging and error context.

Tables Accessed

The package reads and writes several application tables through APPS synonyms, notably:

• OKC_REP_CONTRACTS_ALL and OKC_REP_CONTRACTS_ALL_EXT_B — the repository contract header and its extensible attributes, providing the contract identifier that the token g_contract_id_token references.
• OKC_DOC_QA_LISTS, OKC_BUS_DOC_TYPES_B, OKC_BUS_DOC_TYPES_TL — QA rule definitions and business document types governing which checks apply.
• OKC_DELIVERABLES — the deliverables being QA-checked.
• OKC_CONTRACT_RISKS — risk records that a QA check may produce or reference.
• OKC_REP_CONTACT_ROLES_TL, HZ_PARTIES, HZ_RELATIONSHIPS — party and contact role data validated during QA.
• FND_USER, FND_DESCR_FLEX_COLUMN_USAGES, EGO_FND_DSC_FLX_CTX_EXT, EGO_OBJ_AG_ASSOCS_B, EGO_PAGE_ENTRIES_B — user identity and descriptive flexfield/page metadata used when rendering or validating attribute-based checks.

Usage Notes

Because the package is PVT, it is invoked internally by Oracle Contracts forms and by higher-level OKC APIs rather than by custom code. Typical call sites include the contract authoring/repository forms when a user saves or validates a contract, and concurrent programs that perform bulk QA over repository contracts. The g_contract_id_token referenced in the source represents the bind token used to pass the current contract's ID into the QA check, ensuring checks are scoped to the contract in context. Customizations should prefer public OKC APIs; direct calls to OKC_REP_QA_CHECK_PVT are unsupported and may break across patches from 12.1.1 to 12.2.2.