Hi Diwa,
Please find the screen shot for Dep Key.
↧
Re: SYST: Depreciation key
↧
Re: SYST: Depreciation key
Hi,
Please let me know the solution for the issue.
Please reply on urgent base.
Regards,
ramana
↧
↧
Re: SYST: Depreciation key
Hi ,
I asked you to share dep Key config screen shot.please share it.
Regards,
Diwakar
↧
Re: SYST: Depreciation key
Hi Diwakar,
Pls look dep key screen shot your reference.
and do the needful on urgent.
↧
Re: SYST: Depreciation key
Hi,
In the error you have provided the screen shot its stating 'Correct the multi-level method of depreciation key IN8.' but you are showing us the screen shot of Depreciation key S012. Kindly show the screen shot of IN8 Depreciation key and also the Multi level method assigned to IN8.
Regards,
Malhar.
↧
↧
Re: Legacy asset transfer
Hi,
By uploading the assets through AS91 tcode you are just entering the values in Asset Module but actually in Finance nothing is posted. So to post in Finance you have to use OASV or ABF1 tcode and post an entry in the system. e.g. if the asset is purchased at 1000 and accumulated depreciation is 600 then entry would be:
Asset Acquisition A/C Dr 1000 - AO90 T-Code
To Accumulated depre Cr 600 - AO90 T-Code
To Suspense GL Cr 400
By this the NBV of asset will come to 400.
Regards,
Malhar.
↧
Re: Sub Assets with remaining life
Hi Nisit,
After transfer the balance to sub asset, change the capitalization date and depreciation start date, here you have to maintain the date of the main asset, then system will automatically derive the expired useful life of the sub asset. Or if you have more sub assets for transfer the balance, then do it by LSMW, here you have to upload the capitalization date & dep.start date along with other details.
Regards,
Mukthar
↧
Re: Legacy asset transfer
Hi Viru,
If you are uploading the assets in mid year, then you have to input current year depreciation by click on transactions button and select the appropriate transaction type. After that do FI posting in OASV. However, you have to input the last posted depreciation period in OAYC.
Regards,
Mukthar
↧
Re: Legacy asset transfer
Thanks a lot everyone for the valuable inputs. I will close my querry 
↧
↧
Message no. AA660 in ABAA
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.
↧
Re: Message no. AA660 in ABAA
Hi
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
↧
Re: Message no. AA660 in ABAA
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.
↧
Re: Message no. AA660 in ABAA
Please read the KBA document 1896699 - Error message: AA660 occurs in T-code: MB1A to analysis for this error message.
↧
↧
Re: Message no. AA660 in ABAA
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.
↧
Re: Message no. AA660 in ABAA
Hi,
Can you try to change the depreciation start date of 30.06.2015 and then try with transaction type 640.
Regards,
Malhar.
↧
Re: Why line item settlement is not working for AuC created in previous FY
Please check Table ANLA ,field ANLA-XOPVW for this asset may not be flagged.
↧
Re: Why line item settlement is not working for AuC created in previous FY
Hi Sam,
Yes you are right, no flag at XOPVW field. Is it possible to make changes directly in table ANLA to fix this asset?
Thanks
Marianna
↧
↧
Re: Why line item settlement is not working for AuC created in previous FY
Hi
What was the previous AUC capitalization process ? investment measures ?? so the old AUC is posted using this method and you now change the AUC asset class from investment measure to line item settlement ?
Regards
Mahmoud El Nady
↧
Re: Why line item settlement is not working for AuC created in previous FY
When Auc was created initially, the settings for the asset class were different (no line item -ANLA-XOPVW). When asset setting was changed manually, there was no line item created. So one way out , is to create a new AuC, reverse old and post it to new.
↧
Re: Why line item settlement is not working for AuC created in previous FY
Instead of reverse, we can also use ABUMN and transfer old to new. It will work.
↧