@jvarughese23 - What I recommend is shutting off the “Automatically Release In Documents” in Sales Orders Preferences.  This will allow you to review the inventory issue batch and make the necessary changes to the reason code.

Is there any way around other than doing this , for each transaction to go and update gl account is not possible all the time .. I have seen  The Issue and receipts Working without using  reason Codes in  other  instances though Reason code has been defined , however am not clear  how    we can restrict  using or update reason code while releasing  the document 

Hi @jvarughese23 were you able to find a solution? Thank you!

@Chris Hackett  Not yet :(

@jvarughese23 There is no good solution here its the way it is designed. Only other option is to create a Reason (issue) code per posting class and ensure users pick the correct one when raising the issue.

Hi, does anyone know if there is a plugin/customisation available for this:

Currently the default issue/return reason code is set in “Inventory Preferences”. 
If they can change it so that the default reason code is set in the“Posting Class” it would be much better and eliminate a lot of manual work and opportunity for mistakes.

I have created a new Idea; please vote.

Thank you,

Laura

I came across the same issue. I think I found a solution.

On the issue you can change the Type to Invoice. If it is type invoice it allows releasing without ReasonCode and uses the Item/Posting class to pick the COGS from.