• Personal
  • Corporate


02 Oct 2016

Migrating Secured Assets Into SAP – A Harlex Guide


1      Overview

1.1    Introduction

This document is supposed as a person guide in exactly how overcome the normal dilemmas in moving fixed assets into SAP.

For a one-time conversion into SAP, we favour making use of the LSMW device. It permits that leverage the total energy of ABAP when using standard SAP processing functions, yet it can a lot of the file management and processing work immediately. But also within LSMW there are a number of feasible options for moving fixed assets. 

This document will discuss loading fixed assets making use of the standard load program RAALTD01, although two choices are fleetingly discussed below. 

1.2    Load techniques

1.2.1    BDC recording of transaction AS91

This is basically the simplest solution and thus it might be suitable for a really fundamental upload. If including you are not generating fixed assets in SAP, but alternatively upgrading one industry in fixed assets which already occur within the system, after that this could be the best method. However it is perhaps not flexible adequate to be utilized for the creation of fixed asset information.

1.2.2    Company item BUS1022

This will produce IDOCs of kind FIXEDASSET_CREATEINCLVALUES01 and process all of them through the SAP BAPI purpose BAPI_FIXEDASSET_OVRTAKE_CREATE.

This is possibly the solution that SAP would suggest. SAP is thinking about BAPIs since they are effective, flexible and certainly will easily be known as from an external system via an RFC. But that will not necessarily cause them to become the best choice for information migration. The dwelling of BAPIs is not always specifically intuitive and upfront development work can be complicated.

Also this technique requires the processing of IDOCs. While the standard mistake handling and reprocessing functionality for IDOCs in SAP is impressive, it is really not always transparent. Migrating fixed assets that way would be suitable for someone who is particularly powerful in your community of BAPIs and IDOCs..

1.2.3    Standard load program RAALTD01

This is generally the method I would prefer for the migration of fixed assets into SAP.

The standard load program is not perfect. As discussed later, you can find a couple of areas which it will not cover and like numerous SAP standard programs, it offers its quirks: including, whenever you started to load the assets, there is no need the option to create a BDC program yet if any of the transaction calls fail, then program can establish a BDC program for all those files.

Nevertheless, it’s a strong and versatile program, and it’s also not at all hard to utilize. That you are able to run the asset load in test mode before generating any information is also a major benefit, even though the test run will not always collect 100percent regarding the errors.

1.3    Assumptions

This document assumes a functional familiarity with LSMW, at the very least some fundamental knowledge of the dwelling of fixed assets information in SAP.

2      The Basics

2.1    Data frameworks

There are two information frameworks within the asset load program RAALTD01 – BALTD and BALTB.

2.1.1    BALT D

This construction is necessary and contains most of the fundamental fixed asset master information.

2.1.2    BALT B

This construction is for what exactly are known as asset transactions. The 2 common situations where this construction needs to be populated are:

a) a secured asset had been capitalised following the beginning of the current economic year (the present economic year being the season in which you are going to migrate these assets into SAP), or

b) a secured asset had been discarded in the present economic year

2.2    essential areas

Secret Areas

BALTD- ANLN1             resource number (typically perhaps not made use of – internal numbering)

BALTD- ANLN2             resource subnumber (typically perhaps not made use of – internal numbering)

BALTD- BUKRS             Company rule

BALTD- ANLKL             Resource class      

BALTD- OLDN1              Legacy asset primary number

BALTD- OLDN2              Legacy asset sub number

BALTD- TCODE             SAP transaction           

BALTD- RCTYP             Record kind

Master Information

BALTD- AKTIV               Capitalisation date        

BALTD- TXT50               Description      

BALTD- TXA50              New description   

BALTD- STORT              Location          

BALTD- WERKS            Plant    

BALTD- KOSTL              Price centre      

BALTD- LIFNR               Vendor

BALTD- INVNR             Stock number          

BALTD- LIEFE               Vendor name   

BALTD- AIBN1               First Vendor Number

Depreciation Data (numerous files per asset)

BALTD- AFABEnn          Depreciation area         

BALTD- NDJARnn          organized of use life (years)         

BALTD- NDPERnn         organized of use life (months)      

BALTD- AFASLnn          Depreciation key          

BALTD- AFABGnn         Depreciation begin date 

BALTD- KANSWnn         Gross book value         

BALTD- KNAFAnn          Accumulated decline

BALTD- NAFAGnn         Ord dep posted


BALTD- BWCNT Amount Of transactions

BALTB- BUKRS             Company rule

BALTB- ANLKL             Resource class      

BALTB- OLDN1             Legacy asset primary number

BALTB- OLDN2             Legacy asset sub number

BALTB- TCODE             SAP transaction

BALTB- BZDAT             Transaction date           

BALTB- RCTYP             Record kind

BALTB- BWASL             Transaction kind

BALTB- ANBTRnn          Amount

2.3    Modifying the conventional asset construction

You are able (and sanctioned by SAP) to change SAP frameworks BALTD and BALTB. You only need certainly to alter BALTB if you have added additional decline areas to BALTD.

You will definitely definitely require an item crucial to do this, but so long as the areas you’re including are active in transactions AS91, AS92, an such like, after that here is the only modification it is important to make. RAALTD01 can do the remainder.

Common cause of altering BALTD might-be to remove to boost the number of financial investment secrets (standard environment is 2) or even the amount of decline areas (standard environment is 8). See more about the decline areas below.

There is certainly more details in SAP OSS note 23716.

3      Common Problems

3.1    Alpha conversion

As RAALTD01 is very closely related to the direct upload program RAALTD11, it keeps a number of the popular features of a primary upload program. These is the fact that it checks during upload whether crucial information referenced within the asset exists in SAP. It will this without making any alpha conversion.

Therefore, if you’re generating a secured item with asset course (industry ANLKL) ‘100’, you must specify this within the LSMW mapping in its internal SAP structure, ie. ‘00000100’. Exactly the same is true of cost centers, suppliers, etc.

3.2    Legacy asset number

It is crucial when migrating information into SAP to keep a reference to the history information key.

It’s important for business reasons – making sure that a person can easily see the hyperlink between their old information and brand-new – but it is also essential for technical reasons. This is obvious for many things like suppliers and clients in which you need certainly to shop the hyperlink to become able to migrate follow-on transactional information like AR and AP. However it is also ideal for assets.

It is very useful in the test stages of a data migration to run and rerun your load program without fear of running duplicate information. By storing the legacy asset number somewhere in the asset master, it is possible to seek the advice of some ABAP rule inside LSMW whether this legacy asset was already produced in table ANLA.

The most common industry for storing the history number is AIBN1 (Original resource Number) but do not place your history number here without examining. This industry had been designed to be utilized for the original asset number in SAP after an it has-been used in a new number.

If utilizing AIBN1 will probably be an issue, another option is ANLH-ANLHTXT. This is a text industry which is frequently unused.

One red-herring within the load program is OLDN1 (Old asset number). This industry exists within the load frameworks yet not within the database tables. Its only found in the processing regarding the load program. See more info on this industry below in ‘Other quirks’.

If you learn that AIBN1 and ANLHTXT aren’t showing up within the AS91 screens, you are able to replace the screen layouts in customising.

Financial Accounting > Asset Accounting > Master Data > Screen Layout > Define Screen Layout for Asset Master Data

3.3    Missing customising

Before running your ensure that you live asset migrations, kindly check that here customising is within place. For reasons uknown, these actions tend to be over looked because of the FI-CO practical specialists:

Transfer date – this would be set to near the date you migrate the assets. As AS91 is specifically for information migration, it wants that the capitalisation date for all your assets you migrate are ahead of the transfer date. Check this in table T093C.

Existing fiscal year – also in T093C, check that it has already been correctly set.

Number ranges – transaction SNUM.

3.4    NBV – Net book value

It isn’t feasible to straight migrate the net book value of a secured item. You must migrate the gross book value (purchase cost) and built up decline. SAP will likely then calculate the NBV.

3.5    Time-dependent information

Some of the asset information is time-dependend, ie. you can observe the annals of these areas. Example areas are cost centre, plant, internal order, place and business area. They all are stored in table ANLZ. The standard SAP load programs can only manage the present values of these areas. You can’t migrate numerous ANLZ files per asset.

If you need to repeat this, you should first create your assets utilizing RAALTD01 and load the first values of these areas. After that produce another LSMW program utilizing an AS92 recording to upload any modifications.

3.6    Mid-year asset migration

Due to the way the fixed asset decline backlinks in aided by the General Ledger, if you’re moving assets midway through a fiscal year you have to divide the decline up to now into two quantities: decline as much as the termination of the last fiscal year, and decline during the current fiscal year.

One-way of doing this will be inside LSMW rule: within the Takeover Values screen, go into the decline amount as much as the termination of the last year in to the industry Accumulated Depreciation (BALTD-KNAFAnn) and amount of decline in the present year in to the industry Ordinary Depreciation published (BALTD-NAFAGnn). This is generally the hottest technique.

The next method will be move the assets as at the end of the last fiscal year and then run decline in SAP for all months in the present year. This involves even more work with the practical specialists.

3.7    Assets produced in this year

For similar reasons as described in ‘Mid-year asset migration’ above, you have to distinguish in SAP between assets produced in earlier years and assets produced in current years. Your capitalisation in the present year needs to be defined as a transaction.

Within circumstance it is important to post both a BALTD record and a BALTB record.

Your publishing will differ from the conventional asset creation within the following techniques:

·         BALTD-BWCNT needs to be populated with ‘0001’ (assuming you’re only publishing single transaction)

·         You’ll want to map the purchase value into BALTB-ANBTRnn with transaction kind ‘100’ rather than mapping it as normal to BALTD-KANSWnn

·         BALTD-KNAFAnn doesn’t have is populated

·         BALTD-NAFAGnn should be populated aided by the decline amount

·         BALTB-BZDAT should be populated aided by the capitalisation date

3.8    resource disposals

Disposals in the present fiscal year must be defined as transactions.

Within circumstance it is important to post both a BALTD record and a BALTB record.

Your publishing will differ from the conventional asset creation within the following techniques:

·         BALTD-BWCNT needs to be populated with ‘0001’ (assuming you’re only publishing single transaction)

·         You’ll want to map the disposal value into BALTB-ANBTRnn with transaction kind ‘200’

·         BALTB-BZDAT should be populated aided by the date of disposal

3.9    Depreciation areas

When creating fixed assets in SAP you are going to frequently populate numerous decline areas. Common decline areas create in SAP might-be neighborhood Depreciation, Group Depreciation (in case the company is worldwide) and Tax. The decline guidelines for every of these might-be slightly different, therefore you are going to produce one decline area for every.

Hardly ever, you may want above the 8 decline areas supplied as a default by SAP in construction BALTD and BALTB. We have only previously experienced this once while loading fixed assets in Italy. It was required as a result of the numerous money devaluations that the Italian lira had encountered over the past thirty years or more.

This is often managed by altering the conventional frameworks BALTD and BALTB. See all about this above within the part ‘Modifying the conventional asset construction’.

3.10Other quirks

3.10.1Invalid characters

You might not place the hash character # in any regarding the BALTB or BALTD areas.

3.10.2Long texts

The standard upload program will not manage lengthy texts. These would need to be filled in an independent program. But this situation happens seldom.

3.10.3’Unexpected record kind found’

This mistake happens in the event that you go into the wrong record enter the two RCTYP areas. It must be ‘A’ in BALTD and ‘B’ in BALTB.

However, it you’re sure that you don’t have this issue and you are clearly nonetheless obtaining mistake, check whether any of the master information you have referenced exists. Like, are your cost centre figures valid. We have had this mistake before when moving assets with transactions. The ‘real’ mistake of invalid information inside BALTD record is not given by SAP. It offers this mistake instead.

The ethical for this tale: always validate your master information areas in LSMW when loading fixed assets. Some individual routines including CHECK_KOSTL, CHECK_WERKS, CHECK_LIFNR, an such like, will save you a lot of time.

3.10.4Audit and Error report

The mistake reporting is dreadful in RAALTD01 unless you populate the industry BALTD-OLDN1. If you don’t populate this industry, the program will list any errors you have aided by the asset information only, which is perhaps not specifically helpful. Therefore, always populate OLDN1 even if you aren’t migrating transactions.

4      Footnote

This guide should be seen as a starting point for talks and is perhaps not meant as an exhaustive examination of the many techniques available. There will undoubtedly be conditions specific to individual circumstances that can’t be covered here.

You can find much more Harlex Guides to SAP information migration here: http://www.harlex-ltd.com/downloads.html

For more info regarding migration of fixed assets into SAP or without a doubt on any information conversion topic, be sure to contact Harlex at: info@harlex-ltd.com