2018

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

2018.4 SP5

Resolved Issues

Microsoft® Dynamics GP integration

  • NSUITE-207010
    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

Rating

  • NSUITE-206896
    Fixed problem a client was having with their Calculated Revenue rates.

2018.4 SP2

Resolved Issues

3PL Billing

  • NSUITE-206413
    Fixed issue that kept record locked and prevented processing in cost detail generation or post-settlements worker threads during 3PL Billing Process.

Final Settlements

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

Microsoft Dynamics GP integration

  • NSUITE-206557
    When transferring master bills or dedicated bills, transfer the Bill To’s alternate ID if it is recorded.

2018.4 SP1

Resolved Issues

Final Settlements

  • 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.

Agent Settlements Folder

  • NSUITE-205762
    Four Issues:

    1. When recomputing pay in Agent Settlements, the costs (pay of other assets) is 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.

2018.4

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

Warnings

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 2018.4, check that these requirements have been met:

  • TMWSuite®
    You must be using TMWSuite V. 2018.4.0.0004 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

Holiday pay (CR-170)

Now you can set up the system to calculate holiday pay automatically for your drivers. The system creates the holiday pay details during the Collect process in Final Settlements. To use the feature, you set up:

  • A calendar specifying the days eligible for holiday pay

  • Additional Earning pay rates using the Holiday Group rate table option

In addition, you can set up primary or secondary rate tables based on the Premium Day option that will create pay in the Trip Settlements Folder for the holidays you set up. These rates can be based on distance, flat amount, etc.

Imaging

Visual indicator added to the TMW Imaging tab (INT-201435)

Now, when an image is attached to the TMW Imaging tab, the tab is highlighted. In addition, when you move the pointer over the tab, the system displays the number of attachments.

Microsoft Dynamics GP

Revenue Allocation enhancements (PB-200072, PB-200073)

The Revenue Allocation feature allows you to allocate revenue to the assigned resources. You can see the allocations in the Allocate Invoice window before transferring the invoice to your accounting system.

In previous versions, the system calculated the currency conversion during the transfer process to your accounting system.

Now, you can see and edit the converted amounts in the Allocate Invoice window before you transfer the invoice.

Also, the Allocate Invoice window now contains these additional fields:

  • Type* (read only)

    • Debit Amt

    • Credit Amt

  • Conv Debit* (for currency conversion)

  • Conv Credit* (for currency conversion)

Warning: Clients using the current Revenue Allocation process should contact Trimble Support before switching to the new process.

Multi currency support (PB-200109)

Now, the system supports multi-currency in the Cash Receipts window.

Resolved issues

3PL Billing

  • NSUITE-205237
    The system is not updating invoice header information on the associated pay details.

Dedicated Billing

  • NSUITE-205394
    Minimum charge is not computing correctly.

Final Settlements

  • NSUITE-205468
    When settling accounts payable resources in TMW Back Office, the Carry Over Pay functionality automatically adds a positive pay item to zero out a negative settlement.

General System Setup

  • NSUITE-205410
    Error received when you have the InvoicingRecordLocking General Info Table setting enabled.

Invoicing

  • NSUITE-204565
    There is an issue with updating the invoice header’s reference number and reference type values when an invoice is modified.

  • NSUITE-205623
    Unable to fix invoices already printed on a master bill.

Microsoft® Dynamics GP integration

  • NSUITE-204526
    When multi-currency is disabled, an error message is displayed when using the Accounts Receivable Export.

  • NSUITE-204956
    The AP Export fails to consider pay adjustments in the total purchase amount and does not compute the sums of debit and credit values correctly.

  • NSUITE-205351
    Several issues related to driver transfer to GP including:

    • Last Day Worked is being populated with a date. This is a termination date in GP.

    • Updating a driver in TMW blanks out the Work Hours per Year field.

    • Initial transfer of Driver to GP - TMW Accounting Settings for Department and Position are set to None. This should pull the information from the GP Employee Class.

  • NSUITE-205469
    Fixed several vendor export issues:

    • The Tax Type does not transfer to GP, when the Class option is selected in TMW for the 1099 Type.

    • Tax ID is not updating in GP.

    • Fixed format of Tax ID for 1099’s.

    • Created new Address ID in GP - added REMIT TO field on Vendor card.

    • After a vendor is updated, the address card in GP is blanked out.

  • NSUITE-205651
    When transferring invoices to GP an error on one invoice causes all the invoices being transferred to error out.

Paperwork Tracking

  • NSUITE-205467
    When the paperwork is configured by leg, the system improperly identifies missing paperwork for split trips.

Rating

  • NSUITE-104329
    The tariff index mileage table supports only 99 mileage buckets of two digits.

  • NSUITE-205207
    TMW Operations calculates the per 100 weight and the rate that applies to that weight, but does not look at the Best Charge calculation of the next weight row from the tariff table, therefore applying the incorrect charge expected and agreed upon with their customer.

Third party pay

  • NSUITE-205584
    When re-computing Agent pay within the Agent Pay Settlement screen with a percent of profit rate, the system always include the agent pay and that adjusts the profit.

  • NSUITE-205617
    Carrier line haul pay is being doubled, which causes the system to incorrectly calculate the percent of revenue for third parties.

Trip Settlements

  • NSUITE-205558
    On split trips, the system is using the end date of the trip to determine the pay period to which the pay should be released. It should be using the end date of the trip segment to which the driver is associated.

2018.3

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

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 2018.3, check that these requirements have been met:

  • TMWSuite®
    You must be using TMWSuite V. 2018.3.0.0021 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

Data grids

Customizing double-click functionality - (NSUITE-202820, NSUITE-202898)

The system frequently displays data in the form of a spreadsheet-like grid.

By default, double-clicking a row in some grids opens the selected record in a new window. For example, when you double-click an order in the Order Scroll, the system opens the order in a new window.

Now, you can set up grids so that different cell types can provide different results when double-clicked. For example, double-clicking:

  • An order cell could open the order

  • A company or resource cell could open the appropriate profile
    Note: You can even specify which tab in the profile should be visible by default.

  • A particular cell could open a hyperlink, web browser, or SSRS report

Note: When using this feature in a cell that uses the instant best match functionality, you must double click the arrow, not the text in the cell.

Final Settlements

Resolving Out of Period Overtime Pay (NSUITE-204334, NSUITE-204335, NSUITE-204336)

If you pay drivers on an hourly basis, you may also pay overtime for hours exceeding the threshold you define for regular pay. You can set up the system to calculate overtime pay automatically for these extra hours.

In the Time Settlements Folder, the system creates pay details for the driver’s hours. These are paid at the assigned hourly rate. When you run the Collect process in the Final Settlements Folder, the system creates an additional pay detail for all overtime hours.

Sometimes, after you transfer a pay period, you may realize that you did not pay a driver for all the hours he or she worked. To correct this, you need to add those hours to the current pay period and, if applicable, create overtime pay. However, you must create the overtime pay based on the hours actually worked in the previous pay period.

In previous versions, you had to fix these types of errors manually.

Now, when you record the driver’s current hours in the Time Settlements Folder, you can also record any missed hours from the previous period. When you run the Collect process, the system automatically calculates overtime pay for the missed hours based on the hours recorded for the previous pay period.

For example, in the previous pay period, you paid a driver 40 hours of regular pay. However, the driver actually worked 50 hours. To fix this error, you need to add 10 hours to the current pay period in the Time Settlements Folder. The system creates the pay detail for the 10 hours of regular pay. When you run the Collect process in Final Settlements, the system creates an additional pay detail for 10 hours of overtime pay based on the missed hours.

Microsoft® Dynamics GP integration

Credit memos automatically applied to transferred invoices (NSUITE-202684)

In previous versions, applying credit memos to invoices transferred and posted in Microsoft Dynamics GP was a manual process. Now, the system automatically applies a credit memo when the remaining invoice amount is equal to that of the credit memo.

Note: This functionality applies only to a previously transferred invoice when:

  • The invoice is posted.

  • The invoice is unaltered. No payment has been applied to it. It does not already have a credit or debit memo applied to it.

Vendor export validation added to Tax ID data (NSUITE-203735)

In previous versions, when you transferred Pay To information using the Vendor Export window, the system would overwrite existing entries in the Pay To’s Vendor Card to match the Pay To’s profile. Overwritten data included Tax IDs.

Now, when you transfer a Pay To’s information, the system:

  • Updates the Vendor Card with the Pay To’s Tax ID only if the field in the Vendor Card is blank.

  • Does not overwrite the value in the Vendor Card if the Tax ID # field in the Pay To profile is blank.

The Batch Process Results window displays messages confirming what has happened. When the Tax ID is:

  • Updated, the message is: "Tax ID updated to: <new value>"

  • Not updated, the message is: "Existing Tax ID: <existing value> will not be overwritten with Tax ID: <new value>"

  • Not overwritten with no value, the message is: "Existing Tax ID: <existing value> will not be overwritten with a blank Tax ID"

Resolved issues

Final Settlements

  • NSUITE-204404
    Fixed an issue causing the system to time out when closing a pay period for an extensive number of carries.

Invoicing

  • NSUITE-107114
    For supplemental invoices in LTL, fixed the issue causing Synergize to attach paperwork requirements for the Bill To on the original invoice rather than the paperwork requirements for the Bill To on the supplemental invoice.

  • NSUITE-203907
    Fixed the issue causing the system to generate incorrect/unclear data for Synergize to process a master bill when it contains only one invoice.

  • NSUITE-203963
    Performed cleanup to bring processes up to DBA standards.

  • NSUITE-203975
    Fixed issue causing the Locations grid in the Edit Details tab to display incorrect delivery information for cross-docked, split trips.

  • NSUITE 204236
    Fixed the issue causing TMWSuite Billing Desk to miscalculate out of route miles for secondary rates. Correct calculations show in TMW Back Office.

Time Settlements Folder

  • NSUITE-204324
    Compute in Time Settlement Folder is not considering table rates with row/column based on driver type when the time log source is Elog.

Trip Settlements

  • NSUITE-204168
    Fixed issue that prohibited saving Manual as the default Pay Schedule Mode on the Restrict tab.

2018.2

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

ALK Warning

In very limited circumstances, your system could generate incorrect mileages when using PC*MILER version 32 with any of these products:

  • TMW Operations version 2018.2 or lower

  • TMW Back Office version 2018.2 or lower

  • Fuel Dispatch version 2018.2 or lower

  • TMWSuite version 2018.2.0.0275 or lower

This problem is associated only with systems that have one of these options set in their TTS50:

  • [MileageInterface]ExOptions[x]=I

  • [MileageInterface]ExOptions[x]=X

Having either of these options set will cause Practical mileage to be computed as Shortest, and Shortest mileage to be computed as Practical.

This will not affect mileages previously retrieved and stored in the mileage table.

The issue is fixed in the next general release, such as 2018.3 for TMW Operations.

A temporary workaround to bypass the incorrect code is to do any of the following:

  • Use an additional ExOption in conjunction with the I or X option.

  • Remove the I or X option entirely.

  • Install an earlier version of PC*MILER.

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 2018.2, check that these requirements have been met:

  • TMWSuite®
    You must be using TMWSuite V. 2018.2.0.0275 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

Accounting interface

Using flat files to transfer billing and settlements data to your accounting package (NSUITE-202851)

Now, you can set up TMW Back Office to create a flat file to transfer billing and settlement data to your accounting package. This feature uses SQL Server Integration Services (SSIS).

The flat file accounting interface offers the following benefits:

  • SSIS packages are customer specific.

  • You can set up packages on your own, or work with a TMW database administration group to set up your packages.

  • The only required elements needed for setting up the configuration in TMW Back Office are the package’s folder, project, and name.

Note that you are required to use Windows authentication to execute packages.

Final Settlements

Setting up hourly pay for on call time (NSUITE-203280, NSUITE-203281)

The hourly pay feature allows you to calculate hourly pay based on the driver’s shift time. You can set up different rates based on the type or category of hours.

Previously, you could categorize the driver’s time by any of these options:

  • Driving

  • On Duty

  • Meals

Now, a new option allows you to categorize a driver’s time as On Call.

Calculating overtime pay (NSUITE-303382)

If you pay drivers on an hourly basis, you can set up the system to calculate overtime pay automatically. It is calculated during a pre-collect routine triggered when you run the Collect process in Final Settlements. The system:

  • Sums the driver’s hours based on hourly pay details released to the pay period.
    Note: You must base the pay details on pay types approved for overtime pay.

  • Compares the total number of hours with a user-defined threshold for regular hours, such as 40 hours per week, or 8 hours per day.

  • Creates an overtime pay detail for any hours greater than the threshold based on pay rates you set up for overtime pay.

If you do not want to pay a driver for overtime, you can mark him or her as exempt in the driver’s profile.

Invoicing

Printing PDF copies for imaging from the Master Billing window (NSUITE-203470)

A master bill is a summary statement that lists the totals for individual invoices for a specific Bill To company. This change affects clients who use imaging functionality when printing master bills.

In previous versions, you could not print a PDF copy of a master bill for imaging from the Master Billing window.

Now, you can print a hard copy as well as an Adobe Acrobat (PDF) image from this window.

This PDF image is automatically saved to the user’s files to be emailed to the user’s customer.

Recurring adjustments

Basing recurring escrow adjustments on mileage (NSUITE-202673)

A recurring adjustment is a pay adjustment that is processed on a regularly scheduled basis. An escrow adjustment is one type of recurring adjustment. You use it to fund an escrow account for a resource.

Previously, you could set up the terms for recurring escrow adjustments in one of two ways:

  • Apply the adjustment once per pay period

  • Apply the adjustment according to a custom schedule

Now, you can also set up recurring escrow adjustments based on the number of miles traveled. You can specify the quantity, rounding technique, and type of mileage to use for calculations.

Scrolls

Add restrictions to the Reference Number Scroll (NSUITE-203256, NSUITE-202694)

You use the Reference Number scroll to look up orders based on reference numbers. In the scroll window, you can set restrictions to limit the record retrieval.

Now, you can set up your system to include four additional restriction fields:

  • Order Header Bill To

  • Stop Company ID

  • Order Ship Date

  • Order Invoice Date

Settlements

Pay Period Date Enhancements (NSUITE-202592, NSUITE-203478, and NSUITE-203477)

A pay period is a set date range that determines which trips are included in a resource’s pay. By default, the trip’s completion date must fall within a resource’s pay period to be included in that pay cycle. Pay for work completed after the cutoff is rolled over to the following period.

Two enhancements have been made to the way the system handles pay periods:

  • Previously, a pay schedule’s cutoff time was always set to midnight. Now, you can set up your system so that you can specify a different cutoff time, such as noon.

  • Previously, the system always used the Trip Completion Date to determine if the trip should be paid in the current pay period. Now, you can direct the system to use the Trip Start Date or the Trip Completion Date.

TMW Rating

Creating percent of revenue accessorial rates based on user-defined types of revenue (NSUITE-202848, NSUITE-203293, NSUITE-203294, NSUITE-203296, PB-200019)

You can set up accessorial charges that are based on an order’s revenue.

Now, you can set up percent of revenue rates that calculate their charge based only on the revenue types that you specified.

You specify the types of revenue to include in the calculation on the charge type used to create the percent of revenue rate.

Closest Distance rating (NSUITE-203010)

TMW Back office now supports the Dist (ClosestPoint) row/column option for billing rate tables.

  1. When this option is used to rate an order, the system does the following:

    1. Calculates the mileage traveled on the order

    2. Compiles the mileage between all the pickup stops as they are sequenced on the order
      Note: This feature assumes that all pickup events occur before any of the drop events. This means that the mileage is computed for all pickup stops and then the mileage is computed for all the drop stops.

    3. Determines which of the drop stops is located closest to the last pickup stop, and then it adds the mileage between those two stops.
      Note: The system picks the drop stop that is closest to the last pickup stop. In other words, it does not base its mileage calculation on the stop sequence recorded on the order.

    4. When there are additional drop stops, it calculates which one is located closest to the previous drop stop and adds the mileage between those two stops. Then, it repeats the process for each remaining drop stop.

  2. Uses the total calculated mileage found in Step 1 to select a rate from the rate table defined by the Dist (ClosestPoint) option

Notes:

  1. This feature is available only for Rate by Detail.

  2. Mileage is calculated only for pickup (PUP) or drop (DRP) stops.

Rate by Detail based on pickup and drop locations (NSUITE 202866, 203290, 203292)

When hauling multiple commodities, you can use the Rate by Detail mode to calculate charges for each commodity separately.

Now, you can set up the system so that it will rate each commodity based on its pickup and drop locations.

Trip Settlements Folder

Using the invoice quantity to calculate pay (NSUITE-203464)

You use the compute function in the Trip Settlements Folder to automatically calculate pay.

In previous versions, when calculating weight-, volume-, or count-based pay, the system required that the quantity was recorded on the trip or that you manually enter it.

Now, when the quantity is not recorded on the trip, you do not have to enter it manually. The Trip Settlements Folder will pull the quantity from the invoice.

Note: This enhancement affects only weight-, volume-, or count-based pay.

Resolved issues

Final Settlements

  • NSUITE-203067
    After upgrading, running the Close Final Settlements queue returns an error and the pay header is not closed. The stored procedure TPLActiveObjectsQueue fails when the iut_payheaderTplActive trigger is active.

  • NSUITE-203061
    The Final Settlements folder returns an error when retrieving a pay period for an asset assigned to multiple pay headers.

Invoicing

  • NSUITE-202996
    Fixed an issue that was causing the system to not invoice some cross docked orders. The system was incorrectly notifying the user that an order is not invoiced or that the Bill To is missing.

  • NSUITE-203916
    The system incorrectly allows credit memos with a status of Transferred to be deleted if the corresponding rebill has been deleted.

  • NSUITE-204222
    Exporting a credit memo to accounting was resulting in an incorrect distribution type.

Microsoft® Dynamics GP integration

  • NSUITE-204223
    The GL Reset data retrieval logic for pay was fixed to handle pay not associated with an order.

Settlements

  • NSUITE-103748
    Fixed an issue where TMW Back Office and TMWSuite Settlements were using different mileage quantities to calculate pay.
    This issue affected only clients who used different mileage interfaces in Operations and Settlements.

2018.1

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

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

ALK Warning

In very limited circumstances, your system could generate incorrect mileages when using PC*MILER version 32 with any of these products:

  • TMW Operations version 2018.2 or lower

  • TMW Back Office version 2018.2 or lower

  • Fuel Dispatch version 2018.2 or lower

  • TMWSuite version 2018.2.0.0275 or lower

This problem is associated only with systems that have one of these options set in their TTS50:

  • [MileageInterface]ExOptions[x]=I

  • [MileageInterface]ExOptions[x]=X

Having either of these options set will cause Practical mileage to be computed as Shortest, and Shortest mileage to be computed as Practical.

This will not affect mileages previously retrieved and stored in the mileage table.

The issue is fixed in the next general release, such as 2018.3 for TMW Operations.

A temporary workaround to bypass the incorrect code is to do any of the following:

  • Use an additional ExOption in conjunction with the I or X option.

  • Remove the I or X option entirely.

  • Install an earlier version of PC*MILER.

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 2018.1, check that these requirements have been met:

  • TMWSuite®
    You must be using TMWSuite V.2018.18_01.0192 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

Data grids

Using logic operators with grid column filters (NSUITE-202501)

In TMW Back Office, you can apply multiple column filters to a grid. This restricts the number of items that appear in the grid.

When working with two or more filters, you set the logic operator - AND or OR - for values within a single column.

Now, you can also use the Column Conjunction field to apply AND or OR between columns.

Final Settlements

Final Settlements enhancements (NSUITE-202246)

Enhancements have been made to how Final Settlements handles pay details.

Now:

  • When you retrieve pay records in Final Settlements:

    • In the Unsettled Details section, the system pulls only pay details having an On Hold status.

    • In the Ready to Collect Details section, the system pulls pay details in a Released status that have a pay period the same as or earlier than the current period.

      If the pay detail’s pay period is not the same as the selected pay period, the system highlights the pay detail in yellow.

      Notes:

      1. In the past, when you retrieved Released pay details with a pay period earlier than the current period, the system placed them in the Unsettled Details section.

      2. The system does not retrieve Released pay details that have a pay period later than the selected pay period.

  • When you run the Collect process, the system:

    • Updates the pay period of the pay details highlighted in yellow to the selected pay period

    • Generates the appropriate pay details, such as recurring adjustments or overtime pay

  • When you change the status of a pay detail in the Unsettled Details section to Released, the system:

    • Changes the detail’s pay period to the selected pay period

    • Moves the detail to the Ready to Collect Details section

  • The Remove Pay button is renamed to the Hold Pay button. It has two functions:

    • It deletes unsaved pay details that were manually added.

    • It moves saved pay details to the Unsettled Details section. It sets the detail’s status to OnHold and sets its date to 12/31/2049.

Calculating hourly pay based on a driver’s shift time (NSUITE-201648)

In previous versions, you could calculate hourly pay based on trip times or on manually entered hours.

Now, you can set up the system to calculate hourly pay based on the driver’s shift time.

This feature will automatically calculate hourly pay based on hours of Service (HOS) data.

Fuel Dispatch features

Specify whether a company’s charges are based on gross or net volume (NSUITE-202093)

In Fuel Dispatch, you can specify a Bill To’s default billing quantity type as gross or net volume. You do this on the Company Relations Profile window’s Bill To/Cmd Billing QTY tab.

In the TMWSuite Invoicing application, charges are calculated using the Bill To’s default billing quantity type.

In previous versions of TMW Back Office Invoicing, charges were always based on gross volume.

Now, you can set up TMW Back Office to use the volume type specified for the Bill To company.

Show the Freight Supplier column in the Edit Invoice Folder (NSUITE-202094)

In Fuel Dispatch, you must record the supplier company on the order. The supplier is the company that provides fuel to the rack.

By default, TMW Back Office does not display the supplier company.

Now, if you are licensed for Fuel Dispatch, you can add the Freight Supplier column in the Edit Invoice Folder. This allows you to view and edit the supplier listed on the invoice.

Notes:

  1. The Freight Supplier column in the Edit Invoice Folder displays information from the fgt_supplier column in the freightdetail table.

  2. Changing the supplier on the invoice does not change the order’s freight detail.

Shift restrictions added to the Trips Ready to Settle Queue (NSUITE-202776)

You use the Trips Ready to Settle queue to retrieve a list of trips for processing. The queue contains numerous restriction fields you can use to filter the trips retrieved.

Now, for trips created in Fuel Dispatch, you can set up the queue to filter trips based on a shift’s start and end dates.

General system setup

Choosing the currency conversion rate to use (NSUITE-202242)

You create and edit currency conversion rates in TMWSuite System Administration. When creating a rate, you determine the date the rate should take effect.

By default, when processing invoices and pay, TMW Back Office chooses the currency conversion rate based on the date the order was created. Now, you can require the system to choose the rate based on the trip’s start date.

Layouts - Windows

In TMW Back Office, you can add hyperlinks to screen layouts in QuickDesigner. When clicked, a hyperlink can open a program, file, or webpage. You use the Add New Item feature to create a hyperlink.

Now, you can pass one or more command line arguments when the hyperlink is clicked. A command line argument can contain static text, a field value from the host window, the result of an expression, or the contents of a variable.

A new Command Arguments field has been added to the Add New Item window. It is available only when creating hyperlinks. In it, you can enter a string containing the arguments to be passed.

TMW Rating

Cell-based minimums in rate tables supported for all users (NSUITE-202095)

You use TMW’s Rate Schedules application to establish your billing rates and pay rates.

The rate header can contain a single per unit rate, or it can be linked to a rate table that contains a matrix of per unit rates.

Existing functionality allows you to set a single minimum for a rate. When the calculated charge or pay is less than the specified minimum, the system applies an additional line item to meet the minimum.

Starting in V.16.40, you could set up the system to use cell-based minimums in rate tables. This feature allowed you to set a minimum for individual cells in a rate table.You could specify any of the following:

  • A minimum quantity

  • A minimum charge amount

  • A minimum pay amount

Now, this functionality is always active. No system setup is required.

Trip Settlements Folder

New field displays allocation rate for split trips (NSUITE-202245, NSUITE-202538)

If you assign a driver to a split trip and pay the driver a percent of revenue, the system uses the number of miles that the driver traveled on the trip segment to determine the appropriate revenue amount on which to base the driver’s pay. We refer to this process as mileage allocation.

For example, suppose a move consists of a total of 100 miles.

  • Driver A, who drives 30 miles (or 30% of the total miles), will have an allocation rate that is 30% of the revenue.

  • Driver B completes the remainder of the trip, which is 70 miles (or 70% of the total miles), and will have an allocation rate that is 70%.

The system then calculates each driver’s pay by multiplying the revenue amount times the allocation rate then times the driver’s percent-of-revenue pay rate.

[revenue X percentage of miles driven X resource’s percent-of-revenue pay rate]

To make this calculation more apparent, a new read-only field displays the allocation rate for each resource in the Trip Settlements Folder.

Resolved issues

Invoicing

  • NSUITE-105309
    DCC application is counting invoices using a NVARCHAR parameter for invoice number when the column is VARCHAR. This causes a table scan. The parameter needs to be changed to VARCHAR.

  • NSUITE-203338
    After upgrading to 17.60, the billing queue doesn’t retrieve data. The stored procedure d_invoices_printqueue3_sp fails when the INI setting PrintInvoicesByUser=Y

Microsoft® Dynamics GP integration

  • NSUITE-202774
    When customer uses the Reverse Pay option in Trip Settlements, the system is unable to transfer the pay to Great Plains as an AP Settlement because the Credit amount is being added to the Purchases amount.

  • NSUITE-202433
    The Tax Type field in the Vendor Maintenance window for the GPI export is not being populated with the 1099 type from the Pay To profile.

  • NSUITE-202833
    Invoices are not transferring to Great Plains with ALT - ID enabled.

TMW Rating

  • NSUITE-203172
    When computing charges in the Profit and Loss window, the system does not apply billing rates that have a Trailer Type restriction.

  • NSUITE-202078
    When computing charges for a consolidated trip in the Profit and Loss window, the system does not pull appropriately a billing tariff configured with a distance (route) and lgh_type1 based table index.

  • NSUITE-201982
    When pre-computing pay, secondary pay details are not applied if the primary pay tariff has multiple tariff indexes and the only difference between the indexes is the Route.

  • NSUITE-202277
    Third Party Pay isn’t working when a manual pay exists for other assets.

Trip Settlements

  • NSUITE-203307
    Error received when retrieving trips in the Trips Ready To Settle queue and there are movements with consolidated orders.