Enter a reason code when the status of the batch is set to restricted

Hello Experts,

I have a requirement to enforce a reason code, when the status of the batch is set to restricted. This includes transactions QA11, QA12, MSC1N and MSC2N. I have few options in mind but looking for best approach from the experts.

1. Create a characteristic named reason code and use an enhancement spot to make this field mandatory when the status of the batch is set to restricted. This should address MSC1N and MSC2N transactions.

2. Enhance UD screen to call the batch classification (Like the MIGO screen) and use the above mentioned logic from QA11 & QA12.

Please let me know if there is any better approach to address this requirement.

Thanks for your time and valuable suggestions in advance!

Sunil.