Once a reason code is used in a transaction; it becomes a permanent record. Need the ability to deactivate reason codes; especially those used for special one time purpose.
Solved
Reason Codes: Need the Ability to Deactivate
Best answer by brockinl
You can create a “dummy” account in the Chart of Accounts, add the account to the reason code and then mark the account inactive. This won’t prevent a user from selecting the reason code but it does prevent the transaction from posting upon Release (with accompanying error message). We use this method for obsolete reason codes used on the Issue and Receipt screens in Inventory.
+16Hi
Once there is a record attached to a reason code, you can not delete it, even if it was only for one time usage.
The only suggestion would be to change the name to DO NOT USE. You can not even delete the accounts associated with it.
Kandy ~ If a member helped you, please *Like* their post, and if a member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
Thank you for the response. I did change description to DO NOT USE. I also changed the usage from Adjustment to Production. That way it does not show in the reason code selection for inventory adjustments. Acumatica should provide the capability to deactivate reason codes.
+1Has anyone added this to the feature ideas for consideration in a new release? This really seems like we should be at least abie to deactivate. My Controller is going crazy with people using them even though they say DO NOT USE!
+16fosterjeff01 wrote:
Has anyone added this to the feature ideas for consideration in a new release? This really seems like we should be at least abie to deactivate. My Controller is going crazy with people using them even though they say DO NOT USE!
Here is a similar one: https://community.acumatica.com/ideas/the-capability-to-modify-the-id-for-reason-code-at-ui-level-15573
You could comment on it that you would like the ability to deactivate them as well.
Kandy ~ If a member helped you, please *Like* their post, and if a member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
A possible option would be to create a customization that adds an active checkbox to the reason codes DAC, then remove inactive reason codes as part of the selector lookup via with a conditional parameter. As it mostly is just a foreign reference key lookup to the reason codes table so if we change it at the reason codes DAC they should all be adjusted elsewhere as well.
Another option is just customizing the ReasonCodeID in the DAC editing the attributes for PXSelector and make it filterable, then you can set a filter during the lookup on the other screens and have it not display based on however you filter it. If you or no one else does the customization, I can probably help some time next week.
Thanks! - Johnny Tang
1 person likes this
Here ya go! Covers all DAC’s, but not graphs, so possible areas that are missed. I was unable to simply make the change in the reason code DAC and have it flow down to the child, so had to edit each DAC separately.
This should do what you need it to do though. Also, you’ll need mark the reason codes active since I did everything strictly from the DAC side. If you have other customizations, you may also run into errors. You’ll have to add what I did into your other customizations at that point depending on the code/DAC.
Thanks! - Johnny Tang
1 person likes this
You can create a “dummy” account in the Chart of Accounts, add the account to the reason code and then mark the account inactive. This won’t prevent a user from selecting the reason code but it does prevent the transaction from posting upon Release (with accompanying error message). We use this method for obsolete reason codes used on the Issue and Receipt screens in Inventory.
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.