Skip to Content

Delivery Split

HI Guru's

The requirement is to split the delivery based on following conditions:

1) If the Quantity is equal to 500 make a separate delivery for those particular line item. If i found in 1st line item make a separate delivery for 1st line item only.

2) If the line item is equal to 300 and quantity is less than 500 for those 300 line item make a separate delivery.

3) If 1st line item is more than 500 (eg:- 600) then do a partial delivery for that particular line item (eg:- D1= 500 and D2=100).

4) If the first line item is equal to 700 and second is equal to 300 (Same Material Group) then the Delivery should be created like D1 for L1 =500 and D2 for L1=200+L2=300.

5) Above condition (4th point) different material group then D1 for L1 = 500 and D2 for L2=200.

what i found is we can create a routine and assign in Copy Control item data. But can all this conditions can be achieved in one routine and without any complications.

Note: Client has implemented SAP AFS.

I know there is lot answers on Delivery split but my requirement are having the above validation which is making it tough for me.

Regards

Azhar Iqbal.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Dec 03, 2016 at 07:11 PM

    It seems to me that the whole story is not about item quantity, but more about weight/volume and product compatibility. It looks as if the business is looking for a way to implement pack optimization with cartonizing for single/multi-material and automatic subsequent delivery split to fit into containers or vehicles. The only thing, which I have seen working, that is similar to this, was Ortec LEO.
    In contrast to Jelena, I would suggest, before going to your ABAP colleague, to spend more time with the business people and get the full picture.
    What is now 2 materials and 3 quantities, can really fast turn into such complex set of requirements, that your developer will throw you out of the window if you suggest that he does all the checks at delivery save (I refer to the ones, which the business will 'remember' about in a later stage of the project).

    Add comment
    10|10000 characters needed characters exceeded

    • Well, I was only suggesting to sit together with an ABAPer so that OP could see how the routines actually work. :) I might be mistaken but based on the verbiage here I suspect OP has been misinformed about what the routines can or cannot do.

      Could not agree more about going back to business to clarify the requirements. This can definitely be more complex than it seems.

  • Dec 02, 2016 at 07:54 PM

    Don't know about AFS but in general SD the short answer is - no. Your requirements are too complex to achieve with just a routine in general. I didn't read all of them (not a big fan of the "spec dumping", sorry) but right there at #3 you have a "complication". I believe when you have to break apart quantity for the same item you already need to use splitting profile or something like that.

    A routine cannot create an additional item, it can only tell "we need to start a new delivery for this item". And you can't even use it to analyze all the items on the delivery (well, not without "complications"), you can only make a decision whether current item needs to be split up. I highly recommend sitting together with an ABAPer just once and checking in the debugger how the routine actually works.

    Add comment
    10|10000 characters needed characters exceeded

    • I don't have any more information that already posted there. It was a while ago and we used a splitting profile, which is a configuration that you can easily test. A program was needed because splitting profile alone did not work exactly like we needed. It's not required.

      Not sure if some better/newer functionality became available since then (it was about 10 years ago) but that's out of the scope of this question.

  • Apr 14, 2017 at 10:27 AM

    Business drooped this due to lot of validation which is making a huge mess.

    So closing this loop

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 14, 2017 at 10:27 AM

    Business drooped this due to lot of validation which is making a huge mess.

    So closing this loop

    Add comment
    10|10000 characters needed characters exceeded