Search Results fte_sel_result_assignments




Overview
Explore in AI Chat

Overview

FTE_SEL_RESULT_ASSIGNMENTS is a Transportation Execution (FTE) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores the association between selection rules and their corresponding results, providing the mechanism by which multiple results can be assigned to multiple rules. In Oracle Transportation Management and Execution flows, selection rules evaluate shipment, order, or planning data and then trigger one or more downstream results; this table is the persistent mapping that defines which result records fire when a given rule is satisfied. Without this assignment layer, rules and results would exist in isolation and the selection engine would have no instruction set for what outcome to produce.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as a link. This is a modeling suggestion based on its structure: it resolves a many-to-many relationship between two independent entities — FTE_SEL_RULES on one side and FTE_SEL_RESULTS on the other — through a dedicated surrogate key and two foreign keys. The table therefore carries no descriptive master attributes of its own beyond audit columns, which is characteristic of a link (associative) entity rather than a hub or satellite.

Key Information Stored

The table is documented with eight physical columns. The most significant are:

  • RESULT_ASSIGNMENT_ID — The surrogate primary key that uniquely identifies each rule-to-result mapping row. It is enforced by the constraint FTE_SEL_RESULT_ASSIGNMENTS_PK1.
  • RULE_ID — Foreign key to FTE_SEL_RULES. Identifies the selection rule that owns this assignment.
  • RESULT_ID — Foreign key to FTE_SEL_RESULTS. Identifies the result that should be applied when the associated rule is satisfied.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by which application user the assignment row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification, its user, and the login context.

The surrogate primary key (RESULT_ASSIGNMENT_ID) has no business meaning; the business uniqueness is expressed through the combination of RULE_ID and RESULT_ID, which together prevent duplicate mappings between the same rule and the same result. No alternate unique index is separately documented in the metadata, so the composite RULE_ID/RESULT_ID pairing should be treated as the effective business key for query and validation purposes.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include determining which results are attached to a given rule, identifying all rules that share a common result, and auditing recently changed assignments.

  • Results for a specific rule: SELECT r.RULE_ID, s.RESULT_ID FROM FTE_SEL_RESULT_ASSIGNMENTS r, FTE_SEL_RESULTS s WHERE r.RESULT_ID = s.RESULT_ID AND r.RULE_ID = :rule_id;
  • Reverse lookup (rules using a result): filter on RESULT_ID and join to FTE_SEL_RULES.
  • Duplicate-detection query: group by RULE_ID, RESULT_ID having count(*) > 1 to detect orphaned or redundant mappings.
  • Data auditing: order by LAST_UPDATE_DATE descending to review recent configuration changes made by administrators.

Related Objects

The metadata documents two foreign key relationships that anchor this table to its parent entities:

  • FTE_SEL_RULES — joined on FTE_SEL_RESULT_ASSIGNMENTS.RULE_ID = FTE_SEL_RULES.RULE_ID. The rule definition hub.
  • FTE_SEL_RESULTS — joined on FTE_SEL_RESULT_ASSIGNMENTS.RESULT_ID = FTE_SEL_RESULTS.RESULT_ID. The result definition hub.

Because the table is purely associative, most queries against it will require both parent tables to produce human-readable output. In an Oracle EBS 12.2.2 deployment the table resides in the FTE schema and is typically accessed through the Transportation Execution application modules rather than directly by end users. Any deletion of a rule or result should be evaluated against dependent rows in this table to avoid orphaned assignments.