Results for “fulfillment_element_name”

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

Overview

The view XNP_SV_FE_MAPP_DETAILS_VL is an Oracle E-Business Suite database object owned by the APPS schema within the XNP - Number Portability product. It presents subscription version data that has been provisioned onto a fulfillment element, joining the internal service management mapping records to the fulfillment element definitions and their translated display names. The "VL" suffix indicates that the view incorporates a language-sensitive translation join, returning the display name that matches the session's language environment.

In EBS 12.1.1 and 12.2.2, Number Portability operations depend on mapping subscription versions to the network elements that fulfill them. This view consolidates that relationship into a single reporting-friendly structure, exposing the provisioning status, its decoded meaning, the fulfillment element identity, and the element type. It serves as a read-only reporting and integration surface, allowing concurrent programs, OAF pages, and custom SQL reports to retrieve provisioning details without navigating the underlying normalized tables directly.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

• XNP_SV_SMS_FE_MAPS — the driving subscription version to fulfillment element mapping table, supplying SV_SMS_ID, FEATURE_TYPE, and PROVISION_STATUS.
• XDP_FES — the fulfillment element master, providing the element name and the link to its type definition.
• XDP_FES_TL — the language-translated table for fulfillment elements, filtered by FES_TL.LANGUAGE = USERENV('LANG').
• XDP_FE_TYPES — the fulfillment element type definition, supplying FULFILLMENT_ELEMENT_TYPE.
• FND_LOOKUP_VALUES — restricted to LOOKUP_TYPE = 'XNP_PROV_STATUS', decoding the provisioning status code into its meaning.

The joins are enforced on FE_ID between the mapping table and XDP_FES, between XDP_FES and XDP_FES_TL, and on FETYPE_ID between XDP_FES and XDP_FE_TYPES. The lookup join matches PROVISION_STATUS to LOOKUP_CODE.

Key Columns

• SV_SMS_ID — identifier linking the record to the subscription version service mapping.
• FEATURE_TYPE — the feature type associated with the provisioned mapping.
• PROVISION_STATUS — the internal status code for provisioning.
• PROVISION_STATUS_MEANING — the decoded meaning of the status from FND_LOOKUP_VALUES.
• FULFILLMENT_ELEMENT_NAME — the name of the fulfillment element from XDP_FES.
• DISPLAY_NAME — the language-specific translated display name from XDP_FES_TL.
• FULFILLMENT_ELEMENT_TYPE — the element type from XDP_FE_TYPES.

Common Use Cases and Queries

Typical scenarios include auditing provisioning status across fulfillment elements, building language-aware reports of element display names, and diagnosing mappings tied to a specific subscription version. The following query lists provisioned mappings and their decoded status:

SELECT sv_sms_id,
       feature_type,
       fulfillment_element_name,
       display_name,
       fulfillment_element_type,
       provision_status_meaning
FROM   apps.xnp_sv_fe_mapp_details_vl
WHERE  provision_status_meaning = 'Provisioned';

To isolate all elements for a given subscription version mapping:

SELECT fulfillment_element_name,
       display_name,
       fulfillment_element_type,
       provision_status_meaning
FROM   apps.xnp_sv_fe_mapp_details_vl
WHERE  sv_sms_id = :p_sv_sms_id;

Because the translation join is filtered by USERENV('LANG'), results returned reflect the display language of the executing session, making the view suitable for concurrent programs and self-service pages that must respect the logged-in user's language preference.