2019.4

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.4, 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, SQL Server 2016, and SQL Server 2017 are supported. Trimble Transportation 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

Accessing the new Learning Center (NSUITE-208173)

You now have access to the new Learning Center when you select Help from the main menu.

Splitting a split order (NSUITE-204079)

The new cross dock split order edit functionality allows you to edit an existing split order. The functionality is useful for scenarios where an operational decision is made to change the destination of one of the splits. For example after the order is split at the origin, split 1 may be routed to a hub terminal and split 2 may be routed to the destination terminal.

Using QuickDesigner to change the Advanced Search window layout (207458)

Previously, you were unable to change the layout of the Advanced Search window. Now, you can use QuickDesigner to change the window’s layout in these windows:

  • Order Entry

  • Manifest Edit

  • Invoice Entry

  • Equipment Edit

  • Tariff Profile

The editing functionality is only available when you first open the widow. Then follow these steps:

  1. Right-click and select Toggle QuickDesigner.

  2. Select Show hidden controls from the menu.

  3. When the Search tab opens, make changes as needed and then click Save.

Resolved issues

Appointments

  • NSUITE-206304

    Fixed the issue where opening the Appointments window from an order resulted in fields missing from the window.

  • NSUITE-207890

    Fixed the issue where a user could not book an appointment in LTL operations. The following conditions applied:

    • TL sourced order had a leg pushed to LTL operations

    • The LTL manifest and orders were created

    • The LTL manifest and orders were then cancelled due to plans changing

    • The LTL manifest and orders were then re-created

    • A database Concurrency Error message appeared.

Company Profile

  • NSUITE-208161

    Fixed the issue where the Process Imaging button did nothing when the Company Profile for the BillTo was set to No Output.

Deliveries

  • NSUITE-204076

    Fixed the issue where changing the linked LTL order delivery stop to DRL did not update the stop in TL Operations.

  • NSUITE-208185

    Fixed the issue where the inbound Trailer ID was incorrect for TL Turnpike Doubled LTL Manifests.

  • NSUITE-208197

    Fixed the issue where the DLD/DUL defaults were applied properly in all scenarios except for missed deliveries.

Dispatch

  • NSUITE-207875

    When tendering loads to a rail carrier for an interchange piece of equipment, the system did not validate that the required information was on the Equipment profile. This issue was fixed.

  • NSUITE-208117

    When a trailer was assigned to the pickup event in LTL Operations, the trailer number appeared on all stops in TL Operations, including those occurring after the HCT event. This was incorrect since the HCT represents the change from one trailer to the next. This issue was fixed.

Doors

  • NSUITE-208222

    The Finish Trailer Storage button in the Doors window on a Loaded Trailer Storage Manifest did not work correctly.

EDI

  • NSUITE-208217

    Fixed the issue where the updates were not processed by DX when the original 204 New was handled by LTL.

  • NSUITE-207886

    Fixed the issue detected in the current Shaw Mobile integration.

Invoicing

  • NSUITE-207835

    When we export to Great Plains, either AR (from invoice queue) or AP (from carrier queue), the system generally exports many rows at a time. Hence, the system does not receive immediate feedback if some of the records are rejected by Great Plains (for example, invalid customer/vendor or invalid GL account number). Rather, the rejected records do not have their status changed; so the user knows there is an issue (for rows that do not disappear from the pre-export status section of the grid), but they do not know the nature of the issue. In both AR and AP, the system logs the error messages received from Great Plains to the expedite_audit table. For AR, the system displays these in the Audit tab in Order/Invoice Entry. However, for AP, the system does not display the expedite_audit rows anywhere. These issues were fixed.

  • NSUITE-208151

    Fixed the issue where invoices transferred to Microsoft Dynamics GP did not get ivh_xferdate set if there was no associated order, for example an f-bill.

  • NSUITE-208171

    Made changes to prevent releasing an invoice that is part of a consolidation if any other invoice in it has an error. This fix also applies to transferring invoices to Microsoft Dynamics GP.

Manifests

  • NSUITE-207541
    Fixed the issue where redundant manifests were created under the following interop / turnpike scenario:

    1. Two TL orders had pickup legs pushed to LTL.

    2. Mid way through completion of the corresponding LTL manifests, the two orders had subsequent legs placed on a turnpike.

    3. The turnpike creation caused redundant pickup manifests for the TL orders. These manifests were different from the manifests used to perform the pickups in LTL. They remained in an open status after the (original) LTL manifest was completed.

  • NSUITE-207863

    Fixed the issue where freight details were missing when multiple orders, with the same Consignee, were Delivered Enroute on the same manifest.

  • NSUITE-207865

    Fixed the issue where attempting to push a manifest more than one day in the future caused an error message. It indicated that no active shift was found, even though one existed.

  • NSUITE-207924

    Fixed the issue where offloading freight from a trailer moved as a turnpike did not complete the LTL Crossdock Unload (XDU) events.

  • NSUITE-208140

    Fixed the issue where some leg header fields that contain information about the assigned trailers, were not always populated with the correct values from the Trailer Profile. These fields include:

    • trl_company

    • trl_fleet

    • trl_division

    • trl_terminal

    • trl_type1

    • trl_type2

    • trl_type3

    • trl_type4

  • NSUITE-208164

    Fixed the issue where the trailer status did not change from Planned to Loaded when an HPL stop was completed.

  • NSUITE-208172

    Fixed the issue where processing manifests in Mobile Comm and LTL Ops prevented the next manifest in line from being pushed to the Shaw unit.

  • NSUITE-208185

    Fixed the issue where the inbound Trailer ID was incorrect for TL Turnpike Doubled manifests.

  • NSUITE-208193

    Fixed the issue where a duplicate ManifestDetail record was created for LTL Item Level Details. This issue only appeared for the Delivery Manifests created by the TL Turnpike Double process.

  • NSUITE-208243

    When an HPL Pickup Order with an Appointment was assigned to a newly created Manifest with an inserted DMT stop at the order’s Shipper, the dates on the HPL event Start/End dates were set to 01/01/0001 00:00:00 and 12/31/9999 23:59:59.

    The issue did not occur when there was no appointment on the order. It only occurred on the first assignment. If the order was removed or reassigned, the problem was resolved.

Miscellaneous

  • NSUITE-207893

    Fixed the issue where in the generic Checkcalls() function, the date of processing needed more granularity.

  • NSUITE-207984

    Fixed the issue where the rest point only returned manifests for which the driver had completed all assigned stops, except the RTT, within the hours specified.

  • NSUITE-207985

    Fixed the issue where the field length imposed on the Optional Zones field was inadequate. This limitation prevented the YMT service from communicating optional zones to a driver.

  • NSUITE-207986

    Fixed the issue where the Move to door option was not enabled.

  • NSUITE-208131

    Fixed the issue where duplicate errors showed for a failed search in the Turnpike Double Edit window.

Mobile

  • NSUITE-207867

    Fixed the issue where the message, "Last Stop Completed, No Work Assigned," was issued after the RTT was received on the driver’s unit.

  • NSUITE-207919

    Fixed the issue where driver handheld devices were sending duplicate messages to dispatchers

  • NSUITE-207985

    Fixed the issue where the field length imposed on the Optional Zones field on the handheld device was inadequate. This limitation prevented the Yard Management Tool service from communicating optional zones to a driver.

  • NSUITE-208111

    Fixed the issue where you were only able to golden state the first stop on a leg but not the second. This occurred when a manifest began at the child terminal, ended at the parent terminal, and had multiple legs in between.

  • NSUITE-208132

    When a driver was assigned to a Thread number greater than the Max Thread number, the manifest could be pushed to the handheld, but any changes to the manifest after the initial push were not picked up.

  • NSUITE-208139

    At times, the pickup order did not include the state/province value, which prevented the stop from getting to the driver’s unit.

  • NSUITE-208202

    When an HPL event occurred on the same stop as a drop empty; and was completed using the handheld; the Depart Shipper EDI214 transaction was not being sent out. This only occurred when the handheld was used.

Order entry

  • NSUITE-206181

    Fixed the issue where Order Entry did not comply with Company Profile Default Event Codes.

  • NSUITE-207864

    Fixed the issue where records in the LTL order notify table were pointing to an event number that no longer exists.

  • NSUITE-207876

    Fixed the issue where depending on setup, the system was not calculating freight detail volume in Order Entry correctly.

  • NSUITE-207884

    Fixed the issue where users were unable to edit a multi-split order once it was created.

  • NSUITE-207885

    The Edit Split window showed duplicate item details after a split was made, cancelled, and then re-split. This prevented editing on any ss-split orders.

  • NSUITE-207887

    Fixed the issue where Order Notify records were orphaned on Multi-Order Direct Delivery and Deliver Enroute scenarios.

  • NSUITE-207980

    Fixed the issue where the freight volume calculation was incorrect due to an item edit-timing issue.

  • NSUITE-208136

    Fixed the issue where the order header’s Order Trailer Type 1 field did not populate with the value from the assigned trailer’s profile.

  • NSUITE-208158

    Fixed the issue where you could save an order after deleting the City/Prov field value in either the Shipper or Consignee Information sections. This issue does not occur when you use keyboard keys to enter an order.

Routing

  • NSUITE-207868

    Fixed the issue where using the Remove Deliver Enroute functionality on a multi-order stop corrupted routing. This issue also affected Remove Direct Delivery.

Terminal Profile

  • NSUITE-204344

    Fixed the issue where the Search field on the Users tab in the Terminal Profile did not work.

Turnpike Double

  • NSUITE-207926

    Fixed the issue where undoing a turnpike double, after opening and closing the Turnpike Double Edit window, caused an error.

  • NSUITE-208207

    Fixed the issue where LTL Finish Load created a false positive error message when:

    • Two TL orders were Turnpike doubled together

    • LTL handled both the Pickup and Delivery legs