Wrong Ship to party determination in return outbound delivery 502 MVT

[Pranab]

Dear Experts,

Below is my business scenario.

I want to return RTP material to vendor. My plant and storage location is EWM activated. I receive material with RTP material via inbound delivery into EWM where I do putaway and goods receipt, later when I have considerable amount of RTP material accumulated in my warehouse I want to return it to the vendor.

I am using transaction code MIGO_GI with movement 502. Here I enter the material, dispatching plant and storage location, quantity and destination vendor. Here in my case the plant and storage location is EWM managed. Thus when I save, an outbound delivery gets created which gets distributed to EWM.

My plant is maintained as a customer, I have also maintained customer in vendor master in the content view.

When I display my outbound delivery in ECC, I find that the dispatching plant as customer is determined as ship to party customer in header and not the ship to party customer from vendor master.

I hope I am able to explain my scenario.

Expecting some guidance. Pl suggest where am I going wrong.

Regards,

Pranab

[JL23 · Accepted solution]

A 501 is a unplanned receipt, a 502 a cancellation of an unplanned receipt.

if you get a delivery because that is the desired communication path to EWM then the delivery created for a 502 movement is so to speak a cancellation of the initial delivery.

But a cancellation of an activity to store goods in your warehouse is not automatically an outbound delivery to your customer (vendor)

Just imagine the same process without EWM in the background, then 502 is just removing stock, but it is not creating a delivery to your vendor.

From this point of view I think that the ship-to party in your delivery is absolutely correct with your dispatching plant as it is a pure internal process. Your entered vendor number is just needed and used to find the right RTP stock