Search Results fte_lane_search




Overview
Explore in AI Chat

Overview

FTE_LANE_SEARCH is an Oracle Applications (APPS) PL/SQL package that belongs to the Oracle Transportation Management / Freight and Transportation Execution (FTE) module of Oracle E-Business Suite. Its business purpose is to perform lane-based searches that support freight rating, trip rating, and delivery auto-creation processes. A "lane" in FTE represents a transportation corridor between an origin and a destination, typically associated with carriers, service levels, transit times, and rate charts. FTE_LANE_SEARCH encapsulates the logic used to identify eligible lanes, retrieve associated rate chart identifiers, and determine transit times for a given search criteria set. The package is classified under the ETRM metadata as API classification OTHER and is owned by the APPS schema with a VALID status, indicating it is a supported, compiled database object. It depends on several FTE-specific collection and record types, including FTE_LANE_TAB, FTE_SCHEDULE_TAB, FTE_SEARCH_CRITERIA_REC, and FTE_SEARCH_CRITERIA_TAB, which confirms its role as a procedural engine for bulk lane evaluation. In Oracle EBS 12.1.1 and 12.2.2, this package is a foundational component invoked by higher-level freight rating and delivery planning APIs rather than being called directly by end users.

Key Procedures and Functions

The documented package exposes four procedures/functions. Their exact signatures are not published in the ETRM metadata, so only their functional purposes are described here.

  • SEARCH_LANES — The core entry point that accepts a search criteria structure (based on FTE_SEARCH_CRITERIA_REC / FTE_SEARCH_CRITERIA_TAB) and returns matching lanes into FTE_LANE_TAB. It evaluates origin, destination, carrier, and related attributes to determine which lanes satisfy the request.
  • GET_RATE_CHART_IDS — Retrieves the rate chart identifiers associated with the lanes identified by the search. These identifiers are subsequently used by freight and trip rating engines to price shipments.
  • GET_TRANSIT_TIME — Calculates or returns the transit time for a selected lane, populating schedule-related output (FTE_SCHEDULE_TAB). This supports delivery scheduling and promise-date calculations.
  • The fourth documented routine complements the above search, rate chart, and transit calculations, operating within the same lane-selection workflow.

Tables Accessed

Based on the documented metadata, the package references the following tables via APPS synonyms:

  • FTE_LANE_GROUP_COMPONENTS — Used to identify the constituent components of lane groups when expanding group-level search criteria into individual lanes.
  • FTE_LANE_VEHICLES — Provides vehicle equipment details associated with lanes, supporting vehicle-specific lane qualification.
  • WSH_CARRIER_VEHICLE_TYPES — Supplies carrier vehicle type definitions used to validate or filter lanes against eligible equipment.
  • WSH_LOCATIONS — Resolves origin and destination location identifiers required to match lanes geographically.
  • WSH_NEW_DELIVERIES — Links lane search results to delivery records, particularly in the delivery auto-create flow.
  • DBMS_SQL and PLITBLM — Dynamic SQL and PL/SQL table utilities used internally for dynamic query construction and bulk collection handling.

Usage Notes

FTE_LANE_SEARCH is not typically invoked directly by end users. Instead, it is referenced by several higher-level packages: FTE_FREIGHT_RATING_DLVY_GRP, FTE_FREIGHT_RATING_PUB, FTE_TRIP_RATING_GRP, and WSH_DELIVERY_AUTOCREATE. These calls occur during freight cost calculation, trip rating, and automatic delivery creation in the Order Management and Shipping Execution flows. The package is also self-referenced, indicating internal recursive or helper utilities. In Oracle EBS 12.1.1 and 12.2.2, customizations that extend rating or delivery logic should call the public routines rather than reimplement lane selection. Because the package depends on WSH and FTE collection types, any custom callers must initialize the appropriate criteria and lane tables correctly to avoid runtime errors. Debugging is generally performed through the dependent rating and delivery APIs, since the package itself is invoked internally.