Results for “fe_name”

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

Overview

The XDP_FE_GENERIC_CONFIG_V view is an APPS-owned database view within the XDP – Provisioning product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It consolidates configuration data relating to current and future software generics associated with fulfillment elements. The view joins fulfillment element definitions, software generic lookups, generic configuration records, and adapter type descriptions into a single reporting surface. It is intended primarily for reporting and integration scenarios in which provisioned service definitions, adapter mappings, and configuration validity windows must be presented in a readable, denormalized form. Because it exposes human-readable display names alongside internal identifiers, it serves as a convenient source for operational dashboards, provisioning audits, and extracts that feed external fulfillment or order management systems.

Underlying Base Objects

The view is defined over four referenced base objects. It draws the fulfillment element identity and naming from XDP_FES_VL, aliased as A. Software generic lookup attributes are supplied by XDP_FE_SW_GEN_LOOKUP_VL (alias B), which contributes the adapter type and software generic display name. The configuration validity window is sourced from XDP_FE_GENERIC_CONFIG (alias C, accessed via synonym), while adapter type display descriptions originate from XDP_ADAPTER_TYPES_VL (alias D). The join is anchored on FE_ID linking the fulfillment element to the generic configuration, FETYPE_ID linking the fulfillment element to the software generic lookup, FE_SW_GEN_LOOKUP_ID linking the generic lookup to the configuration record, and ADAPTER_TYPE linking the generic lookup to the adapter type description. The predicate further restricts results to configurations whose validity period covers the current system date, or which start in the future, ensuring both active and planned generics are surfaced.

Key Columns

• FE_ID — The unique identifier of the fulfillment element, the primary linkage key across the underlying objects.
• FE_NAME — The fulfillment element name as stored on XDP_FES_VL, used as the internal reference.
• FE_NAME_DISPLAY — The user-facing display name of the fulfillment element.
• ADAPTER_TYPE — The internal adapter type code associated with the software generic, sourced from the lookup view.
• ADAPTER_TYPE_DISPLAY — The descriptive, translated display name resolved from XDP_ADAPTER_TYPES_VL; this is the column most frequently searched, as it translates the technical adapter code into a readable label.
• SW_GENERIC_DISPLAY — The display name of the software generic associated with the fulfillment element.
• START_DATE — The effective start date of the generic configuration.
• END_DATE — The effective end date; a null value indicates an open-ended configuration, interpreted by the NVL logic as extending indefinitely.

Common Use Cases and Queries

Typical usage includes verifying which adapter types are currently active per fulfillment element, identifying future-dated configurations scheduled for activation, and extracting display-friendly provisioning data for downstream systems. Because the view already applies the date filter and name resolution, queries remain concise.

To retrieve all current and planned software generics with their adapter descriptions:

• SELECT fe_name_display, adapter_type_display, sw_generic_display, start_date, end_date FROM apps.xdp_fe_generic_config_v;

To isolate configurations using a specific adapter type description:

• SELECT fe_name_display, adapter_type, adapter_type_display FROM apps.xdp_fe_generic_config_v WHERE adapter_type_display = :adapter_display;

To locate future-dated generics, filter on start_date > SYSDATE. These queries are safe for read-only reporting, and effective-dated filtering is already embedded in the view definition, ensuring consistency across reports.