Oracle eBusiness Suite Technical Reference

Release 11i - Copyright (c) 2001 - 2005 Oracle

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend

This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.

eTRM - XNP Tables and Views

TABLE - XNP.XNP_AUDIT_DISCREPANCIES

TABLE - XNP.XNP_AUDIT_SMS_FAILURES

TABLE - XNP.XNP_CALLBACK_EVENTS

TABLE - XNP.XNP_DEBUG

TABLE - XNP.XNP_EVENT_SUBSCRIBERS

TABLE - XNP.XNP_GEO_AREAS_B

TABLE - XNP.XNP_GEO_AREAS_TL

TABLE - XNP.XNP_GEO_HIERARCHY

TABLE - XNP.XNP_INTERCONNECT_AREAS

TABLE - XNP.XNP_MSGS

TABLE - XNP.XNP_MSG_ACKS

TABLE - XNP.XNP_MSG_ATTR_VALUES

TABLE - XNP.XNP_MSG_ELEMENTS

TABLE - XNP.XNP_MSG_ELEMENT_ATTR

TABLE - XNP.XNP_MSG_STRUCTURES

TABLE - XNP.XNP_MSG_TYPES_B

TABLE - XNP.XNP_MSG_TYPES_TL

TABLE - XNP.XNP_NETWORK_MAPS

TABLE - XNP.XNP_NUMBER_RANGES

TABLE - XNP.XNP_NUMBER_SPLITS

TABLE - XNP.XNP_ROUTING_NUMBERS

TABLE - XNP.XNP_SERVED_NUM_RANGES

TABLE - XNP.XNP_SERVICE_AREAS

TABLE - XNP.XNP_SERVICE_PROVIDERS

TABLE - XNP.XNP_SP_ADAPTERS

TABLE - XNP.XNP_SP_CONTACTS

TABLE - XNP.XNP_SP_FILTERS

TABLE - XNP.XNP_SV_AUDITS

TABLE - XNP.XNP_SV_EVENT_HISTORY

TABLE - XNP.XNP_SV_FAILURES

TABLE - XNP.XNP_SV_ORDER_MAPPINGS

TABLE - XNP.XNP_SV_SMS

TABLE - XNP.XNP_SV_SMS_FE_MAPS

TABLE - XNP.XNP_SV_SOA

TABLE - XNP.XNP_SV_SOA_JN

TABLE - XNP.XNP_SV_STATUS_TYPES_B

TABLE - XNP.XNP_SV_STATUS_TYPES_TL

TABLE - XNP.XNP_SYNC_REGISTRATION

TABLE - XNP.XNP_TIMER_PUBLISHERS

TABLE - XNP.XNP_TIMER_REGISTRY

VIEW - APPS.XNP_GEO_AREAS_VL

VIEW - APPS.XNP_LOOKUPS

VIEW - APPS.XNP_MSG_TYPES_VL

VIEW - APPS.XNP_SV_FE_MAPP_DETAILS_VL

VIEW - APPS.XNP_SV_ORDER_MAPP_DETAILS_VL

VIEW - APPS.XNP_SV_SMS_V

VIEW - APPS.XNP_SV_SOA_VL

VIEW - APPS.XNP_SV_STATUS_TYPES_VL

Table: XNP_AUDIT_DISCREPANCIES

Primary Key: XNP_AUDIT_DISCREPANCIES_PK

1. AUDIT_DISCREPANCY_ID

Primary Key: XNP_AUDIT_DISCREPANCIES_UK1

1. SUBSCRIPTION_TN
2. SP_ID
3. AUDIT_ID
4. ERROR_CODE

Foreign Keys from this table:

Comments

XNP_AUDIT_DISCREPENCIES stores discrepencies between a subscription version and the data in a given service provider's network. Discrepancy reports are direct results of an audit.Network data of a subscription version typically includes a Routing Number(RN) and vertical services that are associated with a telephone line.
Services may include Caller Naming (CNAM), Integrated Services Voice Mail (ISVM), Line Information Databases (LIDB) for calling card verification, Custom Local Area Signaling Services (CLASS), and Wireless Short Message Service Center(WSMSC).This table will not be used in the current release.

Indexes

Columns

[top of page]

XNP.XNP_AUDIT_DISCREPANCIES does not reference any database object

XNP.XNP_AUDIT_DISCREPANCIES is referenced by following:

APPS

SYNONYM - XNP_AUDIT_DISCREPANCIES

[top of page]

Table: XNP_AUDIT_SMS_FAILURES

Primary Key: XNP_AUDIT_SMS_FAILURES_PK

1. SMS_FAILURE_ID

Primary Key: XNP_AUDIT_SMS_FAILURES_UK1

1. AUDIT_ID
2. SP_ID
3. FAILURE_DATE

Foreign Keys from this table:

Comments

XNP_AUDIT_SMS_FAILURES stores a list of service providers that failed to provide requested audit information. This is an optional list in the audit results. This table will not be used in the current release.

Indexes

Columns

[top of page]

XNP.XNP_AUDIT_SMS_FAILURES does not reference any database object

XNP.XNP_AUDIT_SMS_FAILURES is referenced by following:

APPS

SYNONYM - XNP_AUDIT_SMS_FAILURES

[top of page]

Table: XNP_CALLBACK_EVENTS

Primary Key: XNP_CALLBACK_EVENTS_PK

1. CALLBACK_EVENT_ID

Foreign Keys from this table:

Comments

XNP_CALLBACK_EVENTS stores a registry of callbacks for instances of message types (messages or events). This enables the Event Manager to invoke the callback procedure specified in the particular instance of the program which is awaiting the data rather than the default callback procedure which is specified as part of definition of the message type.

Indexes

Columns

[top of page]

XNP.XNP_CALLBACK_EVENTS does not reference any database object

XNP.XNP_CALLBACK_EVENTS is referenced by following:

APPS

SYNONYM - XNP_CALLBACK_EVENTS

[top of page]

Table: XNP_DEBUG

Primary Key: XNP_DEBUG_PK

1. DEBUG_ID

Comments

XNP_DEBUG stores general debug information in NP system.

Indexes

Columns

[top of page]

XNP.XNP_DEBUG does not reference any database object

XNP.XNP_DEBUG is referenced by following:

APPS

SYNONYM - XNP_DEBUG

[top of page]

Table: XNP_EVENT_SUBSCRIBERS

Primary Key: XNP_EVENT_SUBSCRIBERS_PK

1. EVENT_SUBSCRIBER_ID

Primary Key: XNP_EVENT_SUBSCRIBERS_UK1

1. MSG_CODE
2. FE_ID

Foreign Keys from this table:

Comments

XNP_EVENT_SUBSCRIBERS stores the list of subscribers for a given event.

Indexes

Columns

[top of page]

XNP.XNP_EVENT_SUBSCRIBERS does not reference any database object

XNP.XNP_EVENT_SUBSCRIBERS is referenced by following:

APPS

SYNONYM - XNP_EVENT_SUBSCRIBERS

[top of page]

Table: XNP_GEO_AREAS_B

Primary Key: XNP_GEO_AREAS_B_PK

1. GEO_AREA_ID

Primary Key: XNP_GEO_AREAS_B_UK1

1. GEO_AREA_TYPE_CODE
2. CODE

Foreign Keys to this table:

Comments

XNP_GEO_AREAS_B stores given geographic areas.
There can be hierarchy of geographic areas.
EXAMPLE: EU Europe, WE West Europe, PA Paris, US, United States of America, CA California
SF San Francisco, LA Los Angeles
In the context of NP, Geographic areas are used to describe the area covered by a Service provider,
Routing Number and Number Range.

Indexes

Columns

[top of page]

XNP.XNP_GEO_AREAS_B does not reference any database object

XNP.XNP_GEO_AREAS_B is referenced by following:

APPS

SYNONYM - XNP_GEO_AREAS_B

[top of page]

Table: XNP_GEO_AREAS_TL

Primary Key: XNP_GEO_AREAS_TL_PK

1. GEO_AREA_ID
2. LANGUAGE

Foreign Keys from this table:

Comments

XNP_GEO_AREAS_TL is a translation table to XNP_GEO_AREAS_B.

Indexes

Columns

[top of page]

XNP.XNP_GEO_AREAS_TL does not reference any database object

XNP.XNP_GEO_AREAS_TL is referenced by following:

APPS

SYNONYM - XNP_GEO_AREAS_TL

[top of page]

Table: XNP_GEO_HIERARCHY

Primary Key: XNP_GEO_HIERARCHY_PK

1. GEO_HIERARCHY_ID

Primary Key: XNP_GEO_HIERARCHY_UK1

1. PARENT_GEO_AREA_ID
2. CHILD_GEO_AREA_ID

Foreign Keys from this table:

Comments

XNP_GEO_HIERARCHY holds information about the geographic area hierarchy.

Indexes

Columns

[top of page]

XNP.XNP_GEO_HIERARCHY does not reference any database object

XNP.XNP_GEO_HIERARCHY is referenced by following:

APPS

SYNONYM - XNP_GEO_HIERARCHY

[top of page]

Table: XNP_INTERCONNECT_AREAS

Primary Key: XNP_INTERCONNECT_AREAS_PK

1. INTERCONNECT_AREA_ID

Primary Key: XNP_INTERCONNECT_AREAS_UK1

1. ROUTING_NUMBER_ID
2. GEO_AREA_ID

Foreign Keys from this table:

Comments

XNP_INTERCONNECT_AREAS stores geographic area covered by a Routing Number. The geographic area covered by a Routing Number is known as an Interconnect Area.

Indexes

Columns

[top of page]

XNP.XNP_INTERCONNECT_AREAS does not reference any database object

XNP.XNP_INTERCONNECT_AREAS is referenced by following:

APPS

SYNONYM - XNP_INTERCONNECT_AREAS

[top of page]

Table: XNP_MSGS

Primary Key: XNP_MSGS_PK

1. MSG_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_MSGS stores the actual instance of a message that passes over a network association.

Indexes

Columns

[top of page]

XNP.XNP_MSGS does not reference any database object

XNP.XNP_MSGS is referenced by following:

APPS

SYNONYM - XNP_MSGS

[top of page]

Table: XNP_MSG_ACKS

Primary Key: XNP_MSG_ACKS_PK

1. MSG_ACK_ID

Foreign Keys from this table:

Comments

XNP_MSG_ACKS stores the relationship between messages in the application. An outgoing message can result in one or more incoming messages. The information in this table can be used by the application process to register or wait for the resulting incoming messages.

Indexes

Columns

[top of page]

XNP.XNP_MSG_ACKS does not reference any database object

XNP.XNP_MSG_ACKS is referenced by following:

APPS

SYNONYM - XNP_MSG_ACKS

[top of page]

Table: XNP_MSG_ATTR_VALUES

Primary Key: XNP_MSG_ATTR_VALUES_PK

1. MSG_ATTR_VALUE_ID

Foreign Keys from this table:

Comments

XNP_MSG_ATTR_VALUES contains attribute values for XML message elements. This table will not be used in the current release and elements will not have attributes.

Indexes

Columns

[top of page]

XNP.XNP_MSG_ATTR_VALUES does not reference any database object

XNP.XNP_MSG_ATTR_VALUES is referenced by following:

APPS

SYNONYM - XNP_MSG_ATTR_VALUES

[top of page]

Table: XNP_MSG_ELEMENTS

Primary Key: XNP_MSG_ELEMENTS_PK

1. MSG_ELEMENT_ID

Primary Key: XNP_MSG_ELEMENTS_UK1

1. NAME
2. MSG_CODE

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_MSG_ELEMENTS stores a lookup of all elements in the message. A message is a collection of elements or attributes

Indexes

Columns

[top of page]

XNP.XNP_MSG_ELEMENTS does not reference any database object

XNP.XNP_MSG_ELEMENTS is referenced by following:

APPS

SYNONYM - XNP_MSG_ELEMENTS

[top of page]

Table: XNP_MSG_ELEMENT_ATTR

Primary Key: XNP_MSG_ELEMENT_ATTR_PK

1. MSG_ELEMENT_ATTR_ID

Primary Key: XNP_MSG_ELEMENT_ATTR_UK1

1. MSG_ELEMENT_ATTR_ID
2. NAME

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_MSG_ELEMENT_ATTR contains attributes of Extensible Markup Language (XML) elements. XML is markup language for documents containing structured information. This table is used to store the attributes or context of a message element. This table will not be used in the current release and elements will not have attributes.

Indexes

Columns

[top of page]

XNP.XNP_MSG_ELEMENT_ATTR does not reference any database object

XNP.XNP_MSG_ELEMENT_ATTR is referenced by following:

APPS

SYNONYM - XNP_MSG_ELEMENT_ATTR

[top of page]

Table: XNP_MSG_STRUCTURES

Primary Key: XNP_MSG_STRUCTURES_PK

1. STRUCTURE_ID

Primary Key: XNP_MSG_STRUCTURES_UK1

1. MSG_CODE
2. CHILD_ELEMENT_ID
3. PARENT_ELEMENT_ID

Foreign Keys from this table:

Comments

XNP_MSG_STRUCTURES contains the structural relationship or hierarchy of all elements in the Extensible Markup Language (XML) message. XML is a markup language for documents containing structured information. The information in this table is used to generate the SEND(), PUBLISH(), VALIDATE(), PROCESS() and DEFAULT_PROCESS() procedures. The information in this table can also be used to generate the Document Type Definition (DTD). DTD is a series of definitions for element types, attributes, entities and notations.

Indexes

Columns

[top of page]

XNP.XNP_MSG_STRUCTURES does not reference any database object

XNP.XNP_MSG_STRUCTURES is referenced by following:

APPS

SYNONYM - XNP_MSG_STRUCTURES

[top of page]

Table: XNP_MSG_TYPES_B

Primary Key: XNP_MSG_TYPES_B_PK

1. MSG_CODE

Foreign Keys to this table:

Comments

XNP_MSG_TYPES_B stores the message information. The code generated for a message differs according to the type of the message. This table provides a lookup and serves as a data dictionary for the message.

Indexes

Columns

[top of page]

XNP.XNP_MSG_TYPES_B does not reference any database object

XNP.XNP_MSG_TYPES_B is referenced by following:

APPS

SYNONYM - XNP_MSG_TYPES_B

[top of page]

Table: XNP_MSG_TYPES_TL

Primary Key: XNP_MSG_TYPES_TL_PK

1. MSG_CODE
2. LANGUAGE

Foreign Keys from this table:

Comments

XNP_MSG_TYPES_TL is a translation table to XNP_MSG_TYPES_B.

Indexes

Columns

[top of page]

XNP.XNP_MSG_TYPES_TL does not reference any database object

XNP.XNP_MSG_TYPES_TL is referenced by following:

APPS

SYNONYM - XNP_MSG_TYPES_TL

[top of page]

Table: XNP_NETWORK_MAPS

Primary Key: XNP_NETWORK_MAPS_PK

1. NETWORK_MAP_ID

Primary Key: XNP_NETWORK_MAPS_UK1

1. PARENT_FE_ID
2. CHILD_FE_ID
3. MAP_TYPE

Foreign Keys from this table:

Comments

XNP_NETWORK_MAPS stores the relationship between network elements. When a number range is opened for porting, the network data in the switch serving the number range must be updated. Switches transfer control to STPs (Signal Transfer Point) for resolving address and database queries. Every switch is served by its home STP as the primary and a mated STP for backup. When a number range is open for porting, the STP should also be provisioned with the address of the SCP (Service Control Point). The SCP will resolve all routing information queries for the given number range. The network mapping gives the info about which switch is connected to which STP or SCP. This tool can be used to identify all related network elements which need an update when a number range is opened to portability.

Indexes

Columns

[top of page]

XNP.XNP_NETWORK_MAPS does not reference any database object

XNP.XNP_NETWORK_MAPS is referenced by following:

APPS

SYNONYM - XNP_NETWORK_MAPS

[top of page]

Table: XNP_NUMBER_RANGES

Primary Key: XNP_NUMBER_RANGES_PK

1. NUMBER_RANGE_ID

Primary Key: XNP_NUMBER_RANGES_UK1

1. STARTING_NUMBER

Primary Key: XNP_NUMBER_RANGES_UK2

1. OBJECT_REFERENCE

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_NUMBER_RANGES stores information about the characteristics of a service provider TN ranges.

Indexes

Columns

[top of page]

XNP.XNP_NUMBER_RANGES does not reference any database object

XNP.XNP_NUMBER_RANGES is referenced by following:

APPS

TRIGGER - XNP_NRE_BRI

SYNONYM - XNP_NUMBER_RANGES

[top of page]

Table: XNP_NUMBER_SPLITS

Primary Key: XNP_NUMBER_SPLITS_PK

1. NUMBER_SPLIT_ID

Primary Key: XNP_NUMBER_SPLITS_UK1

1. OLD_NUMBER_RANGE_ID
2. NEW_NUMBER_RANGE_ID

Foreign Keys from this table:

Comments

XNP_NUMBER_SPLITS stores information about a number split. The split algorithm represents the transformation from the old number range to the new number range.
For example, in the case of an Number Planning Area (NPA) split in the US from area code 415 to 415 and 650, the algorithm would specify the first 3 characters (the NPA) to be modified from 415 to 650 for only certain number ranges that meet a specific criteria such as the geographic region where the range is located.

Indexes

Columns

[top of page]

XNP.XNP_NUMBER_SPLITS does not reference any database object

XNP.XNP_NUMBER_SPLITS is referenced by following:

APPS

SYNONYM - XNP_NUMBER_SPLITS

[top of page]

Table: XNP_ROUTING_NUMBERS

Primary Key: XNP_ROUTING_NUMBERS_PK

1. ROUTING_NUMBER_ID

Primary Key: XNP_ROUTING_NUMBERS_UK1

1. SP_ID
2. ROUTING_NUMBER
3. INTERCONNECT_TYPE

Primary Key: XNP_ROUTING_NUMBERS_UK2

1. OBJECT_REFERENCE

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_ROUTING_NUMBERS stores Routing Numbers for a given Service ProviderThe Routing Number is used by all service providers to port telephone number to the appropriate service provider.
A Routing Number typically identifies a specific destination within a service provider's network such as switch.

Indexes

Columns

[top of page]

XNP.XNP_ROUTING_NUMBERS does not reference any database object

XNP.XNP_ROUTING_NUMBERS is referenced by following:

APPS

SYNONYM - XNP_ROUTING_NUMBERS

[top of page]

Table: XNP_SERVED_NUM_RANGES

Primary Key: XNP_SERVED_NUM_RANGES_PK

1. SERVED_NUMBER_RANGE_ID

Primary Key: XNP_SERVED_NUM_RANGES_UK1

1. NUMBER_RANGE_ID
2. FE_ID
3. FEATURE_TYPE

Foreign Keys from this table:

Comments

XNP_SERVED_NUM_RANGES stores the mapping of number ranges served by network element for each feature type

Indexes

Columns

[top of page]

XNP.XNP_SERVED_NUM_RANGES does not reference any database object

XNP.XNP_SERVED_NUM_RANGES is referenced by following:

APPS

SYNONYM - XNP_SERVED_NUM_RANGES

[top of page]

Table: XNP_SERVICE_AREAS

Primary Key: XNP_SERVICE_AREAS_PK

1. SERVICE_AREA_ID

Primary Key: XNP_SERVICE_AREAS_UK1

1. SP_ID
2. GEO_AREA_ID

Foreign Keys from this table:

Comments

XNP_SERVICE_AREAS holds information regarding geographic areas that are served by a service provider.

Indexes

Columns

[top of page]

XNP.XNP_SERVICE_AREAS does not reference any database object

XNP.XNP_SERVICE_AREAS is referenced by following:

APPS

SYNONYM - XNP_SERVICE_AREAS

[top of page]

Table: XNP_SERVICE_PROVIDERS

Primary Key: XNP_SERVICE_PROVIDERS_PK

1. SP_ID

Primary Key: XNP_SERVICE_PROVIDERS_UK1

1. CODE

Foreign Keys to this table:

Comments

XNP_SERVICE_PROVIDERS is the definition table for service providers. This table holds service provider details used by the Number Portability Service delivery Management System (NP SMS), Number Portability Service Order Administration (NP SOA) and Number Registration Center (NRC).

Indexes

Columns

[top of page]

XNP.XNP_SERVICE_PROVIDERS does not reference any database object

XNP.XNP_SERVICE_PROVIDERS is referenced by following:

APPS

SYNONYM - XNP_SERVICE_PROVIDERS

[top of page]

Table: XNP_SP_ADAPTERS

Primary Key: XNP_SP_ADAPTERS_PK

1. SP_ADAPTER_ID

Primary Key: XNP_SP_ADAPTERS_UK1

1. FE_ID
2. SP_ID

Foreign Keys from this table:

Comments

XNP_SP_ADAPTERS stores mapping of a service provider to an external system.
This configuration data is used by SDP to send and receive messages to/from service providers.

Indexes

Columns

[top of page]

XNP.XNP_SP_ADAPTERS does not reference any database object

XNP.XNP_SP_ADAPTERS is referenced by following:

APPS

SYNONYM - XNP_SP_ADAPTERS

[top of page]

Table: XNP_SP_CONTACTS

Primary Key: XNP_SP_CONTACTS_PK

1. SP_CONTACT_ID

Primary Key: XNP_SP_CONTACTS_UK1

1. BUSINESS_ROLE
2. SP_ID
3. NAME

Foreign Keys from this table:

Comments

XNP_SP_CONTACTS holds contact information for the service provider

Indexes

Columns

[top of page]

XNP.XNP_SP_CONTACTS does not reference any database object

XNP.XNP_SP_CONTACTS is referenced by following:

APPS

SYNONYM - XNP_SP_CONTACTS

[top of page]

Table: XNP_SP_FILTERS

Primary Key: XNP_SP_FILTERS_PK

1. SP_FILTER_ID

Primary Key: XNP_SP_FILTERS_UK1

1. OBJECT_REFERENCE

Primary Key: XNP_SP_FILTERS_UK2

1. SP_ID
2. NUMBER_RANGE_ID

Foreign Keys from this table:

Comments

XNP_SP_FILTERS stores a list of filtered Telephone Number ranges that a service provider is interested in.

Indexes

Columns

[top of page]

XNP.XNP_SP_FILTERS does not reference any database object

XNP.XNP_SP_FILTERS is referenced by following:

APPS

SYNONYM - XNP_SP_FILTERS

[top of page]

Table: XNP_SV_AUDITS

Primary Key: XNP_SV_AUDITS_PK

1. SV_AUDIT_ID

Primary Key: XNP_SV_AUDITS_UK1

1. OBJECT_REFERENCE

Primary Key: XNP_SV_AUDITS_UK2

1. SP_ID
2. STARTING_NUMBER

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_SV_AUDITS stores all the subscription audits issued from a service provider . When no target service provider is specified, all service provider's data will be audited.
In places where the product is installed as NP SMS or NP SOA for a service provider, this table has entries for the audits that were issued by that service provider.
In case of a service bureau, the entity holds all the audits that were issued by the member service providers.
An NRC installation holds all subscription audits from all service providers.

Indexes

Columns

[top of page]

XNP.XNP_SV_AUDITS does not reference any database object

XNP.XNP_SV_AUDITS is referenced by following:

APPS

SYNONYM - XNP_SV_AUDITS

[top of page]

Table: XNP_SV_EVENT_HISTORY

Primary Key: XNP_SV_EVENT_HISTORY_PK

1. SV_EVENT_HISTORY_ID

Foreign Keys from this table:

Comments

XNP_SV_EVENT_HISTORY stores the information about any kind of event on the porting number or message.
It is mainly associated with the status change events in SOA.

Indexes

Columns

[top of page]

XNP.XNP_SV_EVENT_HISTORY does not reference any database object

XNP.XNP_SV_EVENT_HISTORY is referenced by following:

APPS

SYNONYM - XNP_SV_EVENT_HISTORY

[top of page]

Table: XNP_SV_FAILURES

Primary Key: XNP_SV_FAILURES_PK

1. SV_FAILURE_ID

Primary Key: XNP_SV_FAILURES_UK1

1. SP_ID
2. SV_SOA_ID
3. FAILURE_DATE

Foreign Keys from this table:

Comments

XNP_SV_FAILURES stores a list of service providers that failed to download the subscription version data. In the business process for Number portability, the SOA or NRC broadcasts a subscription version to allservice provider's network system. An entry for a service provider is added into this table on encountering a failure. Attempts to broadcast are abandoned after a maximum number of retries.

Indexes

Columns

[top of page]

XNP.XNP_SV_FAILURES does not reference any database object

XNP.XNP_SV_FAILURES is referenced by following:

APPS

SYNONYM - XNP_SV_FAILURES

[top of page]

Table: XNP_SV_ORDER_MAPPINGS

Primary Key: XNP_SV_ORDER_MAPPINGS_PK

1. SV_ORDER_MAPPING_ID

Primary Key: XNP_SV_ORDER_MAPPINGS_UK1

1. ORDER_ID
2. SV_SOA_ID
3. SV_SMS_ID
4. WORKITEM_INSTANCE_ID

Foreign Keys from this table:

Comments

XNP_SV_ORDER_MAPPINGS stores event information associated with subscription versions or messages.

Indexes

Columns

[top of page]

XNP.XNP_SV_ORDER_MAPPINGS does not reference any database object

XNP.XNP_SV_ORDER_MAPPINGS is referenced by following:

APPS

SYNONYM - XNP_SV_ORDER_MAPPINGS

[top of page]

Table: XNP_SV_SMS

Primary Key: XNP_SV_SMS_PK

1. SV_SMS_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_SV_SMS stores downloaded network data for porting requests from NRC. The records can only be created, deleted or modified upon instructions from the Number Registratin Center. Data in this table cannot be modified directly from a NP SMS or SOA system.
The five vertical services associated with a telephone line are included in the table. Services include Caller Naming (CNAM), Integrated Services Voice Mail (ISVM), Line Information Databases (LIDB) for calling card verification, Custom Local Area Signaling Services (CLASS), and Wireless Short Message Service Center(WSMSC).

Indexes

Columns

[top of page]

XNP.XNP_SV_SMS does not reference any database object

XNP.XNP_SV_SMS is referenced by following:

APPS

SYNONYM - XNP_SV_SMS

[top of page]

Table: XNP_SV_SMS_FE_MAPS

Primary Key: XNP_SV_SMS_FE_MAPS_PK

1. SMS_FE_MAP_ID

Primary Key: XNP_SV_SMS_FE_MAPS_UK

1. SV_SMS_ID
2. FEATURE_TYPE
3. FE_ID

Foreign Keys from this table:

Comments

XNP_SV_SMS_FE_MAPS stores a list of fulfillment elements provisioned with subscription version data.

Indexes

Columns

[top of page]

XNP.XNP_SV_SMS_FE_MAPS does not reference any database object

XNP.XNP_SV_SMS_FE_MAPS is referenced by following:

APPS

SYNONYM - XNP_SV_SMS_FE_MAPS

[top of page]

Table: XNP_SV_SOA

Primary Key: XNP_SV_SOA_PK

1. SV_SOA_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

XNP_SV_SOA contains a log of all subscription versions created. This entity will also service subscription version queries and contains a local copy of NRC porting data for a given SP.
In case of a service bureau, this entity contains all subscription versions created by its members.
The five vertical services that are associated with a telephone line are included in the table. Services may include Caller Naming (CNAM), Integrated Services Voice Mail (ISVM), Line Information Databases (LIDB) for calling card verification, Custom Local Area Signaling Services (CLASS) and Wireless Short Message Service Center (WSMSC).

Indexes

Columns

[top of page]

XNP.XNP_SV_SOA does not reference any database object

XNP.XNP_SV_SOA is referenced by following:

APPS

TRIGGER - XNP_SVA_ARD

TRIGGER - XNP_SVA_ARI

TRIGGER - XNP_SVA_ARU

SYNONYM - XNP_SV_SOA

[top of page]

Table: XNP_SV_SOA_JN

Primary Key: XNP_SV_SOA_JN_PK

1. SV_SOA_ID
2. JN_ORACLE_USER
3. JN_DATETIME
4. JN_OPERATION

Foreign Keys from this table:

Comments

XNP_SV_SOA_JN is a journalling table for the XNP_SV_SOA table.

Columns