Search Results oks_wf_k_approve




Overview
Explore in AI Chat

Overview

OKS_WF_K_APPROVE is a PL/SQL package owned by the APPS schema that supports the Oracle Workflow-driven approval and signature process for service contracts and related contract documents managed by Oracle Service Contracts (OKS) and Oracle Contracts Core (OKC). It exposes a set of selector and callback routines that the seeded contract approval workflow invokes to determine who must approve a contract, to determine which contracts are subject to approval, and to record the outcome of approval or signature actions against the contract header. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as VALID and as an OTHER API, meaning it is a supporting internal package rather than a public, committed business API. It bridges the Workflow engine, the Approvals Management (AME) framework and the contract data model in OKC, and it is a dependency of the workflow definition logic that governs contract approval routing.

Key Procedures and Functions

  • SELECTOR — Entry point used by the workflow to evaluate routing or selection logic for the contract approval process.
  • SELECT_APPROVER / SELECT_INFORMED, SELECT_INFORMED_A, SELECT_INFORMED_AR, SELECT_INFORMED_S, SELECT_INFORMED_SR — Populate the lists of approvers and of informed (notification-only) recipients. The suffixed variants address distinct recipient categories or contract roles so that the correct parties receive approval requests or informational notifications.
  • INITIALIZE — Sets up the package and workflow context at the start of an approval cycle.
  • IS_RELATED / IS_K_TEMPLATE / MAKE_ACTIVE — Predicate and state functions used to qualify the contract, for example to test whether a contract participates in the approval relationship, whether it is a template, or to transition an approved contract to active status.
  • UPDATE_AME — Synchronizes approval data with the Approvals Management Engine.
  • POST_APPROVAL / POST_SIGN / NOTE_FILLED — Post-action callbacks executed after approval, after signature, and when a required note has been supplied.
  • RECORD_APPROVED / ERASE_APPROVED / RECORD_SIGNED / RECORD_REJECTED — Persist or clear the recorded approval/signature outcome for the contract, including rejection handling.
  • WAS_APPROVER — Determines whether a given user acted as an approver during the workflow.

Tables Accessed

The package reads and writes the contract data model through APPS synonyms. OKC_K_HEADERS_ALL_B and OKC_K_HEADERS_TL supply the contract header identifiers and descriptive attributes. OKC_K_REL_OBJS holds related-object relationships used for relationship and template qualification. OKC_K_PROCESSES stores contract process/status rows advanced by make-active and post-approval actions. FND_USER resolves approver and informed-party identities. WF_ROUTING_RULES supports workflow routing evaluation, while DUAL and PLITBLM are used for trivial selects and PL/SQL table manipulation.

Usage Notes

OKS_WF_K_APPROVE is invoked indirectly by the Oracle Service Contracts approval workflow rather than by end users. It is triggered when a contract is submitted for approval, when approver and informed-party lists must be built, when AME data requires refresh, and when approval, signature or rejection results must be recorded against the contract header. The package is referenced by no other packages and references OKC_K_REL_OBJS, indicating it sits near the top of the contract approval call stack. Customizations that extend approval routing or notification recipients should use the supported contract and AME APIs rather than modifying this package, since the workflow configuration and AME rules are the intended extension points. Direct invocation is not recommended and may conflict with workflow state management.