Search Results freeze_checklist

Overview

OKC_REP_CLOSEOUT_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, specifically within the Repository Contracts (OKC_REP) schema domain. It encapsulates the business logic for closing out and revising repository-type contracts, including the management of contract deliverables, checklists, and closeout validation tasks. The package is declared with AUTHID CURRENT_USER and defines the standard FND_API global constants (G_FALSE, G_TRUE, G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR) alongside QA (quality assurance) status constants sourced from OKC_TERMS_QA_GRP. Because it is a private API, it is not intended for direct external invocation and is instead called by other OKC packages and internal processing routines.

A distinguishing element of this package, relevant to the user search term g_status_signed, is the constant G_STATUS_SIGNED CONSTANT VARCHAR2(30) := 'SIGNED'. This global constant represents the contract status value indicating that a repository contract has reached its signed state. Closeout logic in this package depends on this status to determine whether a contract is eligible for closeout processing — for example, validating that a contract is fully signed before allowing deliverables to be copied, checklists to be revised or frozen, or closeout tasks to be validated and activated. The companion constant G_NORMAL_QA (value 'NORMAL') and the OKC_TERM_QA_LIST lookup further support quality-assurance-driven validation during the closeout workflow.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions:

• CREATE_CONTRACT — Creates a new repository contract record.
• CREATE_NEW_CONTRACT_VERSION — Generates a new version of an existing contract, supporting version-controlled contract revisions.
• DELETE_CONTRACT — Removes a contract record.
• CHECK_CONTRACT_EXISTS — Validates whether a specified contract exists.
• COPY_DELIVERABLES — Copies deliverable definitions, typically from a source contract or template to a target contract.
• REVISE_CHECKLIST — Modifies the contract's checklist to reflect revised terms or conditions.
• FREEZE_CHECKLIST — Locks the checklist, preventing further modification once closeout criteria are met.
• VALIDATE_CLOSEOUT_TASKS — Verifies that all required closeout tasks are complete and valid before final closeout.
• ACTIVATE_TASKS_CLOSEOUT — Activates the closeout task set for the contract.
• DELIVERABLE_COMPLETED_EVENT — Raises or handles the workflow event signalling deliverable completion.
• COPY_SET_TASKS_TO_EACH_PO — Copies task sets to each associated purchase order line or order.
• CHECK_TASKS_EXISTS — Determines whether tasks already exist for the given contract context.

Tables Accessed

The package reads and writes several core OKC tables through APPS synonyms:

• OKC_REP_CONTRACTS_ALL — The primary contract master table; the source of contract header and status data (including the SIGNED status).
• OKC_DELIVERABLES — Stores deliverable records copied or revised during closeout.
• OKC_REP_CONTRACT_PARTIES — Holds party role information associated with the contract.
• OKC_REP_CONTRACT_USAGES — Records usage or reference relationships for the contract.
• OKC_REP_IMPORT_RUN_ID_S — A sequence used to generate import run identifiers.
• WF_EVENT_T — The Oracle Workflow event table, used when raising the deliverable-completed event.
• DUAL and PLITBLM — Utility objects used for single-row queries and PL/SQL associative array handling.

Usage Notes

As a PVT-class package, OKC_REP_CLOSEOUT_PVT is invoked internally rather than directly by end users or external integrations. It is typically called by public OKC APIs and by Oracle Forms or OAF pages handling repository contract maintenance and closeout. The metadata indicates the package is referenced by one other package, reinforcing its role as a supporting module within the OKC closeout framework. Closeout actions such as validating tasks, activating closeout workflows, and freezing checklists are commonly triggered through the contract closeout user interface or through concurrent programs that process contract lifecycle events. Customizations that touch closeout should call the public OKC APIs rather than this private package, since its signature and internals may change between patch levels such as 12.1.1 and 12.2.2.