The same ticket reprint rules apply to customer pickup tickets and customer service work order tickets.Printing the delivery ticket is a key step in the process of completing an order. If changes are made to the order after the initial delivery ticket has been printed, the system flags the order to remind you to reprint the ticket to reflect the changes. Examples of changes that flag a ticket for reprint include COD amount, line item quantity, delivery date, route code.
Orders for which a delivery ticket has been printed display a "Y" in the D column of the grid in the Logistical Scheduling routine. Orders flagged for reprint have an "R" in the D column. Note that the "R" flag does not prevent you from continuing to process the order - it is only a reminder that the order has changed since the ticket was printed.
The reprint ticket function is complex. When reprinting tickets, it is important to keep the following conditions in mind:
The first date in the header may not be the first date on all of the line items.
A line item may have the same first two dates as the header (both tickets can be printed).
A line item may have the same first date (ticket can be printed) but a different second date (no ticket can be printed).
While a line item may have a first date that matches the header’s second date (ticket can be printed), any second date then could not have a ticket printed.
A line item could have two dates which are neither the first or the second date on the header (no tickets can be printed).
The primary rule for ticket reprints is that if an update is made that affects any of the inventory scheduled to be delivered on the first date, the flag for the first date on the line item that was updated and the flag for the header change from P to R. If that update also affects the inventory scheduled to be delivered on the second date, the flag for the second date on the line item that was updated and the flag for the header are cleared. If the user makes an update that affects any of the inventory scheduled to be delivered on the second date, the flags for the second date on the line item and on the header change from P to R.
Additional rules include:
When changing a line item, the only flags in the header record that can be changed are those for which that line item is scheduled.
Example: If the header is scheduled for 06/01 and 07/01 and a line item is scheduled for 06/01 and 08/01, only the first flag in the header can be changed as a result of a change to that line item. This scenario results in the header being set to R:P.
When changing a line item that has tickets for two dates printed and the change affects the first scheduled date, the line item flag for the second date must be cleared. This includes changes to lines where the first flag is already R.
Example: If the header is scheduled for 06/01 and 07/01 and the line item is scheduled for 06/01 and 07/01 and both tickets are printed (P:P in both the header and the line item flags), a change to the inventory scheduled for the first date on that line item results in both the line item and the header flags being set to a single R indicating that the first date should be reprinted and the second date must be reprinted.
Example: If the header is scheduled for 06/01 and 07/01, both tickets are printed, and the first date is changed to 08/01, all flags in both the header and line item are cleared, requiring a reprint of the 07/01 ticket.
A change in the status of an order from scheduled to estimated clears all delivery ticket flags on the header and the line items.
Any time that the delivery ticket flag is set to null for a date, the pick list print flag for that date must also be set to null.
Changes at the header level, such as next delivery date, deposits of any kind, or addition of line items, reset the header flags to R, causing the line items also to reset to R.
The second delivery status and second route fields are future settings for those fields; these values do not indicate the current status or route for the associated lines. These are the values that the order inherits when the first date’s delivery is completed and the second delivery date becomes the first delivery date. The only updates performed using these values are to the route calendar. The inventory to be delivered on the second and subsequent dates appears in the route calendar using the second status and route if those values are present.
A ticket can only be printed for the second date if a ticket has already been printed for the first date and one of the following scenarios is true:
There is one line on the order that is only scheduled for the second date and also has pieces reserved. The line may be scheduled for dates other than the first date.
There is one line that is scheduled for both the first and second dates that has all pieces assigned for the first date and some or all pieces reserved for the second date.
When changing dates on line items there are many possible scenarios. The following scenarios all assume an example of an order with 3 line items and 3 dates: the first line scheduled for the first date (06/01) with an additional unscheduled quantity; the second line scheduled for the second date (06/03) and the third date (06/08); and the third line scheduled for all three dates.
The user changes the first date on any line item to a new date (05/29) that was not previously on the order and it is earlier than any of the previous dates.
Result: All flags are cleared because there is a new first date on the order.
The user changes the first date on line item 3 to a new date (06/02) that was not previously on the order, which becomes the order’s new second date.
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is set to R because it no longer includes line 3.
-The second header flag is cleared because there is a new second date.
The user changes the first date on line item 3 to a new date (06/04) that was not previously on the order, which becomes the order’s new second date.
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is set to R because it no longer includes line 3.
-The second header flag is set to R because it no longer includes line 3.
The user changes the first date on line item 2 to a new date (06/02) that was not previously on the order that is still the second date on the order.
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is unchanged because this change does not affect it.
-The second header flag is cleared because there is a new second date.
The user changes the first date on line item 2 to a new date (06/04) that was not previously on the order and is not the second date on the order.
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is unchanged because this change does not affect it.
-The second header flag is reset because it no longer includes line 2.
The user changes the first date on line item 1 to the second date on the order (06/03).
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is set to R because it no longer includes line 1.
-The second header flag is set to R because it now includes line 1.
The user changes the first date on line 3 to the second date on the order (06/03).
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is set to R because it no longer includes line 3.
-The second header flag is set to R if the quantity for line 3 has changed; otherwise it remains a P.
The user changes the first date on line 2 to the first date on the order (06/01), leaving some inventory scheduled on 06/03.
Result:
-All line item flags are cleared because there is a new first date on the line.
-The first header flag is set to R because it now includes line 2.
-The second header flag is set to R because the inventory from line 2 has changed.
The user changes the second date on line 3 to the third date on the order (06/08).
Result:
-The line item flag is set to a single R for the first date, while the second date is cleared.
-The first header flag is unaffected.
-The second header flag is set to R because it no longer includes line 3.
The same ticket reprint rules apply to customer pickup tickets and customer service work order tickets.
As described above, once you print a delivery ticket for an order, certain changes to an order cause the system to flag an order for reprint. The following describes how the system applies the delivery ticket reprint flag when you change orders with multiple delivery dates. The following examples assume tickets have already been printed for both the first delivery date and the second.
If the changes affect any of the inventory scheduled for delivery on the
first delivery date, the system flags the first delivery ticket for reprint.
second delivery date, the system flags the second delivery ticket for reprint.
both the first and second delivery dates, the system flags the first delivery date flag for reprint and clears the delivery date information for the second delivery date.
To print only tickets that have been flagged for re-print, use the Selection Options field in the Print all Delivery Tickets routine.