Search Results xnp_event_subscribers




Overview
Explore in AI Chat

Overview

The XNP_EVENT_SUBSCRIBERS table is a core data object within the Oracle E-Business Suite (EBS) Number Portability (XNP) module. It functions as a registry, defining the routing logic for business events or messages within the complex number portability workflow. Its primary role is to store and manage the list of system components, specifically Front-End (FE) agents, that are configured to receive and process specific types of messages. This subscription mechanism is essential for orchestrating the automated flow of portability requests, acknowledgments, and other critical notifications between different processing entities in the EBS system, ensuring that messages are delivered to the correct handlers as defined by the business configuration.

Key Information Stored

The table's structure is designed to map message types to their intended processing agents. The key columns, as indicated by the primary and unique keys, are the primary data points. The EVENT_SUBSCRIBER_ID serves as the unique system identifier for each subscription record. The MSG_CODE column holds the code identifying a specific message type, such as a port-in request or a cancellation notification. The FE_ID column stores the identifier for the Front-End agent (a processing engine or service) that is subscribed to receive messages of the specified MSG_CODE. Together, the MSG_CODE and FE_ID form a unique combination (enforced by the XNP_EVENT_SUBSCRIBERS_UK1 constraint), preventing duplicate subscriptions for the same agent and message type.

Common Use Cases and Queries

This table is central to the configuration and troubleshooting of the XNP message bus. Common operational scenarios include validating the setup of new message handlers, auditing message routing paths, and diagnosing why a particular agent is not receiving expected notifications. A typical administrative query would list all subscribers for a given message type to verify routing:

  • SELECT fe_id FROM xnp_event_subscribers WHERE msg_code = 'PORT_IN_REQ';

Conversely, to see all message types a specific Front-End agent is configured to process:

  • SELECT msg_code FROM xnp_event_subscribers WHERE fe_id = 100;

Reporting often involves joining to related tables to get descriptive names for the codes, providing a clear view of the entire subscription landscape for support or audit purposes.

Related Objects

The XNP_EVENT_SUBSCRIBERS table maintains defined foreign key relationships with other critical tables in the XNP and XDP modules, ensuring referential integrity for its key data. As per the provided metadata:

  • XNP_MSG_TYPES_B: The MSG_CODE column in XNP_EVENT_SUBSCRIBERS references this table, which contains the master definition and description of all available message types within the Number Portability module.
  • XDP_FES: The FE_ID column in XNP_EVENT_SUBSCRIBERS references this table from the TeleService (XDP) module. XDP_FES stores the master list of configured Front-End agents or service components, defining the executable entities that can act as subscribers.

These relationships mean that a valid record in XNP_EVENT_SUBSCRIBERS must correspond to a pre-defined message type and an existing, active Front-End agent, maintaining a consistent and valid configuration.