Process for Automatic Asset Data
Transfer
Purpose
The following process flow can be used for transferring fixed assets from a legacy system to the SAP System.
Process Flow
To transfer legacy assets (master data and values or transactions), you convert the legacy data into a sequential transfer file, and then transfer it to the SAP System, either using report RAALTD01 (batch input) or RAALTD11 (direct data import). The transfer file contains the data in the format that is required by SAP for a successful data transfer.
Preparations
The following settings have to be made in Customizing for Asset Accounting in preparation for the legacy data transfer (choose Asset Data Transfer):
· Decide on the transfer date and the transfer options for each company code and/or depreciation area.
· Specify the sequence in which the depreciation areas are to be supplied with values. It makes sense to arrange the depreciation areas so that those areas with values that are not, or only partially, calculated by the system, appear first on the screen in dialog transactions.
· If you are using a year-dependent fiscal year version, you also have to carry out the following steps. For all historical fiscal years, from the capitalization year of your oldest asset minus 1, up to the current fiscal year, you have to
· Maintain the calendar date assignments for the fiscal year variant (in Customizing forFinancial Accounting).
· Generate the depreciation period controls for Asset Accounting (in Customizing for Asset Accounting, choose Periodic processing).
You can display the asset master record using transaction AS91 (create legacy asset). Use an asset class with a screen layout that displays all fields.
Modify the transfer structures BALTD (master data and values) and BALTB (transactions) that are supplied by SAP, if modification is necessary. You need to make modifications if you want to transfer more than eight depreciation areas, since the BALTD structure provided only allows for eight depreciation areas. The same applies to transactions and their posting amounts in the depreciation area.
3. Example- Create sample data transfer file
Analyze legacy
dataYou might want to generate a record structure from the SAP transfer structures in a particular programming language. To do so, you have to make the following entries:
· Enter the transaction.
· Enter BALTD (master data and values) or BALTB (transactions) in the Table name field.
· Enter AM_ANLA in the Identifier in TSRCG field.
· Enter the full name of the file to which the system should transfer the data structure.
Before an update run or test run of the transfer program, you mustcarry out a preliminary sort of the transfer records in the transfer file according to their keys.
After a test transfer of fixed assets, you can reset the company code (in Customizing for Asset Accounting, choose Preparing for Production Startup → Production Startup → Reset Company Code).
Postprocessing
· Complete the transfer by comparing the values of your legacy system with the values in SAP Asset Accounting (reconciliation of balances).
· Then block the legacy asset data transfer transactions. You block them at the company code level, since you might be transferring asset data for different company codes at different points in time.
The following status settings are possible in the Customizing definition of the company code:
· The company code is in test operation (transfer of legacy asset data is allowed at any time, also parallel to transactions).
· Transfer of legacy asset data is not yet finished (asset transactions are not possible).
· Transfer of legacy asset data is finished (asset transactions are possible).