General Info Table settings that are used by LTL Operations

These General Info Table settings are used by LTL Operations, and are saved within the TMWSuite database.

DrvTrcProt

Applies to

TMWSuite: 2000 and later, TMW Operations

Description

By default, the driver profile lists the tractor that was assigned to the driver’s last Started or Completed trip. Similarly, the tractor profile lists the driver who was assigned to the tractor’s most recent Started or Completed trip.

This setting allows you to protect the driver/tractor relationship you record in the driver and/or tractor profiles. In other words, it prevents the system from updating the driver and/or tractor listed in the profiles based on trip assignments.

For example, suppose you link DriverA with TractorA in the driver and tractor profiles. With no protection on either profile, the system would update both the driver and tractor profiles if either of the following occurs:

  • DriverA is started on a trip with a different tractor.

  • TractorA is started on a trip with a different driver.

Your entry in the String1 field tells the system how to handle driver/tractor pairing.

String1

  • NONE (default)
    Offers no protection

  • DRV
    Protects the driver profile from being updated with the driver’s current tractor assignments on a trip.

  • TRC
    Protects the tractor profile from being updated with the tractor’s current driver assignment on a trip.

  • BOTH
    Protects both the driver profile and tractor profile from being updated with current resource assignments on a trip.

Additional Notes

In TMW Operations, this setting does not protect driver/tractor pairing from changes made in the Maintain Tractor-Driver Assignment window.

LTLAllowManRecalUpTo

Applies to

LTL Operations Module 2020.3 and later

Description

When stops are set to the Golden State status (stops sent to MobileComm) on a manifest, a dispatcher can communicate to a driver that the trip’s stop(s) were either canceled or postponed. There comes a point during this process where it is no longer practical to allow a dispatcher to recall a manifest. Use this setting to specify the terms under which a dispatcher can recall a manifest.

String1

  • ArrCust (default)
    Permit a manifest recall up until the driver arrives at the first non-terminal pickup or drop stop.

    Notes:

    1. This option allows you to recall a manifest when a driver is en route to the first customer location.

    2. This option uses the default value for a missing value or a value other than ArrTerm.

  • ArrTerm
    Permit a manifest recall up until the driver starts the trip from the first terminal stop.

Additional Notes

  1. Option values are not case-sensitive.

  2. Setting options apply to local manifests only, not line-haul manifests.

LTLAllowMassLTGWithoutOrders

Applies to

LTL Operations Module 2021.3 and later

Description

The delivery window workflow lets you set a manifest with no orders to Loaded To Go status. To do this you use the Pickups window. The system performes error checking that could prevent the status change. This setting lets you turn off the checking for two errors:

  • Movement.PreManifestHasOrders

  • Movement.PreManifestLoadedToGo (firstStopHasValidEvent)

With this checking turned off, the manifest status change is successful.

String1

  • N (default)
    Do not allow manifest with no orders to be set to Loaded To Go status.

  • Y
    Allow manifest with no orders to be set to Loaded To Go status.

LTLAllowResequenceStops

Applies to

LTL Operations Module 2022.1 and later

Description

This setting controls whether or not you can use drag/drop to resequence stops on the Trip Manifest Control Stops tab. The new setting keeps you from inadvertently using the drag/drop feature to resequence stops.

String1

  • Y (default)
    Allow the drag/drop function to operate for resequencing stops.

  • N
    Disallows the drag/drop function to operate for resequencing stops

  • W
    Warns users that they are about to use drag/drop and asks them if they want to do it.

LTLAllowTripAssetRemoval

Applies to

LTL Operations Module 2022.4 and later

Description

This setting determines whether users can remove a trailer and/or tractor from an active manifest.

String1

  • N (default)
    If a user attempts to remove a trailer from an active manifest, an error is displayed.

  • Y
    No error occurs when a trailer is removed from an active manifest.

String2

  • N (default)
    If a user attempts to remove a tractor from an active manifest, an error is displayed.

  • Y
    No error occurs when a tractor is removed from an active manifest.

LTLAllowTripForceAssetSwitch

Applies to

LTL Operations Module 2020.3 and later

Description

This setting controls whether you can change the assets on an active manifest. .

String1

Your entry in this field controls changing the tractor assignment on the manifest.

  • Y (default)
    Show a warning, but allow tractor assignment changes when the manifest’s IsActive check box is selected. The check box appears on the Trips tab.

  • N
    Do not allow tractor assignment changes.

String2

Your entry in this field controls changing the trailer assignment on the manifest.

  • Y (default)
    Show a warning, but allow trailer assignment changes when the manifest’s IsActive check box is selected. The check box appears on the Trips tab.

  • N
    Do not allow trailer assignment changes.

LTLAppianDRExportDistFileDflt

Applies to

LTL Operations V.2022.4 and later

Description

This setting controls whether a distance file is exported and, if so, the data that is included.

String1

  • SEL (default)
    A distance file is exported that contains routes selected in the Terminal profile’s Routes tab.

  • ALL
    A distance file is exported that contains the entire mileage table.

  • N
    A distance file is not exported.

LTLAppianDRExportExtensions

Applies to

LTL Operations V.2020.3 and later

Description

This setting controls the file types that are sent when you use the DirectRoute Export command. The default values for the files ensure that they can be opened in Microsoft Excel for review before they are imported into Appian DirectRoute.

String1

Your entry in this field identifies the file type used for stop data.

  • <filename>.stop (default)
    The data is sent as an .csv file. Trimble recommends using this default value.

  • User-specified number
    Data files cannot be opened in Excel until they have been imported into Appian DirectRoute.

String2

Your entry in this field identifies the file type used for truck data.

  • <filename>.truck (default)
    The data is sent as an .csv file. Trimble recommends using this default value.

  • User-specified number
    Data files cannot be opened in Excel until they have been imported into Appian DirectRoute.

String3

Your entry in this field identifies the file type used for route data.

  • <filename>.route (default)
    The data is sent as an .xml file. Trimble recommends using this default value.

  • User-specified file extension
    Data files cannot be opened in Excel until they have been imported into Appian DirectRoute.

String4

First available: LTL Operations V.2022.4

Your entry in this field identifies the file type used for the distance file.

  • <filename>.dist (default)
    The data is sent as an .xml file. Trimble recommends using this default value.

  • User-specified file extension
    Data files cannot be opened in Excel until they have been imported into Appian DirectRoute.

LTLAppianDistanceFileMin

Applies to

LTL Operations 2022.1 and later

Description

When you send routes to Appian, and validate the distance, the system often rounds the miles between stops down. This affects the drive time for the stops. For example, it would change a stop with mileage less than a mile, with a four-minute drive time to 0 (zero) miles and a one-minute drive time.

You can use this setting to specify the minimum mileage value at which the system should no longer round down the miles between stops.

String 1

  • 0 (default)
    The system will round down the mileage and recalculate the distance for stops.

  • User-specified fraction of a mile
    Enter the decimal value of a mile at which the system should not round down the mileage. For example, 0.5. The system will not recalculate miles less than this value when validating distance.

LTLAppianMapStopDefaults

Applies to

LTL Operations Module 2022.4 and later

Description

This setting defines the default LTL Appian (Import/Export) settings for mapping stops in DirectRoute.

String1

Symbol

  • Circle (default)

  • Any other allowed DirectRoute symbol value, as shown in this table:

    Asterisk

    LfArrow

    Truck

    Boat

    Phone

    TruckE

    Bus

    Pin

    TruckN

    Car

    Plane

    TruckNE

    Church

    Plus

    TruckNW

    Cross

    RtArrow

    TruckS

    Diamond

    School

    TruckSE

    DnArrow

    Star1

    TruckSW

    Factory

    Star2

    UpArrow

    Flag

    Star3

    Vdiamond

    Hdiamond

    Tower

    X

    House

String2

Color

  • Cyan (default)

  • Any other allowed DirectRoute color value, as shown in this table:

    Blue

    LightBlue

    Orchid

    Brick

    LightCyan

    PaleGreen

    Chocolate

    LightGray

    PaleTurquoise

    Crimson

    LightGreen

    Peach

    DarkBlue

    LightPeach

    Pink

    DarkGray

    LightPink

    Purple

    DarkGreen

    LightViolet

    Red

    DarkKhaki

    LightYellow

    RoyalBlue

    DarkOliveGreen

    Lime

    SaddleBrown

    DarkPurple

    LimeGreen

    Silver

    DarkRed

    Maroon

    Teal

    DarkTeal

    MediumBlue

    Turquoise

    Fuchsia

    Navy

    Violet

    Gray

    Olive

    White

    Green

    Orange

    Yellow

    LemonChiffon

String3

Size

  • 30 (default)

  • Any integer between 4 and 36, inclusive

LTLAppianRouteResponseMaxUndo

Applies to

LTL Operations V.2020.3 and later

Description

WWhen you send a manifest to Appian, you view the returned results in the Appian Response window. You can modify the suggested route in the window. However, there may be times when you would like to reverse your edits. This setting lets you:

* Activate the Undo command in the window header

* Specify how many times you can reverse your changes in a single session

Integer1

  • 0 (default)
    The Undo command is not active.

  • User-specified number
    Enter a value greater than 0 (zero) to activate the command. Your entry also sets the number of changes you can reverse.

LTLApplySchedChngsToActMnfsts

Applies to

LTL Operations Module 2022.1 and later

Description

Sometimes you need to make changes to a route’s master schedule. This setting controls how those changes are reproduced on the route’s manifest.

String1

  • Y (default)
    Always make changes to manifests.

  • N
    Never make changes to manifests.

  • W
    Prompt the user to accept changes to manifests.

LTLApplyRoutePickupCutoff

Applies to

LTL Operations 2023.1 and later

Description

This setting changes an order’s service plan to match the pickup cutoff with the shipper’s pickup time.

String1

  • N (default)
    Pickups can be assigned to routes that have a pickup cutoff that is before the pickup at the shipper.

  • Y
    The setting selects a different route for pickups that do not fall within the shipper’s time frame. The selected route is either later on the same day or any approved time the following day.

LTLAutoCreateRouteDrops

Applies to

LTL Operations V. 2021.4 and later

Description

You can use the Mass Manifest Change command to remove all Scheduled Unload stops from a group of manifests. You will not have to remove single manifests one-at-a-time with this setting.

Options

  • N (default)

    Do not allow the removal of all Scheduled Unload stops from a group of manifests. You will have to remove single manifests one-at-a-time.

  • Y

    Allow the removal of all Scheduled Unload stops from a group of manifests.

LTLAutoCreateRoutePicks

Applies to

LTL Operations V. 2021.4 and later

Description

You can use the Mass Manifest Change command to remove all Scheduled Load stops from a group of manifests. By default, you must remove single manifests one-at-a-time. This setting lets you have the system remove all of them from a group of manifests at the same time.

Options

  • N (default)

    Do not allow the removal of all Scheduled Load stops from a group of manifests. You must remove single manifests one-at-a-time.

  • Y

    Allow the removal of all Scheduled Load stops from a group of manifests.

LTLCheckSumShiftless

Applies to

LTL Operations Module V. 2021.3 and later

Description

You may have drivers who are not assigned to shifts. This setting lets you make driver manifest assignments for those drivers.

String1

  • N (default)
    You cannot assign a driver to a manifest if they are not assigned to a shift.

  • Y
    You can assign a driver to a manifest if they are not assigned to a shift.

LTLDefaultTerminalRoutesView

Applies to

LTL Operations Module 2021.1 and later

Description

Use this setting to determine which route view opens by default when you access the Routes tab in the Terminal Profile window.

String1

  • R (default)
    Open the Routes view by default.

    This view shows columns from the SQL terminalroute table only. It is the view available in earlier versions of the application.

  • RS
    Open the Routes/Schedules view by default.

    This view shows routes based on an actual SQL Server view that combines and displays columns from both the terminalroute and terminaltripschedule tables. In this view, you can:

    • View and edit fields from both tables in the same grid.

    • Use the Schedule Grouping, Group By box to group routes based on Schedule Groupings.

    Note: In this view:

    • The Routes grid shows routes with schedule assignments only.

    • You can make field value changes in one table at a time. For example, after you make changes to route fields, you must save them before making changes to schedule fields.

    • The system requires you to save or cancel changes before switching to a different view.

LTLETACutoffMinutes

Applies to

LTL Operations Module 2021.3 and later

Description

The ETA service runs every few minutes but will only update an individual manifest once every 15 minutes. You may want to have the system process ETA leg updates more often or less often.

Use this setting to specify the number of minutes you want the system to wait before processing updates.

Int1

  • 15 (default)
    The service runs every 15 minutes.

  • User-specified interval
    Enter the number of minutes you want the service to wait between updates.

LTLDriverShiftReqd

Applies to

LTL Operations Module V. 2022.1 and later

Description

You can use this setting to set driver shift requirements for Local, Linehaul, and Truckload manifests.

To use this functionality, LTLChecksumShiftless must have a String1 value of N.

String1

Your entry in this field controls the assignment of drivers in Local manifests.

  • W (default)
    Prompt to allow assignment of drivers not assigned to shifts to Local manifests

  • N
    Shift not required

    Always allow assignment of drivers not assigned to shifts to Local manifests.

  • Y
    Shift required

    Never allow assignment of drivers not assigned to shifts to Local manifests.

String2

Your entry in this field controls the assignment of drivers in Linehaul manifests.

  • N (default)
    Shift not required

    Always allow assignment of drivers not assigned to shifts to Linehaul manifests.

  • Y
    Shift required

    Never allow assignment of drivers not assigned to shifts to Linehaul manifests.

  • W
    Prompt to allow assignment of drivers not assigned to shifts to Linehaul manifests.

String3

Your entry in this field controls the assignment of drivers in Truckload manifests.

  • N (default)
    Shift not required

    Always allow assignment of drivers not assigned to shifts to Truckload manifests.

  • Y
    Shift required

    Never allow assignment of drivers not assigned to shifts to Truckload manifests.

  • W
    Prompt to allow assignment of drivers not assigned to shifts to Truckload manifests.

LTLDriverShiftValidateLegEnd

Applies to

LTL Operations Module 2020.3, 2021.1 and later

Description

LTL Dispatch and TMW Operations limit a driver’s shift duration to a maximum of 24 hours. This limitation can cause issues with a leg that spans several days. When assigning a driver to a leg, the system validates whether a leg’s start and end times fall within a driver’s shift. Use this setting to have the system validate a leg’s start time only.

String1

  • N (default)
    Verify that a leg’s start time falls within a driver’s shift.

    Validation does not consider the leg’s end time.

  • Y
    Verify that a leg’s start time and end time fall within a driver’s shift.

LTLForceAssetSwitchValidation

Applies to

LTL Operations Module 2022.1 and later

Description

Allow/Denies Force Asset Switch validation when the asset is changed on an active manifest in pickups/deliveries/etc.

By default, when a driver requests a self-dispatch route, their tractor’s last manifest must be completed. This setting lets you have the system ignore the incomplete manifest and perform the assignment.

As of V.2022.1, only the String2 field is active.

String1

Entry in this field controls Force Asset Switch validation for the trip’s Trailer assignment At this time, no setting is necessary.

String2

Entry in this field controls Force Asset Switch validation for the trip’s Tractor assignment.

  • Y (default)
    Allow Force Asset Switch validation when the asset is changed on an active manifest.

  • N
    Deny Force Asset Switch validation when the asset is changed on an active manifest.

String3

Entry in this field controls Force Asset Switch validation for the trip’s Driver1 assignment At this time, no setting is necessary.

String4

Entry in this field controls Force Asset Switch validation for the trip’s Driver2 assignment At this time, no setting is necessary.

LTLFreightOrdImportDateOffset

Applies to

LTL Operations 2023.1 and later

Description

If the dispatch date of an order is after the dispatch Day of Week, the delivery date incorrectly gets pushed back one week. This setting corrects this error.

String1

  • N (default)
    If the dispatch date is one day after the expected day, the delivery date can get pushed back one week.

  • Y
    The setting offsets the load date by -1 Day during import. This keeps orders with a mismatched load date from being dispatched seven days later than expected.

String2

  • N (default)
    If the chosen dispatch date is before the delivery date, the error message "Pickup Less than Delivery date" appears.

  • Y
    The setting lets you bypass the error message "Pickup Less than Delivery date." The delivery date will be pushed back one week.

LTLGreyOutDoneDisabledGridRows

Applies to

LTL Operations Module 2022.1 and later

Description

This setting allows you to set a color scheme for grid rows. This allows for better visibility.

String1

  • 0 (default)
    No extra color formatting will be applied so that you can create your own color scheme for completed/disabled rows.

  • 1
    Completed/disabled rows will have dark grey text and a light grey background.

  • 3
    Completed/disabled rows will have black text and a Gainesboro (blue) background.

LTLHoursOfOperationIncrement

Applies to

LTL Operations Module 2020.3 and later

Description

When scheduling product deliveries, the system checks for an open delivery window based on a company’s hours of operation. By default, the system checks for a window in one-hour increments. This means each increment has a one-hour (60 minutes) duration. Some companies are open for periods that are less than 60 minutes.

Use this setting to specify a number of minutes less than 60 to check a company’s hours of operation. For example, if a company has a 30-minute delivery window, you should set the time increment to a number less than or equal to 30 minutes. Otherwise, the system may fail to find a valid delivery time.

Int1

  • 60 (default)
    Check company hours of operation in one-hour increments (60 minutes).

  • User-specified number
    Specify the number of minutes to increment when checking for company hours of operation.

    Note: Enter any number greater than 0 (zero) and less than 60.

LTLIgnoreApmtRequireContact

Applies to

LTL Operations Module 2020.3

Description

The Company Profile’s Scheduling tab allows you to specify if contact information is required for scheduling appointments. To do this, you go to the Contact Information section and enter a value in the Contact Required field.

When you specify a requirement, the Appointment window validates whether contact information is available.

Use this setting to determine whether you want the appointment validation process to ignore contact information requirements when booking an appointment.

String1

  • N (default)
    The Appointment window validation issues an error message when the contact information requirement is not satisfied.

  • Y
    The Appointment window validation ignores the contact requirement.

Additional Notes

This setting only applies to the LTL application. Other applications that use Contact Required are not affected.

LTLMappingMaxManifests

Applies to

LTL Operations Module 2021.2 and later

Description

When you use Appian DirectRoute integration, you can view returned routes on the Route Response window’s map. By default, the map shows 10 routes. If you often send more than 10 routing requests at a time, use this setting to specify how many routes you want to show on the map. You make your entry in the Integer1 field. Entries are not required in any other field.

Use this setting to control how the validation is handled.

Note: This setting applies only to the To Be Loaded and Loading statuses.

Integer1

  • 10 (default)
    Up to 10 routes are displayed on the map.

  • User-specified number
    Enter the number of routes you want to see on the map.

Additional Notes

The Route Response window provides two shortcut menu options that are affected by the value you set.

* Show On Map – All
If there are more routes than you have specified in the Integer1 field, the system shows a warning. For example if the value is 10, the message states, "Cannot map more than 10 routes at a time (per G.I. LTLMappingMaxManifests)."

* Show On Map – Selected
You can select the check box for each route you want to show on the map. Selecting more routes than the value in the Integer1 field will also show the warning.

LTLMappingRouteLabels

Applies to

LTL Operations Module 2020.4 and later

Description

LTL maps allow you to view and track trip data on a graphical map. Use this setting to determine how you want a route label to appear on a map. You can specify the type of ID or number you want to show in a label based on the setting options you select.

String1

Maps now show the Route Label drop-down field. Use the String1 field to specify which route label option you want to use when you first open a map. When the map is open, you can select other options as needed.

  • N (default)
    Show no labels when the map opens.

    You must select an option from the Route Label drop-down field to view labels.

  • L
    Show the label on the map’s route line.

  • C
    Center the label on the map’s route line.

String2

Use this field to determine what text to show in the labels for Appian Response maps.

  • RI (default)
    Show the Appian route ID in the label.

  • RN
    Show the manifest route number in the label.

String3

Use this field to determine what text to show in labels for other maps, such as those that show pickups and deliveries.

  • MAN (default)
    Show the manifest number in the label.

  • MOV
    Show the movement number in the label.

  • LEG
    Show the leg number in the label.

  • RN
    Show the LTL route ID or number in the label.

  • RD
    Show the route description (Appian ID) in the label.

LTLMnfstStopsInclAppianInfo

Applies to

LTL Operations Module 2022.1 and later

Description

This allows you to populate ManifestEdit and/or TripManifest with read-only Appian information.

String1

  • Y (default)
    Allow read-only Appian information to populate ManifestEdit.

  • N
    Allow read-only Appian information to populate ManifestEdit.

String2

  • Y (default)
    Allow read-only Appian information to populate TripManifest.

  • N
    Allow read-only Appian information to populate TripManifest.

LTLMnfstStopsInclApptInfo

Applies to

LTL Operations Module 2022.2 and later

Description

Populates read only Appointment information into the Stops grid in ManifestEdit

String1

  • Y (default)
    Allows read-only Appointment information to be sent to the Stops grid in ManifestEdit

  • N
    Blocks population of read-only Appointment information into the Stops grid of ManifestEdit

String2

Use this field to determine what text to show in the labels for Appian Response maps.

LTLMultiUserApptsImport

Applies to

LTL Operations 2023.2 and later

Description

You can import appointments from the Appointments window on any terminal. Importing shortens the time it takes to create appointments. Formatting grid rows from an imported .CSV file is faster than adding appointment data manually.

When users add rows to the appointment grid view, their user login name attaches to the data. This shows which user added the data. Users can manipulate appointments with their login names.

Appointments imported from another system will not capture login names. This means users cannot view those appointments. This setting determines which appointments users can view.

String1

  • Y (default)
    Only the appointments created or imported by the user are visible.

  • N
    All appointments are visible to all users.

LTLOEMoveMgrOnNew

Applies to

LTL Operations Module 2018.1

Description

Use this setting to have LTL Operations Module communicate with TMW Operations. When you do, Move Manager creates freight detail records for each stop on an LTL order’s routing record. This allows you to open LTL manifests in TMW Operations.

String1

  • N (default)
    Communication between LTL Operations Module and TMW Operations is disabled.

  • F
    Communication between LTL Operations Module and TMW Operations is enabled. Move Manager creates freight detail record for each stop on an order’s routing records so that you can open LTL manifests in TMW Operations.

  • Y
    Communication between LTL Operations Module and TMW Operations is enabled.

LTLOrderClearedCustoms

Applies to

LTL Operations Module 2020.3 and later

Description

The Rail Drayage functionality lets dispatch processing include cross-border rail. This addresses customs clearance requirements associated with moving intermodal freight between the USA and Canada.

When you create a Rail Reservation, you specify a Customs broker stop and stop type. You do this by making entries in these fields:

* customs_cmp_id * customs_event_code

When a manifest is assigned to a Rail Reservation, the system inserts a stop based on your entries in these fields. The stop is created on the rail leg when it is created.

For manifests and orders that cross borders, Customs clearance/Broker validation checks are made.

Entries in different fields control whether validation takes place in different situations.

String1

Your entry in this field controls whether validation takes place.

  • A (default)
    Check when:

    • The order is assigned

    • The manifest departs a Terminal or Rail Terminal location

    • The manifest departs a Shipper or Consignee location

    • The dispatcher tries to send the Manifest to a Mobile Comm unit

  • L
    Check when:

    • The order status is set to Finish Loading

    • The manifest departs a Terminal or Rail Terminal location

    • The manifest departs a Shipper or Consignee location

    • The dispatcher tries to send the Manifest to a Mobile Comm unit

  • N
    Do not check

String2

Your entry in this field controls whether validation takes place when the order status is set to Deliver Enroute.

  • N
    The Customs clearance/Broker validation checks are not made when you click the Deliver EnRoute button.

  • Y
    The Customs clearance/Broker validation checks are made when you click the Deliver EnRoute button.

LTLPayCarrierByOrder

Applies to

LTL Operations Module V. 16.10.86 and later

Description

When an order is manifested to a pickup or delivery trip, the leg from the order routing is lost. The events are tied to the trip leg. This causes the Advance or Beyond carrier to be tied to the trip leg. For carrier pay, the carrier must be tied to the order.

Use this setting to have the system create an extra leg that links the carrier pay record to the order.

String1

  • N (default)
    Do not create an extra leg linking a carrier pay record to the order.

  • Y
    Create an extra leg linking a carrier pay record to the order.

LTLRateBy

Applies to

LTL Operations Module 2018.1

Description

Use this setting to specify the default rating mode used by LTL Order Entry when the Bill To has no Rate Mode set in its profile.

String1

  • D (default)
    Rate by Detail

    Each freight detail line is rated separately, based on the rate for the commodity.

  • T
    Rate by Total

    The rate is based on a sum total, such as weight or mileage, for all stops.

  • A
    Rate by aggregate

    Freight details are grouped by commodity class and charges are calculated based on the rate for the commodity class.

LTLServiceLevel

Applies to

LTL Operations Module 2018.1

Description

Use this setting to specify the default service level used by LTL Order Entry when the Bill To has no service level set in its profile.

String1

  • Blank, that is, no entry (default)
    No default service level is specified.

  • Any valid service level
    Your entry must match the Abbr field value of the level you want to use.

    Note: Your company defines the level options in the ServiceLevel label. You access the label in the TMW Operations application’s Edit User Definable Fields window. For details, see the TMW Operations help system.

LTLShiftAutomaticReopen

Applies to

LTL Operations Module 2020.3 and later

Description

Logging out of a shift causes a driver’s shift to shut down for that day. When a driver’s shift is shut down, you must reopen the shift manually to assign the driver to another load in the same day. Use this setting to have the system reopen a driver’s shift automatically when you assign a new load.

String1

  • N (default)
    You must reopen the shift manually before assigning the driver to a new load for that day.

  • Y
    The system reopens the shift automatically when you assign a driver to a new load for that day.

    Note: The system clears the Shift Shut Down check box in the Manifest Shift grid.

LTLShiftCheckSumStopApmts

Applies to

LTL Operations Module 2020.3 and later

Description

When a stop’s Scheduled Arrival Early or Scheduled Arrival Latest date is modified, the MobileComm solution sends the update to the driver’s handheld unit as a re-dispatch. Typically, a driver does not need this information. The change is made by the integration between TruETA and LTL Operations, not a dispatcher.

Use this setting to determine whether a change to a stop’s scheduled appointment time should cause a re-dispatch on MobileComm.

String1

  • Y (default)
    The system sends changes to a stop’s scheduled appointment time to MobileComm.

  • N
    The system does not send changes to a stop’s scheduled appointment time to MobileComm.

LTLShowMultipleApptsTab

Applies to

LTL Operations V.2022.4 and later

Description

This setting determines whether the Multiple Appointments tab is available in the Stop Appointment window when multiple stops are selected. On this tab, you can adjust times and reschedule appointments.

String1

  • N (default)
    The Multiple Appointments tab is not available.

  • Y
    The Multiple Appointments tab is available.

LTLSlottingSpecialHandling

Applies to

LTL Operations Module V. 2022.3 and later

Description

This setting determines how orders are assigned to manifests within LTL Operations.

String1

  • Blank; that is, no entry (default)

  • User-defined handling code
    Used to dictate automatic slotting of the order’s pickup stop

String2

  • Blank; that is, no entry (default)

  • User-defined handling code
    Used to dictate automatic slotting of the order’s delivery stop

String3

  • N (default)
    Orders are automatically assigned to a manifest via the LTL background service.

  • Y
    Orders can be assigned to manifests manually.

LTLStopTimeGroupingEvents

Applies to

LTL Operations Module 2020.2 and later

Description

Event codes identify the activity that occurs at a stop. You can create codes to record and identify a driver’s time. Use this setting to add the Break, Layover, and Wait Time codes for a stop.

The total time recorded for these types of events show in the Total Break Time, and Total Wait Time fields for manifests and trips. You access the fields from the Trips grid in the Terminal Pickups and Terminal Deliveries windows.

String1

  • BRK (default)
    Add the Break option to the Event Type field in the Status Change window

String 2

  • LAY (default)
    Add the Layover option to the Event Type field in the Status Change window

String 3

  • WAIT (default)
    Add the WaitTime option to the Event Type field in the Status Change window

Additional Notes

If you want, you can add other times to be included in the Total Break Time and Total Wait Time fields in Stop grids. For example, in the String1 field, you can have BRK,LUNCH. The system would add the driver’s lunchtime to the break time and display it in the Total Break Time field. Separate the options with commas. Do not enter any spaces.

LTLTripMnfstColorDomLegs

Applies to

LTL Operations Module V. 2022.3 and later

Description

This setting determines whether you can color Trips grid rows from the same domicile route for better visualization.

String1

  • N (default)
    Disallows coloring of Trips grid rows from the same domicile route.

  • Y
    Allows coloring of Trips grid rows from the same domicile route.

LTLTripMnfstInclLegsGrpID

Applies to

LTL Operations Module 2022.2

Description

The setting allows you to populate the legs_grp_id column in the Trips grid (for legs from the same domicile trip) to allow better visualization by color.

String1

  • Y (default)
    Allows population of the legs_grp_id column in the Trips grid to allow better visualization by color

  • N
    Disallows population of the legs_grp_id column in the Trips grid

LTLValidateAssetsOnTBLLDG

Applies to

LTL Operations Module 2021.2 and later

Description

When you change a manifest’s status to To Be Loaded or Loading, the system performs an asset validation. There may be times when do not know the trailer that will be used. Changing the status produces an error message. It states, "Trailer in use on Manifest #__". You cannot complete the status change.

Use this setting to control how the validation is handled.

Note: This setting applies only to the To Be Loaded and Loading statuses.

String1

  • Y (default)
    The system performs an asset validation. If an error occurs, you cannot save the status change.

  • N
    The system does not perform an asset validation.

  • W
    The system performs an asset validation. If an error occurs, you can save the status change.

MobComSingleManifestDisplay

Applies to

LTL Operations 2023.2 and later

Description

This setting changes the manifest display on mobile devices when LTLCheckSumShiftless is set to N.

String1

  • Y (default)
    Only the first manifest in the sequence for one driver with the same tractor for the same shift appears. Pending manifests do not appear.

  • N
    All manifests for one driver with the same tractor for the same shift appear. Only the active manifest can be manipulated.

RateWareXL

First available in

TMWSuite: 2009.08_08.0312, LTL Operations Module: 2018.1

Description

This setting applies to TMW clients who have RateWare XL accounts with SMC3 and who have purchased TMW’s RateWare XL interface. It activates the interface and is used to record the RateWare XL user name, password, and license key. Entries are required in the String1 - String4 fields.

String1

An entry in this string determines if the interface is active.

  • N (default)
    The RateWare XL interface is not active.

  • Y
    The RateWare XL interface is active.

String2

If String1 is set to Y, enter your Rateware XL user name.

String3

If String1 is set to Y, enter the RateWare XL password (case sensitive).

String4

If String1 is set to Y, enter the RateWare XL license key.

RowSecurity

Applies to

TMWSuite: 2008.07_08.0637 and later; TMW.Suite 14.20 and later

Description

This setting activates the Row Level Security (RLS) feature. RLS lets you secure records on a user level. For example, you can apply security to records belonging to specific companies, divisions, or terminals. It limits access so that only users or groups assigned to them retrieve their records.

Starting with V.2022.1, if you use RLS, you can also restrict access to field options defined in the Edit User Definable Fields window. You specify which options a user can select in fields that have security applied to them.

String1

* N (default)
User-level security is not applied. Field option filtering is not available.

* Y
User-level security is applied. If field option filtering is set up, it is applied. + You define the security in the Row Level Security Setup window. You assign security to users in the Row Level Security Assignment window. If you want, you can turn on field option filtering in the setup window.

String2

First available in TMW.Suite and CRMRight, V.14.20.

If the String1 field has a value of Y, the system automatically applies a table’s security to its instant best match fields. Instant best match fields include:

  • Carrier

  • Company

  • CRM Work Company

  • Driver

  • PayTo

  • Third Party

  • Tractor

  • Trailer

If you want, you can have security applied to instant best match fields on a case-by-case basis.

  • Y (default)
    Security is applied to all instant best match fields.

  • N
    Security is not applied to all instant best match fields.

    Note: When you use this option, you can apply security to individual fields. You use QuickDesigner to set it up. In each application window, you set the field preferences for the instant best match fields. If you want security applied, you set the TMW Properties section’s UseRowLevelSecurity option to True. See Applying security to fields in the application’s online help for instructions.

Note: As of V.2022.1, RLS functionality lets you filter the field options users can see in drop-down lists. It is based on the Labelkey field you select in the Row Level Security Setup window. Label filtering does not affect security set up for instant best match fields.

+

Additional Notes

Row Level Security is a licensed add-on module. For more information, contact Trimble Sales.

SmtpEmailer

Applies to

TMWSuite, CRM Right, TMW Operations, TMW Back Office

Description

Use this setting to provide information the system needs to send reports and free form messages using SMTP e-mail. SMTP allows you to send reports/messages to recipients outside your company’s network securely.

  • In TMWSuite
    You can send integrated reports.

  • In TMW Operations
    You can send load confirmations from the Brokerage add-on module.

  • In TMW Back Office
    You can send invoices and settlement sheets.

  • In CRM Right
    You can send e-mails to contacts.

String1

Identifies the SMTP server.

  • Blank, that is, no entry (default)
    No e-mails will be sent using an SMTP e-mail server.

  • SMTP e-mail server address
    E-mails will be sent using the identified SMTP e-mail server.

String2

Provides the reply address for e-mails sent from within TMW applications.

  • Blank, that is, no entry (default)
    No reply address will be available for e-mails sent using a SMTP e-mail server.

  • Enter the e-mail reply to address
    Reply e-mails will be sent to this address.

    If you want all replies to go to a single address, enter that e-mail address. If you do not provide an optional reply address, the system will use the e-mail address of the logged-in user.

Notes:

  1. TMW Operations does not use this string. Each user using SMTP e-mail must have an e-mail address defined in his/her user profile.

  2. CRM Right requires an entry in this field.

String3

The String3 and String4 options work together to provide a user name and password to the SMTP server.

Note: If your SMTP server is set up to use Windows authentication, no entry is required in String3 and String4.

  • Blank, that is, no entry (default)
    No SMTP server user ID is provided.

    Unless your SMTP server is set up to use Windows authentication, e-mails will not be sent by the SMTP server.

  • User ID for the SMTP server
    When you click in this field, the SMTP Authentication Credentials window opens. Enter the SMTP user ID and password in this window.

    Notes:

    1. An entry in this field causes the [Misc]SMTPServer INI setting to be ignored.

    2. Once a value is set, you cannot clear entries in this field. If you no longer need to use this field, contact your TMW customer service representative.

String4

The String3 and String4 options work together to provide a user name and password to the SMTP server.

Note: If your SMTP server is set up to use Windows authentication, no entry is required in String3 and String4.

  • Blank, that is, no entry (default)
    No SMTP server password is provided.

    Unless your SMTP server is set up to use Windows authentication, e-mails will not be sent by the SMTP server.

  • Password (encrypted) for the SMTP server
    When you click in this field, the SMTP Authentication Credentials window opens. Enter the SMTP user ID and password in this window.

    Notes:

    1. The system encrypts your password when you save your changes.

    2. Once a value is set, you cannot clear entries in this field. If you no longer need to use this field, contact your TMW customer service representative.

Int1

Determines whether Secure Sockets Layer (SSL) authentication is active.

  • 1 (default)
    The system enables SSL authentication when sending e-mails in CRM Right or TMW Back Office.

    Note: The SMTP server must support SSL authentication for this setting to function correctly.

  • 0
    The system disables SSL authentication when sending e-mails in CRM Right or TMW Back Office. Instead, it uses the entries in String3 and String4.

Note: TMWSuite and TMW Operations do not support this field.

Int2

Determines whether the SMTP server uses Windows authentication when sending e-mails in CRM Right.

  • 0 (default)
    Windows authentication is not used by CRM Right.

    Instead of using Windows authentication, CRM Right uses the entries in String3 and String4.

  • 1
    Windows authentication is used by CRM Right.

    Note: You can use this field to enable/disable Windows authentication for CRM Right, or you can use it for the SMTP server port number. However, TMW recommends using Int3 for all port numbers instead of Int2.

Int3

Specifies the port used by the SMTP server.

  • Blank, that is, no entry (default)
    Uses the default SMTP port 25.

  • User-defined number
    User-defined numbers indicate the SMTP server’s port number.

Int4

First available in TMWSuite: 2019.4

In TMWSuite, determines whether Secure Sockets Layer (SSL) authentication is active.

  • 0 (default)
    The system disables SSL authentication when sending e-mails in TMWSuite.

  • 1
    The system enables SSL authentication when sending e-mails in TMWSuite.

    Note: The SMTP server must support SSL authentication for this setting to function correctly.

Note: This setting affects only TMWSuite.

Additional Notes

  1. When Integrated Reporting was first introduced, the [Misc]SMTPServer INI setting was used to send integrated reports and free form messages from within any TMWSuite application.

  2. Fuel Dispatch does not support this setting.