Search Results xnp_timer_registry

Overview

The XNP_TIMER_REGISTRY table is a core data object within the Oracle E-Business Suite Number Portability (XNP) module. Its primary function is to serve as a central registry for managing and tracking all active timers within the system. In the context of telecommunications and number portability processes, timers are critical for orchestrating workflow steps, enforcing service level agreements (SLAs), and triggering subsequent automated actions or notifications after a predefined interval. The table's existence is essential for ensuring the reliable, stateful execution of long-running portability transactions across both Oracle EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's structure is designed to capture the complete state of an active timer. While the full column list is not detailed in the provided metadata, the foreign key relationships and primary key indicate the critical data points stored. The TIMER_ID column serves as the unique primary identifier for each timer instance. The table links to message types via TIMER_MESSAGE_CODE and NEXT_TIMER, defining the timer's purpose and the subsequent action. Crucially, it stores references to the business objects the timer governs: ORDER_ID links to the fulfillment order in the XDP module, FA_INSTANCE_ID points to a specific fulfillment action, and WI_INSTANCE_ID associates the timer with a work item in the fulfillment worklist. Additional columns likely track creation time, scheduled expiration, status, and contextual parameters.

Common Use Cases and Queries

This table is primarily used for operational monitoring, troubleshooting, and system administration within the XNP module. Common scenarios include identifying hung or overdue timers that may be blocking order progression, auditing timer activity for a specific order, and cleaning up orphaned timer records. A typical diagnostic query would join to related fulfillment tables to assess timer impact.

• Identifying all active timers for a specific order: SELECT * FROM xnp.xnp_timer_registry WHERE order_id = <ORDER_ID>;
• Finding timers that have exceeded their expected duration (assuming a CREATION_DATE or EXPIRY_DATE column): SELECT timer_id, order_id FROM xnp.xnp_timer_registry WHERE expiry_date < SYSDATE AND status = 'ACTIVE';
• Joining to view the associated message type and order details: SELECT t.*, m.message_name, o.order_number FROM xnp.xnp_timer_registry t, xnp.xnp_msg_types_b m, xdp.xdp_order_headers o WHERE t.timer_message_code = m.message_code AND t.order_id = o.order_id;

Related Objects

The XNP_TIMER_REGISTRY table maintains integral relationships with several key tables in the XNP and XDP (Fulfillment) modules, as documented by its foreign keys.

• XNP_MSG_TYPES_B: Linked twice. TIMER_MESSAGE_CODE defines the message associated with the current timer event. NEXT_TIMER references the message code for the action to be triggered upon timer expiration.
• XDP_ORDER_HEADERS: Linked via ORDER_ID. This ties the timer to a specific service order being processed within the fulfillment system.
• XDP_FA_RUNTIME_LIST: Linked via FA_INSTANCE_ID. This associates the timer with a specific instance of a Fulfillment Action being executed.
• XDP_FULFILL_WORKLIST: Linked via WI_INSTANCE_ID. This connects the timer to a specific work item assigned to an agent or automated process.