Results for “xdp_fes_vl”

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

Overview

The XDP_FES_VL view is a multi-language (ML) view owned by the APPS schema within the XDP – Provisioning product module. It exposes the master definitions of Fulfillment Elements (FEs), also referred to as Network Elements (NEs). As documented, this data "contains the definition of a fulfillment element," with representative examples including a DMS200 switch, a Cisco CPC, or an HA Server. In the Oracle EBS 12.1.1 and 12.2.2 environments, the object is reported with a status of VALID.

The "_VL" suffix denotes a view that joins a base entity table to its translation table to surface both the installation-independent attributes and the language-specific display text. Because XDP_FES_VL presents the translated display name and description alongside the core technical attributes, it is the canonical read-only interface used by provisioning reports, concurrent programs, and integrations that need human-readable fulfillment element names. Direct use of this view insulates downstream logic from the underlying translation join and the language determination handled inside the view definition.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

• XDP_FES — the base fulfillment element table holding the language-independent attributes, aliased as B in the view text.
• XDP_FES_TL — the translation table holding language-specific text, aliased as T.

The join is performed on B.FE_ID = T.FE_ID, combined with a language filter of T.LANGUAGE = USERENV('LANG'). This restricts returned translation rows to the session's current language, ensuring each fulfillment element appears once with the correct localized text. The view also exposes B.ROWID as ROW_ID, providing a pseudo-key for the base row.

Key Columns

The view exposes the following columns, drawn from both base objects:

• ROW_ID — the ROWID of the underlying XDP_FES record.
• FE_ID — primary identifier of the fulfillment element.
• FETYPE_ID — foreign key indicating the fulfillment element type.
• FULFILLMENT_ELEMENT_NAME — the internal name of the element.
• MAX_CONNECTION / MIN_CONNECTION — connection capacity bounds for the element.
• SESSION_CONTROLLER_ID — associated session controller reference.
• VALID_DATE / INVALID_DATE — effective dating range for the element definition.
• GEO_AREA_ID — geographic area to which the element belongs.
• ROLE_NAME — the role assigned to the fulfillment element.
• NETWORK_UNIT_ID — reference to the associated network unit.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• DISPLAY_NAME, DESCRIPTION — language-specific text from XDP_FES_TL.

Common Use Cases and Queries

Typical scenarios include listing all fulfillment elements for reporting, validating that effective-dated definitions are active on a given date, and joining to type or geography lookups by FETYPE_ID or GEO_AREA_ID.

List all current fulfillment elements:

SELECT fe_id, fulfillment_element_name, display_name,
       fettype_id, valid_date, invalid_date
FROM   apps.xdp_fes_vl
ORDER BY fulfillment_element_name;

Retrieve only elements effective as of the current date:

SELECT fe_id, display_name, max_connection, min_connection
FROM   apps.xdp_fes_vl
WHERE  SYSDATE BETWEEN NVL(valid_date, SYSDATE)
                   AND NVL(invalid_date, SYSDATE);

Search by localized name pattern:

SELECT fe_id, fulfillment_element_name, display_name, description
FROM   apps.xdp_fes_vl
WHERE  UPPER(display_name) LIKE UPPER('%CISCO%');

Because the view applies the language filter internally, no additional translation join is required in these queries.