Results for “xnp_prov_status”

10 results




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

Overview

APPS.XNP_SV_FE_MAPP_DETAILS_VL is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment. It resides in the APPS schema and belongs to the Service Fulfillment Management / order capture feature layer associated with the XNP application family. The view consolidates the mapping between service features (SMS feature mappings) and their corresponding fulfillment elements, enriched with translated display names and decoded provisioning statuses.

The object functions as a denormalized presentation layer. Rather than requiring callers to join the feature mapping table to the fulfillment element definitions, the bilingual translation table, the feature type table, and the lookup repository independently, this view performs all joins internally and exposes a single flat result set. This makes it particularly suited to concurrent program reports, OAF-based UI regions, and outbound integration extracts where a stable, human-readable projection of fulfillment configuration is required.

The "_VL" suffix indicates that the view is intended to return language-sensitive (translated) values, sourcing display text through the user's session language.

Underlying Base Objects

The view is defined exclusively over synonyms that resolve to base tables in the XNP and XDP schemas, plus the standard lookup repository:

All five synonyms are documented as referenced objects; the view performs inner joins across them, so a row appears only when a matching active, language-specific translation and a valid lookup entry exist.

Key Columns

  • SV_SMS_ID — identifier from XNP_SV_SMS_FE_MAPS tying the mapping to its service/subscription context.
  • FEATURE_TYPE — the feature classification carried on the mapping record.
  • PROVISION_STATUS — the lookup code representing the provisioning state of the fulfillment element.
  • MEANING — the decoded, translatable description of PROVISION_STATUS obtained from FND_LOOKUP_VALUES.
  • FULFILLMENT_ELEMENT_NAME — the internal/business name of the fulfillment element, from XDP_FES.
  • DISPLAY_NAME — the language-specific translated name from XDP_FES_TL, constrained by USERENV('LANG').
  • FULFILLMENT_ELEMENT_TYPE — the element type descriptor from XDP_FE_TYPES.

Common Use Cases and Queries

Typical usage centers on reporting the provisioning state of fulfillment elements per service mapping, or driving integration extracts that must emit the customer-facing display name. Because translation is applied via USERENV('LANG'), the view respects the caller's language session.

Retrieve all mappings for a given service ID:

  • SELECT sv_sms_id, feature_type, fulfillment_element_name, display_name, fulfillment_element_type, meaning FROM apps.xnp_sv_fe_mapp_details_vl WHERE sv_sms_id = :p_sv_sms_id;

Report configuration by provisioning status:

  • SELECT meaning, fulfillment_element_type, COUNT(*) FROM apps.xnp_sv_fe_mapp_details_vl GROUP BY meaning, fulfillment_element_type;

Because the view limits FES_TL.LANGUAGE to the session language, callers requiring all languages must query XDP_FES_TL directly. The join to FND_LOOKUP_VALUES is also unfiltered by view or enabled flag, so results depend on the contents of the XNP_PROV_STATUS lookup type.