Results for “xnp_event_subscribers_u2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XNP_EVENT_SUBSCRIBERS is a transaction and configuration table owned by the XNP schema in Oracle E-Business Suite, within the XNP – Number Portability product module. Its documented purpose is to store a list of subscribers for a given message type. In practical terms, the table functions as the routing or distribution map that determines which front-end systems (FEs) receive notifications when a specific message type is raised within the number portability message infrastructure.

The table is registered as VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema in 12.2.2 contains 10 columns. Based on the foreign key structure mined from the metadata, the heuristic Data Vault classification for this object is a link — that is, a modeling suggestion that the table resolves a many-to-many relationship between message types and front-end entities rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The table’s principal columns and their roles are as follows.

• EVENT_SUBSCRIBER_ID — the surrogate primary key, enforced by XNP_EVENT_SUBSCRIBERS_PK. It uniquely identifies each subscription row and is also the leading column of the unique key XNP_EVENT_SUBSCRIBERS_U1.
• MSG_CODE — the message type code that is being subscribed to. It is a foreign key to XNP_MSG_TYPES_B and forms part of the business-key candidate XNP_EVENT_SUBSCRIBERS_U2 in combination with FE_ID and ZD_EDITION_NAME.
• FE_ID — the identifier of the subscribing front-end entity. It is a foreign key to XDP_FES and constitutes the second component of the U2 business key.
• SECURITY_GROUP_ID — the multi-tenant / security group discriminator, with a documented foreign key to FND_SECURITY_GROUPS. This column enables data isolation when multiple operating units or security partitions coexist.
• ZD_EDITION_NAME — the editioning column that supports Oracle EBS 12.2 online patching and edition-based redefinition. It appears in both unique indexes, meaning uniqueness is scoped per edition rather than globally.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture the standard who/when audit trail maintained by EBS concurrent processing and the Forms layer.

Together, MSG_CODE and FE_ID express the actual business relationship: one message type may be delivered to many front-end systems, and one front-end system may subscribe to many message types. The unique indexes XNP_EVENT_SUBSCRIBERS_U1 and XNP_EVENT_SUBSCRIBERS_U2 enforce this intent, with U2 acting as the true business-key candidate.

Common Use Cases and Queries

Typical usage centers on administration and diagnostics of number portability message routing. Common scenarios include identifying all front-end systems subscribed to a specific message type, validating that no duplicate subscription exists, and auditing which message types have no active subscribers.

To resolve subscribers for a given message type, join to XDP_FES on FE_ID:

• SELECT s.MSG_CODE, s.FE_ID, f.FE_NAME
• FROM XNP.XNP_EVENT_SUBSCRIBERS s, XDP.XDP_FES f
• WHERE s.FE_ID = f.FE_ID
• AND s.MSG_CODE = :msg_code;

To list valid message types with their subscription counts, join to XNP_MSG_TYPES_B on MSG_CODE and aggregate. When configuring or troubleshooting order/porting messages that fail to reach a downstream system, the absence of a row in this table for the relevant MSG_CODE and FE_ID is a primary diagnostic indicator. Reporting use cases include subscription matrices for interface inventories and pre-patch validation of edition-scoped uniqueness, since ZD_EDITION_NAME partitions rows across editions in 12.2.2.

Related Objects

• XNP_MSG_TYPES_B — referenced via XNP_EVENT_SUBSCRIBERS.MSG_CODE; defines the message type catalog and is the parent of the subscription code.
• XDP_FES — referenced via XNP_EVENT_SUBSCRIBERS.FE_ID; defines the front-end systems that receive messages.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs visibility and tenancy of each subscription row.
• XNP_EVENT_SUBSCRIBERS_PK / _U1 / _U2 — the primary and unique indexes that enforce identity and business-key uniqueness, including the ZD_EDITION_NAME edition scope.
• The associated XNP message framework tables that drive event publication and consumption across the number portability stack, which depend on the subscription map to resolve delivery targets.