Search Results xnp_wf_timers




Overview
Explore in AI Chat

Overview

XNP_WF_TIMERS is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM taxonomy as OTHER. It belongs to the XNP product family, which supports Oracle's Supply Chain and order-management workflow infrastructure. The package serves as the interface layer between Oracle Workflow and the underlying timer engine that schedules, monitors, and recalculates deadline-based activities associated with workflow items. In practice, XNP_WF_TIMERS exposes public APIs that Workflow activity functions, order-processing flows, and functional administrators call to fire timers, examine their status, restart or recalculate them, and remove them when they are no longer required. The package is compiled with AUTHID CURRENT_USER, meaning that execution privileges are resolved against the calling schema rather than the defining schema, an important consideration when granting EXECUTE to custom or non-APPS users.

Key Procedures and Functions

The documented API surface consists of eight public procedures. FIRE invokes the Fire procedure within the timer package, effectively triggering a specific timer so that its associated deadline logic executes. START_RELATED_TIMERS begins the set of timers related to a given message or workflow item, allowing multiple dependent deadlines to be scheduled together. GET_TIMER_STATUS retrieves the current status of a timer, giving callers visibility into whether a timer is active, expired, or complete. RESTART_ALL restarts all timers associated with the context passed in, while RECALCULATE_ALL recomputes all timer deadlines. REMOVE deletes an individual timer, and DEREGISTER removes all timers related to an order. GET_JEOPARDY_FLAG, the procedure matching the user's search term, returns a flag indicating whether a workflow item has entered jeopardy — that is, whether a deadline is at risk of being missed or has already been exceeded. The metadata does not expose the full parameter lists beyond the common signature pattern of ITEMTYPE, ITEMKEY, ACTID, FUNCMODE, and a RESULTOUT output parameter; these are standard Oracle Workflow activity-callback arguments and should not be altered or assumed beyond what the ETRM documents.

Tables Accessed

The ETRM metadata lists no explicit table references for XNP_WF_TIMERS via APPS synonyms. Oracle Workflow timer functionality is normally persisted in tables such as WF_TIMERS, WF_ITEM_ACTIVITY_STATUSES, and related Workflow runtime tables, accessed through APPS synonyms. Because the documentation does not document direct table access, administrators should treat the package as operating indirectly through the Workflow timer engine rather than performing direct DML on base tables. The referenced-by count of zero other packages confirms that XNP_WF_TIMERS is a leaf-level utility invoked by external callers rather than a shared dependency within the APPS code base.

Usage Notes

XNP_WF_TIMERS is typically invoked from Oracle Workflow activity functions, from order and shipping forms that need to manage deadline-driven workflow steps, or from custom PL/SQL that integrates with Workflow timers. The GET_JEOPARDY_FLAG procedure in particular is useful in custom alerts, OAF pages, or concurrent programs that must report whether an order or workflow item is in jeopardy. Because all procedures share the standard activity callback signature, they can be wired directly into Workflow process definitions as function activities. Callers should supply valid ITEMTYPE and ITEMKEY values for an existing workflow item, ensure ACTID corresponds to the correct activity, and pass FUNCMODE consistent with Workflow's RUN, CANCEL, or timeout modes. The RESULTOUT parameter receives the procedure's outcome and should be checked by the caller. The $Header line indicating version 120.1 dated 2005/06/24 shows the package has remained stable across the 12.1.1 and 12.2.2 releases covered here.