4Site
Support Request System
View Patch #50.013.026
Description
Patch ID:
Date Implemented:
Patch Title:
Patch Type:
Request IDs:
Bug
Enhancement
Other
02241 -
Can't inactivate an account if JV status is Reversed
02105 -
Reversed JE prevents account inactivation
Symptoms:
Req. 2105 Reversed JE prevents account inactivation Req, 2241 Can't inactivate an account if JV status is Reversed Cindy: The reason why it doesn't allow you to inactivate an account if the JV status is "R" is because a JV with that status can be voided. If it is allowed it would then use an inactive account and put the transaction line(s)to the suspense account instead of it's real account. The onus is then on the user to check the suspense account periodically and fixup the problem. This has to be a 2 part fixup. Allow the account to be deleted but then JV post has to change to validate that the account(s) are still active, on the off chance the Reversed JV is ever voided.
Solution:
In AC: Retrieve Journal entry ids that reference the account selected for inactivation, Then display the JE IDs that need to be posted prior to deactivating the account. IN JV: Retrieve a list of accounts (jvline.accid) related to the JE selected for Posting, then test each account to ensure that that is exists and that its status is A(active). Display a message reporting any missing or inactive accounts, if found, and prevent Posting the JE. Note: above validation is performed app in JV prior to selecting when to execute posting, (now in foreground or later in background) so the BJV (background posting) application should not need revision.
Browse Patches
Find a Patch
Return to Request System Menu
