17.30

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.

Enhancements

Common dispatch features

Adding a trailer wash at the beginning of a trip (PTS-104970)

Now, you can add a Trailer Wash (WSH) event at the beginning of a trip.

Menu options

Reorganization of commands on the Operations menu (PTS-104968)

Now, the Planning Worksheet, Trip Folder, and Order Entry commands are located at the top of the Operations menu by default. Clients still have the option to reorganize this menu, and the menu will preserve custom layouts when applying an upgrade to the system.

Fuel Maintenance

Managing declined fuel transactions in real time (PTS-86655)

Two changes have been made to how transactions are recorded in the cdfuelbill table:

  • You can now set up Fuel Import Integration to send an e-mail notification when an error occurs that causes a fuel purchase to be stopped. You can have notifications sent to one or more users. The e-mail provides the transaction number and the error message. Transactions with errors do not create entries in the cdfuelbill table.

  • When cancelled transactions are processed in Fuel Import, entries in the cdfuelbill and paydetail tables for these transactions are removed.

Currently this configuration is available for the Comdata interactive interface only.

Restricting miscellaneous purchases (PTS-101403)

In previous versions, to restrict non-fuel card purchase by product types, you had to access the vendor’s site. Now, you can determine which non-fuel, or miscellaneous, purchases are allowed for a card using the Product Codes window. You access the Product Codes window from Card Maintenance. It lists all non-fuel product codes. For any selected product code, you can define or update a daily maximum amount, a one-time amount, and/or an override amount. You can also view the daily and/or one-time amounts used.

Currently this feature is available for the Comdata interactive interface only.

Resolved issues

Dispatch

  • 97093
    The .Net Advances/Misc Labor window from the Add-Ins does not restrict the pay types that are displayed to those flagged as Edit in Dispatch (pyt_editindispatch=Y) like TMW Operations does. This allows users to create pay details for things like child support and 401k deductions, right from the Advances/Misc Labor window. This should be prevented by the flag on the pay type.

  • 99725
    Without a limit of empty miles, clients are overpaying for empty miles in TMW Operations.

    There is a GAP item of functionality existing in TMWSuite Dispatch, but it does not exist in TMW Operations. TMW Operations does not currently have a way to limit the empty miles that a trip can have like TMWSuite does. The customer is trying to limit the empty miles that are allowed to be on a trip, but have not found a way to do this yet.

  • 103112
    Accessorial pay is being duplicated on consolidated loads. This prevents the users from being able to invoice their Rate by Move Bill To’s in the queue. This is causing billing errors and extra steps by the users to remove the additional line haul rows.

    In TMW Operations, if an order is pre-rated or the linehaul charge is edited in the Profit and Loss tab, the Linehaul line is saved to the database as an invoicedetail row. If there are multiple orders on the move this causes problems for Bill To’s set as Rate by Move.

    In the Invoicing folder a Rate by Move invoice expects only one LineHaul invoicedetail for the whole move. TMW Operations creates one Linehaul invoicedetail for every order. When retrieved in the Invoicing folder, that causes the invoice to be overstated. The interface does not allow the user to delete these Line Haul rows.

  • 104272
    Customer is at risk of dispatching trucks without trailers. Dispatchers are receiving a "Stop #: x at xxx Requires a Trailer, but does not have one assigned" save error when they attempt to start a trip with the following events (BMT, DMT, HPL, DRL) and no trailer is yet assigned at the HPL stop.

  • 104740
    Incorrect calculation of mileage due to the DistanceBasedOnDrvConfig=Y General Info Table setting being ignored. The customer uses the setting to specify Dispatch/Settlement Mileage Bucket by driver. This works in TMWSuite Dispatch, but does not work in TMW Operations. TMW Operations appears to be ignoring the General Info Table setting and using only the default mileage bucket specified for TMW Operations in the TTS50. This setting should override the TTS50 defaults with what is specified in the Driver Profile.

EDI

  • 69006
    Need to have the ability to identify/audit when multiple 210 messages are received for a shipment.

  • 93151
    Found a bug in Data Exchange: if a person creates a custom script that is like 'dx_204', in this case 'dx_204v2' the system will try and run both scripts during a normal 204 import.

  • 98825
    Companies are coming in UNKNOWN and the stop events are changing from LLD to HPL when it should remain LLD since it is a drop.

  • 99033
    When an order comes in with the same Bill To and same SID as a manual order, it matches to the manual order even when the LTSL2 setting update manual orders is turned off.

  • 101201
    The earliest/latest dates on a 204 are showing correctly on the EDI Details but these dates are not applying on the event. When the global setting LTSL configuration utility setting UpdatePastDates is enabled, the earliest/latest dates on the pickup are not being updated with the values mapped in the 204. The dates are staying how they were originally sent in on the 204.

  • 102615
    Clients switching from EFS Transcheck to TCH Fuel Interactive face changes for how they pay their third party carriers once EFS officially takes the old interface offline. Currently, the solution does not elegantly support third-party pay.

    In TMWSuite, we can assign cards to PayTo’s and assign cards to multiple tractors. The business need for this is as follows:

    InTransit uses Smart Funds cards to pay their third-party carriers. They assign one card to a Pay To and then they assign multiple tractors to that specific card. .Net does not allow either of these functions. PTS 33838 documents this.

    This is a GAP item that works in TMWSuite, but we do not have this functionality in TMW Operations or Add-Ins.

  • 103434
    Client is using company based EDI so the trading partners on the order do not represent the bill to on the order. In the Edit 214’s on hold screen the e214ph_bill to column represents the trading partner. PTS 103361 was created to modify these column headers to represent trading partner. The client needs to be able to identify and use filter rows to restrict by the bill to on the order. To accomplish this the order bill to needs to be added to the results grid on the Edit Auto 214’s on Hold screen.

  • 104676
    Fix trip updates to grab active current activity using the get_cur_activity_sp.

  • 104778
    \.Net Comdata Fuel Import needs to set the cfb_otherfuelprocessed flag like TMWSuite Fuel Import.

File Maintenance

  • 103343
    The customer needs to be able to have Comdata Fuel Cards set by Tractor. We need to be able to trip updates by tractor. The assumptions are:

    • Client will have unique customer codes for their Board/Gold Carriers.

    • Trip Validation will be done by Order Number.

  • 104349
    Issues with the Route Maintenance window:

    1. Creating a new Route via Route Maintenance, RevType1 can get saved over the branch value in certain cases. See steps to reproduce.

    2. When retrieving a route, it was retrieving only by Route ID and Branch — it was ignoring Bill To and always returning the first if there were multiple routes based on just route ID and branch.

    3. The Route ID drop-down wasn’t displaying correctly in the following case: Branch set, Bill To set to UNKNOWN. If two route IDs were the same, but differed only by the Bill To, four rows would show (and all had the same order number, which is incorrect). The one retrieved would be the first one always.

    4. Make Bill To read-only like the other fields Route ID and Branch when editing an existing route.

  1. Issue with the Route Generation window: When processing, it processed only by Route ID and branch, didn’t include Bill To, so only the first matching one would be processed (even if it wasn’t selected to be processed). Related settings: TrackBranch GIS1= , NSetRevType1DefaultFrom=B3

Order Entry

  • 101181
    When the Load Trailer Compartments window is closed, the Compartment Status icons (in the Cmpt Status column) of the Stops Grid should update to the appropriate icons depending on the compartment loading status.

    This automatic update is not occurring when the Load Trailer Compartments window is opened from the Trip Folder > Edit menu; however, the automatic update does occur if the Load Trailer Compartments window is opened by clicking the status icon button in the Cmpt Status column of the Stops Grid.

  • 101416
    When you have more than one trailer in the Trailer1 column on a leg and update an order, the Trailer Drop Maintenance window keeps displaying. This should happen only when you have multiple trailers in the different "trailer buckets" (Trailer1, Trailer2, Trailer3, etc.). The client has a lot of these scenarios, so this is popping up for them a lot. You should be able to reproduce in any 16.20.105 database. The issue is isolated to split trips (the Drop Maintenance window does not open on non-split trips).

  • 102603
    Receive Out Of Memory GEH when creating an order that has assets, quick dead head enabled and actualized first stop.

  • 102857
    HPL issue within the Asset Assignment window: Customer modifies the pickup event in Asset Assignment window from LLD (Live Load) to HPL (Hook PreLoad). Currently, if there is a deadhead event, the trailer from the deadhead is inserted into the Trailer1 field in the current segment. The trailer should be left as UNKNOWN to allow the customer add the trailer as appropriate. This is a correction of PTS 101872, which had incorrect information.

    6/27/2016 - Customer identified additional scenarios that they felt were not handled properly after the initial scenario was coded properly. All scenarios that have been identified (so far) for the customer in the Asset Assignment window have been documented in a XLSS spreadsheet.

  • 103299
    Undo Cross Dock. Cross dock an order that is LLD / LUL / LUL.

    On the LLD / XDU / XDU trip: Select the first XDU and choose Edit, Cross Dock, Undo Cross Dock.

    Once that is done, the order sequence of the stops is now incorrect. Should be: LLD 1 LUL 2XDU 0 ------XDL 0LUL 3But is LLD 1 LUL 2XDU 1 ------XDL 4LUL 3

    Even odder things happen if, instead of the first XDU, you pick the last and undo it.

  • 103884
    When generating a fuel solution for a split trip, the second leg of the trip is generating with the last stop only. No other stops on that leg are being included. The first leg is working properly.

  • 104142
    Application is throwing a validation error after the customer attempts to split a trip after using a CTR event. The CTR event should be completed instead of throwing an error.

  • 104487
    Once settlements have been run against a trip, no stops can be unactualized, but pay can be deleted.

Planning Worksheet

  • 102298
    Customer is experiencing a GEH error when using the Sort Power Closest To Trip feature in the Planning worksheet.

Systemwide

  • 105183
    TMW Operations will not automatically update entries in the TTS50.ini file

TMW Rating

  • 97063
    When computing pay for a trip via the Profit and Loss tab, the system does not set the currency value correctly. The system always assumes the default US$ currency regardless of the currency set at the tariff level, the pay type level, the resource level, the company level, the orderheader level, and the [Invoice]DefaultCurrency TTS50 setting.

    This can also be replicated in the 16.20.41 build of TMW Operations.

  • 97724
    Per the business specification, users are allowed to create only one rating rule per tariff. The TM Billing Rating Rule Maintenance window is currently enforcing this requirement, but not handling it gracefully. Handle the duplicate tariff rule scenario gracefully upon save, letting the user know that duplicate rules exist without relying on a GEH message.

  • 105614
    The Get Rate button does not enable when there are valid cities and postal codes entered for origin and destination.

Trip Folder

  • 99584
    Trip Folder - HCT - Asset Assignment

    1. The Status is not auto changing from Dispatched to Available when the assets are removed.

    2. The DMT and HCT event are being removed from the second leg so the only events left are BMT/LUL when the assets are removed.