2019.2

Fixed an issue so that all parts of consolidated invoices are moving forward and backward together as a unit through status changes.

Fixed an issue with the billing queue shipper/consignee address information not showing correctly if the shipper or consignee was changed after the stop had been completed.

Included a fix so that the AR transfer to GP honors terms set up from the Customer profile.

Fixed an issue where users will receive a "Leg not ready to settle" error when attempting to process driver/carrier pay.

When transferring invoices to Great Plains, the multicurrency records will display the correct calculation method.

Fixed an issue where the LTL batch order re-rate functionality did not update the order rates.

Fixed an issue where supplemental invoices were allowed to be part of the billing consolidation.

Included an error message to display when an SQL timeout occurs, performance, and filter results resolutions.

Fixed an issue that occurred if a routing was corrupt (missing PU or DRP). The invoice header had blank entries for origin or destination states, which led to the system displaying and recording taxes incorrectly.

Fixed an issue with a mismatch existing between the length of the shift name in the dispatch and buffer databases.

Fixed an issue where driver shifts that were shut down were no longer showing in the control.

Fixed an issue with the stored procedure timing out for master bills that contained many bills and no consolidations.

Fixed an issue with stored procedure UtStopsConsolidated_AddSecondaryLoadUnloadEvents. This procedure was creating an additional PUL stop (not just an event) on LTL orders when the AddSecondaryLoadUnloadEvents General Info Table setting was used. This corrupted LTL Orders/Routing, and left the orders unusable.

The Map Control window now displays both Arrival and Departure dates and times.

Fixed an issue where there was a TL-sourced order, but it was cross-docked in LTL Operations, and the Hook Change Trailer (HCT) stop occurred at a different location than both the pickup and delivery. The pickup and delivery companies require appointments, but there is no communication of the stop appointments between TL and LTL Operations. Transparency of appointments is required for appointments booked for cross-dock scenarios to ensure the load departs the cross-dock location with enough time to make the delivery.

Fixed an issue with LTL/TL interoperability scenario where the LTL order was refused. The application was incorrectly showing the driver, tractor and trailer from the first (refused) manifest and the carrier from the second (successful delivery) manifest. It should have been showing all the resources from the second manifest.

Fixed an issue where the spot trailer set to deliver enroute was not dropping the chassis at the consignee, and was instead returning it to the terminal.

Fixed an issue where LTL resources still appeared as assigned in TMW Operations even after cancelling the LTL manifest and order. This caused time conflict errors in LTL when the assets were planned on a subsequent move.

Fixed an issue that occurred when attempting to assign an empty trailer drop order to the third leg of a multi leg trip, where the user received an error stating "Cannot assign order. No active leg!"

Fixed an issue where trips created using the Schedule selection in the New Trip window had a potential to be assigned to an incorrect shift.

Fixed an issue to make the extra info fields that were screen designed in the Trip Folder editable for LTL manifests.

Fixed an issue with a TL Stop type order where the delivery portion was cancelled, but it was still allowed to be assigned to manifest using the quick assign option.

Fixed an issue where TL sourced orders with multiple deliveries presented multiple conflict errors.

Fixed an issue that occurred when an 'F' type consolidated invoice failed to transfer - there was no record in the audit table for that invoice.

Fixed an issue where trailers were showing on incorrect company planner boards.

Fixed a routing corruption issue that occurred when a stop containing two events (Spot Loaded Trailer and Hook Empty Trailer) was dispatched.

Fixed a routing corruption issue that occurred when the re-route option was used in the trip grid.

Fixed an issue with LTL/TL interoperability scenario where the TL trailer was not being correctly updated when a combination of DRL (drop trailer) and HPL (hook loaded trailer) occurred.

Fixed an issue with order assignment applying to the incorrect manifest stop/event.

The system will now copy check calls when a driver and either a tractor or a carrier field are set for a leg.

Fixed an issue that occurred when unhooking a line-haul trailer at destination terminal - the asset assignment records would get the evt_number updated to the destination stop. As such, the first stop city in Asset Assignment History Window would then show as the last stop.

Fixed an issue that occurred after clicking on Start Trailer Storage from the door screen - delivery orders with appointments could not be added to the Storage manifest.

Fixed an LTL/TL interoperability issue that occurred where the BMT / DMT stops and associated trailer were not carried over to the LTL leg.

Fixed an issue that occurred when LTL completed one of the pickups - the trailer assigned in LTL did not cascade across the subsequent doubles moves/legs.

Fixed an issue that occurred with a drop and switch manifest. When changing the pickup from Live Load to Hook Preloaded, event codes for delivery and pickup changed to Hook Preloaded.

Fixed an issue with the LTLStatusJobs table. When processing turnpike doubles stops, an erroneous "Stop not found for update" error appeared due to multiple manifests being involved.

Fixed an issue that occurred with a multiple manifest scenario where the Driver Current ETA and current route information were incorrect.

Fixed a performance issue that was causing the Cross Dock window to load slowly.

Fixed an issue in the ReRoute window, where the user could enter a company (any company ID) rather than a terminal code. When this occurred, the manifest was rerouted with XDL/XDU stops at the company code.

Fixed an issue where stops that were previously set to Live Unload but were changed to Spot Trailer following a stop arrival did not have the Post Unload event created.

Fixed an issue that caused order routing corruptions. When the following were completed in the system, the routing on the delivery order was corrupted:

Fixed an issue where the system deleted the second leg of a split leg manifest when the routing on one of the orders assigned to the first leg was recalculated.

Fixed an issue that occurred when a TL order indicated that a stop was both arrived and departed when only the arrival had taken place. In addition, TMW Operations now updates with the correct departure time when the LTL driver uses the handheld to indicate a stop departure.

When an HPL order was assigned to the manifest, the system would clear the Hook Preloaded check box. When the order was subsequently updated (by saving it), the system added a live load routing stop in addition to the pre-existing HPL event. This issue has been resolved.

Fixed an issue where orders for the same customer, which were doing the same activity, were not consistently sending EDI 214s.

Fixed an issue with an object reference error in the LTSL 204 outbound logs. This issue occurred when an RT18 record was present in the edi_outbound202_refs table with a NULL value.

Fixed an issue where the LTL ETA calculation for linehauls was incorrectly using local Route ID/Pickup cutoff times.

Fixed a time conflict issue that occurred with LTL assets on TL orders.

Fixed an issue that caused false time conflicts as well as incorrect detention changes on the TL orders.

Fixed an issue that caused a false positive time conflict error to occur when a TL user attempts to use an asset on a subsequent move.

Fixed an issue that caused a GEH error after creating Turnpike Doubles movement.

Fixed an issue with refresh times increasing on the Deliveries window.

Fixed issues with the RateWare integration no longer functioning.

The TMWRating (LTL) integration with RateWare was no longer working for orders that had more than one freight detail record. Detail rows were sent to RateWare for each freight detail, but the system left invalid details blank rather than omitting them. This issue has been resolved.

The "last stop enroute" warning message appears for 'deliver enroute', and 'deliver direct' orders as well as assigned pickups.

Fixed an issue where the order status was incorrect when the rail pickup to linehaul manifest arrived at a DLT stop but the unhook event had not been completed. The Order Status field will now accurately list Arrived Term instead of Depart Term.

Fixed an issue that occurred when a manifest departs a hook preloaded pickup stop. The trailer was set to Planned, but should have been set to Loaded.

Fixed an issue that occurred when a rail line haul manifest contained a set direct delivery stop that involved a final drop loaded trailer. The available company of the trailer represented the terminal rather than the company ID of the customer at which the trailer was dropped.

Fixed an issue that occurred if the Rail Reservation is assigned prior to clicking Finish Load - the stops created by assigning a rail reservation had been showing up as Hook/Drop Empty Trailer.

Fixed an issue where 'Incorrect trailer propagation' followed a 'Rail Reservation assignment to a Manifest' that had a DRL stop and then an HPL stop.

Fixed an issue that occurred when setting the order to deliver enroute, and then setting the spot trailer. The trailer is not cleared off the remaining stops, and must manually be set to UNKNOWN.

Fixed an issue where the object reference error occurred when trying to undo a turnpike with two LTL manifests with assigned trailers.

When undoing the turnpike execution, the leg type values of the newly-created leg were set to those of the preceding leg in the TL order. This caused issues with visibility of the order within the company planners. The leg types of the newly-created leg are now set to UNK when creating a leg using the Un-Do turnpike functionality.

Fixed an issue that occurred on a pickup manifest with multiple orders. When the Leave On Trailer button was pressed for one order, multiple orders were left on the trailer.

Fixed an issue that occurred when users attempted to execute the LTL manifest. A false positive error message indicated that the cancelled LTL order was required on the appt ID of the LTL pickup order.

Fixed an issue with the manifest hyperlink in the LTL Mobile Messages screen not functioning.

Fixed an empty trailer drop order issue where the manifest contained two end terminal stops.

Fixed an issue that occurred when creating a TL/LTL manifest option. An error message would appear when a user accepted the move in LTL.

Fixed an issue where the handheld display did not include event details or container numbers.

Fixed an issue to display a warning message to a driver advising that a previous shift needed to be shut down before the current shift could begin.

Fixed an issue where the driver had to complete two events: one for the container and one for the chassis.

Fixed an issue that occurred when manually inserting a drop empty trailer stop to a manifest and then assigning a container and chassis. The handheld would display two separate stops (as expected), but the second stop would not display the chassis.

Fixed an issue that occurred when reverting an LTL manifest, completed through a handheld, using the Manifest Editor window to fix errors. When the LTL dispatch user "re-completed" the stops through the dispatch process, the times were not updated.

A similar issue occurred when a pickup stop was pushed to LTL Ops and the leg contained a Drop Loaded Trailer (DLT) event at an LTL terminal. The arrival was initially actualized with the time the driver arrived at the DLT stop, but before the manifest was completed, the DLT arrival time was modified using the Manifest Editor. When this occurred, the stop arrival time in TMW Operations was not updated correctly.

Fixed an issue that removed an in-progress manifest from the driver. This occurred when a manifest was pushed to a driver and the driver started working on it. When a new manifest was created and assigned to the same driver, and the sequence of the new manifest was changed to occur before the previously-started manifest, that initial manifest that was in progress was removed on the next mobile comm cycle.

Fixed an issue that occurred when a TMW Operations-sourced order has a leg pushed to LTL Operations. When the LTL manifest/orders were created using the Create TL / LTL button, the manifest / orders were then canceled, and the LTL manifest / orders were then re-created, a DB Concurrency Error message appeared, and the user could not book an appointment from within LTL Operations.

Fixed an issue in the Stop Departure - Add Pickup window, where the Bill To field was not modifiable by the user.

Fixed an order routing corruption issue that occurred when removing an order from a manifest.

Fixed an issue involved with executing T48 with the rerouting functionality when used at a relay terminal.

Fixed an issue with an error occurring when setting and saving a branch in the Terminal Profile.