8/10/2019 0000377501.pdf

http://slidepdf.com/reader/full/0000377501pdf 1/2

SAP Note 

Header Data

Symptom 

During the delivery of purchase orders or when deliveries are created from projects or for theprovision of materials for subcontract orders, a delivery split occurs which cannot be followedlogically.

Other Terms 

ME2O, CNS0, VL04, stock transport orders, replenishment deliveries

Reason and Prerequisites 

l The analysis of the deliveries created using the report from Note 355404 does not return anysplit-relevant differences between the deliveries.

l The causes of the split, which are specified in Note 155565 or 339412 (missing partner inpartner determination procedure of the delivery), are also ruled out.

Solution 

Check whether the planned delivery date (or the time) or the goods issue date of the items to bedelivered are in the past and differ from each other.

First of all, a delivery split occurs if the originally planned delivery date (which is in the past)of the reference items is different. However, when you create the delivery item, a rescheduling isexecuted so that a new delivery date is calculated which is in the future and which is the same forthe 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 codedescribed in the correction instructions in copy routine 301 (or a copy of this routine in thecustomer name space). The correction ensures that overdue delivery dates or goods issue dates areuniquely set to the current date for the data transfer from the preceding document. As a result, thedelivery 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 currentdate), the manipulation of the delivery or goods issue date in the copy routine has no effect on thescheduling result.

Note that changing the standard copy routine 301 is a modification. Therefore, after you import theSupport Packages or perform an upgrade, check whether the modification still exists (transactionSPAU or SPAM).

Note: The changes to the copy routines are a modification that you may not be able to implementusing SAP Note Assistant. If you cannot implement the modification automatically due to a changedsource code environment, use the editor function of SAP Note Assistant and enter the changed rowsmanually. After you implement the modification, you may no longer be able to implement thesubsequent standard notes or modification notes automatically. In this case, also use the editorfunction to implement the source code changes at the required place.

Other Attributes

Validity

377501 - Delivery split with backlogged delivery date 

Version  12 Validity: 23.12.2013 - active Language  English

Released On  23.12.2013 14:56:12

Release Status  Released for Customer

Component  LE-SHP-DL Delivery Processing

LE-SHP-DL-STO Stock-Transfer-Order  MM-PUR-GF-SC Subcontracting

 PS-MAT-DLV Delivery

Priority  Recommendations / Additional Info

Category  Consulting

the note contains a modification

Other Components

Modification

8/10/2019 0000377501.pdf

http://slidepdf.com/reader/full/0000377501pdf 2/2