Search Results xnp_timer_mgr




Overview
Explore in AI Chat

Overview

XNP_TIMER_MGR is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Applications advanced queuing and event messaging infrastructure that underpins asynchronous processing across the EBS technology stack. The package is classified under the API classification OTHER and holds VALID status in the ETRM repository for releases 12.1.1 and 12.2.2.

The central business function of XNP_TIMER_MGR is the management of timer-based message processing. In EBS, timer messages allow delayed, scheduled, or deferred execution of business events rather than immediate processing. XNP_TIMER_MGR coordinates the construction and enqueueing of these dynamic timer messages, working closely with the underlying Oracle Streams Advanced Queuing (AQ) facilities. It bridges application-level messaging requirements and the database queue mechanics so that timer-driven notifications, workflow events, and deferred processing requests are reliably delivered.

The dependency metadata confirms this role: XNP_TIMER_MGR references APPS.XNP_MESSAGE and the SYS.STANDARD package, and it is itself referenced by XDP_AQ_UTILITIES, XNP_TIMER_CORE, and recursively by XNP_TIMER_MGR. The mutual reference between the package and XNP_TIMER_CORE indicates a layered design in which the timer manager handles message assembly while the timer core handles timer registration and scheduling semantics.

Key Procedures and Functions

Five documented procedures and functions are associated with the package. Their purposes are summarized below; parameter lists are not published in the ETRM metadata and are therefore not reproduced here.

  • PROCESS_IN_TMR — Processes inbound timer messages. This routine is the entry point through which timer-related payloads are received and handled within the manager's processing flow.
  • CONSTRUCT_DYNAMIC_MESSAGE — Builds a dynamic message structure at runtime. Rather than relying on a static message definition, this routine assembles message content programmatically so that timer notifications can carry context-sensitive payloads.
  • PROCESS — The general processing driver for the package, responsible for orchestrating the handling of timer messages and dispatching them to the appropriate internal logic.

The remaining documented procedures are internal helpers supporting these three primary entry points. The grouping reflects a construct-then-process pattern: messages are dynamically constructed and then consumed through the timer processing routines.

Tables Accessed

Two data sources are documented for this package. The first is XNP_MSGS, accessed through an APPS synonym. This table stores message content and metadata used by the XNP messaging layer. XNP_TIMER_MGR reads and writes this table to persist message definitions and payloads associated with timer-driven activity.

The second is DBMS_AQ, the Oracle-supplied Advanced Queuing package. Although it is a package rather than a table, it is listed among the accessed objects because XNP_TIMER_MGR invokes DBMS_AQ routines to enqueue and dequeue messages from the underlying queue tables. This reliance on DBMS_AQ is what enables the timer manager to participate in the EBS asynchronous messaging architecture, where queue tables physically hold messages and DBMS_AQ provides the programmatic interface to them.

Usage Notes

XNP_TIMER_MGR is not an end-user-facing API. It is an internal infrastructure package invoked by other application components rather than by forms or standard concurrent programs directly. The documented reference from XDP_AQ_UTILITIES and XNP_TIMER_CORE shows that the package is called by the AQ utility layer and by the timer core when timer messages need to be constructed or processed.

Custom code should generally avoid calling XNP_TIMER_MGR directly because its interface is not published as a supported public API; the parameter signatures are undocumented in the ETRM metadata, and the package is subject to change between releases. Instead, developers integrating with EBS timer messaging should use the higher-level, documented messaging APIs and allow XNP_TIMER_CORE and XDP_AQ_UTILITIES to invoke the timer manager on their behalf. When troubleshooting asynchronous or deferred message behavior, DBMS_AQ queue table contents and XNP_MSGS entries are the primary artifacts to inspect, since these reflect the results of XNP_TIMER_MGR activity. Because the package is marked VALID in both 12.1.1 and 12.2.2, its behavior is consistent across these releases.