Search Results update_status_approved

Overview

APPS.EAM_WORKPERMIT_WORKFLOW_PVT is a private PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) module, responsible for orchestrating the Oracle Workflow approval lifecycle of Work Permit Release documents. Its header identifies it as an AUTHID CURRENT_USER package, indicating that it executes with the privileges of the invoking user rather than the definer. The package source file is EAMVWPWS.pls and it carries a $Header revision tag from March 2011 (120.1), with an initial creation date of 18-FEB-2010 attributed to Madhuri Shah. In ETRM 12.2.2 the package is classified as PVT (private), meaning it is not intended as a public integration API and should be treated as internal implementation logic supporting the Work Permit Release approval flow rather than a supported entry point for external customizations.

Key Procedures and Functions

The package exposes six documented procedures and functions. The two primary callback entry points are Update_Status_Approved and Update_Status_Rejected. Both are designed to be invoked by the Work Permit Release Approval workflow when the approval process reaches a terminal state — Update_Status_Approved fires upon approval and Update_Status_Rejected fires upon rejection — and each returns a result out parameter so the workflow engine can evaluate the outcome of the activity. These procedures use the standard Oracle Workflow function signature (itemtype, itemkey, actid, funcmode, resultout), making them directly callable from a workflow function activity.

Launch_Workflow is a function bound to an event subscription. When the subscribing business event is raised, it launches the appropriate workflow process instance, typically by calling the Workflow Engine with the event payload and returning a status string. Get_Next_Approver supports the routing logic of the approval chain, determining the next approver in the hierarchy. Update_AME_With_Response integrates with Oracle Approvals Management (AME) to record the approver response back into AME. Is_Approval_Required_Released evaluates whether approval is required for a Work Permit Release, effectively acting as the decision gate that determines whether the workflow should proceed down an approval path or be released directly.

Tables Accessed

The package references several Oracle Workflow tables via APPS synonyms. WF_EVENT_T is the business event payload structure used by Launch_Workflow to capture the subscription GUID and event data. WF_NOTIFICATIONS is accessed to create, query, and close the approval notifications sent to approvers. WF_PARAMETER_LIST_T and WF_PARAMETER_T are used to build and read the parameter lists that pass context between workflow activities, and PLITBLM is the PL/SQL table type used for indexed collections within those parameter structures. UTL_FILE is referenced for file-level operations, typically for diagnostic or logging output during workflow execution.

Usage Notes

This package is invoked indirectly rather than directly by end users. The typical invocation path begins when a Work Permit Release is submitted, raising a business event to which Launch_Workflow is subscribed. Oracle Workflow then drives the approval process, calling Is_Approval_Required_Released to determine routing, Get_Next_Approver to identify approvers, and Update_AME_With_Response to persist responses. On final disposition, the workflow calls Update_Status_Approved or Update_Status_Rejected to synchronize the Work Permit Release status. The ETRM metadata indicates the package is referenced by one other package, underscoring its role as a shared dependency within the EAM Work Permit workflow stack. Custom developers should avoid calling these procedures directly and instead interact with the supported Work Permit Release forms and workflow configuration. Because it is an AUTHID CURRENT_USER private package subject to change between releases, any custom dependency on its signatures carries upgrade risk.