Search Results xnp_timer_publishers




Overview
Explore in AI Chat

Overview

The XNP_TIMER_PUBLISHERS table is a core data object within the Oracle E-Business Suite (EBS) Number Portability (XNP) module, present in both the 12.1.1 and 12.2.2 releases. Its primary function is to manage and store timer configurations associated with specific message types. In the context of number portability workflows, which are often governed by strict regulatory timeframes, this table enables the system to define and trigger time-based events or actions. It acts as a configuration repository that links a source message event to a subsequent timer message that should be published after a defined interval, ensuring automated process adherence and escalation.

Key Information Stored

The table's structure is designed to establish relationships between message types for timer management. While the full column list is not detailed in the provided metadata, the documented foreign key relationships reveal its most critical columns. The TIMER_PUBLISHER_ID serves as the unique primary key for each timer configuration record. The TIMER_MESSAGE_CODE column holds the code for the message type that will be generated and published when the timer expires. Conversely, the SOURCE_MESSAGE_CODE column stores the code for the originating message type that initiates the timer. These codes are foreign keys referencing the XNP_MSG_TYPES_B table, which defines all valid message types within the system.

Common Use Cases and Queries

The primary use case is the automated scheduling and triggering of follow-up actions within a porting transaction. For example, when a service order activation request (a source message) is received, a timer can be configured to automatically publish a reminder or escalation message if a confirmation response is not received within a service-level agreement window. Administrators may query this table to audit or maintain timer rules. A common SQL pattern involves joining to the message types table for descriptive information:

  • SELECT tp.*, src.MEANING AS SOURCE_MSG, timer.MEANING AS TIMER_MSG FROM XNP_TIMER_PUBLISHERS tp, XNP_MSG_TYPES_B src, XNP_MSG_TYPES_B timer WHERE tp.SOURCE_MESSAGE_CODE = src.MESSAGE_CODE(+) AND tp.TIMER_MESSAGE_CODE = timer.MESSAGE_CODE(+);

This query helps map the technical message codes to their business meanings for reporting and support.

Related Objects

The XNP_TIMER_PUBLISHERS table has defined dependencies on other key XNP tables, as per the provided relationship data. Its two critical foreign key relationships are both with the XNP_MSG_TYPES_B table, which serves as the master list for all message definitions in the Number Portability module.

  • Foreign Key 1: XNP_TIMER_PUBLISHERS.TIMER_MESSAGE_CODE references XNP_MSG_TYPES_B. This links to the message type that the timer will generate.
  • Foreign Key 2: XNP_TIMER_PUBLISHERS.SOURCE_MESSAGE_CODE references XNP_MSG_TYPES_B. This links to the message type that initiates the timer.

These relationships ensure data integrity, guaranteeing that timer configurations are only defined for valid, existing message types. The table is central to the timer engine within XNP and is likely referenced by internal concurrent programs and PL/SQL APIs that manage the publication and consumption of timer-based messages.