Search Results fte_load_schedules




Overview
Explore in AI Chat

Overview

The FTE_LOAD_SCHEDULES table is a core data object within the Oracle E-Business Suite Transportation Execution (FTE) module. It serves as the central repository for storing and managing the scheduling information associated with a shipment. In the context of transportation planning and execution, a load schedule defines the specific timing and logistical plan for moving freight, linking a shipment to a carrier's service schedule and a transportation lane. Its primary role is to maintain the relationship between a shipment, its planned carrier, the applicable lane, and the specific service schedule, forming a critical link in the shipment lifecycle from planning through to freight settlement.

Key Information Stored

While the provided metadata does not list all columns, the foreign key relationships and primary key define its essential structure. The table's unique identifier is the LOAD_SCHEDULE_ID. Crucially, it stores foreign keys that connect the schedule to other fundamental entities in the transportation model. The LANE_ID links to the FTE_LANES table, defining the origin, destination, and route. The CARRIER_ID references HZ_PARTIES, identifying the transporting business entity. The ORIGINAL_SCHEDULE_ID points to the FTE_SCHEDULES table, which holds the detailed timing information such as departure and arrival dates and times for the carrier's service. This structure allows a single shipment to be associated with a concrete plan detailing who is moving it, along which path, and at what time.

Common Use Cases and Queries

This table is pivotal for reporting and operational inquiries related to shipment planning and carrier performance. A common use case is generating a shipment schedule report for a logistics coordinator. A typical query would join FTE_LOAD_SCHEDULES to shipment header tables (like FTE_SHIPMENTS) and the related dimension tables to list all planned shipments for a carrier within a date range. Another critical use case is supporting the freight settlement process, where charges (FTE_LOAD_CHARGES) and payment details (FTE_PA_SHIP_DETAILS) are tied to the specific load schedule. Analysts may also query it to analyze lane utilization by joining to FTE_LANES and aggregating data by LOAD_SCHEDULE_ID. A foundational sample SQL pattern is: SELECT fls.load_schedule_id, fls.carrier_id, hp.party_name, fl.lane_number FROM fte_load_schedules fls, hz_parties hp, fte_lanes fl WHERE fls.carrier_id = hp.party_id AND fls.lane_id = fl.lane_id;

Related Objects

The FTE_LOAD_SCHEDULES table is a central hub within the FTE schema, with several key dependencies as shown by its foreign keys. It is a child of FTE_SCHEDULES, FTE_LANES, and HZ_PARTIES. More significantly, it is a parent table to multiple transactional and settlement entities. The FTE_LOAD_CHARGES table stores freight costs assessed against a specific load schedule. The FTE_LOAD_HISTORY table tracks changes to the schedule. For settlement, FTE_PA_SHIP_DETAILS links payable shipment details to this schedule. Additionally, FTE_LOAD_PRC_ATTRIBUTES likely holds pricing attributes associated with the schedule. This network of relationships underscores the table's importance in connecting shipment planning data to financial and operational execution records.