Results for “transit_time_uom”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FTE_LOCATION_MILEAGES is a reference table within the Oracle E-Business Suite Transportation Execution (FTE) module. It stores the physical distance and expected transit time between pairs of geographic regions, with each region acting as an origin or a destination. This makes the table a foundational data source for transportation planning, carrier rating, freight cost estimation, and delivery scheduling, where accurate lane-level distance and lead-time figures are required.
The table is owned by the FTE schema and is marked VALID in the documented release (ETRM 12.2.2). It contains 16 physical columns. In heuristic Data Vault terms, FTE_LOCATION_MILEAGES is classified as standalone, meaning it is not tied into the FK web as a hub, link, or satellite in the mined relationship model. From a dimensional modeling perspective, it is best treated as a standalone reference or lookup dimension keyed on the origin-destination pair.
Key Information Stored
The composite primary key FTE_LOCATION_MILEAGES_PK1 consists of ORIGIN_ID and DESTINATION_ID. These two columns identify the region-based origin and destination and together form the natural business key of the record; no separate single-column surrogate key is documented.
- ORIGIN_ID — Identifier of the origin region.
- DESTINATION_ID — Identifier of the destination region.
- IDENTIFIER_TYPE — Qualifies the type of identifier used for the origin and destination, allowing the same pair to be expressed under different identifier conventions.
- DISTANCE — The measured distance between the two regions.
- DISTANCE_UOM — Unit of measure for DISTANCE (for example, miles or kilometers).
- TRANSIT_TIME — The expected transit duration between origin and destination.
- TRANSIT_TIME_UOM — Unit of measure for TRANSIT_TIME (for example, days or hours).
- CREATION_DATE, CREATED_BY — Standard audit fields recording when and by whom the row was created.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit fields capturing the most recent modification and session context.
- PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program and request context under which the record was inserted or updated.
Common Use Cases and Queries
Transportation planners and rate engines consult this table to derive lane distances and transit times for shipments. Typical reporting includes lane coverage analysis, transit-time benchmarking, and distance-based freight cost modeling. A simple lookup joins the origin and destination to a single record:
SELECT distance, distance_uom, transit_time, transit_time_uom FROM fte_location_mileages WHERE origin_id = :p_origin AND destination_id = :p_destination;- Reverse or symmetric lane checks:
SELECT origin_id, destination_id, distance FROM fte_location_mileages WHERE identifier_type = :p_type; - Audit and data-quality review of recently changed rows using LAST_UPDATE_DATE.
- Coverage gap analysis to identify region pairs with no mileage record, supporting master-data maintenance.
Related Objects
Because the mined relationship model classifies FTE_LOCATION_MILEAGES as standalone, no documented foreign keys bind it to other tables. In practice, ORIGIN_ID and DESTINATION_ID are expected to resolve to region records in the FTE location/region master data, so joins are typically performed on those columns against the region definition table rather than through enforced FK constraints. Reporting and integration routines frequently combine this table with transportation planning and rating objects that reference lane distance and transit-time values. Where programmatic access is required, standard EBS concurrent program and interface APIs that load or consume lane data provide the main integration surface.
-
This table is used to store the distance and transit times between two locations (origin and destination), where the locations are identified as regions. The primary key for the table is origin_id - destination_id.
-
This table is used to store the distance and transit times between two locations (origin and destination), where the locations are identified as regions. The primary key for the table is origin_id - destination_id.
-
Stores schedule information for each lane. This is the main catalog entity for schedules
-
Stores schedule information for each lane. This is the main catalog entity for schedules
-
Stores services catalog lane descriptions.
-
Stores services catalog lane descriptions.
-
VIEW: FTE.FTE_SCHEDULES# 12.2.2
-
VIEW: FTE.FTE_LANES# 12.2.2
-
VIEW: FTE.FTE_SCHEDULES# 12.2.2
-
VIEW: FTE.FTE_LANES# 12.2.2
-
TYPE: APPS.FTE_LANE_REC 12.1.1
-
TABLE: FTE.FTE_SCHEDULES 12.2.2
-
TABLE: FTE.FTE_SCHEDULES 12.1.1
-
TYPE: APPS.FTE_SCHEDULE_REC 12.2.2
-
TYPE: APPS.FTE_SCHEDULE_REC 12.1.1
-
TABLE: FTE.FTE_LANES 12.2.2
-
TABLE: FTE.FTE_LANES 12.1.1
-
TYPE: APPS.FTE_LANE_REC 12.2.2