cancel
Showing results for 
Search instead for 
Did you mean: 

Message no. AA660 in ABAA

Bohdan
Active Contributor
0 Kudos

Hello Gurus,

I'm facing an error AA660 during posting of unplanned amortization for an asset saying that transaction value in area 31 (local area) contradicts NBV rule. I found references to this error in a lot of SCN threads, but each time the answer boiled down to changes in the settings for particular area in OADB (suggestion being to put "All values allowed" for NBV rule).

Technical side of the issue is ok, but the trouble is why should the asset NBV be negative after posting of unplanned depreciation at all? Asset value in 31 area at the end of the June (by the way, it's also end of fiscal year) equals to appr. 1.500.000,00 RUB, unplanned amortization equals appr. 180.000,00 RUB. So how can the NBV be negative? Could you please advise me what is the logic for calculation of NBV in such cases and how to get rid of the message without modifying NBV rule?

Thank you!

P.S. Some details:

- asset is purchased on 15.06.2015;

- start of depreciation in area 01 - 01.06.2015;

- start of depreciation in area 31 - 01.07.2015.

- unplanned amortization posting date - 30.06.2015;

- depreciation methods - all linear.

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member183424
Active Contributor
0 Kudos

Please read the KBA document 1896699 - Error message: AA660 occurs in T-code: MB1A to analysis for this error message.

Former Member
0 Kudos

Hi,

According to me can you please check the transaction type you are using in T-Code ABAA. Now issue in your case is depreciation for depreciation area 01 starts from 01.06.2015 so it is said as purchased in fiscal year 2014-15 (01.07.2014-30.06.2015) which is purchase in last year, so here transaction type to be used is 640. Now depreciation for depreciation area 31 starts from 01.07.2015 so for this fiscal year is 2015-16 (01.07.2015-30.06.2016) which is said as purchase in current year, so here transaction type 650 needs to be used. So this issue is coming. If you change the depreciation start date from 01.07.2015 to 30.06.2015 then the issue will not come into picture.

Regards,

Malhar.

Bohdan
Active Contributor
0 Kudos

Hello, Malhar!

I've already tried with both transaction types - the same issue.

What is really strange, when I changed the settings to "All values allowed" in test system, there were no error, but the valus of asset at the end of fiscal year were not negative at all. They were perfectly normal positive values.

Former Member
0 Kudos

Hi,

Can you try to change the depreciation start date of 30.06.2015 and then try with transaction type 640.

Regards,

Malhar.

Bohdan
Active Contributor
0 Kudos

Hello,

I've already wrote that I tried to post unplanned depreciation with both transaction types on this date.

Former Member
0 Kudos

Hi Wirtschaftsmann

Go to AO21 - choose the ScrnLayout (Depr. on main asset no. level) > Fields groups rules > check 17 field (Negative values) as optional.

1. Go to asset master data: AS02

2. Go to depreciation

3. double click depreciation area specified in the error.

4. Check "Neg.vals. Alowed" field

5. Save

6. Post again the trasnaction

Regards

Jandoval Nascimento