Search Results ok_to_implement




Overview
Explore in AI Chat

Overview

OKE_CHG_REQ_UTILS is a utility package in the Oracle E-Business Suite Oracle Contracts (OKE) module, classified as an OTHER API under the APPS schema with AUTHID CURRENT_USER privileges. Its business purpose is to support the lifecycle management of change requests associated with contract and project funding arrangements. Change requests in OKE represent modifications to contract terms, funding impacts, or versioned key member assignments that must pass through an approval workflow before taking effect. This package provides the backend plumbing that drives status transitions, interrogates workflow state, and controls the running workflow process instance attached to each change log entry. It is invoked primarily by the change request workflow and by the forms that manage change requests, rather than being an end-user-facing API. Because it manipulates workflow process state directly, it is tightly coupled with Oracle Workflow and the OKE change logging schema.

Key Procedures and Functions

  • Status_Change — Performs the utility work required when a change request moves from one status code to another. It accepts the change request identity, requester, effective date, old and new status codes, change type and reason, funding impact flag, and descriptive text, and returns the change log identifier along with approval and implementation dates.
  • Get_Process_Status — Returns the Workflow status and result of a status change as recorded in the change log history, keyed by change log identifier. Used to determine whether an approval or implementation activity has completed or errored.
  • Update_Process — Suspends, resumes, or aborts an existing workflow process associated with a change log. This is the procedure most commonly referenced in searches, as it is the standard mechanism for intervening in a running change request workflow.
  • OK_To_Implement — Validates whether a change request is eligible to be implemented, typically checking preconditions such as approval completion and version consistency.
  • OK_To_Undo — Validates whether a previously applied change can be reversed, used before initiating an undo operation.
  • Get_Chg_Request — Retrieves change request information for a given identifier, supporting downstream processing and display logic.

Tables Accessed

The package reads and writes OKE_CHG_LOGS and OKE_CHG_LOGS_S, which store change log headers and their history rows, and OKE_CHG_REQUESTS, the master change request records. It references OKE_CHG_STATUSES_B and OKE_CHG_STATUSES_TL for status code validation and translated status descriptions. OKE_K_VERS_NUMBERS_H provides contract version numbering needed to determine whether a change applies to the current version. PER_ALL_PEOPLE_F and FND_USER resolve requester and updater identities, while DUAL is used for simple scalar evaluations.

Usage Notes

OKE_CHG_REQ_UTILS is not intended as a standalone public API for external integrations. It is called by the OKE change request forms and by Oracle Workflow function activities during approval and implementation processing. Custom code should generally not call Status_Change directly, since doing so bypasses workflow orchestration. Update_Process is the exception most commonly used in extensions, allowing administrators or corrective scripts to suspend, resume, or abort a stalled change request workflow by supplying the change log identifier and a mode value of SUSPEND, RESUME, or ABORT. Because the package runs AUTHID CURRENT_USER, callers require direct privileges on the referenced OKE and HR tables. In EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is referenced by two other packages; any changes to its behavior should account for those dependents.