Create outbound delivery based on inbound delivery or inbound DESADV IDoc

[Former Member]

Dear experts,

is it possible to create an outbound delivery (VL01N) based on an inbound delivery (VL32N) or based on an inbound DESADV ASN IDoc? It's very important for us, that the outbound delivery contains the same packaging and handling units as the inbound delivery does. How can this be done?

Best regards,

David

[Former Member · Accepted solution]

Hi,

Can you describe the process in more details? Why the outbound based on the inbound? Usually the process is the other way around, so that you plan your inbound operations given the information what was shipped (as an outbound).

One way to work this out would be to generate delivery idoc from inbound delivery that would post an outbound delivery document in the same system.

Regards,

Dominik Modrzejewski

[Former Member · Accepted solution]

Hello Dominik,

thanks for your answer.

This is the process:

1. We create inbound deliveries in coordination with our suppliers

2. These inbound deliveries are sent to our shipper via EDI

3. The shipper collects several deliveries for one physical shipment and sends us a corresponding ASN notification

4. We create an outbound delivery (which is later used for creating the invoice) based on this ASN notification and forward it to our customer via EDI

That is why we need to know, how an outbound delivery can be created by using an IDoc or by using inbound deliveries.

Thanks and regards,

David

[Former Member · Accepted solution]

Ok, I dont think standard config can support that.

My proposal would be to base the solution on inbound delivery output. And either generate the idoc from this document that would post the outb. delivery, or directly call BAPI to create it.

What you need to make sure is that at PO or inbound delivery there is a reference kept to the sales order for final customer. So that you can find corresponding SO for which delivery needs to be created.

Regards,

Dominik Modrzejewski

[Former Member]

We solved the problem by creating a custom inbound processing.