Hi Fernando,
Not required to change the dep.key as manual. Just you have to post unplanned depreciation by ABAA for previous period depreciation in current year. Once you have done posting, then system will calculate the depreciation for current year on wards as per dep.key.
Regards,
Mukthar
Hi Experts,
My client wants the value posted in currency translation GL based on individual asset number.
When I checked it in BSEG I come to know that asset number field in the BSEG is not field.
When I tried to execute FAGLL03 also for currency translation GL ,definitely it will not be there as it is not in BSEG.( I have attached a excel file with example)
So my question is how to get asset value in BSEG-ALNL1 field for currency translation GL??
Your help will be highly appreciated.
Thanks,
Rashmi Ranjan Sau
Hi,
While change dep key for an asset it run with warning key and after then error key, we want to 100% deprecation for an asset.
Warning Message: "Dep key D162 should no longer be changed "
"Enter d dep key with "Deprectiation by days" such as D162"
Err message:
Thanks and Regard,
Hemant
E662 syst:You cannot change the depreciation periods
Hi Hemant,
You are changing the dep.key from non-dep to the day to dep.to the day or vice versa. If it is, then you cannot change it. Either you have to create a new asset with correct dep.key and transfer the balances to the new asset or use the dep.key which has settings as old dep.key.
Regards,
Mukthar
Hi Mukthar,
Thank You very much
How can we unblock mass vendor ?
The reason for this behavior is an inconsistency in table T093D where and entry for depreciation area 05 is missing in company code XXXX.
Issue is solved by transport the table entry by calling transaction OADB, then select the
depreciation area 05 and choose "Table View - Transport" in the menu.
Note : Before masking above change ,Please make sure that Development systems FY closed will be same as production system. Otherwise you will be having inconsistency in T093B table with respect to the field LGJAN-Closed FY.
In case by mistake if you did not transport as advised above, you can use correction report ZT093B to set it back again as it was before .
Thanks everyone who helped on this thread.
Hi SAP Experts
We are receiving a new client and discover the account responsible
has never post the monthly depreciation posting from six month ago
(including months from last fiscal year).
Of course it is certainly an administrative issue and training subject.
However I would like to know it is possible to post the pending "depreciation amount" (from several months)
to the current fiscal year and period.
I do not like to open the past fiscal year just to run the depreciation run on closed periods.
I only want to post the "accumulated" depreciation posting to the current month.
It is that possible?
I think I could:
1. Change the depreciation key to manual
2. Post the pending depreciation amount with a manual depreciation posting (ABMA)
This will post a AA document
3. Run the depreaciation run
This will post the FI document with reference to the AA document
4. Return the original depreciation key (the lineal one)
5. Run the deprecation run normally (now each month as should to be).
This is the correct approach to solve this?
Many thanks for your inputs!
Hi
I am not commenting in the steps sequence of posting deprecation related to previous period in current period .. but may i bring to your attention that this issue has an accounting side also.. you may need to consult your external auditor to see if you he agreed with this action or not.?
Thanks
Mahmoud El Nady
Hi Folks,
I hope all is well. I am a student at California State University of Sacramento and I am learning a lot about SAP. Fortunately, they offer SAP classes and I work in the Public Sector which also uses SAP. However, I am stumped and was hoping someone could guide me in the right direction.
Background story of the situation is this: I had created assets that were hitting the wrong G/L Account (2310) for Asset class 7000 / 7100 and I needed to break them down to lower GL accounts (2411 and 2414). So, I created new asset classes 7200, 7210, 7300, and 7310 pointing to the relative G/L Accounts. I need to transfer 23,000 Asset from asset Class 7000/7100 to 7200/7210 or 7300/7310.
So, to make the transfer I am using transaction code ABUMN - Transfer within company code. When I do this, everything transfers over correctly. However, I have to manaully do this 23,000~ times. So, I created an LSMW to mass create the assets. So, now i have 23,000~ unposted assets that I have created to replace the original assets and I want to use the LSMW to do the transfers. However, whenever I go through the LSMW Recording and I click "SAVE" nothing happens. It does not take me back to my main screen to upload to file and continue with the mass transfer.
So, I don't need help with using the LSMW or how it works, but I need help figuring out why ABUMN doens't save during the recording. I know that ABUMN does two things. 1) It retires the original assets and 2) it transfers the values to the new asset. So, ABUMN is a two-fold transaction. My theory is that the LSMW is not recognizing the Retirement transaction that occurs in the background and therefore does not save. However, I am new to SAP so I don't know.
Has anyone had success or know why my LSMW -> ABUMN will not save during the screen recording? Is there a way to force it to save? Should I upload screen shots of my process? Any help would be greatly appreciated.. let me know what you experts think and I will provide any information necessary.
Thanks,
Sincerely, your upcoming student expert in SAP (eventually).
Hi Folks,
I hope all is well. Your CSUS College Student back at it again with another question. I work for the State too and they messed up their Depreciation Key when creating Assets. Now, I have to figure out how to fix deprecation for Assets.
Originally Assets were created with Depreication key LINR. LINR, regardless of the month that the Asset is purchased in, depreciates the first year in full and then uses the straightline method to calculate deprecation moving forward.
We updated the configuation and changed the deprecation key to ZINA, ZINA uses the straightline method from the month that the Asset was purchased and depreciates it monthly using the straightline method. This is what we want.
So, 1 solution is to Retire all of the Assets that have the LINR deprecation key and do a complex posting to the new assets using the ZINA deprecation key. However, this process was ruled out. We don't want to retire the Assets to fix them.
Now, we have Assets that have Depreciated too much. And, we have Assets that have fully depreciated when in actuality they still have a useful life. So, my question is how do we debit the asset (GL 2349009700) and credit Depreciation Expense (9033245118).
For Example: Asset 9700000000, Capitalized on 6/15/2012 for $6,245.79 with a 3 year useful life is fully depreciated. The correct useful life is 10 years. So, this Asset is not supposed to fully depreciate until 6/1/2022. As of today it should have 74 more months before it fully depreciates and it should be depreciating at 52.04825 on a monthly basis (6,245.79 divided by 120 months). How do I post $3,851.57 (74 months * 52.05) back to the Asset so it can continue depreciating at the normal monthly rate?
Thanks in advance! Let me know if I need to provide any additional information.
Dear Sau,
Hi Fernando
1. Unless you post depreciation for Previous Year(s), you cant close Asset Year in Asset Accounting
2. If you dont want to post the depreciation in Previous years, change the Dep Key to 0000 and run AFAB for P12 of the last year. You may have to open FI period from OB52, but that wont make any postings, as Dep Key is 0000
3. Post Unplanned Dep in current year to the extent of Previous Year Depreciation. But remember that the NBV at the start of the year would be same as Original Acquisition Cost. This may impact the current year depreciation too
Incase it does impact, you may have to post another unplanned depreciation towards the year end so that the NBV at the start of next year is accurate
Ajay M
Hi Kory / Mukhtar
I dont think there is an issue with Useful Life here. So changing the useful of the asset does not arise, in my opinion
It is only an issue because of Period Control that the asset was depreciated for the full year and not from the month of purchase. Am I right?
If yes, then you have excess booked your depreciation. The only and quick solution is to do ABZU (Asset Write Up). So, here are the steps
1. Calculate outside SAP the amount excess charged per asset
2. Do ABZU in current year with value date = 01.01.2016 (Start of the Fiscal year) and Value calculated in (1)
3. After that, the depreciation should calculate as per ZINA
Regards
Ajay M
Hi,
According to me, can you try to run T-Code AFAB and in that select the radio button of Unplanned Depreciation and then select the current period and check whether the cumulative depreciation tat was required to be posted for period which are not posted can be posted or not.
Regards,
Malhar.
Hi Fernando,
If it is allowed by auditor, you can try to use the more interval function in depreciation area tab to change into 3 time interval.
One for the pending period, with posting key 0000.
2nd for the current period, with posting key which calculate the depreciation for the pending period
3rd for the future perod, with the original depreciation key.
But problem here is the 2nd depreciation key, how to make it calculate the whole pending period depreciation, you need to think more about it.
Hope it could help.
Regards,
Lisa
Hi experts, I am trying to post unplanned depreciation in certain assets in order to balance to 0 the asset unplanned depr. previous to recording a revaluation for the same asset. The thing that at the moment the unplanned depreciation is posted the NBV becomes negative and the asset recalculates depreciation in order to adjust the asset NBV not to be negative. We are entering all the postings with value and posting date 31.12.2015 period 13/2015 and the depr. is recalculated to be posted in 2015.
We've tried posting revaluation previous to the Unplanned depr. So that the asset NBV does not become negative but it seems that the system does not take into account the revaluation and continues recalculating depreciation. Do you know a way for the asset not to recalculate depreciation during current year? thanks in advance.
Victoria
Click on the links in his reply. Mark the post as helpful or answered.
Hi Victoria,
1. Check the depreciation key maintained for the asset or share screen shot of it.
2. Check the dep.area settings for ord.depreciation in OADB. Here you have selected as all values allowed. Change as negative or zero values allowed.
Regards,
Mukthar