Search Results xnp_sv_sms_fe_maps




Overview
Explore in AI Chat

Overview

The table XNP_SV_SMS_FE_MAPS is a core data object within the Oracle E-Business Suite (EBS) Number Portability (XNP) module. Its primary function is to manage the mapping between subscription version data and specific fulfillment elements (FEs) that are provisioned as part of a service order. This table acts as a junction or association table, linking a subscription version's service management system (SMS) record to the individual fulfillment components required to implement the service. It is critical for tracking the complete set of provisioning actions and configurations associated with a given subscription during the number porting process, ensuring that all necessary network and system elements are correctly identified and updated.

Key Information Stored

The table's structure is designed to capture the essential links between a subscription and its fulfillment requirements. The key columns include SMS_FE_MAP_ID, which serves as the unique primary key identifier for each mapping record. The SV_SMS_ID column is a foreign key that links to the parent subscription version record in the XNP_SV_SMS table. The FE_ID column is a foreign key referencing the specific fulfillment element in the XDP_FES table, which is part of the Oracle Order and Service Management (OSM) foundation. The FEATURE_TYPE column further qualifies the type or role of the fulfillment element within the context of the subscription, allowing for categorization of different FE roles (e.g., line, service, feature).

Common Use Cases and Queries

A primary use case involves generating provisioning reports or validating the completeness of a service order setup for number portability. For instance, an administrator may need to list all fulfillment elements associated with a specific subscription version to verify provisioning tasks. A common query pattern would join this table to its parent and reference tables:

  • SELECT sv_sms.sv_sms_id, fe_maps.feature_type, fes.name FROM xnp_sv_sms_fe_maps fe_maps JOIN xnp_sv_sms sv_sms ON fe_maps.sv_sms_id = sv_sms.sv_sms_id JOIN xdp_fes fes ON fe_maps.fe_id = fes.fe_id WHERE sv_sms.order_id = :p_order_number;

This table is also integral to backend processes that drive the fulfillment orchestration, where the mapped FEs are passed to the OSM framework for execution. Troubleshooting often involves querying this table to identify missing or incorrect FE mappings that may cause order fulfillment failures.

Related Objects

The XNP_SV_SMS_FE_MAPS table maintains defined foreign key relationships with two key tables in the EBS architecture, as documented in the provided metadata:

  • XNP_SV_SMS: This is the primary parent table. The relationship is established via the column XNP_SV_SMS_FE_MAPS.SV_SMS_ID, which references XNP_SV_SMS. This links each FE mapping to a specific subscription version record.
  • XDP_FES: This table, from the XDP (Oracle TeleService Dealer Platform) schema, stores the definition of all fulfillment elements. The relationship is through the column XNP_SV_SMS_FE_MAPS.FE_ID, which references XDP_FES.FE_ID. This links the mapping to the actual executable fulfillment component.

These relationships position XNP_SV_SMS_FE_MAPS as a central connector between the Number Portability subscription data (XNP) and the broader Order and Service Management fulfillment infrastructure (XDP).