cancel
Showing results for 
Search instead for 
Did you mean: 

Asset Acq. Cost to be Capitalized/Expense (Depreciated) in a Ledger Based on Amount

Former Member
0 Kudos

Hi Team,

We have a requirement if the asset acquisition amount is less than the limit specified, the same should be expensed (Depreciated) out in Leading Ledger in same month and to get Capitalised in Local Ledger (Non Leading Ledger).

If the amount is greater than the limit specified the same should be capitalised both in Leading and Local Ledger (Non Leading Ledger).

This is possible if we put in Asset Master > Depr Area > Period > "1", the amount will expense out in the same month.

This is user intervention, kindly provide the alternative to the above.

Thanks in advance.

Ratesh M. Pitale

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello Ratesh, i had the same request few years ago and i have solved through a development.

In this way, you can schedule a retirement with a special transaction type of retirement affecting only one depreciation area. With the automatic retirement in a particular depreciation area, the amount is posted to expenses without user intervention..

Former Member
0 Kudos

Hello Aquiles,

Thanks for your information on the subject.

Further we would like to know which special transaction type you have configured

and what logic was given for the development.

Thanks,

Ratesh M. Pitale

shanid_mp
Active Contributor
0 Kudos


Hi Ratesh,

I think this we can do with Low value asset class.

Do the following.

1) Create a low value asset class and create asset where the amount limit is there.

2) In depreciation area where leading ledger is linked, assign a deprn key which includes base method type as 'immediate depreciation' - this will depreciate in immediate month.

3) In depreciation area where non leading ledger is linked, assign 0000 depreciation key if no deprn to be calculated.

Regards

Shanid

Former Member
0 Kudos

Hi Shanid,

Tried with this option before but it does not meet our requirement.

Thanks,

Ratesh M. Pitale