Results for “xdp_fe_attribute_val_vl”

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

Overview

XDP_FE_ATTRIBUTE_VAL_VL is a multilingual (translated) view owned by the APPS schema in Oracle E-Business Suite, part of the XDP – Provisioning product module. Status is VALID in both 12.1.1 and 12.2.2. The view exposes the configuration data that Service Fulfillment Manager (SFM) requires to communicate with a given fulfillment element (FE). A fulfillment element is a logical, named network device or endpoint — for example, a router identified by the logical name ROUTER_NY1 — and each element carries one or more attributes that describe how SFM should reach it. A representative attribute is the IP address, such as 144.126.174.151, stored against that logical FE name. The "_VL" suffix indicates a language view: it joins the base attribute-value table to its translation table and filters rows to the session's language, so display-oriented fields are returned in the user's own language. The view is therefore the primary read interface for FE attribute configuration in reporting, integration extracts, and troubleshooting of provisioning connectivity.

Underlying Base Objects

The documented ETRM metadata lists two referenced base objects, both exposed to the view through APPS synonyms:

• XDP_FE_ATTRIBUTE_VAL — the base (non-translated) table holding the actual attribute values and standard WHO columns.
• XDP_FE_ATTRIBUTE_VAL_TL — the translation table holding language-specific descriptive text (DISPLAY_NAME, DESCRIPTION).

The view text joins these two objects on two keys simultaneously: FE_ATTRIBUTE_ID and FE_GENERIC_CONFIG_ID. This composite join confirms that an attribute value is uniquely scoped within a generic configuration record, not merely by attribute ID alone. The WHERE clause restricts the translation side to T.LANGUAGE = USERENV('LANG'), so each session sees only the row for its current language setting. All base columns are drawn from the non-translated table; only DISPLAY_NAME and DESCRIPTION originate from the translation table.

Key Columns

• ROW_ID — the base table's ROWID, carried through for row identification; useful where an updatable or uniquely addressable handle is required.
• FE_ATTRIBUTE_ID — identifier of the specific attribute definition (for example, the IP-address attribute) belonging to the FE configuration.
• FE_GENERIC_CONFIG_ID — identifier of the generic FE configuration that the attribute value belongs to; together with FE_ATTRIBUTE_ID it forms the logical key of the record.
• FE_ATTRIBUTE_VALUE — the operative configuration datum itself, such as the IP address 144.126.174.151 bound to the logical FE name. This is the column integration and diagnostic queries normally target.
• DISPLAY_NAME and DESCRIPTION — language-specific, user-facing text supplied by the TL table, used for labeling and explanation in reports and UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO audit columns describing row provenance and last modification.

Common Use Cases and Queries

Typical scenarios include auditing the connectivity attributes configured for each fulfillment element, producing extracts that feed external monitoring or inventory systems, and diagnosing provisioning failures where SFM cannot reach a device because an IP address or similar attribute is stale. The following query lists the current language's attribute configuration per generic config:

• SELECT fe_generic_config_id, fe_attribute_id, fe_attribute_value, display_name, description FROM xdp_fe_attribute_val_vl ORDER BY fe_generic_config_id, fe_attribute_id;

To locate all recorded values for a particular IP target, filter on the value column:

• SELECT fe_generic_config_id, fe_attribute_id, display_name FROM xdp_fe_attribute_val_vl WHERE fe_attribute_value = '144.126.174.151';

Because the view resolves the language through USERENV('LANG'), queries automatically return DISPLAY_NAME and DESCRIPTION in the session's language; joining to other XDP generic-configuration views on FE_GENERIC_CONFIG_ID links attribute values back to their owning FE record. As with any "_VL" view, direct DML should be avoided; changes belong to the base table and its translation table.