Search Results fte_lane_services_pk
Overview
The FTE_LANE_SERVICES table is a core data object within the Oracle E-Business Suite (EBS) Transportation Execution (FTE) module. It functions as a child table to FTE_LANES, storing the specific service level details associated with transportation lanes. A lane defines a route between two geographic points, such as a shipping lane from a warehouse to a customer site. This table enables the granular configuration of available shipping services (e.g., standard ground, two-day air, overnight) for each lane, allowing businesses to model and offer differentiated freight options based on transit time, cost, and carrier capabilities. Its role is critical for the rate and service selection processes during shipment planning and execution within the EBS logistics framework.
Key Information Stored
While the full column list is not provided in the excerpt, the documented metadata identifies the primary and foreign key structure that defines the table's core data model. The primary key is LANE_SERVICE_ID, a unique identifier for each service record. The critical foreign key is LANE_ID, which links each service entry to its parent transportation lane defined in the FTE_LANES table. Typically, columns in such a table would store service-level attributes, which may include service type or code, standard transit time (in days), service availability flags, effective dates, and potentially references to rate information or carrier service codes. The data populates lane-specific service lists used during shipment booking and freight cost calculation.
Common Use Cases and Queries
A primary use case is retrieving all active services for a specific lane to present as options during a sales order shipment or a freight booking transaction. Another is reporting on service coverage across the transportation network. Common SQL patterns involve joining to the FTE_LANES table to filter by origin and destination. For example, to find services for a lane between two locations, a query might be: SELECT fls.* FROM fte_lane_services fls, fte_lanes fl WHERE fls.lane_id = fl.lane_id AND fl.from_location_id = :p_from_loc AND fl.to_location_id = :p_to_loc AND SYSDATE BETWEEN fls.start_date_active AND NVL(fls.end_date_active, SYSDATE);. Data from this table is also essential for integration with carrier rating engines and for analyzing service-level performance against planned transit times.
Related Objects
The table maintains a direct, documented foreign key relationship with the FTE_LANES table, which is its primary parent object.
- FTE_LANES: This is the parent table. The relationship is defined by the foreign key column
FTE_LANE_SERVICES.LANE_IDreferencing the primary key of FTE_LANES. All service records must correspond to a valid lane. This table stores the origin, destination, and general attributes of the transportation lane. - The table itself is referenced by its primary key constraint, FTE_LANE_SERVICES_PK, on the
LANE_SERVICE_IDcolumn. Other FTE transactional tables, such as those storing shipment legs or rated freight charges, would likely have foreign keys toLANE_SERVICE_IDto record the specific service used, though these are not listed in the provided metadata.
-
Table: FTE_LANE_SERVICES
12.2.2
owner:FTE, object_type:TABLE, fnd_design_data:FTE.FTE_LANE_SERVICES, object_name:FTE_LANE_SERVICES, status:VALID, product: FTE - Transportation Execution , description: Stores service information for each lane , implementation_dba_data: FTE.FTE_LANE_SERVICES ,
-
Table: FTE_LANE_SERVICES
12.1.1
owner:FTE, object_type:TABLE, fnd_design_data:FTE.FTE_LANE_SERVICES, object_name:FTE_LANE_SERVICES, status:VALID, product: FTE - Transportation Execution , description: Stores service information for each lane , implementation_dba_data: FTE.FTE_LANE_SERVICES ,