Search Results xnp_number_splits_uk1

Overview

The XNP_NUMBER_SPLITS table is a core data object within the Oracle E-Business Suite Number Portability (XNP) module. It provides the foundational data structure for managing a critical telecommunications operation: the splitting of a contiguous range of telephone numbers into new, distinct ranges. This process is essential during network reorganizations, carrier expansions, or regulatory mandates. The table's role is to persistently store the mapping logic that defines how an existing ("old") number range is algorithmically transformed and allocated into one or more new number ranges, ensuring the integrity of number portability data during and after such migrations.

Key Information Stored

The table centrally stores the relationship between old and new number ranges and the conversion logic. The primary identifier is the NUMBER_SPLIT_ID. The two most critical foreign key columns are OLD_NUMBER_RANGE_ID and NEW_NUMBER_RANGE_ID, which link to the XNP_NUMBER_RANGES table to define the specific ranges involved in the split operation. As indicated by the documentation, a third crucial piece of information stored is the algorithm used to convert numbers from the old range to the new range. This algorithm defines the mathematical or logical rule (e.g., a prefix change or a sequential mapping) that governs how each individual number within the old range is assigned its new value within the new range.

Common Use Cases and Queries

The primary use case is operational support and auditing during a number range split event. Administrators use this table to validate split configurations, trace the provenance of a ported number, and generate reports for regulatory compliance. A common query retrieves all splits associated with a specific original number range to understand its fragmentation history. For example: SELECT ns.NUMBER_SPLIT_ID, old_rng.RANGE_NAME as OLD_RANGE, new_rng.RANGE_NAME as NEW_RANGE, ns.ALGORITHM FROM XNP_NUMBER_SPLITS ns JOIN XNP_NUMBER_RANGES old_rng ON ns.OLD_NUMBER_RANGE_ID = old_rng.NUMBER_RANGE_ID JOIN XNP_NUMBER_RANGES new_rng ON ns.NEW_NUMBER_RANGE_ID = new_rng.NUMBER_RANGE_ID WHERE old_rng.RANGE_NAME = '&RANGE_NAME'; Another critical use case is in batch processing engines within the XNP module, which would read records from this table to programmatically apply the defined algorithm and update subscriber and routing records en masse during the cutover to the new ranges.

Related Objects

The XNP_NUMBER_SPLITS table has defined dependencies on the central number range repository. It is intricately linked to the XNP_NUMBER_RANGES table via two foreign key relationships:

• XNP_NUMBER_SPLITS.OLD_NUMBER_RANGE_ID references XNP_NUMBER_RANGES
• XNP_NUMBER_SPLITS.NEW_NUMBER_RANGE_ID references XNP_NUMBER_RANGES

These relationships enforce referential integrity, ensuring that a split record can only be defined for valid, pre-existing number ranges. The table's primary key, XNP_NUMBER_SPLITS_PK on NUMBER_SPLIT_ID, is likely referenced by other transactional or logging tables within the XNP schema that track the execution and results of split operations. The unique key XNP_NUMBER_SPLITS_UK1 on the combination of OLD_NUMBER_RANGE_ID and NEW_NUMBER_RANGE_ID prevents duplicate split definitions between the same two ranges.