2018 LTL Operations Module Release Notes

These release notes give high-level summaries of product updates and resolved issues.

If detailed user documentation exists for a feature, a link to the help topic is included.

If a video exists for a feature, a link is included.

A PDF version of these release notes is available here.

2018.4

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

Requirements

Before you begin installing LTL Operations Module version 2018.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 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

No new enhancements.

Resolved issues

Dispatch

  • NSUITE-203937
    Fixed an issue where the Assignment History in TMW Operations does not display accurate truck assignments. For some of the legs, it displays a different tractor number than the one that is assigned.

  • NSUITE-203940
    Fixed the shift overlap issue with a manifest and the user tries to push it to the handheld unit, LTL will prevent that manifest from being sent. Unfortunately, the user is not told why the manifest was not sent nor how to correct the issue. Instead, the manifest stop remains in the golden state.

  • NSUITE-204053
    Fixed an issue where the Crossdock tab’s Reroute functionality can be used to reroute orders on a route, which do not follow any valid load plans.

  • NSUITE-204061
    If the leg start dates of a rail manifest are out of sequence, the user can set a delivery order to deliver on route. However, the user cannot undo the deliver on route. The error message presented is not descriptive of the issue.

  • NSUITE-204102

    • Issue 1
      When a manifest is pushed to the handheld and a chassis is added after the stops have been pushed, but prior to completion; the chassis does not appear in the hook and drop forms on the handheld.

    • Issue 2
      When the driver at a trailer pick stop via the handheld adds a chassis, the chassis number is not updated in LTL Operations Module. Additionally a new stop is added to the handheld for the chassis pickup, which does not correspond with LTL Operations Module.

  • NSUITE-204126
    Fixed an issue where a hook pre-loaded order is assigned to a straight truck by accident, the manifest disappears from the pickups window. These prevent the current manifest, and future manifests, from being pushed to the drivers handheld.

  • NSUITE-204130
    Fixed an issue with handheld stop push error checking. When a user attempts to push a stop to the handheld and the stop requires an appointment, which has not yet been booked, a non-descriptive error message appears under select scenarios only. This message does not indicate which stop is missing the appointment.

  • NSUITE-204131
    Fixed an issue where the appointment Status gives an undesired change upon assignment of the order to a manifest. A HPL order requires an appointment and the appointment has not yet been booked, a manifest is set up with a pre-assigned Drop Empty at the same location as the HPL. The HPL order is then assigned; however, the appointment status of the HPL order is changed from Need Scheduling to UNKNOWN. This removes the order from the appointment queue.

  • NSUITE-204135
    Fixed the issue the logic used to assign and un-assign a chassis based event codes does not function as expected under the following scenario. This does work as expected with Trailer/Container event codes just not with Chassis.

  • NSUITE-204141
    Empty Trailer Drop Order Scenario Issue:

    • Issue 1

      • An empty trailer drop order is created.

      • The empty trailer drop order is assigned to a manifest.

      • The consignee of the order is changed.

      • When this occurs the last stop of the manifest changes to the consignee code, not the terminal. The return to terminal stop is missing from the manifest.

    • Issue 2

      • An empty trailer drop order is created.

      • The empty trailer drop order is assigned to a manifest.

      • The shipper of the order is changed.

      • When this occurs the first stop of the manifest changes to the shipper code, not the terminal. The return to terminal stop is missing from the manifest. This manifest cannot be pushed to the handheld.

  • NSUITE-204142
    Empty Trailer Drop Order Scenario Issue:

    • Issue 1

      • An empty trailer drop order is created.

      • The empty trailer drop order is assigned to a manifest.

      • The consignee of the order is changed to the terminal.

      • When this occurs the terminal stop is duplicated on the manifest. Once as a Drop Empty, again as an End Bobtail. When the manifest is processed via the handheld, the first return to terminal stop cannot be pushed to the handheld.

    • Issue 2

      • An empty trailer drop order is created.

      • - The empty trailer drop order is assigned to a manifest.

      • - The shipper of the order is changed to the terminal.

      • When this occurs the terminal stop is duplicated on the manifest. Once as Begin Empty, again as an Hook Empty. The manifest cannot be processed thru the handheld.

  • NSUITE-204274
    Fixed an issue when a relay terminal attempts to LOT orders going to different destinations, the LOT process docks all of the freight on the manifest. Electronically docking the freight will lead to lost shipments. The system must generate an error message and stop the LOT process. This will allow the user to re-route the shipments to the same terminal.

  • NSUITE-204856
    Fixed an issue where a driver’s handheld completes a trailer pick stop and the trailer does not show at the company location, it creates a beaming violation LTL business exception and the HH can’t continue.

  • NSUITE-205370
    Fixed an issue where completing a DRL type stop on the HH, the dimensions are being cleared (length, width, and height) and re-rating is occurring. As a result, if the rate was based on dimensions/cube, then the re-rate will likely use a weight based tariff. The dimensions should not be cleared when completing a DRL type stop.

  • NSUITE-205644
    Fixed an issue where the driver has a shift from day prior that has not been shut down. System allows for push of manifest for today’s shift without notification that a shift from prior day not shut down.

  • NSUITE-205674
    Fixed an issue where the commodity was not updating correctly on handheld devices after being changed on the order.

  • NSUITE-205689
    Fixed an issue where the order reference number masking was ignoring the second mask.

  • NSUITE-205696
    Fixed an issue where a discrepancy occurs when an inbound line haul manifest has arrived at the delivery terminal with an order status of To Be Unloaded, Unloading, or Docked.

EDI

  • NSUITE-204148
    Fixed an issue with the EDI 214 Hold Queue. It was displaying incorrect event codes for the events, which triggered a 214. The EDI status itself was created correctly.

  • PB-200263
    Fixed an issue with the EDI 214 using the wrong reason code when actualizing a stop.

Intermodal

  • NSUITE-204759
    Fixed an issue with the Intermodal Scenario I7. An issue was found where the LTL application locks up (freezes) when the following step of the scenario is performed. The user must terminate the application and re-start to resume work. When assigning the terminal driver to the outgate drayage leg; the leg start date does not match the shift date, the user will be prompted to modify the leg start date to match the shift. When this prompt is accepted, the system locks up. This issue only occurs under rail scenarios that had a prior drayage leg completed in TMW Operations.

Invoicing

  • NSUITE-107084
    Fixed an issue where the currency conversion being used on LTL invoices was being multiplied instead of divided by the correct factor. As a result, the functional currency amount on all LTL invoices transferred to GP in the foreign currency is incorrect and the batch could not be posted.

  • NSUITE-107118
    Fixed an issue where the client is transferring F-Invoices to GP that fail.

  • NSUITE-203847
    Fixed an issue where the Set Validation in Invoicing Queue does not display error messages or indicates invoices that are at issue.

  • NSUITE-204214
    Fixed an issue where an order is missing either a PUP or DRP event due to bad routing, the order does not appear in the Billing Queue in LTL.

  • NSUITE-204731
    Fixed an issue when creating credit memos and rebills that a number of the credit memos are not pulling in GL numbers for the invoice details. This caused issues with trying to get them transferred into GP.

  • NSUITE-204932
    Fixed an issue where auto creation of items is causing the cube calculation to compute incorrectly. This is causing customers to get over and under billed causing the client lost revenue. When a pickup is processed via a handheld and the driver updates the weight or dimensional information via the handheld, similar issues happen to the volume figures in the LTL ops order.

Manifests

  • NSUITE-204210
    Fixed an issue with the rail 404 preferred customer flag issue.

  • NSUITE-204128
    Fixed an issue when pushing work to the handheld, a warning message appears if the driver has higher priority manifests on their shift. However, this warning message appears for each manifest on the shift. If a shift has 6 - 10 manifests, the pop up message appears 6-10 times.

  • NSUITE-204132
    Fixed the Assignment of Partial Appointments to a manifest issue. A pickup appointment is booked with two (or more) orders and a local manifest is in progress, one of the pickup orders on the appointment is assigned to the in progress manifest, the other is omitted by the dispatcher

  • NSUITE-204269
    Fixed the issue where the status of a trailer being used on a Trailer Storage manifest is inaccurate at various stages.

  • NSUITE-205361
    Fixed an issue where split manifests are not correlated to any specific scenario.

  • NSUITE-205650
    Fixed an issue where the system allowed you to push a manifest with out of service equipment to the handheld.

Mapping

  • NSUITE-204502
    Fixed issues with the way maps function in LTL Dispatch.

    • Issue 1

      When the map is undocked it no longer shows the correct data once the user makes a new selection (the map works fine when docked).

    • Issue 2

      The Tractor selection check box does not work properly. The user can select data in the lower part of the screen (select different tractor(s)). When refreshed the map does not show the proper data based on the user selection.

Paperwork

  • NSUITE-204411
    Fixed an issue where paperwork requirements do not match between TMW.Suite and LTL Operations Module.

Settlements

  • PB-200336
    Fixed an issue where TMWSuite was not generating settlements correctly when processing the LTL manifest.

Scroll records

  • NSUITE-204199
    Fixed an issue where the reference number scroll does not work.

System

  • NSUITE-205658
    Fixed an issue where the Crossdock and TL Moves windows timeout and return no data.

  • NSUITE-205735
    Fixed an issue where the Pickups window times out.

Terminal actions

  • NSUITE-204052
    Fixed an issue where the search box on the Spotted Trailers window does not function.

  • NSUITE-204134
    Fixed an issue where the TL moves window does not display LTL 'child' orders correctly. They do not appear to be relevant to the terminal from which the tab is being viewed.

  • NSUITE-204273
    Fixed an issue where a tractor assigned to a child terminal does not show up on the parent terminals map display.

  • NSUITE-204275
    Fixed an issue where the system was prompting the user for a late reason code for a non-order based stop.
    Note: EDI reason codes are only required for order based stops/events.

  • NSUITE-204280
    Fixed an issue where a P1 expiration does not stop the (manifest) finish load process from occurring via the Doors window. The Crossdock/Delivery window does not finish load functions as intended and will not let an Out of Service asset be set to loaded to go.

  • NSUITE-205705
    Fixed an issue where special handling charges for appointment deliveries were not applying based on the company’s Hours of Operation Override parameters. They appear to be limited to default Hours of Operation only.

2018.3

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

Requirements

Before you begin installing LTL Operations Module version 2018.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

Invoicing

Transferring invoices between companies that use different currencies - (PB-200072)
Now the system will transfer invoices to companies that use different currencies. Accounting packages will display the correct currency.

Resolved issues

Commodities

  • NSUITE-204932
    Fixed an issue where the auto creation feature was causing issues calculating the volume/cube value for commodities.

Cross-dock

  • NSUITE-204493

    • Fixed an issue where the truckload order contains either a multi pick or multi drop stops, The LTL Cross-dock manifest contains only one LTL order.

    • When a TL Cross-dock scenario has a pickup leg completed by LTL Operations Module and the trailer is assigned in LTL Operations Module, the corresponding TL order has the initial trailer assigned to all stops including the HCT and stops occurring after the HCT.

    • When a TL Cross-dock scenario has a pickup leg completed by LTL Operations Module and the trailer is assigned in LTL Operations Module, the Cross-dock leg cannot be completed in LTL ops.

Dispatch

  • NSUITE-203761
    Fixed an issue where users were unable to change rev types on orders added in the Depart Shipper window.

  • NSUITE-203981

    • Fixed an issue where carriers were not showing up in TMW Operations.

    • Fixed an issue where trailers assigned to BMT / EMT events in LTL Operations Module were not showing up in TMW Operations.

  • NSUITE-204051
    Fixed an issue where an empty trailer drop is assigned to a manifest; however, a trailer ID is not assigned. When this occurs, the begin empty stop is not completed (correctly). However, the Hook Trailer event is completed. This does not allow the trailer to be assigned and prevents the user from correcting their mistake.

  • NSUITE-204058
    Fixed issues found with Current Route and Last Route calculated fields on the DRIVERS window.

    • Following the push of an RTT to the handheld, both route fields do not populate.

    • The Last Route and Current Route fields display a route from the wrong terminal. It appears to be the route from the opposite drayage leg from the terminal in question.

  • NSUITE-204081
    Fixed an issue where a driver is dispatched with a trailer assigned in TMW Operations and the driver arrived at the trailer hook and is required to change the trailer. If the customer loaded a different trailer than originally planned and the driver updates the trailer number in the handheld to a different trailer than planned in LTL Operations Module, the system checks for the following:

    • Trailer is at customer location (cmp id matches stop)

    • Trailer does not have p1 expiration

    • Trailer is not active on another move

  • NSUITE-204122
    Fixed an issue where a TMW Operations order has a leg pushed to LTL Operations Module and the times entered were incorrect.

  • NSUITE-204265
    Fixed an issue where a previous stop has not been completed, even though the driver completed the step using the handheld. Not all events on the prior stop were checked off by the handheld integration.

  • NSUITE-204268
    Fixed an issue where TMW Operations orders were being refused in LTL Operations Module; however, orders in TMW Operations were being shown as completed.

  • NSUITE-204490
    Fixed an issue where a rail line haul order status and the manifest/stop statuses do not match.

  • NSUITE-204491
    Fixed an issue where Shaw mobile devices would not show stops if the driver switches devices mid trip.

  • NSUITE-204501
    Fixed an issue where a driver is dispatched with a trailer assigned in TMW Operations and the driver arrived at the trailer hook and is required to change the trailer. If the customer loaded a different trailer than originally planned and the driver updates the trailer number in the handheld to a different trailer than planned in LTL Operations Module, the system checks for the following:

    • Trailer is at customer location (cmp id matches stop)

    • Trailer does not have p1 expiration

    • Trailer is not active on another move

  • NSUITE-2048568
    Fixed an issue where a driver completes a trailer pick stop using a handheld device and the trailer does not show at the company location, it creates a trailer beaming warning. The handheld device would not allow the driver to move onto the next stop.

  • NSUITE-205370
    Fixed an issue when completing a DRL type stop on the handheld device, the dimensions were being cleared (length width height) and the system was re-rating the order.

EDI

  • NSUITE-204492
    Fixed an issue where the EDI 214 was sending incorrect information or not sending the information at all.

  • NSUITE-204498
    Fixed issue where customer-specific equivalencies were not working correctly.

Expirations

  • NSUITE-204084
    Fixed issue where a Bill To’s expirations were not preventing orders from using those Bill To accounts.

Invoicing

  • NSUITE-204151
    Fixed an issue where the system prevented users from adding or modifying reference numbers after the order was created.

  • NSUITE-204251
    Fixed an issue where users could change invoices after they were printed.

Layouts

  • NSUITE-204137
    Fixed an issue where users could not screen design the Make Appt window.

Manifests

  • NSUITE-204059
    Fixed an issue with the Last Stop Route and Last Stop Company calculated fields on the Trips grid not updating correctly.

    • Local Manifest
      Following the push of an RTT to the hand held device, the Last Stop Route field does not populate.

  • Rail Linehaul Manifests
    The Last Stop Company field displays the company of the final stop when it has not yet been pushed to the hand held device.
    The *Last Stop Route field displays a route from the wrong terminal.

  • NSUITE-205361
    Fixed an issue where a split manifest displayed Completed in the order header; even if the second leg was still set to Available.

Microsoft Dynamics GP

  • NSUITE-204263
    Fixed an issue where LTL Operations Module was not transferring accrued manifest Microsoft Dynamics GP correctly.

Mobile communication

  • NSUITE-204264
    Fixed performance issue where messages were being delayed up to three minutes before sending.

  • NSUITE-204322
    Fixed an issue where Shaw mobile devices would time out and not notify the dispatcher.

  • NSUITE-204494
    Fixed an issue where hand held devices did not display the correct manifest, shift, or stop status.

Order entry

  • NSUITE-204285
    Fixed an issue where a shipper’s ZIP Code in TMW Operations is different from the ZIP Code in LTL Operations Module. This prevented users from being able to create orders in LTL Operations Module.

  • NSUITE-204500
    Fixed an issue where LTL orders are generated through the interop Create TL/LTL functionality and the company is not an LTL company. The LTL order is created with an UNKNOWN company code.

Rating engine

  • NSUITE-204002
    Adjusted rating engine so it uses the same process and database columns as TMW Back Office.

Scheduling

  • NSUITE-204002
    Fixed an issue where users could not add the following fields to the window using the Field Chooser.

    • Schedules window

      • Remarks

      • Trailer Temp Zone

      • Trailer field

    • Deliveries window: Trip Name

Synergize

  • NSUITE-107129
    Fixed an issue where the system did not update the move number at the paperwork level when it updates the move number in the order header.

System

  • NSUITE-204270
    LTL utilizes a custom style file to stylize the application. This file uses several dependencies on the colors of the operating system’s current theme, which has resulted in unreadable text in some areas of the application when used in a remote desktop environment. Removed these color dependencies and hardcoded the color choices.

  • NSUITE-204496
    Fixed an issue where the system would time out while updating the truckload moves screen.

  • NSUITE-204499
    Fixed an issue where the system would time out while updating the truckload moves screen.

  • NSUITE-204759
    Fixed an issue where the system would freeze or lock up when assigning a terminal driver to the Outgate drayage leg and adjusting the start date.

  • NSUITE-205208
    Fixed an issue where it was possible to create an infinite loop in Order Entry by using a consignee that has the default terms to Collect and a shipper with the default terms set to Prepaid.

  • PB-200067
    Fixed an issue where the system was not recognizing LTL trailer statuses.

Terminal actions

  • NSUITE-204271
    Fixed an issue when loading freight through the doors window, the shipment-level Start Load button could be pressed prior to the manifest-level Start Load button.

TotalMail

  • NSUITE-204592
    Fixed an issue where the system no longer flags stops as arrived on finish loads. This was causing problems with processing LTLStatusJob records created by TotalMail.