BluJay Solutions Parcel 21.1.0 - User Guide
How to Configure Time in Transit - Importing Time in Transit Files |
Scroll |
Transit time calculations for some carriers require user-maintained transit time data. (See table in the following Help topic: Overview of Time in Transit Calculation.) You can import this data into the Parcel carrier database using the Import Time in Transit Files screen. This feature also includes the capability for the user optionally to import and maintain carrier Holidays and weekends at the destination level for the Time in Transit calculation to include when calculating an expected delivery date.
Import Time in Transit Files Screen
Use the Import Time in Transit Files screen to import the following data files for transit times and locations (origins and destination):
•Geographical data (destination cities, postal codes, etc.) – Required for first import.
•Time in transit data based on carrier service and destination – Always required for time in transit calculations to return a value.
•Holidays file containing information about destination holidays – Optional.
•Weekends file containing information on which weekend days to count for TinT – Optional.
When you import these files, Parcel inserts the data from these files into the carrier database. If you have Time in Transit enabled, when you perform a Rate or Ship, Parcel displays the transit time for the shipment.
Notes:
•All files that you import must be located on a local drive of the DIServer. The absolute path that you specify according to the following table represents the file location on the DIServer.
•The data in the time in transit files is customer-defined and does not come from the carrier.
To import Time in Transit files:
1.Create the Time in Transit files, and then copy these files to a directory local to the Parcel DIServer.
2.Use the Import Time in Transit screen in the Parcel Configuration (Web Admin) tool to specify the path names and filenames for these files according to the following table:
In this box... |
Do this... |
Geographic Data File |
Type in or paste in the absolute local path name for this file on the Parcel DIServer, including the filename. Note: This file is required the first time you import the set of Time in Transit files but is optional on subsequent file imports. |
Time in Transit File |
Type in or paste in the absolute local path name for this file on the Parcel DIServer, including the filename. |
Holidays File |
Optionally, to include carrier holidays in Parcel's time in transit calculation, type in or paste in the absolute local path name for this file, including the filename. |
Weekends File |
Optionally, to include weekends in Parcel's time in transit calculation, type in or paste in the absolute local path name for this file, including the filename. Note: This option currently applies only to FedEx Ground® and Home Delivery® services and UPS Ground® services. |
Format for Time in Transit Files
The time in transit files that you import (see previous section) must be comma-delimited CSV files of which the first row consists of the column (field) names listed in the following table. Subsequent rows contain comma-delimited data corresponding to the column names.
Caution: Since time in transit CSV files are comma-delimited, do not include commas in the data itself.
Notes:
•You can copy and paste the following column name strings directly into the CSV file.
•The values in the Geo Code fields can be arbitrarily defined, but since this column serves as the primary key, they must follow the same convention in all the files.
•The Destination address data for a shipment must be identical to the corresponding data in the Geographic Data file (Address <n>, City, State).
•The values for Transit Days and Transit Time are those estimated for the route defined by the Destination Geo Code.
File Type |
Web Admin Screen Name |
Required column names |
Geographic Data File |
Geographic Code |
Geo_code, Geo_code_desc, country_code, state, city, zip_low, zip_high |
Time in Transit File |
Transit Days |
Service_id, Geo_code, transit_days, transit_time (hh24:mm:dd), Sat_Delivery |
Holidays File |
Holidays |
serviceid, country, state, Holiday_desc, Date (YYYYMMDD), Allow_delivery, Include_transit |
Weekends File |
Weekends |
Service_id, country, state, Weekend_desc, Allow_delivery, Include_transit |
Note: For more information on TINT file formats, see the following Help topic: Time in Transit Files.
Error logging
If a service is not configured or is invalid, Parcel logs this error to a separate file: ..\Kewill\Flagship\bin\Import_failures.log
