Adding new depreciation area to assets

[srinivasavepa]

Hi,

1.I created a new depreciation area 13( tax depreciation) . When I am executing the transaction AFBN for adding this depreciation area to all the assets, first I am getting the error message

"

+/- sign rule for the new depreciation area is too restrictive

Message no. AU 113 " and

" Closed fiscal years for areas 01 and 13 differ by more than 1 years ".

2. I am in 4.6C and in OAAR, for depreciation area 13 the closed fiscal year is 2002 and for all others 2007.

3. The OSS note 421549 is already implemented.

Any help for resolving this is highly appreciated.

thanks

Srinivasa Vepa

[Former Member · Accepted solution]

Hii

as u said the message says that the closed fiscal year for dep.area 01 and 13 is more than one year.

and u also state that the fiscal year close for dep area 13 is 2002 and for all others is 2007.

so first step u need to do is to close the fiscal year for dep. area 13 till 2006.

here the functionality of AA works like it allows only 2 fiscal year to be open at the same time.. so as the dep. area 13 is open since 2003 it will give u an error..

so please try to close all this and i m sure it will solve ur query......

thanks

sejal

[Former Member]

through AJRW close your fY till 2007

[srinivasavepa]

Sejal and Sourabh,

Thanks for the inputs. I could solve this myself. The problem was in my config client, the last fiscal year closed was 2002 for all the depreciation areas. When I copied the existing depreciation area, the last fiscal year for the new depreciation area was also 2002.

When this was transported to the quality client, where actual master and transaction data exists, except for the new depreciation area all others were 2007. There is no way you can execute AJAB or AJRW for a particular depreciation area.

Hence, in the config client, I executed AJAB for all the years till 2007 and then copied a new depreciation area and transported to QA client. Now all the depreciation areas show the same 2007 as closed fiscal year.

Thanks

Srinivasa Vepa

[srinivasavepa]

The second error message number is AU 158