How is depreciation entered during old assets data takeover?
Depreciation values for previous fiscal years are always entered as cumulative values.
Estimated annual depreciation values for the current fiscal year with an old assets data takeover during the fiscal year cannot be entered because they are calculated automatically by the system. Differences from the estimated annual depreciations can therefore only be adjusted as manual value corrections, that is, by entering an asset transaction.
However, if you use a a depreciation key which does not automatically calculate the depreciation, for example depreciation key MANU, the manual depreciation must be entered during the transfer with a 6xx transaction type.
If depreciations have already been posted for the takeover year in the legacy system, these values must also be entered into the SAP System sothat they can be used by the posting program.
Source: OSS 50607
What are the legacy data transfer methods available in Asset Accounting and how are they different?
Answer:
The following is an overview of the legacy data transfer methods with additional information on the transferring legacy assets R/3 library.
1. Manual transfer with Transaction AS91 - This works with Transaction AS01 and is suitable for transferring smaller datasets.
2. RAALTD01 transfer via batch input - This is suitable for the mass processing of larger datasets. The batch input session fills the fields of Transaction AS91 up to and including Release 4.0B or of Transaction AT91 for subsequent R/3 releases. Therefore, only the data fields of these transactions can be filled.
3. RAALTD11 Transfer via direct input - This is suitable for transferring very large datasets. It transfers the same fields as RAALTD01 does, however it only carries out limited field checks. So that you do not receive any incorrect datasets as a result, first test at random the assets to be transferred in AS91 or as of Release 4.5B with Transaction AT91.
Furthermore, bear in mind that value fields are not converted. If, for example you specify a value field for an amount of money in euro in the BALTD-structure, you must consider the format. If, for example the value field has the format ###,## and you only enter 10 as a value, this value is interpreted as 0,10. Therefore you must specify 10,00 as value in BALTD.
To achieve the high performance of RAALTD11, the writing of change documents was also dropped. When you go into the change document display of an asset that was created with this report, the system generates the message "Asset created with Transaction AS02" or " ... AS92" by mistake.
Both RAALTD01 and RAALTD11 have not been enhanced since Release 4.5B.As of Release 4.6B, the legacy data transfer therefore is recommended via BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE since this offers all of the transfer options of the new Transaction AS91 (as of Release 4.5B).
The following methods use this BAPI.
1. Transaction AS100 data transfer with Microsoft Excel - This is suitable for the transfer of smaller datasets (limited by the line count of your Excel version). This transaction is suitable in particular if you have mapped your Asset Accounting prior to R/3 using Microsoft Excel. However, you can create only main asset numbers. More restrictions are described in Note 303710.
2. Transfers via Workbench LSMW or SXDA - BAPI_FIXEDASSET_OVRTAKE_CREATE is used by Business Object Method BUS1022->Create Incl Values, message type FIXEDASSET_CREATEINCLVALUES and IDoc type FIXEDASSET_CREATEINCLVALUES01.You can also call it for the legacy data transfer even from your own program. You can find more information in the documentation of the function module in Transaction BAPI.
No comments:
Post a Comment