TMWSuite 2019 release notes

These release notes contain the following information for each 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 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.

A PDF version of these release notes is available here.

Warnings

SMTP e-mail port

As of version 2019.2, the setup for the SMTP e-mail feature has changed. You can now set these options in the SmtpEmailer General Info Table setting:

  • String1 = Identify your SMTP server

  • String3 = Identify your SMTP server username

  • String4 = Identify your SMTP server Password

  • Int1 = 587

  • Int2 = 465

This allows you to configure your system to use Secure Sockets Layer (SSL) for SMTP email.

Invoice output configurations

As of version 2019.1, there is a new procedure for setting up and assigning invoice output configurations for print and EDI.

In previous versions, you set up output configurations in the EDI 210 field or in the Advanced EDI Output Settings window in the company’s File Maintenance profile.

Now, those two locations are no longer available. Set up invoice output configurations in the Billing Output Configuration Folder. To access this window, go to Edit > Company Billing Output.

You can also assign invoice output configurations from either of these locations:

  • Billing Output Configuration Folder

  • The Distribution Method window in the company profile

    Note: To access this window, you must use Screen Designer to add the Invoice Output Method button to the company profile.

The new upgrade script automatically imports all the invoice output configurations you previously set up. You should not need to do any additional setup for your existing configurations. However, as with any major upgrade, we recommend that you verify the results after running the upgrade script.

PC*Miler warnings

Incompatibility with later PC*Miler|Mapping products

TMWSuite’s mapping feature works with PC*Miler|Mapping software to plot routes and symbols on a map.

To use these features in TMWSuite, you must use PC*Miler|Mapping version 31 or earlier.

Starting with PC*Miler version 32, ALK supports only ALK Maps for mapping. ALK Maps is a web-based, JavaScript API. TMWSuite does not support ALK Maps.

If you are using TMW.Suite Enterprise (TMW Operations, TMW Back Office, etc.) or another .NET product, you can use ALK Maps.

  1. In TMW.Suite, support for ALK Maps is free of charge. To use it, you need a unique API key value. Contact your Trimble support representative for more information.

  2. This change only affects the compatibility of ALK’s mapping features in TMWSuite. It does not affect the mileage features.

2019.4

General requirements

Before you begin installing TMWSuite, check that these requirements are met:

  • Internet Information Services (IIS) for Microsoft® Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft® SQL Server®

    Microsoft SQL Server 2012, SQL Server 2014, and SQL Server 2016 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • Microsoft Visual C++ 2010 x 86 Redistributables

  • 32-bit SQL Native Client Drivers
    Version 10, 11, or MS OLE DB must match the drivers to your SQL version.

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

    Like most applications, TMWSuite can be installed locally on a user’s system. It is also possible to install TMWSuite 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.

Enhancements

EDI

Specifying the number of EDI 214 records to process (PB-200708)

Previously, when an EDI Scheduler job started, the batch included all 214 records in the database. For very high volume clients, batches could be too large to complete before the job timed out. This caused changes to records to revert, which produced failed records. Failed records were put back in the queue for the next batch.

Now you can set the number of records to be included in a batch. This eliminates an ever-increasing backlog and allows records to be processed in a timely manner.

SMTP email

Disabling Secure Sockets Layer (SSL) for SMTP email (PB-200768)

When set up to use SMTP email in previous version, you were required to use SSL.

Now, you can set up your system to use SMTP e-mail without SSL.

Resolved issues

EDI

  • PB-200668

    Rounding calculation for Multicurrency transfer to Dynamics GP was off by $.02. This caused a balancing issue when the entry was posted in Dynamics GP.

  • PB-200753

    On outbound 204 EDI orders, the flat file output included reference numbers attached to order headers having a reftablekey value of 0 (zero). Now the system only includes reference numbers for stops on the leg where the ord_hdrnumber is greater than 0 (zero).

Final Settlements

  • PB-200741

    In previous versions, when adding a non-leg-based pay detail, such as vacation pay, the system would not pull rates defined by resource ID.

  • PB-200757

    After reopening a settlement in previous versions, the system was not retrieving the pay details correctly in a new pay period.

Freight Board

TSI-217

Freight Board Interface supports receiving the available date and time from the Dispatch system. However, the Create Posting tab allowed only the available date to be entered. Now you can enter the time when you enter the date.

Fuel Import

TSI-215/TS-214

If you had [FuelServ]ProcessEFSRejectedTransactions=Y in your INI file, the interactive EFS integration performed the pulling and processing of transaction records. The table used to store transactions must be seeded, that is, has at least one record. If there were no records, the system used a default start date, such as 1/1/2000, to pull rejected transactions. This could cause too much data to be returned, resulting in timeouts.

Invoicing

  • PB-200102

    Resolved a problem that occurred when you had [Invoice]RebillFromOrder=Y set in your TTS50 and were creating a credit memo/rebill for an invoice with a manually recorded line haul charge.

  • PB-200558

We fixed an issue that was causing the Output Configuration Maintenance window to error out and close.

Microsoft® Dynamics GP integration

  • PB-200747

    The AR Export function was creating out of balance General Ledger entries when:

    • An invoice is in US$, which triggers multicurrency/exchange rate entries in GP

    • An invoice contains a negative invoice detail, such as a currency surcharge

    • The charge type used for the negative invoice detail had the same GL account as any of the positive invoice details

    Note: These criteria applied even when multicurrency was not a factor.

  • PB-200746

    When the system is set up to automatically apply credit memos, it applies the credit memo to the original invoice. This clears the invoice from the Bill To’s open aging report and shows both items with $0 remaining open.

    However, the system is not updating all amount fields in the data transferred to Microsoft Dynamics GP. This results in Aging reports showing the original invoice as unpaid, even though the Amount Remaining is set to $0 during the Apply process.

Rating

PB-200779

Increased rating engine performance by adding the rate’s start date and end date to the search.

System Administration

PB-200730

In previous versions, there was an issue causing row level security to be ignored when row level security was set up for ord_revtype1 and the trip had an empty stop for the first stop.

Settlements

PB-200641

Fixed an issue that was preventing the system from logging the deletion of pay details in the paydetailaudit table consistently

System Updates

PB-200685

Fixed an issue where expiration listings prevented associated tractors from appearing in drop-down lists.

System wide

PB-200755

In previous versions, the system displayed a detailed error message when an incorrect entry was made during the log into TMWSuite or into the PowerSuite Administrator Login window.

Now, for security reasons, the system shows just a generic message.

When the error happens while logging into the PowerSuite Administrator Login window, the system logs the error to an error log in the database.

The PowerSuite Administrator Login window is used to edit users in System Administration.

Trip Settlements

PB-200385

Fixed an issue that was causing the system to calculate the currency conversion every time the row was edited, even for non-currency related edits.

TruETA Agent

  • NSUITE-207953

    Fixed a problem that was causing the TruETA Agent to not update the legheader ETA Status value correctly.

  • NSUITE-208020

    In previous versions, the system was displaying a Not Responding message while it was processing trips. This caused confusion for users. Now, the system displays a progress message while processing trips, so that clients will know the system is working.

  • NSUITE-208203

    Fixed a time stamp error that occurred on the UpdateTripStatus call. The system now applies UTC time rather than the local time for the tractor’s location.

  • NSUITE-208310

    For proper sequencing, check calls sent to TruETA now include time stamps. These time stamps include the time zone offset as well.

Upgrade Script

PB-200754

Our master upgrade script was taking too long to run, especially on large databases. We edited the script to fix the problem.

2019.3

General requirements

Before you begin installing TMWSuite, check that these requirements are met:

  • Internet Information Services (IIS) for Microsoft® Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft® SQL Server®

    Microsoft SQL Server 2012, SQL Server 2014, and SQL Server 2016 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • Microsoft Visual C++ 2010 x 86 Redistributables

  • 32-bit SQL Native Client Drivers
    Version 10, 11, or MS OLE DB must match the drivers to your SQL version.

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

    Like most applications, TMWSuite can be installed locally on a user’s system. It is also possible to install TMWSuite 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.

Enhancements

Application

Changed the trc-transponder column so that it allows up to 50 characters (PB-200659, PB-200661, PB-200693, PB-200694, PB-200695)

Previously, the trc_transponder column in the TMWSuite database supported 17 characters. Now, it supports up to 50 characters. Update all windows, fields, and SQL tables related to this enhancement.

Database

  • Changed the trc_transponder column so that it allows up to 50 characters (PB-200659)

    Previously, the trc_transponder column in the TMWSuite database supported 17 characters. Now, it supports up to 50 characters.

  • SQL changes related to the trc_transponder column update (PB-200661)

    Updated 5 Microsoft® SQL stored procedures in conjunction with the changes related to the trc_transponder column update.

File Maintenance

Updated the Transponder ID field so that it allows up to50 characters (PB-200660)

Previously, the Transponder ID field in the Additional Tractor Information window allowed you to enter up to 17 characters. If you entered more than 17 characters, the system displayed an error message and would not save your changes.

In File Maintenance, you can load this window by opening the Tractor Profile and then clicking on >> next to the VIN field.

Now, you can enter up to 50 characters in this field.

Invoicing

Increased decimal places (PB-200705)

In the Edit Invoice Folder, the Total LH Rate with Rollins field now displays four decimal places instead of two.

TMWSuite Addins

Updated the Tractor profile in conjunction with the Transponder column update (TSI-271)

Updated the Tractor profile window to allow additional characters for the trc_transponder column update

Resolved issues

Database

TSI-239

Fixed an issue where Inbound 204’s would take several minutes to import causing Microsoft® Windows to display the "Application is not responding" error message. However, the application was still running. This message caused users to force-close the application. Users would reboot their machines and try to load the Inbound 204’s again. This could cause 204’s to be lost or duplicated.

Dedicated Billing

PB-200701

Replaced the missing custom code in the Dedicated Billing (PB) procedure. This procedure added an ALL type to the Invoice Splitgroup that allows multiple split groups to pull into a dedicated bill.

EDI

  • PB-200634

    Fixed an issue where Outbound 204’s were not indexing correctly. This caused the system to lock up or freeze.

  • PB-200664

    Fixed an issue where the EDI 214 window was displaying a drop event before a pickup event when there was no drop event.

  • PB-200702

    Fixed an issue where EDI 210’s were listing accessorial charges before linehaul charges. This caused the system to reject the EDI 210’s.

  • TSI-293 and TSI-297

    Fixed an issue with incoming EDI 204’s that required you to create a new company using the Company Matching window

    Previously, the system would not match the newly created company with the EDI 204 row. Now, the system matches the newly created company to the EDI 204 row.

    Note: This issue affected EDI 204’s that contained row-level security.

  • TSI-320

    Improved Planning Worksheet performance related to retrieving data on the EDI tab.

  • TSI-321/TSI-193

    Improved Data Exchange performance related to creating 990s from 204s.

Fuel Import

PB-200331

Fixed an issue where certain transactions were not being labeled correctly during the Fuel Import process.

Load Requirements

PB-200629

When customers had more than one load requirement placed on an order, they were unable to modify or delete the load requirements in TMWSuite. This issue has been resolved.

Settlements

  • PB-2

    Fixed issue that was erroneously deleting intercompany charges when processing pay in the Trip Settlements Folder.

  • PB-200689

    Fixed an issue where carrier settlements in the A/P Export window were combining pay details for split trips. Now the pay details are listed as separate line items.

Trip Folder

PB-200633

We fixed a problem that was causing various errors when you edited stop times manually in the Sequence Stops window for new unsaved trips.

2019.2

General requirements

Before you begin installing TMWSuite, check that these requirements are met:

  • Internet Information Services (IIS) for Microsoft® Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft® SQL Server®

    Microsoft SQL Server 2012, SQL Server 2014, and SQL Server 2016 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • Microsoft Visual C++ 2010 x 86 Redistributables

  • 32-bit SQL Native Client Drivers
    Version 10, 11, or MS OLE DB must match the drivers to your SQL version.

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

    Like most applications, TMWSuite can be installed locally on a user’s system. It is also possible to install TMWSuite 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.

Enhancements

Add-Ins

TMWSuite Fuel Import can access the .NET UI (TSI-18)

Previously, users could not access the Fuel Import feature through the .NET add-ins. This required the user to use the TMWSuite windows when using the Fuel Import feature. Now, users can access the Fuel Import feature using the .NET Add-Ins. Now TMWSuite will display this window the same as in TWM Operations.

EDI

Inbound 214s populate the ckc_tractor field

Previously, inbound 214 check calls did not populate the ckc_tractor field. Added functionality so if a tractor was already assigned to a leg, the inbound check call for 214s populates the ckc_tractor column.

Fuel Import

New setup to determine pay detail creation during fuel import (TSI-18)

TMWSuite uses a new method to determine paydetail creation during fuel import.

Mileage

New classifications for ALK’s HazMat module (PB-200535)

Clients using ALK’s HazMat add-on module in conjunction with PC*MILER can create routes and calculate mileages based on hazardous material classifications.

In previous versions, the ALKHazLevel label provided four classifications as system codes:

  • General hazardous material

  • Explosives

  • Inhalants

  • Radioactive material

Now, the system provides two more system code options:

  • Flammable

  • Corrosive

In previous versions, you could set up these two additional options manually.

Resolved issues

Common dispatch features

PB-200539

Fixed problem in Dispatch Advantage that was preventing assignment of a resource with a Key Date (Priority 2) expiration.

EDI

  • PB-200482

    The lat/long output in outbound 214s was not being presented in a consistent way.

    • When the 214 was sent as a result of an arrival or departure, it would have a leading zero.

    • When it was triggered as the result of a location report (X6), it did not have a leading zero.

    This resulted in mapping failures. The lat/long output will now be presented in a consistent way regardless of the trigger of the 214.

  • TSI-87

    Fixed an issue where users were receiving a GEH error when the in bound 204 process would update an EDI-created order with dx_processed=Done.

  • TSI-169

    Fixed an issue where an inbound X6 with GPS coordinates was failing to import correctly. This caused the system to not create check calls.

Expirations

PB-200161

Fixed problem that was causing an error message when creating an In-Service expiration for a new tractor. This was happening only after you first saved a non-dispatch expiration for a new driver, and then tried saving the In-Service expiration.

Final Settlements

  • PB-200479

    Client was having an issue where the enhanced tax line would show in the user interface but was not being saved to the database.

  • PB-200485

    When you had Settlement]FinalStlmntDetailGrid=Y in your TTS50, the system would not allow you to Close a settlement that included a pay detail for Enhanced Taxes.

  • PB-200557

    Under certain circumstances, the system was duplicating pay header numbers.

Fuel Import

PB-200493 (Comdata)

Fixed an issue where rebates/discounts for Canadian purchases were passing the incorrect value during the US dollars to Canadian dollars transition.

Invoicing

PB-200355

Fixed an issue that was causing duplicate minimum charges when re-computing an invoice with Fix All set.

Microsoft® Dynamics GP integration

  • PB-200408

    The ten-key entry was not working in the Cash Receipts window.

  • PB-200458

    TMWSuite AP export was not retrieving settlements that were not linked to an order.

  • PB-200459

    Fixed an issue that was causing the AP Export window to retrieve the same settlement number multiple times.

  • PB-200461

    For negative invoice details, the AR Export was doubling the debit to sales. This was causing out of balance GL entries.

  • PB-200509

    Fixed an issue that was causing properties to display in error in the A/P Export Status grid when you had [Accounting]CarrierByOrder=1 and transfer by order selected.

  • PB-200529, PB-200554, PB-200562

    Fixed an issue causing an error whenever you attempted to save a new invoice that was set to Ready To Print. The error was due to the system making unwanted attempts to connect to GP.

  • PB-200531

    When applying cash receipts in TMWSuite for transfer to Dynamics GP, we had issues where the system was not pulling the AR account from the invoice to which the cash was being applied.

  • PB-200568, PB-200578, PB-200579

    Fixed an error that was being produced in the Payroll Export window.

  • PB-200581, PB-200580, PB-200573

    Fixed an error that was being produced in the AP Export Process

  • PB-200599

    The Auto Apply of Credit Memo to GP process was applying the credit memo incompletely.

Mileage

PB-200611

Fixed issue that was causing TMWSuite’s AddIns to ignore mileage through buckets greater than 99.

Order Entry

PB-200569

The Copy function was not copying toll information.

Planning Worksheet

  • PB-200513

    Fixed an issue that was causing Master Orders and Quotes to be listed on the Planning Worksheet.

  • PB-200583

    The Trc Trp Comments column was not retaining the entered comments upon save.

Rating

  • PB-200445

    Fixed the rating engine to ignore duplicate stops only when they are sequential.

  • PB-200508

    An error message was displaying when attempting to define a customized rate index hierarchy.

  • PB-200566

    The custom stored procedure sp_ChargeTypeBasisUnitRuleBillToMileAll was causing an error when computing charges.

System wide

PB-200124

Add these capabilities to the SMTP Emailing functionality:

  • Specify the port used by the SMTP server

  • Specify the user name and password to the SMTP server

Trip Folder

PB-200239

The system was preventing the reassignment of a carrier on a split trip when pay details existed for a resource on a different trip segment.

Trip Settlements

  • PB-200504

    Fixed an issue that was causing an error when updating the view restriction in the Trips Ready to Settle queue.

  • PB-200556

    Fixed an issue causing the Revenue Recap section to overlap the radio buttons in the header area. This made it difficult to select a radio button.

Upgrade script

PB-200437

Running the upgrade script results in settings, triggers, and stored procedures that differ from the expected defaults.

2019.1

General requirements

Before you begin installing TMWSuite, check that these requirements are met:

  • Internet Information Services (IIS) for Microsoft® Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft® SQL Server®

    Microsoft SQL Server 2012, SQL Server 2014, and SQL Server 2016 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • Microsoft Visual C++ 2010 x 86 Redistributables

  • 32-bit SQL Native Client Drivers
    Version 10, 11, or MS OLE DB must match the drivers to your SQL version.

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

    Like most applications, TMWSuite can be installed locally on a user’s system. It is also possible to install TMWSuite 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.

Enhancements

Invoicing

PB-200251

Electronic Data Interchange (EDI) allows you to send and receive documents electronically.

When setting up a Bill To company for EDI, you must specify how the system outputs the company’s invoices. You can specify that the system:

  • Prints a physical copy

  • Sends a copy electronically as a EDI 210

  • Prints a physical copy and sends an electronic copy

In previous versions, you set up output configurations in the EDI 210 field or in the Advanced EDI Output Settings window in the company’s File Maintenance profile.

Now, those two locations are no longer available. Set up invoice output configurations in the Billing Output Configuration Folder. To access this window, go to Edit > Company Billing Output.

You can also assign invoice output configurations from either of these locations:

  • Billing Output Configuration Folder

  • The Distribution Method window in the company profile

    Note: To access this window, you must use Screen Designer to add the Invoice Output Method button to the company profile.

The new upgrade script automatically imports all the invoice output configurations you previously set up. You should not need to do any additional setup for your existing configurations. However, as with any major upgrade, we recommend that you verify the results after running the upgrade script.

Resolved issues

Agent pay

PB-200371

Cannot compute pay in the Pay Detail Maintenance window. Added support for the [Settlement]DoActivityPayDetails INI setting.

Invoicing

PB-200339

Date Invoices field on the Print Invoices Queue is not changing the bill date on the invoice. It does not update the date from the default date.

Microsoft® Dynamics GP integration

PB-200358

Client is unable to transfer invoices which contain a $0.00 freight invoice detail along with other charges.

Mileage interface

PB-200381

The Route Mileage Inquiry window was not recalculating the mileage after the first location was changed.

Dispatch

PB-200430

Update_ord not working for many scenarios.

Trip Settlements Folder

  • PB-200240

    Memory leaks cause Trips Ready to Settle queue to crash when processing large number of records.

  • PB-200310

    When total pay is calculated from a secondary tariff with multiple indices and the matching index is not the first, the total pay calculation can improperly exclude invoice line item based pay.

Rating

PB-200502

Branch field for Driver was not editable in Settlement rates.

Trip Folder

  • PB-200159

    Mileage table on order header not getting set correctly on Bill To change.

  • PB-200429

    Adding two splits to a trip at the same time and attempting to save corrupts the order and crashes the application.

  • PB-200503

    When calculating pay for Driver 2, the system was not passing branch information to the rating engine.

Upgrade script

PB-200437

Running the upgrade script results in settings, triggers, and stored procedures that differ from the expected defaults.