17.10 (all)

A PDF version of the complete 2017 release notes is available here.

17.10.10

Resolved issue

  • 200040
    Three-day sales adjustment that was written in code from a workflow has an issue where an old adjustment is canceled and a new one is created. When the adjustment date is today’s date, current code sets the end date to today -1 which is yesterday.

17.10.050

Resolved issue

  • 200001
    On consolidated orders, move manager is updating the cmd_code on the orderheader table to whatever is the first freight detail row found in a list. This is incorrect and is causing issues for FIX. Steps create a consolidated order with two freight detail rows with different commodities and then save. Check the cmd_code on the order header. Both orders will have the same cmd_code.

17.10

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.

Dispatch Dashboard

Tracking stores in critical need of product deliveries (PTS 103155)

Forecasting product demand and scheduling deliveries to retail service stations is no longer a planning-a-day-in-advance model. Higher volumes, frequent changes to retail pricing, and tighter product allocation management by suppliers demand a model that is more agile.

Agility relies on increased visibility and frequent reporting of information, including:

  • Inventory levels from automatic tank gauge systems

  • Actual delivered volumes

  • Wholesale pricing

Armed with this information, dispatchers can rearrange delivery schedules as market conditions change, and do it in real time.

Fuel Dispatch now provides a dashboard showing which stores are most in need of deliveries in real time. A graphical display shows each store’s sales, reading levels, and time to retain/runout. Dispatchers can focus on the stores in critical need instead of reviewing each store individually.

Link to topic: Dispatch Dashboard overview

Quick Copy MasterOrder

Creating and copying master orders (PTS 101008)

A master order is a template from which future orders can be copied. When you create master orders in the Call On Demand Order Entry and Oil Field Order Entry windows, you manually set the order’s status to Master (MST).

The essential difference between a master order and a regular order is that a master order is unavailable for dispatch.

Previously, to copy a master order, you opened it in Call On Demand Order Entry or in Oil Field Order Entry. You then accessed the Copy Order/Trip window to create the copies.

Now, you can copy master orders in the Quick Copy Master Order window. In this window, you retrieve a list of master orders for a specific revenue type or Bill To. If a master order does not specify a commodity’s unit of measure, or if you need to change the commodity quantity, you can add this information to the new orders. You can also enter up to four reference numbers to appear on the new orders.

Link to topic: Copying master orders

Resolved issues

  • 98748
    OFOE will not cascade times in the stop section of an order. This is in direct contrast to CODOE’s functionality. The affected fields include StopArrivalDate and StopDepartureDate of LLD and LUL.

  • 99596
    The customer is seeing a negative sales figure in the Today’s Sales column while in the Forecast Order Review Screen within Fuel Dispatch. The calculation for Today’s Sales is not taking into consideration deliveries that were made that same day.

  • 100039
    Customer cannot edit trips where the first leg has been paid and completed out. They have trailers that are pre-loaded then dropped in a yard, and hauled at a later date. Sometimes the order has to be paid depending on the date so the driver is paid.

  • 102534
    This is happening because of INI ShiftPlanningDeadheadMode=Current From Fuel Dispatch, when planning multiple orders in sequence using the Card Planner, the system will automatically assign an End Empty stop (EMT) to loads in sequence 2, 3, Etc.

    Ex: Load 1 contains - BMT - LLD - LUL (At Company A) Load 2 contains - BMT (At Company A) - LLD - LUL - EMT. The BMT location on load 2 is automatically assigned based on the LUL stop from load 1. The issue occurs when the LUL stop on load one is updated. This is not automatically updating the BMT stop on load 2. In the below example, loads are planned as described above. THEN the LUL stop on load one is updated. This has no effect on load 2. Load 1 contains - BMT - LLD - LUL (Initially At Company A, Updated to Company B) Load 2 contains - BMT (At Company A) - LLD - LUL - EM. The BMT company on load 2 should be automatically updated based on change to LUL company of load 1.

  • 103444
    Site Snapshot was updated in Fuel TMS 16.40 from PTS 99551. Calculations for Manifold Tanks are showing incorrect values on the Target on Hand as well as the Critical Values. This test can be ran against the Database on the SQL2012 Server on the Network. The database needs upgraded to 16.40.14. The test along with the screen shots were done on the DB Locally. Any manifold tank on any 16.40.14 DB should work the same.

  • 103952
    When splitting a trip and selecting a reason code, the reason description and code are not being recorded properly in the SpltTripReasonLog table. Rather than the actual description and code, UNKNOWN is inserted for the description, and 0 for the code.