Skip to Content
avatar image
Former Member

Correction of Depreciation Posted in Area 32

There was one issue reported that previous years in 2015 there was difference in the depreciation posted in Dep area 01 (Book Dep) and 32 (Book Dep in Group Currency). Not able to know/understand why and how can this be happened when we have OABT settings where depreciation area 32 will always adopt values from depreciation area 01. Not seen this scenario before.

Has anyone experienced this issue? Now, client want to post adjustment entry for this difference. How can we post with adjustment with current settings?

Some of the post suggests to use ABSO/ABCO but when I try in ABSO, i get following error message: I guess again due to that OABT settings.

Error: "Contact Your System administrator (table error) - Message number AA380". Is it that we need to remove adoption flag in OABT and post adjustment and than put adoption flag back. I know it is not recommended way but can't think of any other solution. Kindly advise?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jul 05, 2017 at 07:21 AM

    Hi,

    The AA 380 means that you are using a current-year acquisition transaction type (TABWG-XZUGNE = X) but there is no current-year acquisition transaction on the asset or the opposite.

    best regards

    Bernhard

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 25, 2017 at 05:33 PM

    Hi C. Singh,
    I have seen this issue, and currently have it in our system today. We are running ECC 6, release 605, level 0009. I don't have an answer yet, but working on it. We also have Area 01 set up for Leading Ledger, 0L, and Area 32 is set up for Parallel valuation. In OABT, we have Area 01 set up so that Area 32 copies Area 01 for both APC and Depreciation. For one specific asset, there is a difference of .01 USD, or one penny, for the asset in Fiscal 2017. It shows up in the AR08 Depreciation Comparison report. The Asset has been around for several years, and this has decided to show a .01 difference. I am planning to open a ticket with OSS.

    My guess is there must be a configuration setting that is causing or allowing this to happen.

    More to come...

    Add comment
    10|10000 characters needed characters exceeded