2019.3

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

We have updated our company name and logo to the Trimble brand.

Before upgrading your production environment, Trimble Transportation recommends that you read the system requirements and install the latest version in a test environment. If you have questions, please contact your Customer representative.

Requirements

Before you begin installing LTL Operations Module version 2019.3, check that these requirements are met:

  • TMWSuite®

    You must be using TMWSuite V.2018.18_01.0192 or later.

  • Microsoft® .NET Framework

    NET Framework 4.6.2 or later (full package not client)

    The framework must be installed on the LTL Operations Module server, client, and administrator systems before you install LTL Operations Module. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Internet Information Services (IIS) for Microsoft® Windows Server®

    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft® SQL Server®

    Microsoft SQL Server 2012 or later

    Note: SQL Server 2014 and SQL Server 2016 are supported. Trimble recommends using the latest service pack of whichever version you use.

  • You must be logged into the system where you want to install LTL Operations Module, and have administrator rights for that system.

    Like most applications, LTL Operations Module can be installed locally on a user’s system. It is also possible to install LTL Operations Module on a network drive. To do so, you must be logged into the system where the drive is physically located, and have administrator rights for that system.

  • SQL Server System Administrator rights are necessary.

    The installation of LTL Operations Module includes the manual application of a SQL script to the TMWSuite database. You must have a SQL Server administrator login and password to apply it.

Enhancements

General

Add Default Drop At Dock check box to the Zones tab in Terminal Profile (NSUITE-207459)

On the Terminal Profile window’s Zones tab, we’ve added tje Default Zone/Area or Yard check box. You can use it to identify default selections.

Note: Setting a default selection is optional. You may leave the check box cleared for all rows.

You may select only one of the yard types and only one of the other types as defaults. Zone and Staging Area types are used interchangeably within the application.

A staging area is similar to a zone, but it is associated with a door. A staging area is a sub-classification of a zone. Other areas that are not associated with a door, like cold storage, would are only zones. If the check box for a yard zone is selected and you select a second one, the check box for the first yard zone is cleared automatically. This functionality is similar for zones and staging areas.

  • Scenario #1

    If you have only one applicable zone set up, it appears in the drop-down field for the zone by default.

    If you have multiple applicable zones set up and you do not set any as the default, the field is left blank. You are required to choose from the drop-down list. When you do set a zone as the default, the drop-down field is initially set to that value when the window opens. If you want, you can make a different selection.

    This change is available

    • For Yards, in the Cross Dock, Pickups, and Delivery windows' Stops tab, when you use the Return to Terminal or Drop Crossdock Trailer commands and then click the Arrive button and select Dock All Freight

    • For Zones and Staging Areas, in the Order Entry window’s Stops tab, when you use the Drop At Dock command

  • Scenario #2

    If you set up only one zone, the default check box feature is not applicable.

    If you have multiple applicable zones set up, with or without a default, the same zone will always be used. In both cases, the zone may not always be the correct one, but with a default, you can choose the one that is accurate more often than the others are.

    This change is available for Yards:

    • In the Rail Reservations window’s Status Update tab, when you use the Arrive command.

    • In the Work window, when you use the Dock Freight command

    • When an EDI 214 record is processed for an Empty Arrive Terminal stop

    • On the Stops tab in the Cross Dock, Pickups, and Deliveries windows when you make an entry in the Status change window to select the yard that is used.

    This change is available for Zones and Staging Areas:

    • In the Order Entry window when you create a new On Dock order.
      It is also available when you set the Drop At Dock or Return to Shipper options for orders copied using the Advanced Copy command.

    • In the Doors and the Work windows, when you use the Move to Door command

    • On the Stops tab in the Cross Dock, Pickups, and Deliveries windows when you use the Refused Delivery command when marking LUL stops as Departed

    • In the TruckLoad Moves window, when you create a TL/LTL Manifest for moves other than pickups

Default a drop-down’s selected item if there is only one choice (NSUITE-207460)

When a drop-down menu had only one option available from which to choose, you had to click a couple of times to select the option. Now when only one option exists, the system selects it by default.

LTL Currency Conversion Maintenance (NSUITE-207457)

The Tools menu now includes the Currency Conversion command. It opens the Back Office Currency Conversion Maintenance window, where you dentify currency and exchanges rates. This feature is beneficial when using an installation that uses multiple currencies or if you are using the LTL application as a stand-alone product.

LTL EDI Service: Config Screen + Security Enhancement (NSUITE-207462)

An LTL EDI Services Configuration window is now available after you install the application. It is modeled after the existing window used by the LTSL2 services. This feature can enhance security on the LTL EDI Service because it does not store the EDI login information in a plain text configuration file. Using this feature allows you to access the Service Configuration window.

Miscellaneous

New License to make the LTL generic MobileComm API publishable (NSUITE-210248)

The LTL generic MobileComm API is now a licensed feature (TMWLTLMOBCOMMAPI license). It applies to LTL versions 2019.3 and later.

For information on purchasing the license, contact Trimble Support.

Resolved issues

Appointments

  • NSUITE-206373

    The core Appointment functionality in LTL has a dependency on manual setup of one of the system code label files, which is automatically created by the application DB mods. The label file must have the value Complete in order to perform the Appointment Made functionality. Now the system label file is configured in the DB mods so that the Appointments functionality works immediately.

Dispatch

  • NSUITE-207560

    Fixed an issue that caused order routing corruption. When the following were completed in the system, the routing on the order was corrupted.

    1. The order was cut with a relay terminal point

    2. The order was assigned to a line haul manifest with manifest origin and final destination matching the order

    3. The manifest was split at the relay terminal within the order

    4. The manifest was loaded to go and departs origin

    5. The consignee code and destination terminal for the order were changed

    6. A (new) error message appeared indicating that the change could not be done as the order was assigned to a line haul manifest. As implemented under TRX 1798.

      The routing of the order was affected when the user acknowledged the error message. It appeared that the newly added error was not a full stop and a component of the re-routing code still attempted to re-calculate the order routing. As a result, a glitch occurred in the order routing and it could not be fixed by a user.

  • NSUITE-207654

    Fixed the issue where a missed delivery caused routing to be corrupted.

Front Office

  • NSUITE-207621

    Fixed an issue where a leg was deleted after asset assignment in TMW Operations.

General

  • NSUITE-204323

    When tendering a manifest to a rail carrier via 404 EDI with a piece of interchange equipment, (trl_type1 = INTRCG) the system did not validate that all of the necessary equipment profile fields were populated. Previously you could tender the load without setting up all required equipment parameters. This caused a rejection by the rail carrier and a fine was charged to TransX.

  • NSUITE-207610

    Fixed an issue where RTT was not available to send to a driver under a multi terminal scenario.

  • NSUITE-207727

    Fixed the issue where a user attempted to 'export accrual' from the carrier queue but the system did not complete the export nor provide any feedback as to why.

Interoperability

  • NSUITE-207430

    Fixed the issue where the user cannot assign a trailer to LTL Manifests after they were turnpike doubled together in TL. This only seems to happen on Split Leg Manifests.

  • NSUITE-207483

    When an LTL movement with an empty manifest was used to create a turnpike double, the stp_number_start field in the manifestheader table was sometimes set to the wrong value, depending on how the moves used to create the turnpike double were set up. This caused a failure in trailer rippling within LTL as documented in NSUITE-207430.

    This issue has been resolved.

  • NSUITE-207484

    When an LTL movement with an empty manifest was used to create a turnpike double, the BBT/EBT stops remained BBT/EBT stops after the turnpike double was created. These stops needed to be changed to BMT/EMT. This issue was causing a trailer rippling problem as documented in NSUITE-207430.

  • NSUITE-207534

    Fixed an issue that was found with the communication of Stop arrival/departure date/time statuses between LTL Ops and TL Ops when TL orders contain a turnpike move.

  • NSUITE-207747

    Fixed an issue where Leave on Trailer could not be used on a Turnpike Doubled TL order due to a False Positive thrown during error checking.

Invoicing

  • NSUITE-207396

    Fixed the issue that limited the options for LTL’s Invoice Queue.

    Applied the Back Office Advanced Output feature to LTL’s Invoice Queue.

    Changes include:

    • In InvoiceQueueControl.FilterPrintOrEDI (method that determines which subset of the user-selected invoice may be printed or edited) used the back office Advanced Output logic instead of column company.cmp_edi210.

    • Replaced the Distribution Method filter (based on old cmp_edi210) with a Distribution Configuration filter.

    • Added Invoice Kind and Invoice Terms to the filter section (both are filtering options in output configurations).

    • Added Invoice Terms to the grid (one of the filtering options in output configurations).

  • NSUITE-207725

    Fixed the issue where reference numbers related to invoice details could not be changed after the grid was locked down.

LTL Setup

  • NSUITE-206240

    Fixed the issue where the LTL Setup window’s Incompatibilities' subtab Commodity did not display commodity incompatibilities as expected.

  • NSUITE-206284

    Fixed the issue that caused the UNKNOWN value to show twice in the Rev Type 1-4 fields in the Filter section of the Edit Auto 214’s on Hold tab.

Manifests

  • NSUITE-207523

    Fixed an issue found with the unloading process for a manifest, which was moved as a turnpike double.

  • NSUITE-207602

    Fixed an issue where using the Leave On Trailer option for a split leg order, which leaves freight on the trailer at the split location, flagged the linehaul manifest as complete.

  • NSUITE-207609

    Fixed an issue where the Manifest’s Stops tab grid in cross-dock/etc. allowed selection of a dolly in the Trailer and Chassis fields.

  • NSUITE-207622

    Fixed an issue where an LTL Manifest reverted to Not Complete when an asset assignment was modified in TMW Operations

Mobile

  • NSUITE-208240

    Fixed the issue where executing a DMT/HLP split stop with an Appointment, caused an error to occur when the EDI214 pending record was created.

Order entry

  • NSUITE-106586

    Fixed an issue in the Order window’s Invoices tab that occurred when modifying a reference number in the Reference field. The number disappears when saving the changes on the order.

  • NSUITE-106587

    Fixed an issue involved with copying two or more orders using the Advance Copy window. The system prompts the user to save the original order after it completes the copying process.

  • NSUITE 207432

    Fixed the issue that caused the Bill To/Shipper/Consignee instant best match data entry feature to disregard the Switches options that were set up in Company Profiles. For example, if you cleared the Shipper check box in the Switches section of a company profile, that company’s ID would still show as a match when looking up a company in the Shipper Information section on an order.

  • NSUITE-207601

    Fixed an issue where after creating a new order, you could not use the Reroute button on the Order Routing tab. This was due to an error message that was added recently to stop routing corruption in certain scenarios.

  • NSUITE-207692

    When dealing with an Empty Park/Hook stop in Ops, the stops.stp_empty_split flag was set to determine if there was a multi leg scenario.

    LTL does not use the field but needs to add it.

    The default value for all stops is now 0 (stp_empty_split)

    With respect to a split leg:

    • If the stops are empty, set stp_empty_split 1

    • If the stops have orders: leave stp_empty_split = 0. A code change is not required.

    • When assigning an order to a Split leg, set stp_empty_split = 0

  • NSUITE-207719

    Fixed the issue where freight details were being doubled when merging split bills at a relay terminal.

Terminal Profile

  • NSUITE-207624

    Fixed an issue where the Load Plan Service, Day of the week, functionality was not always applying the best/correct load plan.

Trip Folder

  • NSUITE-207533

    Fixed the issue where Turnpike creation resulted in the duplication of order (freight) and event data.

Turnpike Delivery

  • NSUITE-207245

    When a pre-existing turnpike delivery movement was used to create a subsequent turnpike double, and the pre-existing turnpike double’s split location matched the new turnpike double’s merge location, the system created a movement shared by both turnpike doubles with redundant hook/drop stops at that location. Because of the redundancy, the system should not have created this movement. This issue is resolved as of this release.

    Note: If the split/merge locations are not the same (i.e. no redundancy), then the shared movement should be created.