Search Results is_doc_approved

Overview

OKE_K_APPROVAL_WF is the Oracle Workflow integration package for the Oracle Contracts (OKE/OKC) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by APPS and classified as OTHER in the ETRM repository. The package encapsulates the server-side logic that drives the contract approval workflow, exposing a set of PL/SQL procedures that are registered as workflow activity functions within the OKE approval item type. Each procedure is designed with the standard Oracle Workflow activity signature (ItemType, ItemKey, ActID, FuncMode, ResultOut), which confirms that the package is intended to be invoked directly by the Workflow Engine rather than by end-user forms or concurrent programs.

Its role is to evaluate approval-related conditions against a contract, a master agreement (BOA), or a delivery order, and to return a workflow result value—typically WFSTD_YES_NO—that directs the subsequent branching in the approval process. The package therefore acts as the decision layer between stored contract data and the workflow definition.

Key Procedures and Functions

The documented interface contains fourteen procedures and functions. The Is_Doc_Approved procedure, which is the object of the search term, determines whether a contract document has already been approved, returning a WFSTD_YES_NO result so that an approval path can be skipped or continued. Related procedures include: Initialize, which populates the workflow item attributes not set during launch; Is_BOA_Approved, which evaluates whether the master agreement itself is approved; Is_Doc_Delv_Order and Is_Doc_Inactive, which test the document type and status; Is_Final_Approver and Is_Requestor_Approver, which resolve the position of the current approver in the routing chain; Is_Signature_Required, which determines whether a signature step is needed; Rej_Note_Filled, which verifies that a rejection note has been supplied; Select_Next_Approver and Select_Signatory, which choose the next participant; Set_Approval_History, which records the approval action; Validate_Approval_Path, which confirms the routing is valid; and Erase_Approved, which clears approval results. Parameter lists are not reproduced here; each procedure follows the standard workflow activity signature described above.

Tables Accessed

The package reads and writes a defined set of contract and workflow tables through APPS synonyms. Contract header data is sourced from OKC_K_HEADERS_B, OKE_K_HEADERS, and OKE_K_TYPES_B, which supply document identity, type, and status. Status lookups use OKC_STATUSES_B. Approval audit and routing information is persisted in OKE_APPROVAL_HISTORY. Workflow runtime state is read from WF_ITEMS, and approver notifications are managed through WF_NOTIFICATIONS.

Usage Notes

OKE_K_APPROVAL_WF is not called directly from forms or concurrent programs; it is invoked by the Oracle Workflow Engine at the activity nodes of the OKE contract approval process, where each procedure executes and returns a result value that controls branching. Customizations that extend contract approval routing should call these procedures only within a workflow activity context, since they depend on ItemType, ItemKey, and ActID being supplied by the engine. ETRM records show the package is referenced by zero other packages, confirming it is a leaf-level integration point rather than a shared utility. When diagnosing approval behavior, Is_Doc_Approved and its sibling condition procedures should be inspected first, as they determine whether an approval step is bypassed.