cancel
Showing results for 
Search instead for 
Did you mean: 

Depreciation, today posted back to 2018- to be reversed

former_member193516
Active Contributor
0 Kudos
270

Hi,

a colleague did today (2020) a depreciation run by accident for 2018. This created undesired postings. Do you know what we could do to fix this?

This would now need to be reversed, but is not possible?

Thanks in advance

Hein

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member193516
Active Contributor
0 Kudos

I did the re-calculation of values as suggested in that message.

After that, I thought I would change the depreciation key to 0000 and then do the re-run of the depreciation for 2018. But saving is not possible.

Unfortunately, it still brings me the Error message as above-

* Correction to ordinary dep. greater than acc. dep. in area 01

Do you know what else we could try here? Is there another transaction we could use?

Thanks

Hein

former_member193516
Active Contributor
0 Kudos

Thanks Nathan.

Yes, it is ony few transaction, a small company code.

Which transaction would you use then? We tried ABZU and ABAA but system gives messages-

1* Posting transaction is not possible (value date not allowed

2* Correction to ordinary dep. greater than acc. dep. in area 02

3* Correction to ordinary dep. greater than acc. dep. in area 01

Are there other transaction we should use for this?

Also, when we start aw01n the following is issued:

Values for have changed in dep. area 01 in fiscal year 2018

Message no. AU390

Diagnosis

Depreciation terms were changed in depreciation area 01 since the last time depreciation was recalculated. The values for that were saved in the database in fiscal year 2018 are therefore different from the newly calculated values by an amount of 542129.18.

Procedure

Check if the newly calculated values are correct. If they are, then carry out a depreciation recalculation. You should be aware that if you recalculate depreciation, new values could arise for all open fiscal years, and these would then have to be posted to the general ledger by means of a depreciation posting run.

If, on the other hand, you want to keep the values that are saved in the database, you have to set the depreciation terms back to how they were at the time of the last depreciation recalculation.

To see a comparison of the old and new values, you can use the Display dep. calc. function in the asset value display or the Recalculate values function in the Asset Accounting menu.

Proceed

Is there a risk to do so?

Thanks!

Hein

NathanGenez
Product and Topic Expert
Product and Topic Expert
0 Kudos

It can be reversed but requires a correction program. If it's just a few records, I would use some transactional updates but if it's more pervasive, then you'll need something programatic.

former_member193516
Active Contributor
0 Kudos

Thanks for the fast response, Tammy!

Unfortunately the asset year was also already closed but the FI periods not closed (grrrr).

I guess we need to do the reset of the asset fiscal year close and then give it a go.

Cheers

Hein

TammyPowlas
SAP Mentor
SAP Mentor
0 Kudos

Please see SAP Note: https://launchpad.support.sap.com/#/notes/2450680

subset here:

"1) Reversing a depreciation posting run is not possible for safety and consistency reasons.

2) To correct a already posted depreciation you can use "write up", (tcode ABZU) and "unplanned depreciation", (tcode ABAA). This is the foreseen legal solution.

Write-ups are used for correction of depreciation values that are calculated and posted in the past (in closed fiscal years). It is not possible to post a write-up to a asset that have no cumulated derpeciation (for example a assets that have been acquired within the current year).

If there is no cumulated derpeciation, you will get the error AA402.

If you need to make a correction to the asset with no cumulated derpeciation, you could use "unplanned depreciation", (tcode ABAA).

3) There are two workarounds if there is only one or a few assets concerned but they are on your own responsibility and you have to clarify this with your auditor:

a) Change the depreciation key to "0000", recalculate values and post the positive (or negativ) depreciation by executing tcode AFABN in repeat mode." source: SAP

Bernhard has some good suggestions here too: https://answers.sap.com/questions/430161/reversing-the-depreciation-posted.html