Results for “xnp_sv_sms_fe_maps”

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

Overview

XNP_SV_SMS_FE_MAPS is a transaction table in the XNP (Number Portability) module of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the list of fulfillment elements (FEs) that have been provisioned with subscription version data during a number portability or subscription-version processing cycle. In functional terms, it is the mapping bridge between an XNP subscription-version SMS record and the downstream fulfillment element that must be activated, updated, or deactivated on the network.

The table sits at the intersection of subscription-version management (XNP_SV_SMS) and the generalized fulfillment-element catalog (XDP_FES). Each row answers the question: for this subscription-version SMS entry, which fulfillment element was provisioned, and what type of feature does that element represent? The metadata also records a provisioning status, so the row doubles as a lightweight state tracker for fulfillment-element provisioning.

From a data-modeling perspective, the mined foreign-key structure suggests this object behaves as a link in Data Vault terms: it connects two business entities (subscription-version SMS and fulfillment element) and carries a small number of descriptive attributes (feature type, provisioning status) alongside its own surrogate identifier. It should not be treated as a hub or as a standalone satellite.

Key Information Stored

The documented physical schema for 12.2.2 contains eleven columns. The most significant are:

• SMS_FE_MAP_ID — the surrogate primary key, defined by the XNP_SV_SMS_FE_MAPS_PK constraint and also carried by unique index U1. It uniquely identifies each provisioning mapping.
• SV_SMS_ID — foreign key to XNP_SV_SMS, identifying the subscription-version SMS record being provisioned.
• FE_ID — foreign key to XDP_FES, identifying the specific fulfillment element provisioned.
• FEATURE_TYPE — classifies the feature or capability that the fulfillment element implements for this mapping. Together with SV_SMS_ID and FE_ID, it forms the business-key candidate captured by unique index U2 (XNP_SV_SMS_FE_MAPS_U2).
• PROVISION_STATUS — indicates the provisioning state of the fulfillment element for this subscription-version SMS record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / security-group data access.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit and concurrency information.

The distinction between the surrogate (SMS_FE_MAP_ID) and the natural key (SV_SMS_ID, FEATURE_TYPE, FE_ID) is important: integrations should resolve mappings by the business key, while internal joins and updates typically use the surrogate.

Common Use Cases and Queries

Typical usage centres on provisioning reconciliation and troubleshooting portability fulfillment. A frequent query joins the mapping table to the fulfillment-element catalog to describe provisioned elements for a subscription version:

• Retrieve all fulfillment elements provisioned for a given SV_SMS_ID, filtered by PROVISION_STATUS or FEATURE_TYPE.
• Report mappings that reference an FE_ID in XDP_FES but remain in a non-final provisioning state.
• Audit which features were provisioned for a port request by joining XNP_SV_SMS_FE_MAPS to XNP_SV_SMS and onward to the subscription-version header.
• Detect duplicate or ambiguous mappings via the U2 business key (SV_SMS_ID, FEATURE_TYPE, FE_ID).

A representative pattern is SELECT m.SMS_FE_MAP_ID, m.SV_SMS_ID, m.FE_ID, m.FEATURE_TYPE, m.PROVISION_STATUS FROM XNP.XNP_SV_SMS_FE_MAPS m WHERE m.SV_SMS_ID = :sv_sms_id, optionally joined to XDP_FES for element names. Security-group-aware extracts should always include SECURITY_GROUP_ID in the predicate.

Related Objects

• XNP_SV_SMS — parent in the relationship; joined via XNP_SV_SMS_FE_MAPS.SV_SMS_ID.
• XDP_FES — fulfillment-element catalog; joined via XNP_SV_SMS_FE_MAPS.FE_ID.
• FND_SECURITY_GROUPS — joined via XNP_SV_SMS_FE_MAPS.SECURITY_GROUP_ID for access control.
• XNP_SV_SMS_FE_MAPS_PK / _U1 / _U2 — primary and unique constraints enforcing identity and business-key integrity.

Because the surrounding API surface is not enumerated in the ETRM metadata, provisioning and portability processes should be assumed to maintain these rows indirectly through the XNP subscription-version and fulfillment interfaces rather than through direct DML.