All business transacted with Crossflight Limited is subject to the British International Freight Association (BIFA) Standard Trading Conditions, current edition. Copies available on request or via our website at www.crossflight.com
I have a client that is getting the same error on version 10.2.400.9
The other odd thing is that if we select a specific Asset in the filter for the Asset Depreciation Calculation it seems to run for all assets and gives this error for many of the assets.
It was a problem with how we first set our assets up on day one when we migrated from a different a/cs package. The following advice isolated the issue and recommended a solution that worked:
You have loaded the assets at their current nbv position with an asset life of the remaining number of months to be depreciated over so, for example, asset number 14553 has an opening nbv of 0.97 and an asset life of one month. This has meant that there was no need to ‘backdate’ the Fiscal Calendar to cover the lives of existing assets as part of the system build. All things being equal, the depreciation calculation should have resulted in a charge of 0.97 in month one. However, the issue here is that the ‘placed in service’ date of the asset is 09/04/2015. 2015 is not in your calendar and, even if it was, the depreciation would charge in April 2015. To handle the assets the way you want to, the placed in service and asset addition dates need to be the same - in this case 01/04/2018. Note - 01/04/2018 being the date of migration to Epicor.
The only way to fix this is to take all the assets out and re-input them with the correct dates. Unfortunately, as they are posted, we cannot simply take them out using DMT. We will need to delete them from the tables.