7 Steps for SAP Fixed Assets Migration

Dmitry Kaglik

September 5, 2016



Share the knowledge
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInDigg thisEmail this to someone

Fixed Assets 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 specifics 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 specifically 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 find in IMG: Financial Accounting -> Asset Accounting -> Preparing for Production Startup -> Production Startup -> Set or Reset Reconciliation Accounts.

  1. 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 first 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.

You can find both of the transactions for date-related migration parameters in IMG: Asset Accounting -> Asset Data Transfer -> Parameters for Data Transfer -> Date Specifications.

Asset transfer date
Asset transfer date

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.

Asset transfer options
Asset transfer options
  1. Prepare the migration tool

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 fixed 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 fiscal 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 filled 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 fixed 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).

  1. 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 like how SAP does it. Add Office 365 applications with full support from O365CloudExperts .

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

  1. 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.

  1. 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.

  1. 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.

These seven steps will complete your migration cycle for Fixed Assets.

If there are any questions you have about the Fixed Assets or any other SAP module, why not ask them to SAP Expert?

Share the knowledge
Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInDigg thisEmail this to someone

Related Posts

SAP Expert news, part 1

Dmitry Kaglik

November 13, 2017


No Comment

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 […]

Read More

Quick introduction to SAP Bank Communication Manager

Dmitry Kaglik

November 6, 2017


No Comment

Share the knowledgeSAP Bank Communication Manager (BCM) is one of the components of SAP Financial Supply Chain Management (FSCM) module. The responsibility of BCM, as it follows from its name, is in the management of relationships with the bank. Let’s have a look at the processes that BCM supports. We will not look into details […]

Read More


  • SAP Simple Finance online training on October 25, 2016

    Best information.Thanks for sharing helpful information

  • eidqhaddad on November 17, 2016

    Hello, Very good post, but I have two question for you. How I transfer after Asset Accounting Is Already Productive ? and my challenge is, I need to do this in middle of fiscal year.

    • Dmitry Kaglik on November 17, 2016

      You can migrate assets any time you want, even mid-year and when other Finance functionality is already live. I presume the balances on your Assets accounts already exist, so skip this step.
      Best regards,
      SAP Expert

      • eidqhaddad on November 17, 2016


      • Dmitry Kaglik on November 17, 2016

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

  • Benjamin on February 15, 2017

    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 fill it I can’t do the capitalization (ABUMN) anymore.
    Thanks in advance for your feedback.

    Kind regard!

    • Dmitry Kaglik on February 15, 2017

      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.

  • Lorena on May 31, 2017

    Hi, thanks for this article, really useful!

    My question is, how I can open capitalization values fild? I only can fill the depreciation acumulated values.

    Thanks a lot!

    • SAP Expert on May 31, 2017

      Is it for migration of the current or previous year assets?

  • Raj on August 9, 2017

    Thanks for the article.
    I need to do migration of AUC balance using internal orders. Do you have more details/steps or any quick points I should be aware of?

    • Dmitry Kaglik on August 9, 2017

      I don’t have any specific guides for that. From my point of view, there are 2 steps: migration of values to the internal order like normal GL, and then mass8-settlement of IOs to AUCs (KO8G).

  • Greethal on September 14, 2017

    Thanks for the article. Its very helpful.
    I have a requirement to merge two company codes and both are productive in SAP system. Can you please tell me the steps to follow in assets take over.

    • Dmitry Kaglik on September 14, 2017

      If these 2 CoCodes are the same legal entity, then export data for the fixed 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 on September 18, 2017

      Accumulated depreciation of previous years should be migrated to corresponding Balance Sheet GLs during the migration. This goes as a separate task to the Fixed Assets data migration.

  • DErek on October 2, 2017

    These transactions are for old ECC migration. In S4HANA, transactions have changed:
    AS91 Create legacy asset
    AS94 Create legacy asset for subnumbers
    ABLDT Post all transfer values to assets (item acquired in previous FY)
    AB01L Data transfer during the fiscal year: Transfer line items (item acquired in current FY)
    ABLDT_OI Transfer AUC with line item management: transfer line items

  • 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

    • Dmitry Kaglik on October 24, 2017

      AS91 is specifically made for asset migration. You cannot achieve this in AS01. Please request necessary access.

  • Svetlana on October 25, 2017

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


    • Dmitry Kaglik on October 25, 2017

      Hello, I recommend separate LSMWs for previous and current year assets, because they need to have different fields and even screens populated. Current year assets load their values through transactions…

      • 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
        Question is do I need to run ASKB or something else as well?
        Thanks again!

      • Dmitry Kaglik on October 26, 2017

        No additional steps should be required.

Leave a Reply

Your email address will not be published. Required fields are marked *

Search this site



Will you be happy to pay for the 3rd edition of the book FREQUENTLY ASKED QUESTIONS ON SAP FINANCE?

View Results

Loading ... Loading ...
Disclaimer and privacy policy