(This text was previously sent to Gary Bisel on 2/28/18) to add clarity.
Apex seems to have one setting (“Have Valid Ticket Fields For Tare’) controlling two separate processes; taring trucks and sending loads to thirdparty loadout systems.
They should be separate settings. A truck may arrive in a yard and need a tare, but we don't know which job they may be assigned to. Many of our plants have a pool of trucks that work for us and they deliver wherever they are needed. It is the same as a taxi driver doesn't know where he is going next. We need to be able to tare a truck with no specific customer, job, product data. So far so good. However, when a load is sent to Libra batch controls, because “Have Valid Ticket Fields For Tare’ is turned off, it is possible to have the scenario I describe in the original suggestion. Currently its a matter of 'pick your poison'. Turn it on, you have to put dummy info on every truck that is tared. Not good. Turn it off, you can can get perishable product loaded and an error ticket.
Sorry for the lack of clarity. Hopefully that is a more thorough explanation.
This functionality already exists. A customer on credit hold prevents the load from being sent to the interface for example. And as long as 'Have Valid Ticket Fields For Tare' is set to Yes then other required fields (if set to require) such as Order, Zone, PO, etc. will prevent the load from being sent until the information is populated.
It would be helpful if there was more validation of data on the Apex side before sending to a third party loadout system such as Libra Batch. It should not allow a load to be sent to Libra if say, customer is on credit hold, hired truck is not correct, etc. The checks that would be made to print a ticket (apart from weights) need to be enforced before sending a load to a third party loadout system. No good putting perishable product on a truck to then find out Apex won't validate the ticket and prints an Error Ticket
(This text was previously sent to Gary Bisel on 2/28/18) to add clarity.
This functionality already exists. A customer on credit hold prevents the load from being sent to the interface for example. And as long as 'Have Valid Ticket Fields For Tare' is set to Yes then other required fields (if set to require) such as Order, Zone, PO, etc. will prevent the load from being sent until the information is populated.
It would be helpful if there was more validation of data on the Apex side before sending to a third party loadout system such as Libra Batch. It should not allow a load to be sent to Libra if say, customer is on credit hold, hired truck is not correct, etc. The checks that would be made to print a ticket (apart from weights) need to be enforced before sending a load to a third party loadout system. No good putting perishable product on a truck to then find out Apex won't validate the ticket and prints an Error Ticket