1 Review
1.1 Introduction
This document is intended as a user guide for solving common problems when transferring fixed assets to SAP.
For a one-time conversion to SAP, we prefer to use the LSMW tool. It allows you to use the full power of ABAP using standard SAP processing functions, but it also processes and processes files a lot. However, even within the LSMW, there are a number of possible ways to migrate fixed assets.
This document will discuss the loading of fixed assets using the standard download program RAALTD01, although in two versions are briefly discussed below.
1.2 Loading methods
1.2.1 BDC AS91 transaction record
This is the simplest solution, so it can be very convenient to download. If, for example, you do not create fixed assets in SAP, but rather update one field in fixed assets that already exists in the system, then this may be the right approach. But it is not flexible enough to be used to create these fixed assets.
1.2.2 Business Object BUS1022
This will create an IDoc of type FIXEDASSET_CREATEINCLVALUES01 and process them through the SAP BAPI function BAPI_FIXEDASSET_OVRTAKE_CREATE.
This solution is probably recommended by SAP. SAP is keen on BAPIs because they are powerful, flexible and can be easily called from an external system through RFC. But this does not necessarily make them the right choice for data transfer. The structure of BAPI is not always particularly intuitive, and preliminary development work can be complex.
This method also includes IDoc processing. Although the standard error handling and processing function for IDocs in SAP is impressive, it is not always transparent. Migration of fixed assets using this method would be suitable for those who are particularly strong in the field of BAPI and IDOC.
1.2.3 Standard download program RAALTD01
This is usually the approach I would prefer for transferring fixed assets to SAP.
The standard loading program is not perfect. As discussed below, there are one or two areas that it does not cover and, like many standard SAP standard, has its own characteristics: for example, when you come to load assets, you do not have the opportunity to create a BDC session even if any of the calls transaction will fail, then the program will create a BDC session for these records.
However, it is a powerful and flexible program, and it is relatively easy to use. The fact that you can start loading assets in test mode before creating any data is also a major advantage, even though the test run does not always achieve 100% errors.
1.3 Assumptions
This document confirms the working knowledge of LSMW and at least some basic understanding of the data structure of fixed assets in SAP.
2 Basics
2.1 Data Structures
The RAALTD01 resource loading program, BALTD and BALTB, has two data structures.
2.1.1 BALT D
This structure is mandatory and contains all the basic basic master data of fixed assets.
2.1.2 BALT B
This structure is intended for so-called asset transactions. Two common scenarios in which this structure should be filled:
a) The assets were capitalized after the start of the current fiscal year (the current fiscal year is the year in which you intend to transfer these assets to SAP), or
b) The asset has been liquidated in the current financial year.
2.2 Important fields
Key fields
BALTD-ANLN1 Asset number (usually not used - internal numbering)
BALTD-ANLN2 Asset range (usually not used - internal numbering)
BALTD-BUKRS Company Code
BALTD-ANLKL Asset Class
BALTD-OLDN1 Main asset number
BALTD-OLDN2 Legacy Resource Extension
SAP BALTD-TCODE transaction
BALTD-RCTYP Record Type
Basic data
BALTD-AKTIV Capitalization Date
BALTD-TXT50 Description
BALTD-TXA50 Additional Information
Location BALTD-STORT
Factory BALTD-WERKS
BALTD-KOSTL Cost Center
Supplier BALTD-LIFNR
BALTD-INVNR Inventory number
BALTD-LIEFE Supplier Name
BALTD-AIBN1 Original Supplier Number
Depreciation data (multiple records per asset)
BALTD-AFABEnn Amortization
BALTD-NDJARnn Estimated useful life (years)
BALTD-NDPERnn Planned life (months)
BALTD-AFASLnn Amortization Key
BALTD-AFABGnn Start Date Depreciation
BALTD-KANSWnn Gross book value
BALTD-KNAFAnn Accumulated depreciation
BALTD- NAFAGnn Ord dep posted
operations
BALTD-BWCNT Number of transactions
BALTB-BUKRS Company Code
BALTB-ANLKL Asset Class
BALTB-OLDN1 Main asset number
BALTB-OLDN2 Legacy Resource Extension
SAP BALTB-TCODE transaction
BALTB-BZDAT Date of operation
BALTB-RCTYP Record Type
BALTB-BWASL Transaction Type
BALTB-ANBTRnn Amount
2.3 Changing the standard structure of assets
It is possible (and authorized by SAP) to change the structures of SAP BALTD and BALTB. You only need to change BALTB if you have added additional areas of assessment to BALTD.
Of course, for this you will need an object key, but for now the fields you add are active in AS91, AS92, etc. transactions, Then this is the only change you need to make. RAALTD01 does the rest.
Common reasons for changing BALTD can be deletion in order to increase the number of investment keys (the default value is 2) or the number of depreciation areas (the default is 8). For details, see Below is a depreciation section.
For more information, see SAP OSS note 23716.
3 Common problems
3.1 Alpha Conversion
Since RAALTD01 is very closely related to the direct download program RAALTD11, it retains some of the features of the direct download program. One of them is the checks at load time, while the key data specified in the asset exists in SAP. It does this without alpha conversion.
So, if you create an asset with an asset class (ANLKL field) & # 39;, you must indicate this in the LSMW mapping in the internal SAP format, i.e. & # 39; 00000100 & # 39; The same applies to cost centers, suppliers, etc.
3.2. Obsolete asset number
This is important when transferring data to SAP to store a reference to the old data key.
This is important for business reasons - so that the user can easily see the connection between their old data and the new one - but this is also important for technical reasons. This is evident for certain objects, such as suppliers and customers, where you need to save the link in order to be able to transfer subsequent transactional data, such as AR and AP. But it is also useful for assets.
During the data migration test phases, it is very useful to be able to start and re-launch your boot program without fear of downloading duplicate information. By keeping the previous resource number somewhere in the main object, you can easily check with some ABAP code in LSMW whether this obsolete asset has already been created in the ANLA table.
The most common field for storing an obsolete number is AIBN1 (the original asset number), but do not put the previous number here without checking. This field was intended to be used for the original asset number in SAP after it was transferred to the new number.
If using AIBN1 is a problem, another option is ANLH-ANLHTXT. This is a text field that is often not used.
One red herring in the download program is OLDN1 (old asset number). This field exists in load structures, but not in database tables. It is used only when processing a boot program. See Additional Information in this field below in the “Other Fads” section.
If you find that AIBN1 and ANLHTXT are not displayed on AS91 screens, you can change screen layouts when customizing.
Financial Accounting> Asset Accounting> Master Data> Screen Layout> Determining the Screen Layout for the Capital Data on Core Assets
3.3 Lack of customization
Before you start migrating test and live assets, check to see if the following custom is observed. For some reason, these actions are often overlooked by functional FI-CO consultants:
Date of transfer - it should be set close to the date when you transfer assets. Since AS91 is specifically designed to transfer data, he expects the capitalization date for all assets you have transferred to be prior to the transfer date. Check it out in table T093C.
Current fiscal year - also in T093C, make sure it is installed correctly.
Number ranges - transaction SNUM.
3.4 NBV - book value
It is not possible to directly transfer the book value of an asset. You must transfer the gross book value (acquisition cost) and accumulated depreciation. SAP then calculates the NBV.
3.5 Temporary data
Some data on resources depends on time, i.e. You can see the history of these fields. Examples of fields are cost center, plant, internal order, location, and business zone. All of them are stored in the ANLZ table. SAP standard load programs can only process current values of these fields. You cannot transfer multiple ANLZ records for each asset.
If you need to do this, first create your resources with RAALTD01 and load the initial values of these fields. Then create another LSMW program using the AS92 entry to load any changes.
3.6 Intermediate Asset Migration
Because of the depreciation of fixed assets associated with the general ledger, if you transfer assets in the middle of a fiscal year, you must divide the depreciation by the date into two depths: depreciation until the end of the previous fiscal year and depreciation during the current fiscal year.
One way to do this is in your LSMW code: on the “Valid Values” screen, enter the depreciation amount before the end of the previous year in the “Accumulated depreciation” field (BALTD-KNAFAnn) and the depreciation amount in the current year in the Normal depreciation field Added (BALTD-NAFAGnn ). This is usually the most popular method.
The second way is to transfer assets at the end of the previous fiscal year, and then run depreciation to SAP for all months of the current year. This involves a lot of work for functional consultants.
3.7. Assets created this year
For the same reasons as described in “Migrating Assets for the Year” above, you must distinguish in SAP between assets created in previous years and assets created in current years. Your capitalization in the current year should be identified as a transaction.
In this situation, you will need to place both the BALTD record and the BALTB record.
Your publication will differ from standard asset creation in the following ways:
· BALTD-BWCNT is required to populate & # 39; 0001 & # 39; (assuming you only post one transaction)
· You need to compare the received value with BALTB-ANBTRnn with the transaction type & # 39; instead of displaying it as normal for BALTD-KANSWnn
· BALTD-KNAFAnn does not need to be filled
· BALTD-NAFAGnn must be filled with depreciation amount.
· BALTB-BZDAT must be filled with a capitalization date.
3.8 Disposal of assets
Disposals in the current fiscal year should also be identified as transactions.
In this situation, you will need to place both the BALTD record and the BALTB record.
Your publication will differ from standard asset creation in the following ways:
· BALTD-BWCNT is required to populate & # 39; 0001 & # 39; (assuming you only post one transaction)
· You need to compare the value of disposal in BALTB-ANBTRnn with the transaction type & # 200;
· BALTB-BZDAT must be filled in with the date of removal.
3.9 Depreciation Zones
When creating fixed assets in SAP, you often fill in several depreciation areas. Common depreciation areas established in SAP can be local depreciation, group depreciation (if your company is international) and tax. The depreciation rules for each of them may be slightly different, so you will create one depreciation area for each of them.
You may rarely need more than 8 depreciation areas provided by SAP in the BALTD and BALTB structure. I only ever experienced it once when loading fixed assets in Italy. This was necessary because of the many currency devaluations that the Italian lira has undergone over the past thirty years or so.
This can be accomplished by modifying the standard BALTD and BALTB structures. See this information above in the “Changing the Standard Asset Structure” section.
3.10 Other Fads
3.10.1 Invalid characters
You cannot place the hash character in any of the BALTB or BALTD fields.
3.10.2. Long texts
The standard load program does not handle long texts. They must be loaded into a separate program. But this situation is rare.
3.10.3. Unexpected record type found.
This error occurs if you enter the wrong record type in the two RCTYP fields. This should be “A & BALTD and B & BALTB.
However, you are sure that you do not have this problem, and you still get an error, check when there is any of the basic data you specified. For example, all your cost center numbers are valid. I had this error in the past when transferring assets with transactions. A real & invalid data error in your BALTD record is not provided by SAP. He gives this error.
The moral of this story: always check your master data fields in LSMW when loading fixed assets. A set of user procedures, such as CHECK_KOSTL, CHECK_WERKS, CHECK_LIFNR, etc., can save you a lot of time.
Report 3.10.4Audit and Error
Error reporting is terrible in RAALTD01 if you do not fill in the BALTD-OLDN1 field. If you do not fill this field, the program will list all the errors that you have, only with a description of the asset, which is not particularly useful. Thus, always complete OLDN1, even if you are not transferring transactions.
4 Footnote
This guide should be considered as a starting point for discussion and is not intended to thoroughly examine the various methods available. Inevitably there will be circumstances characteristic of individual situations that cannot be considered here.
You can find more Harlex SAP data migration guides here: http://www.harlex-ltd.com/downloads.html
For more information on transferring fixed assets to SAP or even in any data conversion topic, please contact Harlex at info@harlex-ltd.com
