Advanced Return Management / Scrapping with movement type 551

[VitaliT]

Hello all,
we are facing following issue:
One of the logistical follow up activities we want to use is "transfer to scrap". However, the point is we cannot use it, due to some specific characteristics of the movement type 551. It requires a reason code. I would like to change it to the "not mandatory", but we need it for other process.
Question:
There are two possibilities to solve it.
1. We use a copy of the movement type 551 where the reason code isn't mandatory.
Question: Can I change the movement type used for that follow-up activity to another one?
2. There is a field on the material inspection document where I can enter the reason code.
Is it possible to add the field?
Thanks in advance
Vitali

[Lakshmipathi]

Copying movement type 551 or creating a new movement type involves lot of configuration and testing. Instead, what you can do is to create a variant in TVARVC table with the required field values (field values can be Sales Org, Delivery type, Shipping Point, Ship-to etc.,) which is specific to that follow up activity. Now with the delivery user exit, set a validation in such a way that as and when the delivery is created, compare the fields in TVARVC with LIKP and if matches, blank the reason code field.
By implementing this logic, any time, you can change the field values without ABAP help or TR movement

[VitaliT]

Hi Lakshmipathi,
thanks for the response.
I will think about your suggestion. To be honest, I haven't yet understood your idea fully. 🙂
From my point of view. There should be a possibility to enter a reason code e.g. due to compliance reasons.
There are also companies that doesn't allow to scrap without entering a reason code.
best regards
Vitali