Professional Documents
Culture Documents
1 Introduction
This document is intended as a user guide in how overcome the common problems in migrating fixed assets into SAP. For a one-time conversion into SAP, we favour using the LSMW tool. It allows you to leverage the full power of ABAP while using standard SAP processing functions, yet it does a lot of the file management and processing work automatically. However, even within LSMW there are a number of possible methods for migrating fixed assets. This document will discuss loading fixed assets using the standard load program RAALTD01, although two alternatives are briefly discussed below.
1.3 Assumptions
This document assumes a working knowledge of LSMW, and at least some basic understanding of the structure of fixed assets data in SAP.
2 The Basics
2.1.1 BALTD
This structure is mandatory and contains all the basic fixed asset master data.
2.1.2 BALTB
This structure is for what are known as asset transactions. The two common scenarios in which this structure needs to be populated are: a) An asset was capitalised after the start of the current financial year (the current financial year being the year in which you are going to migrate these assets into SAP), or b) An asset was disposed of in the current financial year
Ord dep posted Transactions: Number of transactions Company code Asset class Legacy asset main number Legacy asset sub number SAP transaction Transaction date Record type Transaction type Amount
3 Common Problems
The most common field for storing the legacy number is AIBN1 (Original Asset Number) but do not put your legacy number here without checking. This field was intended to be used for the original asset number in SAP after an it has been transferred to a new number. If using AIBN1 is going to be a problem, another option is ANLH-ANLHTXT. This is a text field which is often unused. One red herring in the load program is OLDN1 (Old asset number). This field exists in the load structures but not in the database tables. It is only used in the processing of the load program. See further information on this field below in Other quirks'. =
If you find that AIBN1 and ANLHTXT are not appearing in the AS91 screens, you can change the screen layouts in customising: Financial Accounting > Asset Accounting > Master Data > Screen Layout > Define Screen Layout for Asset Master Data
Gross amount of depreciable assets and the related total accumulated depreciation As a result, if you are migrating assets midway through a fiscal year you have to split the depreciation to date into two amounts: depreciation up to the end of the previous fiscal year, and depreciation during the current fiscal year. One way of doing this is in your LSMW code: in the Takeover Values screen, enter the depreciation amount up to the end of the previous year into the field Accumulated Depreciation (BALTD-KNAFAnn) and the amount of depreciation in the current year into the field Ordinary Depreciation Posted (BALTD-NAFAGnn). This is generally the most popular method. The second way is to transfer the assets as at the end of the previous fiscal year and then run depreciation in SAP for all months in the current year. This involves more work for the functional consultants.
This can be handled by modifying the standard structures BALTD and BALTB. See information on this above in the section Modifying the standard asset structure'.
3.10Other quirks
4 Footnote This guide should be viewed as a starting point for discussions and is not intended as an exhaustive examination of the various methods available. There will inevitably be circumstances specific to individual situations that cannot be covered here.