Search Results remindar_check

Overview

APPS.GMDOPGAP_WF_PKG is the Workflow integration package for the Oracle Process Manufacturing (OPM) Operations Approval workflow. It belongs to the Process Execution family of modules and provides the server-side PL/SQL logic that the Oracle Workflow engine invokes when an operation (routing/process step) requires approval before proceeding to its next activity or status. The package is declared with AUTHID CURRENT_USER and carries a header signature consistent with a 2002-era OPM release, indicating it has been carried forward into EBS 12.1.1 and 12.2.2 largely unchanged.

The core business purpose is to manage the approval lifecycle of operations: initializing the workflow for a given operation, evaluating whether approval is required for the next activity, capturing approver responses (approval, rejection, no response, request for more information), issuing reminder checks, and appending comments. In Oracle EBS terms, this package implements the standard "PL/SQL callback function" pattern used by Workflow activities, where each callback returns a result value to drive the workflow branch.

Key Procedures and Functions

The package exposes eight documented procedures. Names and roles are as follows:

• WF_INIT — Initializes and runs the Workflow for an operation, taking the operation identifier, number, version, start status, target status, requester, and last update date as inputs. This is the entry point that launches the approval workflow item.
• IS_APPROVAL_REQ — Determines whether approval is required for the next activity, returning a result that the workflow uses to branch between an approval path and a straight-through path.
• REMINDAR_CHECK — The reminder-check callback. When the user search term "remindar_check" retrieves this package, this procedure is the primary match. It evaluates whether a reminder notification must be sent for a pending approval (e.g., when the approver has not responded within the configured time window) and returns the result to the workflow engine.
• REQ_APPROVED — Handles the event where the request or operation is approved by the approver, updating the item and returning the approval result.
• REQ_REJECTED — Handles rejection of the approval request, routing the workflow down the rejection path.
• NO_RESPONSE — Processes the timeout/no-response condition when an approver fails to act, driving escalation or termination logic.
• MOREINFO_RESPONSE — Processes a request for additional information, keeping the item open while further data is gathered.
• APPEND_COMMENTS — Adds comments to the workflow item or operation record as part of the approval interaction.

All response procedures share a consistent callback signature: item type, item key, activity ID, function mode, and an output result parameter using NOCOPY. No additional parameters should be assumed beyond those documented.

Tables Accessed

The package references the following objects through APPS synonyms:

• GMD_OPERATIONS_B — Base table holding operation definitions; supplies the operation ID, number, version, status, requester, and last update date used by WF_INIT.
• GMD_OPERATIONS — Operation detail records consulted during approval evaluation.
• GMD_STATUS_NEXT — Defines the valid next statuses/activities, used by IS_APPROVAL_REQ to determine routing.
• GMA_ACTDATA_WF — Workflow activity data, storing per-item workflow state and responses.
• FND_USER — Resolves requester/approver identity.
• WF_ITEMS — The Workflow runtime item table, read/written to track the approval item lifecycle.

Usage Notes

GMDOPGAP_WF_PKG is not called directly by end users or by typical custom code. It is configured in Oracle Workflow Builder as the callback package for the OPM Operations Approval item type, and the Workflow engine invokes each procedure according to the activity's function definition. WF_INIT is typically launched from the OPM Operations form or from a concurrent process when an operation is submitted for approval, while IS_APPROVAL_REQ, REMINDAR_CHECK, and the response procedures are triggered by workflow notifications and timeouts.

Because the package is documented as referenced by one other package, extensions and customizations should treat it as a dependency of the OPM approval flow rather than as a general-purpose API. Upgrade testing between 12.1.1 and 12.2.2 should verify the callback signatures remain compatible, since the AUTHID CURRENT_USER declaration requires that the invoking schema hold appropriate privileges on the GMD and Workflow tables.