Introduction

Loads in TMWSuite that have zero charge amounts, will by default still be dispatched or invoiced. TMW has functionality that allows a stored SQL procedure to run and make updates to the system during the save process of a movement. This functionality can be harnessed so that if certain criteria exist, the status of the order will be manipulated, so that if a user does not want zero charge orders to be dispatched or invoiced they do not have to be.


How it is done

If an EDI tendered load, a copy of a master order, or a new order is created when the order is saved, a SQL script looks at the order and determines if it meets the requirements: 

  • An “Available” dispatch status is restored on orders with a charge amount other than zero. The system is then set to do nothing further to the order. 
  • A “Review” dispatch status is applied on orders with a charge amount of zero. The system then updates the order: 
  • Dispatch Status: “On Hold”  
  • Invoice Status: “Do Not Invoice”  


If later, a rate is established on that order, either from the rating engine or manually added to the order, when the order is saved, the SQL script reviews the order: 

  • Dispatch Status: “Available” (If the charge was greater than zero) 
  • Invoice Status: “Pending” 


Controls

Typically, orders that are repeated with regularity are copied from the Master Order into a new Master Order. There’s also a possibility, however, that customers can copy an order that’s not a MasterOorder and move planned resources into this order.  When this happens, any planned resources on that order will disappear when the dispatch status is set to “Review.” 

To ensure this doesn’t happen you can make changes to the Copy Assets in TMW by: 

  • changing an INI setting to not allow users to copy any assets over from an existing order. 
  • using a group restriction to make the check box for copy assignments “display only” so the option cannot be selected. 

A screenshot of a computer Description automatically generated 


Reporting

ASR created for other clients a report to show orders that had been moved to the dispatch status of “On Hold.” This allows the customers: 

  • visibility of these loads 
  • to track missing values 
  • to look for charges that don’t meet a standard threshold to ensure that charges meet the requirements

ASR also created a Dispatch Load Board that looks for loads that are “On Hold.” This gives the customer: 

  • visibility of any load that is on the books, but not available for dispatch. 
  • a clean interface because the load will disappear once it’s no longer “On Hold”.