Search Results update_timer_status

Overview

XNP_TIMER_CORE is the central PL/SQL package within the Oracle E-Business Suite Advanced Supply Chain Planning and Order Management timer infrastructure. It belongs to the XNP (timer/notification processor) family of packages and serves as the foundational engine that manages timer registration, scheduling, status tracking, and firing for business events that require time-delayed or time-triggered processing. In Oracle EBS 12.1.1 and 12.2.2, the timer framework supports scenarios such as jeopardy monitoring, workflow synchronization, order header processing, and event publishing, where business logic must execute at a future point in time rather than immediately.

The package is owned by the APPS schema and is classified with an API status of OTHER, indicating it is primarily an internal engine package rather than a public, externally supported API. Its dependents (XDP_ENGINE, XDP_INTERFACES, XNP_TIMER, XNP_TIMER_MGR, XNP_TIMER_STANDARD, and XNP_WF_SYNC) confirm its role as a lower-level service consumed by higher-level timer management and planning packages.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions that collectively govern the timer lifecycle:

• RECALCULATE / RECALCULATE_ALL — Recompute the scheduled fire time for a single timer or for all registered timers, typically after a change in business dates or planning parameters.
• GET_TIMER_STATUS / UPDATE_TIMER_STATUS — Retrieve and modify the current state of a timer (for example, active, fired, or cancelled).
• REMOVE_TIMER / DEREGISTER / DEREGISTER_FOR_WORKITEM — Delete or deactivate a timer, either individually or in the context of a specific work item, cleaning up the registry entries.
• GET_NEXT_TIMER — Identify the next timer due to fire, supporting the polling/processing loop of the timer manager.
• RESTART / RESTART_ALL — Reinitialize a timer or the entire timer set, used for recovery or after maintenance windows.
• START_RELATED_TIMERS — Launch timers associated with a related business entity or event.
• GET_JEOPARDY_FLAG — Return the jeopardy indicator that signals whether a business commitment is at risk, a key output for order and planning exception handling.
• FIRE — Execute the action associated with a due timer, invoking the appropriate handler and updating status.

Tables Accessed

XNP_TIMER_CORE reads and writes several core tables through APPS synonyms:

• XNP_TIMER_REGISTRY — The master registry of registered timers, storing definitions, scheduled fire times, and status.
• XNP_TIMER_PUBLISHERS — Defines publishers responsible for dispatching timer events to downstream consumers.
• XDP_ORDER_HEADERS — Provides order header context used to evaluate jeopardy and scheduling for order-related timers.
• AQ$XNP_IN_TMR_QTAB — The Advanced Queuing queue table that carries inbound timer messages, consumed during timer firing and processing.

Usage Notes

XNP_TIMER_CORE is not intended for direct invocation by end users. It is called programmatically by the timer manager (XNP_TIMER_MGR), timer services (XNP_TIMER, XNP_TIMER_STANDARD), workflow synchronization (XNP_WF_SYNC), and planning engine packages (XDP_ENGINE, XDP_INTERFACES). Typical invocation occurs from concurrent programs that poll the timer queue, from workflow background processes, and from custom extensions that register or restart timers through the higher-level XNP_TIMER APIs. Because the package is documented as OTHER rather than a published API, customizations should preferentially call the supported XNP_TIMER layer, treating XNP_TIMER_CORE as an internal dependency subject to change between releases.