Search Results fl_dest_low




Overview
Explore in AI Chat

Overview

The APPS.FTE_LTL_LOADER package is a bulk data loading utility within the Oracle E-Business Suite Transportation Management (originally Oracle Transportation and Global Trade Management, or ETRM) module. Its specific purpose is to import Less-Than-Truckload (LTL) tariff and rate data — including carriers, lanes, rate charts, zone definitions, and commodity classifications — into the FTE (Freight and Transportation Execution) schema. In Oracle EBS 12.1.1 and 12.2.2, this package enables shippers and logistics administrators to mass-upload negotiated LTL rate agreements from flat files (such as those provided by carriers) instead of manually keying them through the Transportation Management forms.

The package header declares numerous PL/SQL collection and record types — for example LANES_TEMP_RECORD, ZONES_TEMP_RECORD, and ZONE_INFO_RECORD — along with several global package variables such as FL_LOAD_ID, FL_SCAC, FL_ORIGIN_LOW, FL_ORIGIN_HIGH, FL_DEST_LOW, FL_DEST_HIGH, and FL_CLASS. These structures indicate that the loader builds up in-memory arrays of LTL data before performing bulk inserts or validations against the interface and base tables.

Key Procedures and Functions

  • PROCESS_LTL_DATA — The primary driver procedure, and the one most commonly referenced when users search for process_ltl_data. It orchestrates the LTL load process: reading staged bulk-load records, resolving them against tariff and carrier data, and writing the resulting LTL lane, zone, rate-chart, and commodity records into the FTE tables.
  • VERIFY_TARIFF_CARRIER — Validates that the tariff and carrier (SCAC) referenced in the incoming LTL data exist and are consistent before downstream processing proceeds.
  • GET_TARIFF_RATECHARTS — Retrieves the rate chart definitions associated with a given tariff, populating the internal collection structures used to build lane rate chart records.
  • QP_PROCESS — Handles the interaction with the Oracle Advanced Pricing (QP) engine, so that LTL lane rate charts can be linked to pricing list headers and modifiers.

Tables Accessed

The package reads and writes through APPS synonyms, as documented for ETRM 12.2.2. Staging and interim data are held in FTE_BULKLOAD_FILE, FTE_BULKLOAD_DATA, FTE_BULKLOAD_DATA_S, and the interface tables FTE_INTERFACE_ZONES and FTE_INTERFACE_LANES. The permanent LTL definition tables written to include FTE_LANES and its multi-lingual sibling FTE_LANES_S, FTE_LANE_COMMODITIES, FTE_LANE_RATE_CHARTS, and FTE_LANE_SERVICES with FTE_LANE_SERVICES_S. Reference and lookup data are sourced from FTE_PRC_PARAMETERS, HZ_PARTIES (party/carrier names), QP_LIST_HEADERS_TL (pricing list headers), and WSH_REGIONS_TL (region descriptions used in zone definitions).

Usage Notes

FTE_LTL_LOADER is typically invoked through the Transportation Management bulk-load concurrent programs rather than called directly by end users. A user uploads a flat file of LTL rate data; the concurrent program stages it in the bulk-load interface tables and then calls PROCESS_LTL_DATA to validate and transfer the records into the base LTL tables. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the calling schema, and it is referenced by one other FTE package within the module. Custom extensions should call the procedures in the sequence VERIFY_TARIFF_CARRIER, GET_TARIFF_RATECHARTS, then PROCESS_LTL_DATA, and must avoid modifying the declared global collection types, as they form the internal interface between these routines.