When batch requests are processing overlapping sets of transactions, updates for one job will be rolled back while the updates for the other job will complete normally. However, the updates being rolled back could leave some records unprocessed.
For example: Assume Freight Bill Generation Request A is running with a date range from -3 (Start Adjustment Days) to 0 (Cut-off Adjustment Days), while Request B is running using a date range from -2 (Start Adjustment Days) to 0 (Cut-off Adjustment Days). The overlapping vouchers are those that meet the date range criteria for Request B. If a voucher is processed successfully by Request B, the same voucher in Request A will fail causing the creation of the Freight Bill which includes this particular voucher to be rolled back. The Freight Bill being rolled back could have included other vouchers not selected by Request B (vouchers for Start Adjustment Days -3). In this case, those vouchers will be left unprocessed. These vouchers would be eligible when a subsequent Freight Bill Generation Run was performed.