Search Results fte_sel_attributes_u1

Overview

FTE.FTE_SEL_ATTRIBUTES is a seed data table within the Transportation and Logistics (FTE) schema of Oracle E-Business Suite, holding attribute definitions that describe how selection objects behave within the carrier and freight selection engine. Each row represents a single configurable attribute — for example, a cost field, a service code, or a geographic qualifier — that may be attached to an object defined in FTE_SEL_OBJECTS. By linking attributes to objects, the attribute becomes available for use by that object at runtime. The table resides in the APPS_TS_SEED tablespace with a PCTFREE of 10, confirming its role as relatively static, seeded configuration data delivered with the application.

From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification. The table carries a surrogate primary key (ATTRIBUTE_ID) and descriptive attributes, with a foreign key to FTE_SEL_OBJECTS functioning as a parent reference rather than a pure many-to-many link. This makes it a natural descriptor set for the selection-object hub.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• ATTRIBUTE_ID — the surrogate primary key (FTE_SEL_ATTRIBUTES_PK1), uniquely identifying each attribute definition.
• CODE — a 30-character business code for the attribute; together with OBJECT_ID it forms the unique business key enforced by the FTE_SEL_ATTRIBUTES_U1 index.
• OBJECT_ID — foreign key to FTE_SEL_OBJECTS.OBJECT_ID, establishing which selection object the attribute belongs to.
• NAME — a 240-character descriptive name shown to users.
• DATA_TYPE — the attribute's data type, such as 'N'umber or 'C'haracter, governing validation and display.
• RANGE_FLAG — indicates whether the attribute can be used to express a range of values.
• SELECTION_TYPE — indicates whether the attribute is used for 'I'nput criteria, 'O'utput results, or 'B'oth.
• VISIBLE_FLAG — controls whether the attribute is exposed to end users.
• ENABLED_FLAG — controls whether the attribute is active for use.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording the creation and last modification context.

The distinction between the surrogate key (ATTRIBUTE_ID) and the business key (CODE + OBJECT_ID) is central to maintaining referential integrity across the FTE configuration schema.

Common Use Cases and Queries

Typical usage centers on exposing, auditing, and troubleshooting the attribute configuration available to a given selection object. Reporting queries generally join to FTE_SEL_OBJECTS to resolve the object context:

• Listing all enabled, user-visible attributes for a selection object.
• Identifying input versus output versus dual-purpose attributes for a selection screen configuration review.
• Verifying that a CODE is unique within an OBJECT_ID before introducing a new seeded row.
• Auditing attribute definitions that have been disabled or hidden during implementation.

A representative query pattern is:

SELECT a.ATTRIBUTE_ID, a.CODE, a.NAME, a.DATA_TYPE, a.SELECTION_TYPE, a.RANGE_FLAG, a.VISIBLE_FLAG, a.ENABLED_FLAG FROM FTE.FTE_SEL_ATTRIBUTES a WHERE a.OBJECT_ID = :object_id AND a.ENABLED_FLAG = 'Y' AND a.VISIBLE_FLAG = 'Y';

For a business-key lookup across the unique index, filtering on CODE and OBJECT_ID retrieves a single definition reliably. Auditors may also trace changes via the WHO columns, joining to FND_USER on CREATED_BY or LAST_UPDATED_BY.

Related Objects

The most significant relationships include:

• FTE_SEL_OBJECTS — parent object; joined via FTE_SEL_ATTRIBUTES.OBJECT_ID = FTE_SEL_OBJECTS.OBJECT_ID.
• FTE_SEL_ATTRIBUTES# — the underlying reference listed as a dependent of this table, relevant for API-level operations.

The documented dependency section indicates FTE_SEL_ATTRIBUTES references no other database object beyond the OBJECT_ID foreign key and is referenced by FTE_SEL_ATTRIBUTES#. In practice, the carrier and freight selection engine reads these definitions to construct input and output criteria dynamically, making FTE_SEL_OBJECTS and the selection engine itself the primary consumers of this configuration table. Understanding the CODE/OBJECT_ID uniqueness constraint and the DATA_TYPE semantics is essential when extending or troubleshooting selection behavior.