Search Results okc_contract_approval_pub




Overview
Explore in AI Chat

Overview

The APPS.OKC_CONTRACT_APPROVAL_PUB package is the public application programming interface that governs the workflow-driven approval lifecycle for Oracle Contracts (OKC) documents in Oracle E-Business Suite. Its responsibilities include initiating and terminating approval processes, managing the interaction between the contract record and the Oracle Workflow engine, maintaining approval-related status flags, and handling approval template activation. Because it carries the PUB (public) classification, it is intended as a stable, supported entry point for approval operations rather than as an internal utility. The package is delivered with a status of VALID and is installed under the APPS schema, which is the standard location for shared, cross-module PL/SQL APIs in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. Their names indicate the functional grouping below; only purposes are asserted, as parameter signatures are not part of the supplied metadata:

  • K_APPROVAL_START — Initiates the approval workflow for a contract, launching the Workflow process and establishing the approval context.
  • K_APPROVAL_STOP — Terminates or cancels an in-progress approval for a contract.
  • WF_MONITOR_URL — Provides the Workflow monitor URL used to view the status of a running approval process.
  • WF_COPY_ENV — Copies the Workflow environment attributes required to correctly launch the process.
  • K_ACCESIBLE — Determines accessibility or eligibility of the contract/approver combination for the approval action.
  • K_APPROVED — Records the approved outcome of a contract workflow.
  • K_SIGNED — Records the signed outcome, typically following the approval or signature step.
  • K_ERASE_APPROVED — Clears the approved/signed markers so a contract can be re-approved or re-triggered.
  • ACTIVATE_TEMPLATE — Activates or instantiates an approval template for use in the contract approval flow.

Tables Accessed

The supplied metadata does not enumerate base tables; access is achieved through APPS synonyms. Functionally, the package operates against the OKC contracts header and approval-history structures that store approval status, signer information, and workflow identifiers. The approval lifecycle functions (K_APPROVED, K_SIGNED, K_ERASE_APPROVED) update contract approval-status columns, while the workflow entry points (K_APPROVAL_START, K_APPROVAL_STOP, WF_MONITOR_URL, WF_COPY_ENV) interact with Workflow runtime tables to launch and monitor processes. Because the table list is incomplete in the documentation, implementers should confirm physical table usage against the APPS synonym definitions when performing impact analysis or data audits.

Usage Notes

This package is invoked primarily by Workflow activity functions and by the contract business logic that surrounds them. The dependency metadata shows it is referenced by related packages including OKC_CHANGE_CONTRACT_PUB, OKC_CHANGE_CONTRACT_PVT, OKC_OC_INT_PUB, OKC_RENEW_PVT, OKC_WF_K_APPROVE, OKL_CONTRACT_APPROVAL_PVT, OKS_WF_K_APPROVE, and OKS_WF_K_PROCESS_PVT. This pattern confirms that renewal, change, integration, and leasing/service workflow calls reach approval functionality through this public interface. Customizations, form personalizations, and integrations that need to start or stop a contract approval should call the procedures here rather than the corresponding private (PVT) packages, respecting the API classification. Because eight packages depend on it, changes to behavior should be validated across those callers during upgrades between 12.1.1 and 12.2.2.