SP051 template

How to reconcile FI-AA & FI-GL after Fixed Asset data Takeover in SAP

Subhasish Ghosal30th August, 2012

Copyright 2011 Accenture All Rights Reserved.Slide 2Contents2Underlying AssumptionsVerify the no of Fixed Asset Master Data Taken OverUser guide steps to reconcile FI-AA & FI-GL BalanceVerify APC of the Fixed Asset Taken OverFixed Asset legacy Data TakeoverVerify Accumulated DepreciationFuture Depreciation ProjectionReconcile FI-AA & FI-GLInformation RepositoryOpen ForumGood to know FactsIssues & ResolutionsCopyright 2011 Accenture All Rights Reserved.23Fixed Asset Legacy Data TakeoverFixed Asset Legacy Data Takeover

Problem after the above Process is completed

This is a process of loading Fixed Asset Data from a previous system into SAPs Asset Accounting (FI_AA) Module.The reconciliation process between the Asset Accounting (FI-AA) sub-ledger and FI-GL during the initial SAP implementation can be quite labor intensive, especially when we encounter differences between the legacy system and the SAP system.Copyright 2011 Accenture All Rights Reserved.4User guide steps to Reconcile FI-AA & FI-GL BalanceThe following steps required to be followed in order to get an idea on how to reconcile FI-AA & FI-GL after Fixed Asset data Takeover in SAP:Step -1

Verify the no of Fixed Asset Master Records Taken overStep -2

Verify APC of the Fixed Assets Taken overStep -3

Verify Accumulated DepreciationStep -4

Future Depreciation ProjectionStep -5

Reconcile FI-AA & FI-GLCopyright 2011 Accenture All Rights Reserved.5Assumption 1

Underlying AssumptionsAll assets and their corresponding values have been imported into the SAP System via standard SAP Takeover Program RAALTD01 or RAALTD11 or used Similar procedure that use the standard FI-AA load transactions.Assumption 2

Accumulated depreciation is transferred into the SAP system and not recalculated.Copyright 2011 Accenture All Rights Reserved.6Verify the no of Fixed Assets Master Data Taken OverWe must ensure that the total number of assets from our legacy system or input file equals the total number of assets that exist in our SAP system.Objective

How to verify the no of Fixed Assets Master Data Taken Over

Transparent Table ANLA

Transaction Code to display Table SE16

Step -1

Verify the no of Fixed Asset Master Records Taken overCopyright 2011 Accenture All Rights Reserved.7Verify APC of the Fixed Assets Taken OverObjective

We need to ensure that the APC loaded from the Legacy System into SAP matches the APC from the Legacy System.

How to achieve

Report RAHAFA_ALV01/ Transaction Code AR03

Menu Path

Transaction Code SA38/SE38

Step -2

Verify APC of the Fixed Assets Taken over

Transaction Code S_ALR_87012026Copyright 2011 Accenture All Rights Reserved.8Verify APC of the Fixed Assets Taken Over

Selection Screen

Granular check can be achieved by using Sort Variant for various required combinations.

Correct Report date need to be selected while running the report.

Copyright 2011 Accenture All Rights Reserved.9Verify Accumulated DepreciationObjective

We need to ensure that the Accumulated Depreciation of the Fixed Assets loaded from the Legacy System into SAP matches the figure from the Legacy System.

How to achieve

Report RAHAFA_ALV01

Menu Path

Tools

Granular check can be achieved by using Sort Variant for various required combinations.

Follow the same Menu Path & Transaction Code as displayed in the previous slide.Point to Note

The correct Report Date need to be selected while running the Report.Various Program variant creation also can be a consideration.

Step -3

Verify Accumulated DepreciationCopyright 2011 Accenture All Rights Reserved.10Project Future DepreciationTransaction Code - S_ALR_87012936Program - RASIMU02

Step -4

Project Future Depreciation

If our legacy system is capable of forecasting depreciation for several fiscal years, we can use the standard SAP report for simulating depreciation, RASIMU02, to forecast several years of planned depreciation in our SAP system.

Depreciation Simulation Report

Copyright 2011 Accenture All Rights Reserved.11Project Future DepreciationDepending on our legacy system capabilities (e.g., whether our legacy system can forecast depreciation for multiple years, by class), we can project future depreciation for the current fiscal year or for multiple fiscal years.

If we can only project depreciation for one fiscal year, we can use report RAHAFA_ALV01 to display the planned depreciation for the year. Copyright 2011 Accenture All Rights Reserved.12Reconcile FI-AA & FI-GLStep -5

Reconcile FI-AA & FI-GLAfter we verify all values in FI-AA, we need to reconcile the balances in the FI-AA sub-ledger with the account balances in the G/L. The vital point is we need to make sure the amounts from the fixed asset report match the amounts reported by the G/L .

Transaction Code FS10N

Copyright 2011 Accenture All Rights Reserved.13Good to know facts

Report RAABST01(Transaction Code-ABST) is used in order to perform consistency check of GL & AA Balances.

Report RAABST02 (Transaction Code-ABST2) is used in order to display list of accounts showing differences for FI-AA FI-GL.

Old asset data takeover transactions (such as AS91, AS92, and AS94) do not update any G/L balances.

After we reconcile all accounts, we need to set the company code status to productive in configuration to prevent any further asset adjustments with the data takeover transactions because this would cause our two ledgers to be out of balance.

We need to ensure that the FI-AA sub-ledger conversion team interacts with the FI account balances conversion team closely.Copyright 2011 Accenture All Rights Reserved.14Issues & Resolutions

No of Fixed Asset Master Records Taken Over in present system does not equal to the legacy system

APC figure of the Fixed Asset Records Taken Over in present system does not equal to the legacy system

Unable to reconcile Accumulated Depreciation Figure

Unable to reconcile Future Depreciation Figure

Unable to reconcile FI-AA & FI-GL

Copyright 2011 Accenture All Rights Reserved.15Issues & Resolutions

We might face various types of issues during the exercise of reconciling the FI-AA & FL-GL Balances, sometimes these problems are caused due to program error, process error or related reasons.

Following SAP Notes are quite useful while addressing some issues in this regard:

868754 RAABST01 : Incorrect error messages962253 RAABST01 : Missing asset line items wrongly identified1288852 RAABST01: Missing line items for group assets811711 RAABST02 : Reports inexplicable depreciation differences1305275 RAABST02 : Terminates with error message AA 8211700882 RAABST02 : FAGL_EMU 007 when using several ledger groups1152526 RAABST02 : Missing currency types in Non-Leading Ledger1114075 Error w/client copy due to table FAGLFLEXD1262944 No FI document for retirement for fixed asset w/ group asset

Copyright 2011 Accenture All Rights Reserved.Slide 16Information Repositoryhttp://scn.sap.com/thread/1822747http://help.sap.com/printdocu/core/print46c/en/data/pdf/Fiaa/FIAA_cagtfadm.pdf

Source of Information16Copyright 2011 Accenture All Rights Reserved.16Slide 17Open Forum17Thank You?For further queries you can reach at subhasish.ghosal@accenture.comCopyright 2011 Accenture All Rights Reserved.17