Search Results fte_sel_result_attributes




Overview
Explore in AI Chat

Overview

FTE_SEL_RESULT_ATTRIBUTES is a table within the FTE (Transportation Execution) schema in Oracle E-Business Suite, and it belongs to the Transportation Execution module. As its name implies, the table stores attribute definitions and their corresponding values for specific results produced by the selection engine. Each result attribute must be assigned to a result, meaning the table functions as an extension of the parent result entity, capturing qualifying details that describe or annotate a given result instance. In the EBS 12.1.1 and 12.2.2 releases the object is reported as VALID and owned by the FTE schema.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as a satellite-leaning table. It is anchored to its parent via the RESULT_ID foreign key referencing FTE_SEL_RESULTS, and it carries descriptive, non-key attributes rather than defining business relationships of its own. This reinforces its role as a dependent detail table rather than a hub or link.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

  • RESULT_ATTRIBUTE_ID — the surrogate primary key that uniquely identifies each attribute row. It is enforced through the primary key constraint FTE_SEL_RESULT_ATTRIBUTES_PK1.
  • RESULT_ID — the foreign key to FTE_SEL_RESULTS, indicating the parent result to which the attribute belongs. This column is the principal business-key candidate that links the row back to its owning result.
  • ATTRIBUTE_CODE — the code that identifies which attribute is being recorded for the result.
  • ATTRIBUTE_VALUE — the value assigned to that attribute for the specific result.
  • CREATION_DATE, CREATED_BY — standard audit columns capturing when and by whom the row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the session that performed it.

The combination of RESULT_ID and ATTRIBUTE_CODE effectively differentiates attribute instances for a given result, while RESULT_ATTRIBUTE_ID provides the internal surrogate identity.

Common Use Cases and Queries

Typical use cases involve retrieving all attributes for a specific selection result, reporting on attribute values across results, and joining the attribute detail back to the parent result for a complete view of selection output. A representative query pattern joins the two tables on RESULT_ID:

  • SELECT a.RESULT_ATTRIBUTE_ID, a.RESULT_ID, a.ATTRIBUTE_CODE, a.ATTRIBUTE_VALUE FROM FTE.FTE_SEL_RESULT_ATTRIBUTES a WHERE a.RESULT_ID = :result_id;
  • SELECT r.RESULT_ID, a.ATTRIBUTE_CODE, a.ATTRIBUTE_VALUE FROM FTE.FTE_SEL_RESULTS r JOIN FTE.FTE_SEL_RESULT_ATTRIBUTES a ON r.RESULT_ID = a.RESULT_ID WHERE a.ATTRIBUTE_CODE = :code;

These patterns support auditing which attributes were assigned to a result, comparing attribute values across multiple results, and building operational reports on selection outcomes.

Related Objects

The most significant related object is the parent table referenced by the documented foreign key:

  • FTE_SEL_RESULTS — joined via FTE_SEL_RESULT_ATTRIBUTES.RESULT_ID = FTE_SEL_RESULTS.RESULT_ID. This is the primary dependent relationship and the anchor for all attribute rows.

Because metadata beyond the single documented foreign key and primary key is limited, additional related tables in the FTE selection family (such as result headers and selection criteria objects) may reference results, but only FTE_SEL_RESULTS is confirmed in the documentation as a direct relationship. Any query joining to other FTE selection tables should be validated against the actual deployment schema before relying on it.