Search Results fte_tl_cache




Overview
Explore in AI Chat

Overview

FTE_TL_CACHE is the transportation and logistics caching package within the Oracle Freight and Transportation Execution (FTE) module of Oracle E-Business Suite. In releases 12.1.1 and 12.2.2 it resides in the APPS schema with a status of VALID and is classified as an OTHER API, indicating it is an internal engine component rather than a public, externally supported interface. The package body provides the runtime implementation of a cache-building mechanism that assembles the transportation attributes required to plan, price, and execute shipments. Its principal consumers are the FTE planning and pricing engines, which call into the cache to obtain lane, rate chart, schedule, trip move, delivery, and location data in a consolidated form before performing rate shopping, route selection, trip building, and delivery comparison. The cache reduces repeated round trips against the highly normalized FTE and Order Management tables, and centralizes the resolution of references such as carriers, carrier services, and geographic regions. Because it touches both FTE-native tables and WSH (Shipping) tables, the package sits at the intersection of freight planning and outbound logistics execution.

Key Procedures and Functions

The documented interface exposes fifteen procedures and functions. The TL_BUILD_CACHE_* family constitutes the core: TL_BUILD_CACHE_FOR_MOVE constructs cache entries for a trip move, TL_BUILD_CACHE_FOR_TRIP for an entire trip, TL_BUILD_CACHE_FOR_DELIVERY for a single delivery, TL_BUILD_CACHE_FOR_OM for Order Management sourced data, TL_BUILD_CACHE_FOR_LCS for logistics comparison scenarios, TL_BUILD_CACHE_FOR_ESTIMATE for rate estimation, and TL_BUILD_CACHE_FOR_DLV_COMPARE and TL_BUILD_CACHE_FOR_TRP_COMPARE for delivery and trip comparison processing. DELETE_CACHE removes previously constructed cache entries, and DISPLAY_CACHE renders cache contents for diagnostic inspection. GET_APPROXIMATE_DISTANCE_TIME returns an estimated distance and transit duration between locations. FPA_GET_TRIP_INFO retrieves trip information for freight planning activities. GET_VEHICLE_TYPE returns the equipment or vehicle classification applicable to a shipment. CALCULATE_DIMENSIONAL_WEIGHT computes the volumetric (dimensional) weight used to determine chargeable weight in rating calculations.

Tables Accessed

The package reads from a broad set of APPS synonyms. Freight and transportation configuration is sourced from FTE_LANES, FTE_LANE_RATE_CHARTS, FTE_SCHEDULES, and FTE_TRIP_MOVES. Shipping execution data is drawn from WSH_CARRIERS, WSH_CARRIER_SERVICES, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_DELIVERY_LEGS, WSH_NEW_DELIVERIES, WSH_TRIPS, WSH_TRIP_STOPS, and the geographic reference tables WSH_REGIONS, WSH_REGION_LOCATIONS, and WSH_LOCATIONS. Customer and location context comes from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and PO_LOCATION_ASSOCIATIONS_ALL. Item-level characteristics used in dimensional weight and vehicle type determination come from MTL_SYSTEM_ITEMS_B, and global defaults from WSH_GLOBAL_PARAMETERS. DBMS_UTILITY and DUAL are used for PL/SQL utility operations. The package also depends on sibling FTE packages including FTE_DIST_INT_PKG, FTE_FREIGHT_PRICING, FTE_FREIGHT_PRICING_UTIL, FTE_LOCATION_PARAMETERS_PKG, FTE_PROCESS_REQUESTS, FTE_RTG_GLOBALS, FTE_VEHICLE_PKG, and WSH_UTIL_CORE, and it is referenced by four other packages.

Usage Notes

FTE_TL_CACHE is ordinarily invoked indirectly. It is not referenced by any database object outside the FTE and WSH family, and there is no evidence of form-level or concurrent program invocation. Callers are the FTE planning, rating, and comparison engines, which populate the cache before executing a planning or pricing run. Because entries persist until DELETE_CACHE or TL_BUILD_CACHE_* rebuilds them, invocations should be scoped to a single planning session. DISPLAY_CACHE supports troubleshooting when cached values appear inconsistent with underlying lane, rate chart, or delivery records. Custom code should avoid calling these internals directly where a supported FTE or WSH API exists, and any direct use should be validated after patching or upgrade, since the package is classified as OTHER and its signature is subject to change between 12.1.1 and 12.2.2.