Search Results post_sign

Overview

OKC_WF_K_APPROVE is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite. It belongs to the Contracts (OKC) module family and serves as the workflow integration layer that governs the approval and signature life cycle of contract documents. In Oracle EBS 12.1.1 and 12.2.2, contracts created through the Contracts Authoring and related modules move through configurable approval workflows before they become active. OKC_WF_K_APPROVE supplies the programmatic hooks that the Oracle Workflow engine and the Contracts forms call to determine which users should approve or be informed of a contract, to record the outcome of an approval or signature event, and to transition the contract header into its next state.

The package is classified as OTHER within the ETRM metadata, meaning it is an internal support package rather than a public, supported open interface. It is documented as VALID and is not referenced by any other package, indicating that it acts as a top-level workflow consumer rather than a shared library.

Key Procedures and Functions

The ETRM metadata documents twenty-three procedures and functions. The principal entry points include:

• INITIALIZE — establishes the package-level state and context used by subsequent calls during a workflow activity.
• SELECTOR — a generic dispatcher that routes a workflow call to the appropriate specialized selection routine.
• SELECT_APPROVER — determines the approver or set of approvers for a contract based on the approval configuration.
• SELECT_INFORMED, SELECT_INFORMED_A, SELECT_INFORMED_AR, SELECT_INFORMED_S, SELECT_INFORMED_SR — variants that resolve the distribution or "informed" list for the notification, with the suffixes denoting different recipient categories used by the contract workflow.
• POST_APPROVAL / RECORD_APPROVED — persist the outcome of an approved contract and advance its status.
• POST_SIGN / RECORD_SIGNED — record that a contract has been signed and move it forward accordingly.
• ERASE_APPROVED — reverses a previously recorded approval, supporting resubmission or rollback scenarios.
• MAKE_ACTIVE — transitions an approved contract into the active state.
• NOTE_FILLED, IS_RELATED, IS_K_TEMPLATE — supporting checks that evaluate contract attributes such as template status and related-object relationships.
• WAS_APPROVER, VALID_APPROVER — validate whether a given user is or was a legitimate approver for the contract.
• NOTIFY_SALES_REP_W — generates a notification directed to the associated sales representative.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• OKC_K_HEADERS_ALL_B and OKC_K_HEADERS_TL — the base and translated contract header tables, used to read contract status and update it during approval and signature processing.
• OKC_K_REL_OBJS — the relationship table linking contract objects and parties, used to determine who is related to the contract for approver and informed-list resolution.
• OKC_K_PROCESSES — the process definition table that governs approval workflow behavior.
• OKS_K_HEADERS_B — the service contract header table, accessed for service-related contract processing.
• FND_USER — the application user table, used to resolve and validate approver identities.
• DUAL — used for simple scalar evaluations.

Usage Notes

OKC_WF_K_APPROVE is invoked by the Oracle Workflow engine as the Contracts approval process progresses, and indirectly from the Contracts authoring forms when users submit contracts for approval or sign them. Because it directly mutates contract header status, it is not intended for ad hoc invocation. Customizations should extend the workflow through supported configuration and call the supported Contracts APIs in preference to invoking this package directly, since it is an internal component with no documented public interface and no downstream package dependents.