Search Results xnp_routing_numbers
Overview
The XNP_ROUTING_NUMBERS table is a core data object within the Oracle E-Business Suite (EBS) Number Portability (XNP) module, present in both releases 12.1.1 and 12.2.2. It serves a critical operational function in telecommunications management by storing the routing information necessary for the correct delivery of ported telephone numbers. When a telephone number is ported from one service provider to another, the network must be instructed to route calls for that number to the new provider's infrastructure. This table acts as the system of record for those routing instructions, ensuring that calls, messages, and other services for ported numbers are correctly directed to the appropriate service provider's network interconnection point.
Key Information Stored
The table's structure is designed to uniquely identify routing entries and associate them with specific providers and network contexts. The primary identifier is the system-generated ROUTING_NUMBER_ID. The table enforces two unique key constraints: one (XNP_ROUTING_NUMBERS_UK1) on the combination of SP_ID (Service Provider ID), ROUTING_NUMBER (the actual routing code or address), and INTERCONNECT_TYPE, ensuring a provider cannot have duplicate routing configurations for the same type. A second unique key (XNP_ROUTING_NUMBERS_UK2) on OBJECT_REFERENCE suggests this column may be used for integration or external system mapping. The SP_ID column is a foreign key linking directly to the XNP_SERVICE_PROVIDERS table, establishing the provider-owner of the routing number.
Common Use Cases and Queries
Primary use cases involve the administration of routing data and supporting transaction processing. System administrators use this table to create, update, or deactivate routing entries for service providers as their network configurations change. During the processing of a number portability order, the system queries this table to determine the correct destination routing for the ported number. Common reporting and validation queries include retrieving all routing numbers for a specific provider or finding the active routing configuration for a given interconnect type. A sample SQL pattern to list routing details for a provider would be:
SELECT sp.SP_NAME, rn.ROUTING_NUMBER, rn.INTERCONNECT_TYPE FROM XNP_ROUTING_NUMBERS rn, XNP_SERVICE_PROVIDERS sp WHERE rn.SP_ID = sp.SP_ID AND sp.SP_CODE = '&PROVIDER_CODE';
Related Objects
The XNP_ROUTING_NUMBERS table is centrally linked to several key objects in the XNP schema, primarily through foreign key relationships. The parent table is XNP_SERVICE_PROVIDERS, which defines the service provider entity. It is referenced as a parent by multiple child tables, indicating its data is used to qualify specific service attributes or journal entries. These referencing tables include XNP_INTERCONNECT_AREAS, XNP_SV_SMS (likely for SMS service routing), XNP_SV_SOA (likely for Service Order Activation), and its journal table XNP_SV_SOA_JN. This network of relationships underscores the table's role in propagating routing information across various service fulfillment and activation components within the Number Portability module.
-
Table: XNP_ROUTING_NUMBERS
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_ROUTING_NUMBERS, object_name:XNP_ROUTING_NUMBERS, status:VALID, product: XNP - Number Portability , description: Stores routing numbers which are used to deliver ported telephone numbers to the appropriate service provider , implementation_dba_data: XNP.XNP_ROUTING_NUMBERS ,
-
Table: XNP_ROUTING_NUMBERS
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_ROUTING_NUMBERS, object_name:XNP_ROUTING_NUMBERS, status:VALID, product: XNP - Number Portability , description: Stores routing numbers which are used to deliver ported telephone numbers to the appropriate service provider , implementation_dba_data: XNP.XNP_ROUTING_NUMBERS ,
-
Table: XNP_INTERCONNECT_AREAS
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_INTERCONNECT_AREAS, object_name:XNP_INTERCONNECT_AREAS, status:VALID, product: XNP - Number Portability , description: Stores geographic area covered by a routing number , implementation_dba_data: XNP.XNP_INTERCONNECT_AREAS ,
-
Table: XNP_SV_SMS
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SMS, object_name:XNP_SV_SMS, status:VALID, product: XNP - Number Portability , description: Container object for subscription versions downloaded to the network , implementation_dba_data: XNP.XNP_SV_SMS ,
-
Table: XNP_SV_SMS
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SMS, object_name:XNP_SV_SMS, status:VALID, product: XNP - Number Portability , description: Container object for subscription versions downloaded to the network , implementation_dba_data: XNP.XNP_SV_SMS ,
-
Table: XNP_SV_SOA
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SOA, object_name:XNP_SV_SOA, status:VALID, product: XNP - Number Portability , description: Container object for a porting request on a single telephone number , implementation_dba_data: XNP.XNP_SV_SOA ,
-
Table: XNP_SV_SOA_JN
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SOA_JN, object_name:XNP_SV_SOA_JN, status:VALID, product: XNP - Number Portability , description: Journalling table for the XNP_SV_SOA table , implementation_dba_data: XNP.XNP_SV_SOA_JN ,
-
Table: XNP_SV_SOA_JN
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SOA_JN, object_name:XNP_SV_SOA_JN, status:VALID, product: XNP - Number Portability , description: Journalling table for the XNP_SV_SOA table , implementation_dba_data: XNP.XNP_SV_SOA_JN ,
-
Table: XNP_INTERCONNECT_AREAS
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_INTERCONNECT_AREAS, object_name:XNP_INTERCONNECT_AREAS, status:VALID, product: XNP - Number Portability , description: Stores geographic area covered by a routing number , implementation_dba_data: XNP.XNP_INTERCONNECT_AREAS ,
-
Table: XNP_SV_SOA
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SV_SOA, object_name:XNP_SV_SOA, status:VALID, product: XNP - Number Portability , description: Container object for a porting request on a single telephone number , implementation_dba_data: XNP.XNP_SV_SOA ,
-
Table: XNP_SERVICE_PROVIDERS
12.2.2
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SERVICE_PROVIDERS, object_name:XNP_SERVICE_PROVIDERS, status:VALID, product: XNP - Number Portability , description: Stores service provider definitions , implementation_dba_data: XNP.XNP_SERVICE_PROVIDERS ,
-
Table: XNP_SERVICE_PROVIDERS
12.1.1
owner:XNP, object_type:TABLE, fnd_design_data:XNP.XNP_SERVICE_PROVIDERS, object_name:XNP_SERVICE_PROVIDERS, status:VALID, product: XNP - Number Portability , description: Stores service provider definitions , implementation_dba_data: XNP.XNP_SERVICE_PROVIDERS ,
-
View: XNP_SV_SMS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:XNP.XNP_SV_SMS_V, object_name:XNP_SV_SMS_V, status:VALID, product: XNP - Number Portability , description: Shows porting information broadcasted by the NRC for the intention of network update , implementation_dba_data: APPS.XNP_SV_SMS_V ,
-
View: XNP_SV_SMS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:XNP.XNP_SV_SMS_V, object_name:XNP_SV_SMS_V, status:VALID, product: XNP - Number Portability , description: Shows porting information broadcasted by the NRC for the intention of network update , implementation_dba_data: APPS.XNP_SV_SMS_V ,
-
View: XNP_SV_SOA_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:XNP.XNP_SV_SOA_VL, object_name:XNP_SV_SOA_VL, status:VALID, product: XNP - Number Portability , description: Shows porting information for a single telephone number. Removed ( SVA.CREATED_BY_SP_ID=SPR_OWN.SP_ID ) from WHERE clausefor Service Bureau, since this will be handled automagically by VPD. rnyberg, 11/06/2000. , implementation_dba_data: APPS.XNP_SV_SOA_VL ,
-
View: XNP_SV_SOA_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:XNP.XNP_SV_SOA_VL, object_name:XNP_SV_SOA_VL, status:VALID, product: XNP - Number Portability , description: Shows porting information for a single telephone number. Removed ( SVA.CREATED_BY_SP_ID=SPR_OWN.SP_ID ) from WHERE clausefor Service Bureau, since this will be handled automagically by VPD. rnyberg, 11/06/2000. , implementation_dba_data: APPS.XNP_SV_SOA_VL ,