SAP Financial Legacy Data Transfer

SAP Financial Legacy Data Transfer from a legacy system is usually the primary exercise you may want to perform in a new production system after configuration and asset classification. You'll be able to either transfer information mechanically from a legacy system using a batch input procedure, or (with a really small asset portfolio) you may manually enter the data utilizing a transaction for legacy asset data.In addition to the guide transaction (AS91), there are three methods for transferring legacy knowledge routinely:

1. Large amount of legacy data: Batch enter process (RAALTD01)
2. Very massive amount of legacy knowledge: Direct information import (RAALTD11)
3. Several hundred property: Legacy Data Transfer with Microsoft® Excel

Please notice that in all instances only the relevant asset master information and line gadgets in Asset Accounting are up to date and not the final ledger accounts in Monetary Accounting. Balance reconciliation with the related basic ledger accounts should due to this fact take place separately.You start the legacy data switch by setting the corporate code to the standing "Legacy knowledge switch not yet accomplished". In this status you'll have the option to transfer legacy knowledge in FI-AA, however not create posting transactions.

Transfer Data

You can switch legacy knowledge from a legacy system for any date in the past. You cannot create any legacy knowledge within the R/3 System earlier than the transfer date. This ensures that the data transferred from the legacy system is consistent on the switch date.The transfer date can fall either on the finish of the last closed fiscal yr, or in the fiscal yr following the last closed fiscal year.On the finish of the last closed fiscal year:
Grasp information, historic APC, accrued depreciation on the status of the final closed fiscal year Legacy data switch during the fiscal 12 months:along with the grasp information and cumulative values of the last closed fiscal yr (1), depreciation and asset transactions posted within the present year may also be transferred at the identical time.The transfer of the balances for the G/L accounts all the time needs to be carried out separately.Asset transactions occuring through the legacy knowledge transfer have to be posted separately in the R/3 System after the legacy data switch has been completed.

If the switch date is the top of the final closed fiscal yr, you switch only the grasp knowledge, the APC and the collected depreciation as they stood at the finish of the final closed fiscal year.Transactions on line item managed AUCs are posted utilizing special transaction types for legacy knowledge (transaction sorts 900, and 910). This technique ensures that the line items are identified as acquisitions from previous years (prior-yr acquisitions) although/since the system units the asset worth dates to 01/01/CYYY.Legacy knowledge switch doesn't replace the balances of the G/L accounts. You will want to switch the balances as they stand on the date of transfer (that's, fiscal year finish).

1. General ledger personnel can input these balances through FI or
2. Asset accounting personnel can enter these balances through the corresponding transaction (FI-AA Implementation Guide).

So as to verify the reconciliation, use the FI steadiness listing (RFSSLD00) and appropriate FI-AA experiences with the report date "switch date + 1 day".Please observe the next special considerations if you are utilizing a production R/three Financial Accounting system:All steadiness sheet and accumulated depreciation accounts are up-to-date in a production SAP R/3 FI system. You will not need to repeat basic ledger account balances.

Fiscal Year

When the switch date is after the top of the last closed fiscal year, this is called switch throughout
the fiscal year. On this case you transfer the overall grasp information and the gathered values at the begin of the fiscal year. You additionally have to switch the transactions and depreciation posted during the present year.There are two methods of transferring the depreciation posted through the present year:

1. Transfer the depreciation for the current 12 months posted as much as the time of transfer. In Asset Customizing you then have to enter the final depreciation interval posted (within the legacy system) before the time of switch for every depreciation area.Depreciation posted within the legacy system doesn't must have been calculated and posted in accordance with the principles of FI - AA.
2. If you do not want to switch any posted depreciation, you'll find a way to instead run an unplanned depreciation posting after the data transfer for the entire depreciation for the current fiscal yr up to the time of transfer. In this case, the depreciation calculated by the FI - AA system for this era could be posted.

Transactions: When performing a legacy information transfer through the fiscal year, you too can enter the transactions from the end of the last closed fiscal year as much as the time of transfer.

Transfer Parameters

Outline the interval for depreciation posted (legacy knowledge switch throughout the fiscal year): On this case you need to enter for each firm code the final period for which depreciation was posted in the legacy system. The interval therefore applies to the posted depreciation that is to be transferred during the legacy data transfer. R/3 (the brand new system) then posts depreciation from this period. As an different, you probably can catch up the posting of depreciation by finishing up an unplanned depreciation posting run.Recalculation of amassed depreciation: If you need to manage a new depreciation space, you'll have the option to calculate previous depreciation using R/3 FI-AA depreciation terms (the corporate code should be in take a look at operation).Calculation of substitute values/base insurable values: The substitute values and base insurable values are calculated. That is completed on the assumption that the acquisition value was acquired utterly on the capitalization date.Define sequence of depreciation areas: Defining the sequence of depreciation areas improves performance throughout handbook/computerized information transfer utilizing a batch input interface.The depreciation areas with probably the most values to be entered should seem first on screen. Areas which take over values or depreciation should seem last.The interface program doesn't have to be structured in line with these specifications.

Automatic Data Transfer

Using a program you've gotten written yourself, extract the info in your legacy system and construction it in accordance with the FI - AA knowledge structure. You can find this within the Dictionary tables BALTD (master data) and BALTB (transaction data).Your interface program transfers the legacy data from the legacy system to a sequential file. In case you wish to transfer greater than eight depreciation areas, it's a must to modify the Dictionary tables BALTD and BALTB, since the standard structure of BALTD assumes eight depreciation areas.You ought to use the "Assets" function within the Knowledge Transfer Control Middle to check the information to be transferred earlier than the precise transfer and make any modifications required.The transfer program RAALTD01 supplies the data, using background processing, to a legacy knowledge transfer transaction. Data with errors are stored in the form of a batch input session, and need to be processed later.

The documentation for the transfer program RAALTD01 accommodates detailed directions:

1. on the structuring of the sequential transfer file by the interface program
2. on testing options
3. on avoiding errors and deciphering errors that happen
4. on the procedure in the event of program termination.

You can use the direct information import (RAALTD11) if in case you have a really massive number of property to transfer from your legacy system. This increases efficiency significantly throughout the actual takeover of assets.

Data Transfer with Microsoft Excel

Along with the Information Switch Control Heart, it also potential to transfer asset accounting legacy knowledge within the R/3 System utilizing Microsoft® Excel. This method is uitable for transferring relatively small portions of information (a couple of hundred belongings).The Excel sheet consists of two parts:

1. in the five-line header part you outline which entries in the legacy property you wish to transfer (firm code, description, class, and so on)
2. in the asset part you enter the person belongings and their values.

The Excel sheet must contain fields for the identifier (the outdated asset number), company code,asset class, and capitalization date, which should include values for every asset. The same applies to the required entry fields defined in the asset class of the R/3 System.The fields are organized in line with record types. The report type has to be entered in the first column of the Excel file. It is suggested that you just assign the fields in the header half as proven above. At this point, you may add further master information information to document type 2. In record sort three (depr. area information) the depreciation space is all the time acknowledged first. The totally different transactions in record kind four are numbered sequentially, permitting you to distinguish between them.In R/3 Customizing, the fields within the Excel file and the enter fields of the grasp document you would possibly be creating should be assigned to one another (this is called matching). It is crucial that you just assign the identification function (old asset number), asset class, company code, and capitalization date, in addition to every other required entry fields (asset class).

Preparing for Production Start Up

This function provides you a summarized overview of the system settings you've gotten made. It can provide a list of incorrect configurations.This report needs to be used to highlight any significant errors within the configuration.You may analyze the system settings and print them out as documentation. You need to use the following overview reports to test the consistency of your system settings:

1. Charts of depreciation
2. Firm codes
3. Depreciation areas
4. Asset courses

You can too use a consistency report to test the reconciliation accounts for Asset Accounting. A record is created displaying the account allocations and the corresponding common ledger accounts. The report supplies a remark for any allocations which might be incorrect.A consistency report for FI-AA Customizing can be accessible to examine the plausibility of your system settings.After having checked the consistency of the configuration settings you can now begin with manufacturing begin-up.

Reset Posted Depreciation

Use this perform if errors have occurred when testing the depreciation posting run and you need to return to the original status.You may reset the posted depreciation in FI-AA (all depreciation runs). In addition, it resets the depreciation data of a legacy data transfer in the course of the fiscal year. It due to this fact needs to be transferred again.It also deletes all knowledge that's used to handle and monitor the depreciation posting runs.No documents or posting sessions are created to cancel the finished depreciation posting that has been made in FI. You want to make handbook adjustment postings within the collected depreciation accounts within the general ledger.Solely firm codes in test operation can be reset. Resetting the depreciation knowledge will most likely be recorded in the system log.

Set Reconciliation Accounts

Set/reset reconciliation accounts:
In this step, you define the G/L accounts for FI-AA as reconciliation accounts using a report. This program adjustments the definitions of the G/L account grasp document which can be entered in asset accounting's account determination.You can also reset the reconciliation accounts, if:

• You could have entered an incorrect account into an account allocation in Asset Accounting
• Balance corrections have to be posted to reconciliation accounts retroactively.

Please understand that, on this case, the consistency between FI-AA and people G/L balances isn't any longer ensured, because the accounts might be directly posted again.As the company code has the standing "Legacy information switch not yet accomplished", it's a must to bear in thoughts you can only post transactions within the R/3 System after the date of the particular transfer. After this date all asset accounts and worth adjustment accounts have to be re-defined as reconciliation accounts for FI-AA. These accounts can due to this fact no longer be directly posted to after the switch date.

Transfer Balances

The subsequent step in preparing for the production start-up is to transfer the balances of the reconciliation accounts in the basic ledger (see "Transferring Legacy Knowledge at Fiscal 12 months Finish").You even have to do this if FI has previously been working with a non-SAP system.You have to have reconciled the asset stability sheet values in asset accounting with the balances of the affected reconciliation accounts. Use the report RABEST01 (asset list) in Asset Accounting. When you begin this report, specify the primary day of the present fiscal year because the report date. The system will provide knowledge as of the final day of the previous fiscal 12 months (meaning no depreciation from the present fiscal yr is included).To do that, you have to use the corresponding balance record (RFSSLD00) within the FI system.You may then copy the balances from any suspense accounts to the Asset Accounting reconciliation accounts.


RELATED POSTS

SAP Controlling and daily processing 
SAP Financial and Controlling Overview 
SAP Controlling Information System 
SAP Financial Company Organization 
Customizing SAP Controlling 
Creating General ledger accounts in sap controlling
Creation of customer and vendor accounts
SAP Controlling Event Based Posting
SAP Financial Payment Cards
SAP Financial and Controlling Overview
SAP Financial Profit Center Analysis 
SAP Financial Information System
SAP Financial Legacy Data Transfer