cancel
Showing results for 
Search instead for 
Did you mean: 

How to copy asset useful life and expired useful life during ABUMN??

0 Kudos

Hi SAP Friends,

Can you please tell me how can i configure on how to copy the useful life and expired useful life from source asset to target asset during ABUMN?

What i did was,  in SPRO>Asset Accounting>Transactions>InterCompany Asset transfer>Define transfer variant>Define Transfer variant (to create a new variant similar as 2 (net method) then Specify tramsfer of fields (For New asset in Target Cocode) this time, for all areas of the new transfer variant Zxx i created, i ticked on "useful life, expired useful life, original useful life).

Then i perform testing via ABUMN and entered the transfer variant i created but the result is not as expected. It DID NOT copy the original useful life of the asset.

Can anyone help me, pls?

Thank you!

Eve

Accepted Solutions (0)

Answers (1)

Answers (1)

raymond_moynihan
Contributor
0 Kudos

Hello Eve,

Firstly, please clarify if  the depreciation keys are the same for the
old and new asset ? The depreciation key will deter0mine the useful life.
I would like you to have a look at SAP Note No.339528,
if transfering the asset within the same company code.

It will give you the logic of how depreciation is calculated in the
system.

If you require the planned depreciation to be similar as asset
XXXX, you will need to define the transfer variant to copy the
ordinary depreciation start date, expired useful life & period.

You can define this in IMG at the following path:-

Financial Accounting
   > Asset Accounting
    > Transactions
     > Intercompnay Asset Transfers
      > Define Transfer Variants
       > Specify Transfer of Fields (for New Asset in Target CoCd


The transfer is a closed process. In this process the sending and the
receiving asset have to be consistent. That means for example:
If the transfered amount is depreciated on the sending asset
you can not depreciate it again on the receiving asset.

Generally the following points are relevant (in case if you want
to bypass this (certified) logic):

1) Flag "Adopting dep. start date" in the depr. key
If you make a transfers within a company code, then you have to use
special transaction types (e.g. 300, 310) in order to be guaranteed,
that the values at the receiving asset match to the values to the
sending asset. Acc. to note 327088 for transaction type 300 and 310
you have to set the flag "Adopting dep.start date".

F1 Help:
Indicator: Transfer adopting dep. start date
Set this indicator, if you want to adopt the historical depreciation
start date and capitalization date from the retiring asset when you
perform intercompany asset transfers or intracompany transfers.

2) Specify Transfer of Fields

CU: FI-AA:
-> Transactions
-> Intercompany Asset Transfers
-> Automatic Intercompany Asset Transfers
-> Define Transfer Variants
-> Specify Transfer of Fields (for New Asset in Target CoCd)

3) Period control of the depr key

4) Of course also the depreciaiton start date

I hope this information will help to clarify the system functionality.

regards

Ray

0 Kudos

Hi Ray,

Thanks for your reply.

The 2 assets are almost the same as the receiving asset is copy from sending assets (so Dep Key are the same for both).  I did the customizing already and had created custom tty.

Everything is OK, like Expired useful life, Period, Ordinary Dep start date.  EXCEPT for "Useful life".  Useful life of the receiving asset is highier than the sending assets.   We need to have both the same. 

Can you please guide me?

Thank you!