...
What could prevent the system from calculating an asset depreciation?
If the asset does not have the accrued depreciation account registered, does not have the Rate registered, or if the accrued depreciation value is equal to the original value, this means that the asset has already been fully depreciated.
If the asset has indexation, the end of the Depreciation Calculation will be: accrued depreciation + correction of the accrued depreciation equals the original value + correction of the asset.
The calculation must always be processed with the base date on the last day of the month, and always after the MV_ULTDEPR parameter.
When the calculation displays the message: AF050MOEDA, this means that the currencies are not registered for every day of the month.
When the calculation displays the message: 050JACALC, the system says to correct the date of the MV_ULTDEPR parameter, but if the base date is lower than this parameter, it means that the calculation has already been processed, so be careful.
When the calculation displays the message: 050DTDEPR, this means that it is skipping one month of calculation based on parameter MV_ULTDEPR. That is, we have the parameter mv_ultdepr = 2/29/00 and we are trying to calculate base date= 4/30/00.
Only the last month calculated can be de-calculated. Example: The last month calculated was 04/30/2000, so we can only de-calculate this month of April. If the user needs to de-calculate until February, they must back up all the SN files. And enter the additions, deletions, calculations, and backup, all over again. Remember, the user must take responsibility for this backup; after running the de-calculation several times, nothing can be done.