Understand swapped tickets

The Batch Swap functionality can be used to help resolve situations when the next pending ticket's information is incorrect but there isn't time to resolve it before the ticket needs to be started. In this situation, you can allow the next pending ticket to start, despite containing incorrect information. After the pending ticket is started, you can locate the correct pending ticket, if it exists, or you can create a new pending ticket with the correct information. Once done, you can initiate a Batch Swap to replace the current active ticket information with that from the correct pending ticket while still retaining the accumulated volume information.

When the Swap operation is executed, the active ticket information is replaced with that from the selected pending ticket. However, the accumulated volume remains unchanged from what it was before the swap, and the Volume To Go and Estimated End Time are recalculated based on the new information. The pending ticket is removed from the Pending Schedule (as it has become the active ticket), and the previously active ticket is placed back in the Pending Schedule in the same position as the removed pending ticket.

Note: If the Batch Swap results in a different product in the active ticket, a slight inaccuracy in the accumulated volume of the new Active Ticket can be expected. This inaccuracy is a result of volume corrections for density, temperature, and pressure being calculated based on the product defined in the previous Active Ticket. This behavior is unavoidable due to the cumulative nature of volume correction calculations.

After the Batch Swap is completed on the Batch Transfer, the Batch Transfer Sources are updated with the product information from the newly active ticket.

Any Action Sequences associated with the Batch Transfer will not be re-executed. For more information on Action Sequences, see Action Sequence.