Search Results fte_location_mileages_pk1

Overview

The FTE_LOCATION_MILEAGES table is a core data repository within the Oracle E-Business Suite Transportation Execution (FTE) module. It functions as the system of record for pre-calculated distances and transit times between geographic regions. This stored information is critical for automating and optimizing transportation planning, freight rating, and shipment scheduling processes. By maintaining a matrix of origin-to-destination metrics, the table enables the system to perform accurate cost calculations and service time estimations without requiring real-time, external lookups for every shipment. Its design, using region-based locations (as opposed to specific addresses), supports efficient high-level planning and rate zoning.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies a route between two regions. The most critical columns, as confirmed by the provided metadata, are ORIGIN_ID and DESTINATION_ID. These foreign keys reference location or region identifiers, likely linking to tables such as HR_LOCATIONS or a custom FTE regions table. While the specific distance and time columns are not listed in the excerpt, based on the table's description and standard practice, one would expect columns like DISTANCE, DISTANCE_UOM, TRANSIT_TIME, and TRANSIT_TIME_UOM. Additional columns may include creation dates, last update dates, and the identity of the last updater for auditing purposes. The primary key constraint FTE_LOCATION_MILEAGES_PK1 enforces data integrity by preventing duplicate origin-destination pairs.

Common Use Cases and Queries

The primary use case is the retrieval of pre-defined mileage and transit time for freight rating and scheduling engines. When a user creates a shipment or requests a freight quote between two defined regions, the application queries this table to fetch the applicable values. A typical query pattern involves joining the table to location master data. For example, to find the distance between two specific location codes, a query might be:

• SELECT flm.distance, flm.transit_time FROM fte.fte_location_mileages flm WHERE flm.origin_id = (SELECT location_id FROM hr_locations WHERE location_code = 'NYC') AND flm.destination_id = (SELECT location_id FROM hr_locations WHERE location_code = 'CHI');

Reporting use cases include analyzing the mileage matrix for data completeness, auditing rate calculations, and identifying missing routes that need to be populated to ensure smooth transportation operations.

Related Objects

As a foundational table, FTE_LOCATION_MILEAGES is referenced by various components within the FTE module. It is directly linked to location master tables, most commonly HR_LOCATIONS or a similar FTE-specific region table, via the ORIGIN_ID and DESTINATION_ID foreign keys. Key related objects include the Freight Cost Calculation engine and Shipment Scheduling functions, which consume its data. The table may also be referenced by public APIs or views that expose transportation data for integration with other EBS modules, such as Order Management (OM) or Purchasing (PO), which rely on accurate shipping time and cost estimates. The primary key constraint FTE_LOCATION_MILEAGES_PK1 is a direct dependent object.