Search Results schedules_id

Overview

The FTE_SCHEDULES table is a core data object within the Oracle Transportation Execution (FTE) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the primary catalog entity for storing and managing transportation schedules. Each record in this table represents a defined schedule for a specific transportation lane, which is a critical component for planning and executing freight movements. The table's role is to serve as the master repository for schedule information, enabling the system to match shipment requirements with carrier availability and service patterns based on predefined lanes.

Key Information Stored

As the main catalog entity, the FTE_SCHEDULES table contains columns that define the characteristics and operational parameters of a transportation schedule. The primary key for the table is the SCHEDULES_ID column, which uniquely identifies each schedule record. A critical foreign key is the LANE_ID column, which links each schedule to its corresponding transportation lane defined in the FTE_LANES table. This relationship anchors the schedule to a specific origin and destination pair. While the provided metadata does not list all columns, typical data stored would include schedule frequency (e.g., daily, weekly), effective dates, transit time, carrier information, mode of transport, and status indicators to control schedule availability and usage within the planning engine.

Common Use Cases and Queries

This table is central to transportation planning and execution processes. A common use case is during the shipment planning phase, where the system queries FTE_SCHEDULES to find available schedules that match the lane, date, and service requirements of a shipment. For reporting, analysts query this table to analyze schedule adherence, carrier performance, and lane coverage. A fundamental query pattern involves joining FTE_SCHEDULES with FTE_LANES to retrieve a comprehensive list of all active schedules with their associated origin and destination details.

SELECT s.schedules_id, s.lane_id, l.origin_location_id, l.destination_location_id,
       s.frequency, s.effective_start_date, s.effective_end_date
FROM fte.fte_schedules s,
     fte.fte_lanes l
WHERE s.lane_id = l.lane_id
AND SYSDATE BETWEEN s.effective_start_date AND NVL(s.effective_end_date, SYSDATE)
AND s.status = 'ACTIVE';

Another critical use case is tracing the lifecycle of a schedule, as the FTE_LOAD_SCHEDULES table references the ORIGINAL_SCHEDULE_ID back to this table, allowing users to track which specific schedule was used for a particular freight load.

Related Objects

The FTE_SCHEDULES table has defined relationships with several other key EBS objects within the FTE schema. Its primary relationship is with the FTE_LANES table via the LANE_ID foreign key, which is essential for understanding the geographic context of the schedule. Furthermore, it is referenced by the FTE_LOAD_SCHEDULES table through the ORIGINAL_SCHEDULE_ID foreign key. This link is vital for execution, as it connects the master schedule catalog to the actual instantiated loads or trips created during shipment planning. Consequently, any data integrity or purge operations on FTE_SCHEDULES must carefully consider these dependent child records in FTE_LOAD_SCHEDULES to maintain referential integrity within the transportation execution system.