Swap a split ticket

If the currently active ticket has already been split once or more, a Batch Swap is still allowed. The difference in behavior in this situation is that the active ticket being put back in the Pending Schedule will be inserted as a new pending ticket with a Scheduled GSV (Gross Standard Volume) set to the non-split portion of the original Scheduled GSV. For example, if the active ticket’s Scheduled GSV was originally 20,000 m3 and the ticket was split after accumulating 3,000 m3, then when a Batch Swap is executed, the active ticket is put back in the Pending Schedule as a new pending ticket with a Scheduled GSV of 17,000 m3. This accurately reflects that 3,000 m3 of that batch was already written as a completed ticket in the Completed Tickets before the Batch Swap was executed.

Note: Swapping is not recommended on a batch where a split has occurred because historical transactions such as completed tickets will not be adjusted. The following warning is displayed if a swapping action is performed: It is not recommended to perform a swap for a batch that has already been split. Historical transactions will not be affected by this swap operation.