Search Results oke_chg_requests_wf




Overview
Explore in AI Chat

Overview

OKE_CHG_REQUESTS_WF is a PL/SQL package owned by the APPS schema that implements the workflow callback layer for Oracle Change Management (OKE) change request approvals in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is declared with AUTHID CURRENT_USER and is designed to be invoked exclusively from Oracle Workflow activities rather than from forms or concurrent programs directly. Its purpose is to supply the procedural logic that drives the change request approval workflow item type: it initializes workflow item attributes that were not populated during the workflow launch, resolves the next approver and the next informed recipient, enforces rejection note validation, and applies funding and status transitions as the approval process advances through its activities. The package name and header comment ($Header: OKEWCRQS.pls 115.4 2002/11/21) trace the object to the earlier Oracle Quality/Change Management code line, and the package remains part of the standard APPS code set in both release families.

Key Procedures and Functions

The ETRM metadata documents seven callable units, each intended to be wired to a workflow activity node:

  • Initialize — Initializes the remaining workflow item attributes that were not set at launch time, ensuring the item carries complete context before subsequent activities execute.
  • Select_Next_Approver — Determines the next approver for the change request. This is the procedure most commonly targeted by administrators searching for approval-routing logic, since it resolves the approver identity that drives the approval notification.
  • Select_Next_Informed — Determines the next recipient of workflow notifications, supporting the informational (carbon-copy) distribution path of the change request.
  • Rej_Note_Filled — Verifies that a rejection note has been entered when the change request was rejected, enforcing mandatory justification before the workflow continues.
  • Impact_Funding — Handles the funding impact associated with the change request as part of the approval process.
  • Set_Approved_Status — Sets the change request status to approved upon successful completion of approval.
  • Set_Rejected_Status — Sets the change request status to rejected when the rejection path is taken.

All documented procedures follow the standard Oracle Workflow callback signature convention, receiving item type, item key, activity ID, and function mode as input, and returning a result out parameter.

Tables Accessed

The package operates against three documented objects through APPS synonyms:

  • OKE_CHG_REQUESTS — The primary change request entity; read for approval routing context and updated as the workflow progresses.
  • OKE_CHG_STATUSES_B — The change request statuses base table; used when applying approved and rejected status values.
  • FND_USER — The Oracle Applications user repository; consulted when resolving approver and informed-recipient identities.

Usage Notes

Because the header states that each procedure must be called from a WF activity, OKE_CHG_REQUESTS_WF is not exposed as a form-level API or a concurrent program in its own right. It is invoked by the Oracle Workflow engine when the change request approval item type reaches the corresponding function activity — for example, the approver-selection node invokes Select_Next_Approver, and the terminal approval or rejection nodes invoke Set_Approved_Status or Set_Rejected_Status. Customizations should therefore be implemented by modifying or wrapping the workflow process definition rather than by calling this package directly from custom code. In 12.1.1 and 12.2.2 the package is unchanged in classification (OTHER, no public API designation), and ETRM records zero packages referencing it, confirming it sits at the top of the dependency chain rather than being reused by other PL/SQL modules.