Disable mvt 261 for restricted (expired) batches

Hi all,

I've a question. Is it possible to define on mvt type level is this movement can be performed. When batches expire the status is put to restricted. I want to prevent that these batches can be issues on a process order. I know that it's possible to change the warning message to an error message, bt this applies for all movements (including scrap or posting to blocked/quality).

Is there a nicer way to set this up?

Regards,

Maarten