(mailto:?subject=7%20Steps%20for%20SAP%20Fixed%20Assets%20Migration&body=%20http://www.sapexpert.co.uk/7- steps-for-sap- xed-assets-migration-in-sap/) Fixed Assets (http://www.sapexpert.co.uk/tag/asset) is an important part of the accounting. It is usually one of the areas that are implemented in SAP, and often it goes in the same phase as all other Core Finance components: General Ledger, Accounts Payable, Accounts Receivable.

You often need to transfer data from the old (legacy) system to SAP. This process is called “migration”. There are some speci cs in migration of Fixed Assets data. Let’s look into the steps that you need to make and discuss them in details.

1. Detach Fixed Assets and General Ledger

There is a special type of reconciliation accounts in SAP General Ledger: Assets. You assign this type of reconciliation account to the GL accounts speci cally created to hold Assets acquisition costs and accumulated depreciation.

The link via reconciliation account ensures that each transaction with Fixed Assets in your SAP system automatically posts in General Ledger. You don’t need to post the same amount twice in General Ledger and Fixed Assets subledger. It also ensures that you cannot post any amount directly to the GL account linked with the Fixed Assets module.

However, you need to break this link between the ledgers during the migration. Technically speaking, you migrate GL account balances and Fixed Assets values separately.

To do so, change the account type from “Assets” to empty in transaction code OAMK, which you can also nd in IMG: Financial Accounting -> Asset Accounting -> Preparing for Production Startup -> Production Startup -> Set or Reset Reconciliation Accounts.

2. Set parameters for migration

Before migrating data for Fixed Assets in SAP, you need to tell the system what you migrate and what to do with migration data. Most important parameters for the migration are migration date and last closed period in the legacy system.

Last posted period will tell SAP that it needs to calculate depreciation and post it in the Fixed Assets module for the next posting period. For example, if your go-live date is the 1st of January 2017, then last posted period is 12 / 2016.

Migration date is the date when SAP processes the migration transactions. It can either be the last day of the previous period, or the rst day of the new period. Please note that if there are differences in depreciation amount posted during the migration and calculated by SAP, they will be posted in the next period after the migration. In the example above, if your migration date is 01.01.2017, adjustment posting will be planned to P2/2017. If you migration date is 31.12.2016, then adjustment will be posted in P1/2017.

There are a number of other parameters that you can set up for asset migration. They are relevant to amounts that you migrate. For example, you can ask SAP to recalculate the depreciation amount in the past years, or recalculate the insurance value. All these parameters are listed in the Options section of IMG next to the section I mentioned just above.

There are two tools available for Fixed Assets migration in SAP: using Microsoft Excel integrated tool, and using the generic migration transaction for Fixed Assets.

Although Excel tool is available and listed in IMG node Financial Accounting -> Asset Accounting -> Asset Data Transfer, I have never seen it working. The most common case is migration of Fixed Assets using the generic “manual” tool.

There are 7 transactions in that tool:

 AS91 / AS92 / AS93 allow you to migrate individual xed assets. These 3 transactions are for Creation, Editing and Display of the migration data.

 AS81 / AS82 / AS83 / AS84 allow you to migrate group assets. These 4 transactions are for Creation, Editing and Display of the migration data, and for creation of the group asset sub- numbers.

There are two distinct ways for migration of assets capitalized in the current and in the previous scal years. Of course, this note is only relevant if you migrate mid-year. The difference is that you only migrate values for acquisition costs and accumulated depreciation for previous years’ assets. All transactions in the current year should be posted as individual transactions in the relevant section of the entry transaction.

The Current year’s Fixed Assets will only have the Transactions section lled in, and that section will include the acquisition and accumulated depreciation transactions too.

The table below summarizes the section within transaction AS91 that you need to use to enter parts of the xed assets migration data.

Data Current Year Previous year

Acquisition Cost Transactions Takeover Values

Previous Years depreciation n/a Takeover Values

Current Year depreciation Transactions Takeover Values

Current Year transactions Transactions Transactions

You should familiarise yourself with transactions AS91/AS81 before creating the migration tools for your project. When you know each part of AS91 / AS81, you can create LSMWs for transactions AS91 and AS81 (if necessary).

4. Preparing your legacy data

You import data from the legacy system into Excel or any other data management application. It is very likely that the structure of the data will not be exactly the same as you expect it to be imported into LSMWs prepared on the previous step. That is why you will need to manipulate the data, sometimes enhancing it.

You may even need to build your own applications to manipulate the source data. For example, you can use application development environment on a Cloud Virtual Desktop (https://www.clouddesktoponline.com/) like how SAP does it (https://blogs.sap.com/2015/11/25/how-sap-runs-client-virtualization-for-development/). Add O ce 365 applications with full support from O365CloudExperts (http://www.o365cloudexperts.com/).

Do not forget to document each of your manipulation for audit trail purposes.

5. Import data

Once your import tool and source data are ready, you can input data in SAP. LSMWs using transactions AS91 and AS81 (if necessary) will create asset master records with legacy values.

Of course, it is a good idea to dry run the migration in your test system to eliminate the possible hiccups and prepare the solution for known problems beforehand.

Your GL account balances should be migrated separately using any of the available tools, for example LSMW for transaction FB01.

6. Reconcile the ledgers

If you look back at the very beginning of this article, you remember that Fixed Assets and General Ledger accounts were detached during the migration. Now, when the migration is over, you reconcile the ledgers.

To check the balance of GL account, you can run the transaction FS10N or FAGLB03 depending on the version of your SAP system.

To check the balance of your Fixed Assets, you can use many reports in the Information System section of the Fixed Assets menu. For example, there is transaction S_ALR_87011964 – Asset Balances by Asset class. Each Asset Class only has one GL account for acquisition costs and depreciation, meaning that transaction will provide you with information for reconciliation.

I values do not match you can edit migrated Fixed Assets data in SAP using transactions AS92 / AS82.

7. Link Fixed Assets and General Ledger accounts

Once the balances on GL accounts and Fixed Assets ledgers are reconciled, you put the link between the ledgers back. Use transaction OAMK for that. Change reconciliation account type to “Assets” for the GL accounts you use.

Share the knowledgeI promised to share some news from SAP Expert recently. If you get this article via email or RSS, you are now on the new delivery platform. Hope you like it. Another piece of news is that SAP Expert is now not only a blog of SAP-related articles. If you look at the […]

Share the knowledgeDear readers, There are some news from SAP Expert that I would like to share. They will come in small portions. If you subscribe to this blog via email or RSS, today’s news are for you. SAP Expert migrates away from Feedburner, the platform we used for subscription delivery so far. This post […]

exist, so skip this step.

eidqhaddad on November 17, 2016

Thanks!

Dmitry Kaglik (http://sapexpert.co.uk) on November 17, 2016

My pleasure! If you have technical questions – don’t hesitate to ask!

Benjamin on February 15, 2017

Hello, Thanks a lot for you article. It is really useful. Nonetheless I got a question regarding the migration of asset under construction which are not capitalized. In transaction AS91 the capitalization date is required but I ll it I can’t do the capitalization (ABUMN) anymore. Thanks in advance for your feedback.

Dmitry Kaglik (http://sapexpert.co.uk) on February 15, 2017

Hello, Thank you for the good question. I would not migrate assets under construction as assets per se. I would rather follow the full process, i.e. via Internal Orders or WBS elements. When you do the periodic settlement of them, AUCs will be created as a part of that process. If you still have questions, please use this page (http://www.sapexpert.co.uk/you-need- our-help).

Dmitry Kaglik (http://sapexpert.co.uk) on September 14, 2017

If these 2 CoCodes are the same legal entity, then export data for the xed assets from one CoCode, upload into the 2nd, and then forget about the 1st. Otherwise, there should be a sale or a intercompany transfer.

Carolyn on September 18, 2017

mid year. we migrated assets from previous years plus the posted depreciation in current year, which appears in the P&L. However the accumulated depreciation GL balances seem not to have been updated with current year depreciation; what could have been done wrong? During upload, P&L GLs were debited with posted depreciation against the initialisation account for balances…

Dmitry Kaglik (http://sapexpert.co.uk) on October 3, 2017

Pat Carden on October 24, 2017

Hello. I have a question. I need to migrate some old assets purchased around 2009 into SAP. These assets have 2/3 years of useful life remaining. I do not have access to AS91 etc. I have created the assets in SAP in AS01. How exactly do I tell SAP the original cost and accumulated depreciation. I want to manually input this data into SAP. Thanks Pat

Svetlana on October 25, 2017

Hello, our scenario is mid year xed assets migration.Do we have to split the depreciation values and load in separate elds the one for previous closed years and for current year? Or we can load the whole accumulated depreciation in one eld ? Do I have to run ASKB and ABST2 after the Fixed asset migrated and GL balances uploaded as technical steps after all loads?

Svetlana on October 26, 2017

Thank you.Do I need to run ASKB after FAR migration/ For sure I need ABST2, but just wondering are there other technical steps after FAR migration. ABST2 and GL account balances for assets will be uploaded as well.So the sequence would be : 1. FAR migration 2.GL account balances uploads 3.ABST2 Question is do I need to run ASKB or something else as well? Thanks again!

Dmitry Kaglik (http://sapexpert.co.uk) on October 26, 2017

No additional steps should be required.

Frances Ren on November 27, 2017

Thanks so much for this post. It the most helpful! I have a couple of questions. If you could shed some light, I will really appreciate it since we are in the middle of migration.

1. You recommend “separate LSMWs for previous and current year assets, because they need to have different elds and even screens populated. Current year assets load their values through transactions”. Could you explain “load their values through transactions”? Do you mean loading the acquisition values through transactions? e.g. by invoicing creation against a vendor? But AS91 already has a eld for acquisition value for new assets.

2. Our company acquired another company on June 23, 2017. SAP went live with the new company on Nov 1. Between June 23 and Nov 1, we used Excel to keep track of the nancials. Our nance has already posted GL balances for assets from June 23 to Oct in production, e.g. acquisition value, accum depreciation, depreciation expense etc. Can we load the assets from Nov 1 and run depreciation from Nov 1? In this way, the asset subledger will be blank from June to Oct, but there are values for the GL. Will this cause any reconciliation issues?

Dmitry Kaglik (http://sapexpert.co.uk) on November 27, 2017

1. Current year acquisitions are to be migrated via Fixed Assets transactions only. No need to put vendor invoice, settlements etc. Only transaction types 100, 200 etc – whatever is appropriate for your scenarios. AS91 has values for acquisitions of assets from previous years, and there’s a separate button for “transactions” for current year. Even previous year assets may have some additional transactions (additions, impairments etc) in the current year. 2. You can migrate from the 1st of November. The assets and GL balances should reconcile at the year end. If they do, you’re sorted.

Frances Ren on November 30, 2017

Dmitry,

Thanks so much for your reply! It de nitely helps! Please bear with me as I need some clari cations. 1. On my screen for AS91, the button for transactions is greyed out, so I cannot enter anything. Do you know why?

2. If I migrate the asset sub-ledger only from Nov 1, how can the the assets and GL balances reconcile at the year end? Do I need to do something to reconcile?

Dmitry Kaglik (http://sapexpert.co.uk) on December 1, 2017

1. I have the Transactions button in my system. If you want me to look at this in your system, please use the contact form link at the top of the screen. 2. If your GL and assets’ balances reconcile at the end of the year, you don’t need to do anything else.

Leave a Reply Your email address will not be published. Required elds are marked *