Search Results xnp_network_maps_uk1

Overview

The XNP_NETWORK_MAPS table is a core data structure within the Oracle E-Business Suite Number Portability (XNP) module. It functions as a relational mapping table, specifically designed to store and manage the hierarchical and associative relationships between network elements. In the context of telecommunications and number portability processes, network elements represent physical or logical components of the telephony infrastructure. The primary role of this table is to define how these elements are interconnected, which is critical for routing logic, service provisioning, and understanding network topology during number porting operations in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is optimized for defining relationships between two network elements. Its key columns, as defined by its primary and unique keys, are central to its purpose. The surrogate primary key is NETWORK_MAP_ID. The logical uniqueness of a relationship is enforced by a composite unique key (XNP_NETWORK_MAPS_UK1) on the combination of PARENT_FE_ID, CHILD_FE_ID, and MAP_TYPE. This design allows the table to store multiple types of relationships between the same pair of elements. The PARENT_FE_ID and CHILD_FE_ID columns are foreign keys that reference the XDP_FES table, identifying the specific network elements involved in the relationship. The MAP_TYPE column qualifies the nature of the link between the parent and child elements, such as hierarchical, adjacency, or functional dependency.

Common Use Cases and Queries

A primary use case is tracing network hierarchy or dependencies for a given network element. For instance, to find all child elements of a specific parent for operational reporting, a query would join XNP_NETWORK_MAPS to XDP_FES twice to resolve the IDs to names. Conversely, to find the parent or upstream elements for a given node, the join condition would be reversed. The MAP_TYPE filter is essential for isolating specific relationship types, like physical containment versus logical routing paths. This data is vital for impact analysis reports prior to a network change or for validating the network configuration setup during implementation. Sample SQL often involves hierarchical queries (CONNECT BY or recursive CTEs in later versions) to traverse multi-level network maps stored in this table.

Related Objects

The most direct and critical relationship for the XNP_NETWORK_MAPS table is with the XDP_FES table, which stores the master definition of the network elements (Front-End Systems or FEs). Two foreign key constraints (from PARENT_FE_ID and CHILD_FE_ID) enforce referential integrity to XDP_FES.FE_ID. This means every relationship recorded in XNP_NETWORK_MAPS must point to valid, existing records in the XDP_FES table. The table is owned by the XNP schema and is integral to the Number Portability product. While not listed in the provided metadata, it is logically related to other XNP transaction and order management tables that rely on accurate network mapping to execute porting orders correctly.