HTP Delivery type created in logistical follow-up - Advanced returns management ARM

[diego_lewinski]

Hello,

We are implementing ARM for customer returns.

When we perform Logistical Follow up activity “0011 – Transfer to free available stock” in a WM managed warehouse (using tx MSR_INSPWH), the system is creating HTP delivery types “Deliv.for Post.Chge” for movement type 343.

However, when we manually create a 343 movement type using tx MIGO for the same plant / Site and storage location, the system doesn’t create any delivery. Instead it creates directly the material doc (49xxxxxxx doc).

Our customer doesn’t want the HTP deliveries to be created. They would like the Follow up activity 0011 to behave as a standard 343 movement type creating the material document right away (the same way it works in t-code MIGO).

Although I am not a WM specialist, I started playing with table T321 / tx OMLR in a sandbox to see if I could figure out a way to avoid the deliveries to be created but I could not.

So I have three questions:

Q1 – Is there a way to avoid HTP delivery type documents to be created and achieve what the client wants?

Q2 – Is there any customizing for HTP delivery type determination or is it hard coded?

Q3 – Why is the system behaving differently when creating movement type 343 via Tx MIGO vs creation within ARM?

Update: I figured out Q2:

I would appreciate any help you could provide. Thanks

Diego

[diego_lewinski · Accepted solution]

We found a work around:

If you first set the system to post the return for inspection mapping "Storage Location for Receive into Site" to a non WM SL, and then map the "Storage Location for Transfer to Free Available" to a WM managed SL, then the system will not create internal deliveries.

This is customized here:

I hope this helps somebody with the same issue.