Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Daryla on Mar 12 at 8:23 AM Hi
I would suggest that you do the take on for the assets that work and then ask business what you should do with the one's manually changed as in IFRS this was not supposed to be done. These assets will have to have acquisitions posted to them to have them open to depreciate which will affect their P & L account. Fully depreciated assets will not be uploaded on SAP as it is IFRS compliant and assets with a zero value must be scrapped or revalued. Hope this helps you.
| | | ---------------Original Message---------------
From: Filipe Filipe
Sent: Monday, March 05, 2012 9:16 AM
Subject: BAPI_FIXEDASSET_OVRTAKE_CREATE to Create FI-AA Legacy Data
Dear colleagues,
I'm using BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE to create FI-AA legacy data and would appreciate if someone could help me with an issue.
I'm migrating assets from one system to another, using the same asset classes, and company codes. Some assets, however, had depreciation fields, like useful life, changed manually and there are differences between ANLB and ANKB.
When i run the program, that was created using RAALTDBDBR as a reference, ANKB data overwrites ANLB and the assets created do not bring the information i need.
Even considering what is being done correct, i'd like to know if its possible to disregard ANKB and use ANLB data instead. If there is any customing step or parameter in the BAPI that can be set to meet what i'm expecting.
Find bellow and example:
ANLB:
Asset: 223457
Asset class: 2004
Depreciation area: 01
Useful life: 9 years.
ANKB:
Asset Class: 2004
Depreciation area: 01
Useful life: 10 years.
When i run the program, useful life of 10 years is being derived. 9 years is what in need in order to have identical figures.
Thanks in advance and regards,
Filipe Stancioli. |
| Reply to this email to post your response. __.____._ |  _.____.__ |
