Results for “xnp_served_num_ranges”

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

Overview

XNP_SERVED_NUM_RANGES is a transactional table in the XNP (Number Portability) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the mapping of telephone number ranges served by a network element for each feature type. In number portability operations, this table answers the operational question of which network element (feature element, or FE) is responsible for serving a given block of numbers under a given feature. It therefore acts as the intersection between the number range definition and the network element definition.

From a heuristic Data Vault classification mined from the foreign key structure, this table is best modeled as a link — it resolves a many-to-many association between number ranges and feature elements, with the FEATURE_TYPE and PRIMARY_FLAG attributes providing link-level context. This classification is a modeling suggestion based on the FK topology and should be validated against the actual business rules governing range assignment.

Key Information Stored

The table carries 13 documented columns. The most significant are:

• SERVED_NUMBER_RANGE_ID — the surrogate primary key, defined by constraint XNP_SERVED_NUM_RANGES_PK. It is a system-generated identifier that uniquely identifies each served range record.
• NUMBER_RANGE_ID — foreign key to XNP_NUMBER_RANGES, identifying the number range that is being served.
• FE_ID — foreign key to XDP_FES, identifying the network feature element that serves the range.
• FEATURE_TYPE — the feature type under which the range is served; this is a discriminator that allows the same number range and feature element pairing to exist for multiple features.
• PRIMARY_FLAG — indicates whether the served range is the primary assignment for the associated feature element and feature type.
• ACTIVE_FLAG — flags the record as active or inactive for filtering in operational and reporting queries.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / data security partitioning.
• ZD_EDITION_NAME — the editioning column used in 12.2 online patching; it participates in both unique indexes and is essential for querying the correct edition of the data.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard who-columns for change tracking.

Two unique indexes serve as business-key candidates. XNP_SERVED_NUM_RANGES_U1 is defined on (SERVED_NUMBER_RANGE_ID, ZD_EDITION_NAME). XNP_SERVED_NUM_RANGES_U2 is defined on (NUMBER_RANGE_ID, FE_ID, FEATURE_TYPE, ZD_EDITION_NAME), which is the meaningful business key that prevents a duplicate mapping of the same range to the same feature element for the same feature type within an edition. The documentation also references a unique constraint named XNP_SERVED_NUM_RANGES_UK1 on NUMBER_RANGE_ID, FE_ID, and FEATURE_TYPE, which the user searched for; this constraint corresponds to the business rule encapsulated by U2.

Common Use Cases and Queries

Typical use cases include determining which network element serves a given number range, listing all ranges served by a feature element, and reporting on primary versus secondary assignments. A representative query joins the number ranges and feature elements and filters to the current edition:

• SELECT s.SERVED_NUMBER_RANGE_ID, n.NUMBER_RANGE, f.FE_NAME, s.FEATURE_TYPE, s.PRIMARY_FLAG
• FROM XNP_SERVED_NUM_RANGES s, XNP_NUMBER_RANGES n, XDP_FES f
• WHERE s.NUMBER_RANGE_ID = n.NUMBER_RANGE_ID
• AND s.FE_ID = f.FE_ID
• AND s.ACTIVE_FLAG = 'Y'
• AND s.ZD_EDITION_NAME = (SELECT MAX(Z.EDITION_NAME) FROM XNP_SERVED_NUM_RANGES Z);

Additional scenarios include validating that every active number range has at least one served-range mapping, auditing duplicate or overlapping range assignments, and generating coverage reports per feature type for provisioning and routing configuration.

Related Objects

• XNP_NUMBER_RANGES — referenced via XNP_SERVED_NUM_RANGES.NUMBER_RANGE_ID; the parent definition of the number ranges being served.
• XDP_FES — referenced via XNP_SERVED_NUM_RANGES.FE_ID; the feature elements (network elements) that serve the ranges.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data access partitioning.
• XNP_SERVED_NUM_RANGES_PK — the primary key constraint on SERVED_NUMBER_RANGE_ID.
• XNP_SERVED_NUM_RANGES_UK1 / U2 — the unique business key on NUMBER_RANGE_ID, FE_ID, and FEATURE_TYPE.

No additional dependent views or APIs are documented in the supplied metadata; the primary dependencies are the two parent tables and the security group table.