Search Results note_filled

Overview

OKC_WF_CHK_APPROVE is a PL/SQL package in the APPS schema that implements the Oracle Workflow business logic for the Oracle Contracts (OKC) approval and acknowledgement process in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the engine behind the Contract Approval workflow, driving the standard contract approval routing where a contract is submitted, approvers are resolved and notified, approval or rejection responses are recorded, and additional parties are informed of the outcome. The package exposes procedures that map directly to Workflow activity function calls in the approval process definition, meaning each procedure is invoked by the Workflow Engine as an activity is entered or as a response is processed. The header identifies the source as OKCWCHKS.pls, an older file revision (120.1, dated 2005), indicating the package has been stable and largely unchanged across releases. The package is classified as OTHER in the ETRM repository and is not referenced by any other package, so it functions as a top-level workflow support unit rather than a shared library.

Key Procedures and Functions

• Selector — The entry point that determines which subsequent approval process branch to follow based on the contract and the workflow command supplied. It evaluates the necessary conditions and returns the result that directs the workflow to the appropriate activity.
• Initialize — Sets up the contract approval workflow state when the process begins. It establishes the context required by later activities, including reading contract header and approval information needed throughout the process.
• Select_Approver — Resolves the list of approvers for the contract, typically by walking the approval hierarchy or approval rules defined for the contract, and passes those approvers to the notification activity that requests approval.
• Select_Informed — Resolves the list of recipients who should be informed (notified for information) of the contract's approval outcome, rather than being asked to approve. This procedure supports the "informed" routing in the workflow.
• Record_Approved — Handles the workflow callback when an approver responds with an approval, recording the approval against the contract and advancing the workflow.
• Record_Rejected — Handles the callback when an approver rejects the contract, recording the rejection and routing the process to the rejection path.
• Note_Filled — Processes the approver's note or comment captured on the notification response, storing it with the approval record for audit and review purposes.

Tables Accessed

The documented table reference for this package is FND_USER, accessed through an APPS synonym. This is consistent with the notification and approver-resolution logic: the package must resolve workflow user identities, verify active users, and map approver and informed-party notifications to valid EBS users. Contract-specific approval data is stored in the contracts approval tables, and the workflow runtime stores item attributes and activity results in the Workflow schema; validation against FND_USER ensures that approvers and informed parties selected by the routing logic correspond to valid application users.

Usage Notes

OKC_WF_CHK_APPROVE is not intended for direct invocation from forms, concurrent programs, or custom code. It is called by the Oracle Workflow Engine as the implementation of function activities within the Contract Approval workflow process definition. Each procedure signature follows the standard Workflow function-activity convention, receiving the item type, item key, activity ID, and function mode, and returning a result value that the workflow uses to determine the next transition. The most frequently executed procedures are Selector, Initialize, Select_Approver, and Select_Informed, which run as the process resolves routing and recipients, while Record_Approved, Record_Rejected, and Note_Filled execute when approver responses are consumed. Because the package is called only through workflow activity definitions, any customization of approval routing is normally performed by configuring the approval rules and hierarchy rather than by modifying this package. Developers should treat it as a stable, workflow-bound component and avoid changing its behavior, since doing so can break the standard contract approval flow. The "select_informed" search term corresponds directly to the Select_Informed procedure and reflects interest in how informed-party recipients are determined during contract approval.