Skip to Content

Does exist Outbound delivery split in EWM based on weight / value / volume?

Hello experts,

Is it possible to split automatically the Outbound Delivery Order in EWM based on either value / weight or volume?

If this is possible only manually, can you please share the steps?

Thank you very much in advance!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Apr 24 at 01:02 PM

    Hi,

    "On the other hand, I assumed the "Value" of the delivery is in EWM since you can invoice before PGI."

    To clarify that first: no, EWM does not know values. IBGI triggers the creation of the invoice in ERP, that's it.

    "Basically the WHYs are related to the transport. For instance "The Volume in the Outbound Delivery Order doesn't match the physical space in the transport", "The transport planned, cannot arrive and it needs to be substituted", "The weight is too much and quantity needs to be split"

    OK, transport is always a good reason for splits.

    I believe there is a way to trigger a split of the outbound delivery order with the help of a process code (so you still have only one outbound delivery request, but more then one order). But I have never really got the process codes working.

    When planning TUs, you can assign full ODOs, but you can also assign items of ODOs. This would trigger a split later when posting GI from the TU. I have not managed to make this assignment of items in the shipping cockpit, and I have not test if you can remove an individual item after you have assigned the ODO to the TU (but there is an icon for it, so I guess it works).

    Where you have to be careful then, is the creation of WTs and Pick-HUs. Because this does not get affected by this TU assignment (at least when I tried), which means you could create a Pick-HU where the content should go to two different TUs.

    Something you can work with?

    Brgds

    Juergen

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 18 at 07:34 PM

    Hi,

    can you elaborate a little bit more WHY you want to do that? (but value for sure does not work, because how is EWM supposed to know the value of the delivery).

    Brgds

    Juergen

    ---
    Want to learn EWM?
    Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Warehouse+Management-SAP+EWM
    Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

    And it is EWM. NOT eWM - Duh!
    And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 25 at 01:51 PM

    Thank you very much for your Guidence, I will try with your recommendations.

    Closing the Question...

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 23 at 03:26 PM

    Thanks Juergen for your interest.

    +++++++++++++++++++++++++++++++++++++++++++++

    Basically the WHYs are related to the transport. For instance "The Volume in the Outbound Delivery Order doesn't match the physical space in the transport", "The transport planned, cannot arrive and it needs to be substituted", "The weight is too much and quantity needs to be split"


    We know there is a standard functionality in the ECC side we can use, but customer needs to be able to do this in the EWM side, after the Outbound is replicated.

    +++++++++++++++++++++++++++++++++++++++++++++

    I know we can load HUs in different Transport, however by this time it is too late since the transportation planning happens before. Therefore there is a requirement to split the outbound delivery in EWM side.

    +++++++++++++++++++++++++++++++++++++++++++++

    On the other hand, I assumed the "Value" of the delivery is in EWM since you can invoice before PGI.

    +++++++++++++++++++++++++++++++++++++++++++++

    Do you know any alternative? have you faced this before?

    Thanks in advance for your time!

    Cheers!

    Add comment
    10|10000 characters needed characters exceeded