Search Results get_approver

Overview

OKL_RBK_APPROVALS_WF is a workflow-enabled PL/SQL package in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 application schema (APPS). It belongs to the Oracle Lease and Finance Management (OKL) product family — the "RBK" token reflecting the lease rebate/approval sub-area — and is designated under the ETRM functional classification of "OTHER". The package exists to integrate OKL approval processing with the Oracle Workflow engine: it supplies the named workflow activity callbacks that the Workflow engine invokes when an approval process reaches checkpoints such as validating an approval request or determining the next approver. The header revision ($Header: OKLREWFB.pls 115.1 2002/11/30) indicates the package was created in late 2002 and has remained at version 115.1, which is typical of stub or placeholder packages retained for workflow definition backward compatibility.

Key Procedures and Functions

The package body exposes two documented procedures, both following the standard Oracle Workflow function-activity signature (itemtype, itemkey, actid, funcmode, resultout):

• VALIDATE_APPROVAL_REQUEST — Invoked by the Workflow engine (typically in RUN or CHECK mode) to determine whether a submitted approval request is eligible to proceed through the approval workflow. It returns a workflow result value via resultout so the process can branch to approval, rejection, or an error path. In the shipped source, the body contains a NULL placeholder, meaning no validation logic executes and the activity effectively always passes.
• GET_APPROVER — Invoked by the Workflow engine to resolve the approver (or approver list) for the current approval activity and return the result through resultout. This is the procedure matched by the user's search term "get_approver". As shipped, its body is also a NULL stub with no selection or assignment logic.

Both procedures are declared with NOCOPY OUT parameters, which is significant because Oracle Workflow calls these activities repeatedly (once per funcmode: RUN, CHECK, CANCEL, TIMEOUT), and NOCOPY avoids unnecessary copying of the result string. Because the bodies are NULL, neither procedure raises exceptions nor performs database work; any real approver determination must be implemented through customization or by wiring the workflow to alternate PL/SQL activities.

Tables Accessed

The ETRM metadata documents no tables referenced via APPS synonyms for this package. This is consistent with the NULL procedure bodies shown in the source: OKL_RBK_APPROVALS_WF performs no direct SELECT, INSERT, UPDATE, or DELETE against any base table. When the procedures are extended in a customization, approver resolution would ordinarily query OKL approval and workflow tables (for example, approval-group, employee/HR, or workflow role definitions) and the validation procedure would inspect lease or approval-transaction state; however, no such access is present in the delivered object.

Usage Notes

The package is not called by other PL/SQL packages — ETRM records zero referencing packages — and has no concurrent program or form entry point of its own. Its consumers are Oracle Workflow process definitions in the OKL item type, which reference the two procedures as function activities and call them at runtime when an approval process executes. The standard invocation context is therefore: a business event or user action launches the OKL approval workflow, and the Workflow engine calls VALIDATE_APPROVAL_REQUEST and GET_APPROVER with the appropriate funcmode. Custom implementations that require genuine approver derivation or request validation typically copy this stub and register the custom package/version in the Workflow Builder activity definition, leaving OKL_RBK_APPROVALS_WF intact for upgrade safety. Given that all bodies are NULL, administrators should not expect the delivered package to influence approval routing without such customization.