Results for “fte_load_schedules”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FTE_LOAD_SCHEDULES is a Transportation Execution (FTE) table that stores the schedules associated with a shipment. In the Oracle EBS 12.1.1 and 12.2.2 data model, it functions as the operational intersection between scheduled transportation services, the lanes over which those services run, and the carriers who provide them. Each row represents a load schedule — an instance of a shipment tied to a schedule, lane, and carrier — and carries the header-level attributes and cost/rating references that downstream charge, history, price attribute, and shipment detail records depend upon.
The heuristic Data Vault classification for this table is hub-leaning. It holds a stable, uniquely identified business entity (LOAD_SCHEDULE_ID) and serves as the anchor from which several dependent (satellite-like) tables branch. From a modelling perspective, it behaves as a hub with additional descriptive carrier, lane, and original-schedule references that could be provisioned as link relationships rather than attributes in a normalized vault design.
Key Information Stored
The documented primary key is FTE_LOAD_SCHEDULES_PK, defined on the LOAD_SCHEDULE_ID column. LOAD_SCHEDULE_ID is the surrogate primary key and is the value carried by every child table that references a load schedule.
Business-key candidates are represented by the inbound foreign key columns, which reference other master and transactional objects rather than local unique constraints:
- ORIGINAL_SCHEDULE_ID — references FTE_SCHEDULES; identifies the originating schedule from which the load schedule was derived.
- LANE_ID — references FTE_LANES; identifies the transportation lane associated with the schedule.
- CARRIER_ID — references HZ_PARTIES; identifies the carrier party performing the movement.
- LOAD_SCHEDULE_ID — the primary key column and the join key propagated to all child tables.
Additional descriptive columns (such as schedule dates, status, and cost attributes) are held on the table but are not enumerated in the documented metadata; implementers should confirm these against the actual data dictionary for the target release.
Common Use Cases and Queries
Typical reporting and integration scenarios include reconciling load schedules to their charges, tracking shipment execution history, and analyzing carrier and lane utilization. A representative join pattern follows:
- Header-to-charge roll-up: join FTE_LOAD_SCHEDULES to FTE_LOAD_CHARGES on LOAD_SCHEDULE_ID to total accessorial and freight charges per load schedule.
- Carrier spend analysis: join to HZ_PARTIES on CARRIER_ID to aggregate charges by carrier party.
- Lane performance reporting: join to FTE_LANES on LANE_ID to compare scheduled versus actual movement by lane.
- Schedule provenance: join to FTE_SCHEDULES on ORIGINAL_SCHEDULE_ID to trace a load schedule back to its defining schedule.
- Shipment detail expansion: join to FTE_PA_SHIP_DETAILS on LOAD_SCHEDULE_ID for line-level shipment visibility.
A common query shell is: SELECT ls.load_schedule_id, ls.carrier_id, ls.lane_id, c.* FROM fte_load_schedules ls, fte_load_charges c WHERE ls.load_schedule_id = c.load_schedule_id;
Related Objects
The following tables reference or are referenced by FTE_LOAD_SCHEDULES through documented foreign keys:
- FTE_SCHEDULES — referenced by FTE_LOAD_SCHEDULES.ORIGINAL_SCHEDULE_ID; parent schedule definition.
- FTE_LANES — referenced by FTE_LOAD_SCHEDULES.LANE_ID; transportation lane master.
- HZ_PARTIES — referenced by FTE_LOAD_SCHEDULES.CARRIER_ID; carrier party.
- FTE_LOAD_CHARGES — references FTE_LOAD_SCHEDULES.LOAD_SCHEDULE_ID; child charge lines.
- FTE_LOAD_HISTORY — references FTE_LOAD_SCHEDULES.LOAD_SCHEDULE_ID; child status/history records.
- FTE_LOAD_PRC_ATTRIBUTES — references FTE_LOAD_SCHEDULES.LOAD_SCHEDULE_ID; child pricing attributes.
- FTE_PA_SHIP_DETAILS — references FTE_LOAD_SCHEDULES.LOAD_SCHEDULE_ID; child shipment detail lines.
As this table is part of the Oracle proprietary ETRM data model, the documentation excerpt does not disclose every column or index; verification against the target instance is recommended prior to customization.
-
Table: FTE_LOAD_SCHEDULES 12.1.1
Stores the schedules associated with a shipment
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_SCHEDULES 12.2.2
Stores the schedules associated with a shipment
Not implemented in this database·Explore FTE module →
-
Stores transaction information destined for FTE_LOAD_SCHEDULES prior to validation
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_HISTORY 12.1.1
Stores the action history for shipments
Not implemented in this database·Explore FTE module →
-
Table: FTE_PA_SHIP_DETAILS 12.2.2
Stores data for formatting and processing the partial acceptance of tenders
Not implemented in this database·Explore FTE module →
-
This table holds the details of the Qualifiers and/or Pricing Attributes that were used to price a Load and Load Detail for a particular shipment schedule.
Not implemented in this database·Explore FTE module →
-
View: FTE_LOAD_CHARGES_V 12.1.1
Not implemented in this database·Explore FTE module →
-
Stores transaction information destined for FTE_LOAD_SCHEDULES prior to validation
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_HISTORY 12.2.2
Stores the action history for shipments
Not implemented in this database·Explore FTE module →
-
12.1.1 FND Design Data 12.1.1
-
Table: FTE_PA_SHIP_DETAILS 12.1.1
Stores data for formatting and processing the partial acceptance of tenders
Not implemented in this database·Explore FTE module →
-
This table holds the details of the Qualifiers and/or Pricing Attributes that were used to price a Load and Load Detail for a particular shipment schedule.
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_CHARGES 12.2.2
Holds the price related to the details of a tendered shipment
Not implemented in this database·Explore FTE module →
-
View: FTE_LOAD_CHARGES_V 12.2.2
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_CHARGES 12.1.1
Holds the price related to the details of a tendered shipment
Not implemented in this database·Explore FTE module →
-
12.2.2 FND Design Data 12.2.2
-
View: FTE_LOAD_SCHEDULES_V 12.1.1
Not implemented in this database·Explore FTE module →
-
View: FTE_LOAD_SCHEDULES_V 12.2.2
Not implemented in this database·Explore FTE module →