Skip to Content

Error AA687 - You can only post in new year after closing the previous year

Hello experts,

I'm facing the following scenario. For one company we are trying the execute depreciation for year 2017 period 8, but system shows the message AA687.

I have checked the following tables:

- T093C: Here actual fiscal year is 2017

- T093D: Here last period of depreciation is 8/2015

- TABA: Here last entry is for 8/2015

- Transaction OAAQ: Last closed year is 2016.

So i reviewed notes "144441 - AA 688 or AA 687 during depreciation posting run" and note "26073 - RABUCH00 table T093D is inconsistent".

For the first one, it seems would work, but the program will change the period in T093D to 12/2016. So when running again AFAB the system will show that the next period to run depreciation must be 01/2017 but it is closed in financials.

With the second one, the workaround would update T093D with 7/2017 and AFAB wpuld execute but i don't know the colateral effects of this.

Please, i will appreciate your help.

Regards,

Fernando

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Aug 28, 2017 at 12:14 PM

    Dear Fernando,

    The reason for the AA 687 is that there is one or more years between the last depreciation and the current one.

    You have already found the right notes: 144441 and 26073.

    Report ZACORR_TABA_ENTRY_CREATE, from note 144441, is going to manipulate the tables TABA and T093D and makes a line in 12/2016, so the next period to post will be 01 / 2017.

    You say this period (01 / 2017) is closed in financials. this point is not clear for me. In FI, the fiscal year 2017 is closed or is is open whether in FI-AA you can close single periods. But it is not allowed to closed subledgers while you have the main ledger open.

    Therefore generally I would recommend to open 01 / 2017.

    In note 26073 you have a report to adjust the tables in a more flexible way. But the question is if then the depreciation is completely posted. In this case you have to test carefully on a test system.

    best regards

    Bernhard

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Bernhard,

      Yes, i solved the problem applying note 144441. Report ZACORR_TABA_ENTRY_CREATE made the entries for tables TABA and T093D. After this process, I run AFAB with period 8/2017 with "unplanned posting run" and it works flawlessly. I did this in my test system. After that did the same in production system.

      Now, everything is fine.

      Thank ypu very much for your valuable answer.

      Regards,

      Fernando