Search Results fte_sel_rules




Overview
Explore in AI Chat

Overview

The FTE_SEL_RULES table is a core configuration object within the Oracle E-Business Suite Transportation Execution (FTE) module, available in both 12.1.1 and 12.2.2. It resides in the FTE schema and stores header-level definitions for selection rules used by the Transportation Execution engine to determine how shipments, trips, or delivery lines are grouped, matched, and assigned during planning and execution processes. Each row represents a single rule, identified by a rule identifier and a user-facing name, while the granular attributes and restrictions that compose the rule are held in the child table FTE_SEL_RULE_RESTRICTIONS.

From a Data Vault modeling perspective, the documented foreign key structure suggests that FTE_SEL_RULES is hub-leaning: its primary key, RULE_ID, is a stable business key referenced by multiple downstream tables, making it a natural candidate for a hub entity. The rule-level descriptive attributes such as precedence, frequency, and validity dates would typically be modeled as a satellite attached to that hub. This classification is heuristic and intended as a modeling suggestion rather than a prescribed design.

Key Information Stored

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

  • RULE_ID – Surrogate primary key, enforced by the FTE_SEL_RULES_PK1 constraint. Uniquely identifies each selection rule.
  • NAME – Business-key candidate, enforced by the unique index FTE_SEL_RULES_U1. Provides the human-readable rule name used in setup and inquiry screens.
  • GROUP_ID – Foreign key to FTE_SEL_GROUPS, associating the rule with a selection group.
  • PRECEDENCE – Determines the order in which competing rules are evaluated.
  • TYPE – Classifies the rule category.
  • FREQUENCY and UOM_CODE – Define the recurrence and unit of measure associated with the rule.
  • START_DATE and END_DATE – Bound the effective period during which the rule is active.
  • SEQUENCE_NUMBER – Supports ordered processing within a group.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Oracle audit columns.

Common Use Cases and Queries

Typical uses include auditing active rule definitions, reporting on rule precedence conflicts, and tracing which selection groups contain how many rules. A representative query joining the rule header to its group is:

  • SELECT r.RULE_ID, r.NAME, g.NAME group_name, r.PRECEDENCE FROM FTE.FTE_SEL_RULES r JOIN FTE.FTE_SEL_GROUPS g ON r.GROUP_ID = g.GROUP_ID WHERE SYSDATE BETWEEN r.START_DATE AND r.END_DATE ORDER BY r.PRECEDENCE;
  • To enumerate restrictions per rule: SELECT r.NAME, rr.* FROM FTE.FTE_SEL_RULES r JOIN FTE.FTE_SEL_RULE_RESTRICTIONS rr ON r.RULE_ID = rr.RULE_ID;
  • Historical reporting can leverage the audit columns to identify recently modified rules.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

  • FTE_SEL_GROUPS – Parent group referenced via FTE_SEL_RULES.GROUP_ID.
  • FTE_SEL_RULE_RESTRICTIONS – Child table holding the attribute-level restrictions, joined on RULE_ID.
  • FTE_SEL_RESULT_ASSIGNMENTS – References rules via RULE_ID to record assignment results.

These dependencies confirm FTE_SEL_RULES as the central header entity in the rule-selection hierarchy, bridging groups to their detailed restrictions and assignment outcomes.