Hi All,
My requirement is to update the total accumulated depreciation up to the cutoff date during the import process and set the cutoff date as the Thru_Date. Then, when running depreciation using the Depreciation Proposal, depreciation should be calculated correctly only for the period after the cutoff date.
Hi Asanka Dinesh,
I cannot answer your question directly, but I can tell you about our approach, from a migration perspective:
For the migration of fixed assets incl. needed transactions, we don’t use the default wizard in IFS. Instead, we’re creating the FA Objects with the migration tool (currently FNDMIG) and afterwards adding the transactions via script (FA_OBJECT_TRANSACTION_API.NEW__).
This enables us to fill the date information individually (like TRANSACTION_DATE, EVENT_DATE, RETROACTIVE_DATE) → we can set the thru date.
Specifically we create at least 3 transactions per object:
Keep in mind, that there might be more than one ledger / book.
BR
Florian
FLEXiCODE
My company is currently transitioning from IFS10 to Cloud 24R1. We used the External File Assistant for the FA migration, very similar to the method outlined above. Once imported we’ve tried to run a test depreciation proposal for the next current period and we are getting a year cross over error.
Our current thinking is that because our aged assets with Acq Dates in prior years do not show a history of depreciation, just a prior year valuation, the system wants to perform a catch up depreciation that look to prior years, thus the error. This is just an assumption at this point.
Is there an override setup that allows us to not recognize the catch up on the relevant FA objects?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.