Results for “fe_attribute_name”

34 results




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

Overview

XDP_FE_ATTRIBUTE_DEF is the Fulfillment Element Attribute Definition table in the XDP (Provisioning) product module of Oracle E-Business Suite. It resides in the XDP schema, is marked VALID, and functions as the master definition repository for attributes that describe fulfillment elements within the provisioning model. In a typical fulfillment flow, a fulfillment element represents a configurable provisioning or service capability, and each element carries a set of named attributes—for example, connection parameters, identifiers, or display characteristics. XDP_FE_ATTRIBUTE_DEF stores those attribute definitions, providing the metadata layer that downstream provisioning engines and value tables reference.

From a data-vault modeling perspective, the metadata classifies this object as hub-leaning. This is a heuristic suggestion: the table behaves as a hub because it holds a stable, unique business identifier (the attribute definition) and is anchored by surrogate identity via FE_ATTRIBUTE_ID. It does not carry link semantics by itself; relationships to software generation lookups, security groups, translations, and attribute values are represented through separate keys and dependent tables rather than a single associative structure.

Key Information Stored

The table is documented with 13 columns. The most important are:

Two unique indexes define business-key candidates. XDP_FE_ATTRIBUTE_DEF_U1 covers (FE_ATTRIBUTE_ID, ZD_EDITION_NAME), while XDP_FE_ATTRIBUTE_DEF_U2 covers (FE_SW_GEN_LOOKUP_ID, FE_ATTRIBUTE_NAME, ZD_EDITION_NAME). The user's search term, xdp_fe_attribute_def_uk1, corresponds to the earlier unique key naming convention whose role is now reflected by U2: it enforces uniqueness of attribute names per software generation lookup. The surrogate primary key is therefore FE_ATTRIBUTE_ID, whereas the natural business identifier is the combination of lookup and attribute name.

Common Use Cases and Queries

Typical scenarios include retrieving the attributes defined for a given software generation lookup, ordering them for display, and identifying concealed attributes before exposing configuration screens.

A common query lists attribute definitions for a lookup:

  • SELECT fe_attribute_id, fe_attribute_name, default_value, display_seq FROM xdp_fe_attribute_def WHERE fe_sw_gen_lookup_id = :lookup_id ORDER BY display_seq;

Administrators may inspect concealed attributes:

  • SELECT fe_attribute_name FROM xdp_fe_attribute_def WHERE conceal_data = 'Y' AND fe_sw_gen_lookup_id = :lookup_id;

Reporting use cases include extracting attribute metadata for provisioning configuration audits, validating that every attribute has a corresponding value in XDP_FE_ATTRIBUTE_VAL, and generating translation extracts from the TL table. Joining to XDP_FE_SW_GEN_LOOKUP yields the lookup context, while joining to FND_SECURITY_GROUPS supports security-scoped reporting.

Related Objects

  • XDP_FE_SW_GEN_LOOKUP — referenced by XDP_FE_ATTRIBUTE_DEF.FE_SW_GEN_LOOKUP_ID; provides the software generation lookup context.
  • XDP_FE_ATTRIBUTE_DEF_TL — translation table referencing XDP_FE_ATTRIBUTE_DEF.FE_ATTRIBUTE_ID; stores language-specific attribute text.
  • XDP_FE_ATTRIBUTE_VAL — child table referencing XDP_FE_ATTRIBUTE_DEF.FE_ATTRIBUTE_ID; holds actual attribute values.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; enforces data security.

In the 12.2.2 schema, the editioning column ZD_EDITION_NAME places this table within the online patching framework, and joins across the related tables should account for edition-aware filtering where applicable.