Search Results fte_lane_groups_pk

Overview

The FTE_LANE_GROUPS table is a core data object within the Oracle E-Business Suite (EBS) Transportation Execution (FTE) module. It functions as a master table for defining and storing header-level information for logical collections of transportation lanes. A lane group is a critical configuration entity that allows users to aggregate individual shipping lanes (defined from a source location to a destination location) into a single, manageable unit. This grouping is essential for streamlining complex transportation planning, rate management, and carrier assignment processes by applying rules, constraints, or analyses to multiple lanes simultaneously, rather than individually. Its role is foundational to the FTE engine's ability to optimize freight movements and execute transportation plans efficiently.

Key Information Stored

While the provided ETRM excerpt specifies the primary key, the table's purpose indicates it stores metadata that defines the lane group entity. Based on standard FTE table structures and the documented primary key, the central columns include:

• LANE_GROUP_ID: The unique primary key identifier (PK) for the lane group record. This is a system-generated sequence number used to uniquely reference the group throughout the FTE application.
• NAME and DESCRIPTION: Columns to hold the user-defined name and a descriptive explanation of the lane group's purpose or the lanes it contains.
• ENABLED_FLAG: A standard indicator (commonly 'Y' or 'N') specifying whether the lane group is active and available for use in transportation planning and execution.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard EBS audit columns tracking the record's origin and modification history.

Common Use Cases and Queries

This table is primarily accessed for configuration, reporting, and data validation. A common use case is generating a list of all active lane groups for a transportation planner to select from when building a freight plan. Another scenario involves querying to validate lane group setup or to troubleshoot planning issues where a specific group of lanes is not behaving as expected. Sample SQL patterns include fetching basic header information and joining to child tables to see member lanes.

Sample Query: Retrieving active lane groups. SELECT lane_group_id, name, description
FROM fte.fte_lane_groups
WHERE enabled_flag = 'Y'
ORDER BY name;

Reporting Use Case: A report showing the count of active lanes within each lane group would typically involve joining FTE_LANE_GROUPS to its child detail table (e.g., FTE_LANE_GROUP_LANES) and aggregating the data.

Related Objects

The FTE_LANE_GROUPS table sits at the top of a hierarchy. The documented primary key, FTE_LANE_GROUPS_PK on LANE_GROUP_ID, is referenced by foreign keys in related detail tables. Key related objects include:

• FTE_LANE_GROUP_LANES: This is the primary child detail table. It contains the individual lane records (FTE_LANES) that are members of a given lane group. It will have a foreign key column, LANE_GROUP_ID, referencing FTE_LANE_GROUPS.LANE_GROUP_ID.
• FTE_LANES: While not a direct child, lanes are associated with a group via the FTE_LANE_GROUP_LANES intersection table.
• Various FTE planning and engine tables: Other transactional and setup tables within the FTE module likely reference the LANE_GROUP_ID to apply rules or record decisions made for a specific group of lanes.