2019.1

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.

Note: 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.

Warnings

Important information, please read before upgrading V.2019.1 and higher

Version warning

When you upgrade TMW Back Office to V.2019.1, you must also upgrade TMW Operations and TMWSuite to V.2019.1.

Invoice output configurations warning

Starting in 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.

In V.2019, those two locations are no longer available. Now, you set up invoice output configurations in the Billing Output Configuration Folder. To access this window, go to
Tools > Setup > Billing Output Configuration.

Now, you can assign companies to invoice output configurations from either of these locations:

  • The Billing Output Configuration Folder

  • The Distribution Method section on the Distribution Info tab in the company profile

The upgrade script for V. 2019.1 is designed to automatically import 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.

For information about setting up and using invoice output configurations in V.2019.1, see the Configuring your invoice output topic.

Minimum technical requirements for 17.50 or higher warning

Important information, please read before upgrading from a build lower than 17.50 to 17.50 or higher.

Verify that your environment adheres to these minimum technical requirements:

  • Microsoft’s .Net Framework version 4.6.2 must be installed.

  • Client operating systems must be at Windows 7 SP1 or higher.

  • Server operating systems must be at Windows Server 2008 R2 SP1 or higher.

  • In addition, verify that your system adheres to the requirements listed in the General requirements section for the build you are upgrading to.

Case sensitive passwords warning

Starting with V.17.50, the system treats all passwords as case sensitive. This includes existing passwords.

This change affects how you log in with an existing password:

  • If your password was created with [Misc]CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

  • If your password was created with [Misc]CaseSensitivePasswords=ON in your TTS50, you can enter that password as you originally recorded it (case sensitive).

Requirements

Before you begin installing TMW Back Office version 2019.1, check that these requirements have been met:

  • TMWSuite®
    You must be using TMWSuite V. 2019.1 or later.

  • TMW Operations
    If you are using TMW Operations, your version of TMW Back Office must be the same as your version of TMW Operations.

  • Microsoft® .NET Framework
    .NET Framework 4.6.2 or later (full package not client)
    The framework must be installed on the TMW Back Office server, client, and administrator systems before you install TMW Back Office. 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 TMW Back Office, and have administrator rights for that system
    Like most applications, TMW Back Office can be installed locally on a user’s system. It is also possible to install TMW Back Office 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 TMW Back Office 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

Final Settlements

Setting up guaranteed pay (NSUITE-206459, NSUITE-206460)

Now, you can set up a guaranteed pay amount per pay period for drivers. You specify the guaranteed pay amount in the drivers' profile.

If a driver’s pay for the period is less than the specified amount, the system creates an additional pay detail for the difference during the Collect process.

You can specify on the pay type whether the system excludes the pay from the guaranteed amount, such as toll reimbursements.

In addition, you can manually exclude individual pay details from the guaranteed amount.

Invoicing

Setting up invoice output methods in TMW Back Office (NSUITE-90671)

In previous versions, you had to set up invoice output methods in TMWSuite.

Now, you can set up the invoice output methods within TMW Back Office for each Bill To company based on:

  • Output, such as print, EDI 210, both, or none

  • Invoice type, such as line haul, supplemental, or miscellaneous invoices

  • Invoice definition, such as primary, credit memo, and rebilled invoices

  • Credit terms, such as Collect (COL), or Prepaid (PPD)

The system keeps all the invoice output configurations you previously set up for your Bill To companies in TMWSuite.

If you do not assign a configuration to a Bill To company, the system uses the default configuration. This configuration prints a physical invoice for all invoice types and all billing states.

Link to topic: Configuring your invoice output

Introduction to TMW Back Office

Logging additional telemetry data (NSUITE-206273, NSUITE-206274)

Trimble offers you the option to provide application telemetry data.
This information helps Trimble to identify potential problems and plan improvements.
Now, it logs this additional information:
** Processing records in the Invoicing queues

  • Processing records in the Settlement queues

Microsoft Dynamics GP interface

Selecting the view used in accounting export windows NSUITE-202164

A view is a set of restrictions that serves as a filter to narrow down the number of records listed in a grid.

A new field in these accounting export windows allows you to select the view used:

  • AP Export

  • AR Export

  • Vendor Export

  • Customer Export

Sending details to PR Distributions (NSUITE-204547)

When transferring payroll to Microsoft Dynamics GP in previous versions, the GL posting always occurred in Dynamics GP.

Now, you can set up the system to send Details to PR Distributions.

This process sends accounts from pay types, and it follows GL reset rules for payroll.

Setting up Pay To companies for direct deposit (NSUITE-206248)

Now, you can set up Pay To companies for direct deposit to their bank. You specify direct deposit information in the Vendor Maintenance window, which is accessed from the Pay To profile.

Rating

Creating predifined rating rules (NSUITE-205952)

Now, you can create customized rates based on predefined rules you specify in a stored procedure.

Recurring Adjustments

Specifying an initial amount for a recurring adjustment (*NSUITE-205575)

Recurring adjustments allow you to make adjustments to pay on a regularly scheduled basis that are unrelated to pay/deductions for trips.

Now, when you assign a recurring adjustment to a resource, you can specify an initial amount paid or deposited.

Resolved Issues

3PL Billing

  • NSUITE-204473
    Rating Errors/Warnings/Messages do not display for 3PL Billing.

Agent Settlements Folder

  • NSUITE-205762
    Four Issues:

    1. When re-computing pay in Agent Settlements, the costs (pay of other assets)are not being considered. This results in incorrect pay computed for the agent.

    2. Manually added pay for the carrier is not considered as a cost during pay calculation for a third party agent.

    3. Trip pay can be recomputed for an asset even after the pay was Transferred.

    4. Error occurs when a manual line haul pay detail with fixed amount exists before computing pay.

  • NSUITE-205898
    When computing pay details, the pay period and status are not set correctly.

  • NSUITE-206108
    Trips Ready to Settle for Agents queue is not creating pay for all assets on the trip.

Company profile

  • NSUITE-206090
    The Customer Maintenance button in the Company profile no longer appears when loading a Bill To company.

EDI

  • NSUITE-206386
    Error displayed when generating an Outbound 210.

Final Settlements

  • NSUITE-206422
    Fixed issue preventing you from processing a pay record that includes multiple carrier invoice numbers.

  • NSUITE-206426
    Attempting to transfer $0.00 settlements in the Back Office AP Export window causes an error. It shows debit amount and credit amount are not in balance.

General system setup

  • NSUITE-206554
    Error occurs when applying TMWOperationsdbmods.sql for version 2018.4.

Invoicing

  • NSUITE-206206
    Deleting invoices that have reference numbers results in orphaned reference numbers.

  • NSUITE-206421
    The roll into line haul flags were not properly marked in BackOffice.

  • NSUITE-206608
    When printing an invoice, the prompt message states that the Bill To is setup for EDI only, even when the Bill To is not assigned any configuration.

  • NSUITE-206669
    Closing the Billing Output Configuration Folder with active modifications is not giving save prompt dialog box.

  • NSUITE-206674
    Error returned when attempting to add invoice to an existing saved dedicated bill.

Microsoft(r) Dynamics GP integration

  • NSUITE-202689
    In the AR transfer, fixed the restriction and process results.

  • NSUITE-205350
    Fixed export issues for Pay To to Vendor

  • NSUITE-205469
    Fixed transfer issues.

  • NSUITE-206080
    Total charges for dedicated billing AR invoice are not set correctly.

  • NSUITE-206098
    The Vendor Export is not exporting the vendor’s full name to Dynamics GP.

  • NSUITE-206122
    The Customer Export is not correctly updating the Salesperson ID.

  • NSUITE-206557
    When transferring master or dedicated bills, the system does not pull the Bill To’s alternate ID when the option is set.

  • NSUITE-206591
    The Payroll Employee Export erroneously retrieves drivers with an accounting type of None.

  • NSUITE-206636
    AR Export queue is not finding dedicated bills.

  • NSUITE-206645
    When transferring a freight bill invoice with a Salesperson selected on the Accounting Settings tab, the system was not transferring the corresponding value from the invoice to the accounts receivable header.

Mileage interface features

  • NSUITE-200429
    Fixed an error caused by the ALK City validation function when a county code was not included within the City profile.

  • NSUITE-200654
    Fixed problem that caused incorrect mapping when a negative longitude was recorded on a new city profile.

  • NSUITE-203646
    Fixed problem that occurred when you clicked the ALK button on the company profile causing the latitude/longitude values to flip, which resulted in incorrect location information.
    Note: This happened only when you had [PCMilerWeb]EnableAddressValidation=N set in your TTS50.

  • NSUITE-205500
    Fixed the ALK validation process in the City profile.

  • NSUITE-205877
    Fixed the system to honor the [MileageType]ALKRetrieveTollCost INI setting for ALK Web mileage.

  • NSUITE-205891
    When logging was set to verbose, mileage calls to either PC*MILER Web or Rand IntelliRoute could crash the system.

  • PB-200381
    The Route Mileage Inquiry window was not recalculating the mileage after the first location is changed.

Rating

  • NSUITE-93227
    Added the ability to set minimum values at the cell level when a flat pay type is set on the rate and the tariff is setup as an external rate.

  • NSUITE-200824
    Prorating trip segments by weight on segment over weight on move was not calculating correct quantity.

  • NSUITE-203658
    Fixed an issue that was overriding a tariff’s custom invoice detail description with the name of the commodity when a closest point tariff was applied in rate by detail.

  • NSUITE-205613
    Optimized the service area rating query.

Tracking paperwork

  • NSUITE-206922
    Fixed a problem that was preventing the imaging interface from creating paperwork rows for additional legs on a trip.

Trip Settlements

  • NSUITE-205259
    TPLCreatePayFromCostsActive table needs to be removed. It is no longer used.