on 10-31-2011 5:34 PM
Hi Experts,
We are working in a one-year old implementation and a requirement has raised. For almost all of our assets we are required for the fiscal Depreciation Areas to keep the original information on the asset so that the depreciation that is calculated does not change but conversely for the other areas we desire to change the depreciation that is calculated and posted (for example, some assets will suffer a change in the useful life while others might merge into one big asset, etc.) but what we definitely need is to keep the original information in the fiscal areas so we can keep reporting that and therefore can keep paying the correct amount to our local tax authorities.
To solve this what we thought was duplicating the assets (through a mass charge of all our assets with the current values), then transferring the 'clones' to assets with fewer Depreciation Areas in a new Asset Class of course (in the new Asset Class we will eliminate the Fiscal Areas since this new assets will be only useful for the non-fiscal depreciation calculation which is the one that will change).
To sum up: the clones will not generate depreciation because when transferred they will be worthless. The assets they were transferred to will generate the non fiscal depreciation.
And finally on the original assets we will deactivate the non-fiscal Depreciation Areas so that these assets continue to calculate the fiscal depreciation.
We would really appreciate your opinion on this strategy or if you think it is a bad or incorrect strategy we would appreciate even more an advise on this matter.
We are definitely aware that the duplication of all the assets is not something that you do everyday and that we will have a lot of explaining to do to the auditors but we can't seem to get hold of a better alternative. So we are kindly recurring to your expertise on the matter.
Hi,
1) you create a new transfer variant based on the information you find in SAP note 327088 but assign your newly created transaction types to this transfer variant. Then you enter your new transfer variant in ABUMN in tab 'Additional Details1.
2) As long as the asset has still values in any of the depreciation areas, it will not be deactivated. Also, if you want to keep the same values in the original asset as per I understand, maybe you could create a second depreciation area in the sending asset via RAFABNEW before transferring and which takes over the values form the area that you are about to transfer to the new asset. With the limited transaction type you could then transfer the values out of the depreciation areas only that you want and the others remain active on the sending asset.
Or, you post the same value again to the sending asset to the depreciation area that you just transferred the values out and into the new asset...Again, this you can do with a limited transaction type.
However, from what I understand, you cannot transfer all your values onto another asset and expect the same values also
to remain on your original asset (in a way that you might think you could 'copy' the asset).
Have you thought of the option of assigning subassets? I am not sure of course if that would meet your requirements, but this way you can create an asset and have several other assets linked to it via subasset. Or what about creating group assets?
Look up the different options and what they are good for in the R/3 Library.
At this point I am not sure how much I am of help anymore, but these are just points for you to consider - unless someone else has more ideas or inputs of course....
I hope so far I could help to answer some of your questions at least.
Best regards,
Brigitte
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Reading your last reply, another thought that might be an option: you could transfer with a limited transaction type. You can create your own transaction type and limit your transactin type to the depreciation areas that you want to transfer (in IMG). You then create a new asset with exactly the depreciation areas you want to have on the new asset. You do not have to have the same amount or the same depreciation areas in the receiving asset, but you need to be mindful of the following when creating or defining your transfer variant:
In asset accounting we always have the two options when transferring values:
1. Sending company with fewer depreciation areas than receiving company.
2. Sending company with more depreciation areas than receiving company.
In the first case, the transfer variant used must use as "transfer method" 4. So the new areas will be automatically calculated in the receiving company based on the settings of OABC and OABD.
In the second case a transfer variant must be defined, as transfer variant 2 ("net posting").
Also have a look at SAP note 327088 for further information on transfer variant customizing.
I hope this information will help you further.
Best regards,
Brigitte
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Brigitte!
Once again thanks so much for your reply. We have mainly two doubts regarding your last suggestion:
1.- How can we configure the system to instruct transaction ABUMN to use our newly created Transaction types because we haven't been able to do so. The only transaction in which we were able to use our newly created Transaction types was in transaction ABSO - Miscellaneous and we didn't know how to use ABSO to merge two or more assets into a bigger asset.
2.- How can we configure the Transaction types (well actually we think we only need to do this for the Transaction Type for Retirement Transfers) so that our newly created Transaction types DO NOT deactivate our original assets. As I already stated we did try doing this configuration by deselecting the Deactivate Fixed asset checkbox but we think it didn't work because our original assets stop calculating any depreciation for subsequent periods (we expected these assets would continue depreciating the Fiscal Depreciation Areas but they didn't and we think they didn't because the Transaction types deactivated the assets).
Thank you so much for the guidance as usual!
Hi,
I am not sure if I fully understand your requirement. However, to fulfill your requirements from business, could you not simply
create new areas in the asset that do not post to FI and are taking over the values/depr.terms for example from the book area (OABC and OABD). You could then run the report for this area only and use the information for reporting purposes only.
You can assign a different useful life for this area than what you maybe have in area 01 (book area), too.
This are just my initial thoughts and if I understand your enquiry correctly.
Regards,
Brigitte
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Brigitte,
We have read your answer and we have pondered it over the weekend. Unfortunately, we think our previous post was not clear enough.
We absolutely need to make a transfer (or a similar operation that I am not aware of). We are forced to make this operation because as we stated in the previous post we need to merge two or more assets into one. We were planning to achieve this merging of assets with transaction ABUMN. And actually this transaction is working as we need except for one detail: after making the transfer the original assets are deactivated and therefore we loose the original values which are really important for us because we need them to continue having the fiscal information needed to calculate the fiscal depreciation.
I hope it is clearer now that we definitely need to make a transfer (because of our need to merge two or more assets into a new asset).
It is also worth clarifying that some of these new assets (created from the merging of two or more original assets) are the ones which will probably have new different useful lives.
Thank again for you interest in helping it is much appreciated!
Hi,
I do not think you can do a transfer of select depreciation areas while transferring an asset. All depreciation areas are transferred to the new asset on transfer.
I have a suggestion.
You deactivate all non-fiscal depn. areas on the original assets. This will retain on the original asset all other pertinent information that you want.
Then, create new assets with the new information that you want for non-fiscal areas and post values to it using special transaction keys designed only for those areas.
Hope this fits your requirements.
Thanks,
Jagdish
Hi Jagdish,
Thanks for your reply! We have the following comments:
We think we don't fully understand your suggestion because we are not sure how we could integrate two or more assets into one and this is actually one of the two most important parts of our requirement.
(The two most important parts of the requirement are:
1) Merge two or more assets into one bigger asset
2) When executing this integration of two or more asset into one bigger asset DO NOT loose the information of the Fiscal Depreciation Areas of the original assets)
Therefore, we need a way to merge two or more assets and although we already have acomplished that merging (we did it by transferring our two original assets to a new asset) what we haven't accomplished yet is a way to conserve the information of the Fiscal Depreciation Areas because after the merger, transaction ABUMN deactivates the original assets and therefore they do not generate the fiscal depreciation information that we need.
(As another test we tried editing the transaction types that we assume ABUMN was using so that the checkbox Deactivate Fixed asset wasn't selected but ABUMN anyway deactivated our original assets...)
(PS. we are only familiar with Special Ttransaction Keys in MM such as in MIGO but don't really know how to relate them to FI-AA could you please point us to a source where we could read them more about them. We have never posted values to assets using Special Transaction Keys designed only for specific areas and we have doubts of how to make that posting with the exact aggregated sum of our two original assets. Also would this have to be done manually? That might be an issue since we have a really big number of assets in some of the company codes involved.)
Thanks so much in advance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.