Yep, it will create it automatically, but it will ...
# fixed-assets-mgmt
k
Yep, it will create it automatically, but it will not be a history per se, it will be assets’ “future”
l
It makes sense to me now after testing. What's the best practice related to DHRs from the old system? 1. Not import them 2. Import them since the acquisition 3. Import a lump sum depreciation history prior to transition to NS I guess 2 is the most ideal but are historical depreciation reports really distorted if this is not followed?
k
you never import DHR, but you upload midlife assets data twice - ones as a new upload into asset listing and another - you run a saved search from that listing for DHR upload and upload that data; NS calculates DH on its own based on the data in that search. Beware - it HAS to be precise and exactly like it is in FAM manual
l
That sounds scary considering the number of assets multiplied by that history. Thanks. I'll test it thoroughly.
k
well, if you read the manual, it is very clear which fields you need for the DHR search, you should be able to do it without any issues.
l
Gotcha. Thanks.
I ran into this guide which says: If the prior year net book value is not equal to the asset original cost, set the asset original cost to an amount equal to the prior year net book value and then import the asset record. Does that mean that the Asset Original Cost must be equal to the Prior Year Net Book Value? For example, a fixed asset was purchased in Jan 2020 by our newly acquired subsidiary's legacy system. Original cost is 36000 with 36 month-life. That gives me a prior year net book value of 24000 as of 12/31/21. If I am to migrate it to NS starting 1/1/22, is my Asset Original Cost and Prior Year NBV 24,000? Based on the guide above
k
this is for generic view of the assets, not for midlife assets data migration