3
Logged this w/ Microsoft support desk (SR # 118120319409654) but was directed here.
There's a bug in the asset retirement window that allows a user to enter 2 lineitems of detail (say 1 line for Proceeds & 1 line for Expenses of Sale) by manually clicking into an amount field on the 2nd line.
When retiring with this type of incorrect split, the user will receive a 'Return Code 17' error but more significantly, there will be an UNBALANCED set of G/L distributions created (which can be posted to G/L) AND creates an UNBALANCE FA00902 table which is relied on heavily for all subledger reporting.
Outside of training, there's nothing to do from stopping users from incorrectly processing this way and the impact is significant...
There's a bug in the asset retirement window that allows a user to enter 2 lineitems of detail (say 1 line for Proceeds & 1 line for Expenses of Sale) by manually clicking into an amount field on the 2nd line.
When retiring with this type of incorrect split, the user will receive a 'Return Code 17' error but more significantly, there will be an UNBALANCED set of G/L distributions created (which can be posted to G/L) AND creates an UNBALANCE FA00902 table which is relied on heavily for all subledger reporting.
Outside of training, there's nothing to do from stopping users from incorrectly processing this way and the impact is significant...
STATUS DETAILS
Needs Votes