cancel
Showing results for 
Search instead for 
Did you mean: 

New Depreciation Area - AFBN

Former Member
0 Kudos


Dear Experts,

My user has given a new scenario where we have to calculate tax depreciation for assets transferred from US books to SG books. When the transfers were executed, the tax depreciation area was not set up in the SG books' Chart of Depreciation. We do have other company codes assigned to the same chart of depreciation. For these other company codes, tax depreciation calculation is not required. In addition, the transferred assets and the assets in the other company codes share the same asset classes. The requirement is that we want to calculate the tax depreciation in the SG book only but not the other company codes.

Initially, we are looking at setting up the tax depreciation area in the SG book and activate the depreciation area via AFBN (program RAFABNEW). This will activate the tax depreciation area for all existing assets under the chart of depreciation/asset class assignment. However, we found out that we could not deactivate the depreciation area in the existing assets in the other company codes. This is regardless of whether we activate the field XAFBE (deactivate depreciation area) in the depreciation area layout. Seems that this only works with new assets.

Would like to seek your advice on the options available other than creating new asset classes for these transferred assets.

Is it possible to enhance the program RAFABNEW to include company code and asset classes?

Thank you.

Accepted Solutions (0)

Answers (1)

Answers (1)

ryszard_belec
Active Participant
0 Kudos

hi,

if you want activate depreciation area in one company code you should enhance RAFABNEW.

regards

Ryszard

Former Member
0 Kudos

Hi Ryszard,

Thank you for your reply. If we enhance this program and add selection parameters for company code and asset class, do you see any risk in data integrity? The contention from my consultants is that they are concerned that selective activation of depreciation area of legacy data will results in data integrity inconsistencies.

Kind regards, TL

former_member351125
Contributor
0 Kudos

This is another option that I used on that scenario, but it is up to you if you want to follow the same approach. We created a custom program that will put a temporary deactivation date on the assets the we do not want to extend the new book. Basically this is direct update on field ANLA-DEACTIV.

Then we run AFBN, since the assets are deactivated, new depreciation area will not be created on these assets, but only on those assets that are active.

Then you can set the deactivation date again back to "Blank" after you run AFBN.

Thanks!

Jhero