Results for “xnp_network_maps”

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

Overview

The XNP_NETWORK_MAPS table is a core data object within the Oracle EBS XNP – Number Portability product module. As documented in the ETRM repository (12.1.1 / 12.2.2), it "stores the relationship between network elements," capturing how functional elements (FEs) within a telecommunications network are hierarchically or logically connected to one another. This relationship data is fundamental to number portability processing, where calls, messages, and porting requests must be routed between the correct network endpoints.

The object resides in the XNP schema and is marked VALID. Its documented structure of 10 columns, one surrogate primary key, one business-key unique index, and two foreign keys to XDP_FES suggests a narrow, association-style table. Using Data Vault heuristic classification mined from the foreign-key structure, this object is best modeled as a link table — it sits between two hub-like references (parent FE and child FE) and records the nature of their association through MAP_TYPE. This classification is a modeling suggestion rather than a physical constraint of the EBS table itself.

Key Information Stored

Although the table contains 10 documented columns, the substantive business content is concentrated in a small set of attributes:

• NETWORK_MAP_ID — the surrogate primary key, enforced by XNP_NETWORK_MAPS_PK and also carried by the unique index XNP_NETWORK_MAPS_U1. It uniquely identifies each network-element relationship row.
• PARENT_FE_ID and CHILD_FE_ID — foreign keys into XDP_FES that define the two endpoints of each mapping. Together with MAP_TYPE, they form the documented business-key candidate XNP_NETWORK_MAPS_U2.
• MAP_TYPE — classifies the kind of relationship existing between the parent and child functional elements.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enabling multi-org / security-group-based data partitioning consistent with EBS standards.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns, populated by the WHO columns framework for every inserted or updated row.

The distinction between the surrogate key (NETWORK_MAP_ID) and the composite business key (PARENT_FE_ID, CHILD_FE_ID, MAP_TYPE) is significant: the business key guarantees that no duplicate relationship of the same type may exist between a given parent and child FE.

Common Use Cases and Queries

Typical usage centers on resolving and validating network topology during number porting operations. Practical scenarios include:

• Determining all child elements attached to a given parent FE.
• Validating that a proposed porting route is permissible (a mapping of the required type exists).
• Reporting on relationship patterns by MAP_TYPE for capacity and topology analysis.

A simple traversal of a parent's children can be expressed as:

SELECT parent_fe_id, child_fe_id, map_type
FROM   xnp.xnp_network_maps
WHERE  parent_fe_id = :p_fe_id
AND    security_group_id = :p_sec_group;

Joining to the functional element definition table resolves readable names:

SELECT pf.fe_name AS parent_fe, cf.fe_name AS child_fe,
       nm.map_type
FROM   xnp.xnp_network_maps nm,
       xdp_fes pf, xdp_fes cf
WHERE  nm.parent_fe_id = pf.fe_id
AND    nm.child_fe_id  = cf.fe_id
AND    nm.security_group_id = :p_sec_group;

Related Objects

The following objects are most significant to XNP_NETWORK_MAPS, based on documented relationships:

• XDP_FES — referenced twice, via XNP_NETWORK_MAPS.PARENT_FE_ID → XDP_FES and XNP_NETWORK_MAPS.CHILD_FE_ID → XDP_FES. This is the primary dependency, supplying both endpoints of each mapping.
• FND_SECURITY_GROUPS — referenced via XNP_NETWORK_MAPS.SECURITY_GROUP_ID; governs row-level access partitioning.
• XNP_NETWORK_MAPS_PK — primary key constraint/index on NETWORK_MAP_ID.
• XNP_NETWORK_MAPS_U2 — composite unique index on PARENT_FE_ID, CHILD_FE_ID, MAP_TYPE, enforcing business-key uniqueness.
• XNP_NETWORK_MAPS_U1 — unique index on NETWORK_MAP_ID, reinforcing the primary key.

Any Number Portability processing, validation, or reporting that depends on network-element adjacency should treat XNP_NETWORK_MAPS as the authoritative source for inter-FE relationships, always filtered by SECURITY_GROUP_ID where organizational visibility applies.