Search Results fte_sel_attributes




Overview
Explore in AI Chat

Overview

FTE_SEL_ATTRIBUTES is a configuration and metadata table within the Oracle E-Business Suite Transportation Execution (FTE) module. It functions as the attribute definition repository for the FTE selection engine, which drives rule-based evaluations such as carrier selection, routing, and constraint matching during transportation planning and execution. Each row in this table defines a single attribute and associates it with a parent object defined in FTE_SEL_OBJECTS. When an attribute is linked to an object — for example, an object representing "Carrier_selection" — that attribute becomes available for use by the selection logic bound to that object.

The table is owned by the FTE schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. Its physical schema comprises 14 columns. Under a heuristic Data Vault classification derived from its foreign key topology, FTE_SEL_ATTRIBUTES is satellite-leaning: it holds descriptive, versioned-style attribute metadata that hangs off the hub-like parent object FTE_SEL_OBJECTS, rather than acting as a pure hub or a many-to-many link table.

Key Information Stored

The table stores attribute definitions and their usage controls. The most significant columns are:

  • ATTRIBUTE_ID — the surrogate primary key, enforced by FTE_SEL_ATTRIBUTES_PK1.
  • OBJECT_ID — foreign key to FTE_SEL_OBJECTS, binding the attribute to its owning selection object such as Carrier_selection.
  • CODE and OBJECT_ID together form the business-key candidate, enforced by the unique index FTE_SEL_ATTRIBUTES_U1. This guarantees that an attribute code is unique within its parent object.
  • NAME — the descriptive display name of the attribute.
  • DATA_TYPE — defines the value domain (for example character, numeric, or date) that the attribute is expected to return.
  • RANGE_FLAG — indicates whether the attribute supports range-based comparisons rather than simple equality.
  • SELECTION_TYPE — classifies how the attribute participates in selection criteria evaluation.
  • VISIBLE_FLAG — controls whether the attribute is exposed in the selection setup user interface.
  • ENABLED_FLAG — controls whether the attribute is active and usable by the selection engine.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit columns recording the creation and maintenance history of each definition.

Common Use Cases and Queries

Typical usage centers on inspecting which attributes are available for a given selection object and verifying their configuration before troubleshooting rule evaluation. A common query joins this table to FTE_SEL_OBJECTS to list attributes for the Carrier_selection object:

  • SELECT a.attribute_id, a.code, a.name, a.data_type, a.enabled_flag FROM fte.fte_sel_attributes a, fte.fte_sel_objects o WHERE a.object_id = o.object_id AND o.code = 'Carrier_selection'

Reporting scenarios include auditing enabled versus disabled attributes, identifying which attributes are hidden from setup users via VISIBLE_FLAG, and confirming DATA_TYPE consistency before extending custom selection rules. Administrators also use CODE and OBJECT_ID lookups to resolve business keys during data migration or comparison between environments.

Related Objects

The following objects are most significant in relation to FTE_SEL_ATTRIBUTES:

  • FTE_SEL_OBJECTS — parent table; referenced through FTE_SEL_ATTRIBUTES.OBJECT_ID (the only documented foreign key), defining the selection object to which attributes belong.
  • FTE_SEL_ATTRIBUTES_PK1 — primary key constraint on ATTRIBUTE_ID, used for direct row identification.
  • FTE_SEL_ATTRIBUTES_U1 — unique index on (CODE, OBJECT_ID), the business-key candidate used to enforce intra-object attribute uniqueness.
  • FTE_SEL_CRITERIA and related FTE selection rule tables — consume attribute definitions when evaluating carrier selection and other selection criteria.
  • FTE_SEL_OBJECTS child objects — selection criteria, rule groups, and evaluation result tables within the FTE selection framework depend indirectly on the attribute registry defined here.