First of all, a delivery split occurs if there is a difference between the originally planned delivery date (which is in the past) or the goods issue date of the items to be delivered. However, when you create the delivery item, a rescheduling is executed so that a new delivery date is calculated which is in the future and which is the same for the deliveries created. As a result, the split can no longer be followed logically.
To stop the unnecessary delivery split for overdue delivery items, you can implement the source code described in the correction instructions in copy routine 301 (or a copy of this routine in the customer name space). The correction ensures that overdue delivery dates or goods issue dates are uniquely set to the current date for the data transfer from the preceding document. As a result, the delivery split is avoided for the time being.
Afterwards, the delivery is rescheduled. As forward scheduling is executed for outstanding delivery items regardless (that is, picking date or transportation planning date are set to the current date), the manipulation of the delivery or goods issue date in the copy routine has no effect on the scheduling result.
Note that changing the standard copy routine 301 is a modification. Therefore, after you import the Support Packages or perform an upgrade, check whether the modification still exists (transaction SPAU or SPAM).
Note: The changes to the copy routines are a modification that you may not be able to implement using SAP Note Assistant. If you cannot implement the modification automatically due to a changed source code environment, use the editor function of SAP Note Assistant and enter the changed rows manually. After you implement the modification, you may no longer be able to implement the subsequent standard notes or modification notes automatically. In this case, also use the editor function to implement the source code changes at the required place.