Results for “fte_sel_objects”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FTE_SEL_OBJECTS is a table in the FTE (Transportation Execution) product schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It functions as a registry of object definitions that participate in the rule-based selection framework used by Transportation Execution. Each row defines a logical "selection object," such as carrier_selection, which enables the rule-based retrieval of information for a specific selection purpose. In practical terms, this table identifies the categories of things that can be selected through the engine, and it anchors the attributes and grouping metadata that drive those selections.

Heuristically, the FK structure classifies FTE_SEL_OBJECTS as hub-leaning in a Data Vault model. It holds the core business entity (the selection object) with a surrogate key and a natural business key, while dependent attribute and group tables reference it as satellites and links. This is a modeling suggestion only; the physical schema is a conventional 3NF normalized Oracle table owned by FTE with eight columns and status VALID.

Key Information Stored

The table is compact, comprising eight documented columns. The most important are:

• OBJECT_ID — the surrogate primary key, enforced by constraint/index FTE_SEL_OBJECTS_PK1. It uniquely identifies each selection object and is the column referenced by all dependent FK tables.
• NAME — the business-key candidate, protected by unique index FTE_SEL_OBJECTS_U1. This value is the human-readable identifier of the selection object, e.g. carrier_selection, and is the value most often supplied in configuration and lookup queries.
• DESCRIPTION — a textual explanation of the object's purpose, aiding administrators who must map a name to a business function.
• CREATION_DATE, CREATED_BY — audit columns recording when and by whom the object definition was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the login under which it occurred.

The separation of the surrogate key (OBJECT_ID) from the unique business key (NAME) is significant: downstream tables persist OBJECT_ID rather than the descriptive name, so renaming an object's NAME does not break referential integrity, while the unique index prevents duplicate object definitions.

Common Use Cases and Queries

Typical usage centers on resolving a selection object's identity and joining it to its attributes and groups. A common lookup resolves a known business name to its surrogate key:

• SELECT object_id, name, description FROM fte.fte_sel_objects WHERE name = 'carrier_selection';
• Enumerating all defined selection objects: SELECT object_id, name, description FROM fte.fte_sel_objects ORDER BY name;
• Joining to attributes for a full selection definition: SELECT o.name, a.attribute_name FROM fte.fte_sel_objects o, fte.fte_sel_attributes a WHERE a.object_id = o.object_id;
• Joining to groups: SELECT o.name, g.group_name FROM fte.fte_sel_objects o, fte.fte_sel_groups g WHERE g.object_id = o.object_id;

Reporting scenarios include auditing which selection objects are configured in a given environment, verifying that the expected objects (for example, carrier selection) exist after a patch or upgrade, and diagnosing selection failures caused by missing or misnamed object definitions. Because only NAME and DESCRIPTION are descriptive, most reports join to the dependent tables to render meaningful output.

Related Objects

Referential relationships are well-defined through foreign keys that point back to the OBJECT_ID primary key:

• FTE_SEL_ATTRIBUTES — references FTE_SEL_OBJECTS via FTE_SEL_ATTRIBUTES.OBJECT_ID. Stores the attributes that belong to each selection object.
• FTE_SEL_GROUPS — references FTE_SEL_OBJECTS via FTE_SEL_GROUPS.OBJECT_ID. Stores grouping definitions associated with each selection object.

These two dependent tables are the primary consumers of the hub. Together with FTE_SEL_OBJECTS they form the structural backbone of the Transportation Execution selection framework, where OBJECT_ID is the common join column linking object definitions to their attributes and groups. Administrators and support analysts should treat FTE_SEL_OBJECTS as the master reference for selection-object identity, using OBJECT_ID for joins and NAME for user-facing lookup and validation.