Time of Transfer

The transfer date is the cut-off date for the transfer of legacy data. The transfer will only include data up to this point in time. There are two possibilities:

The transfer date can be the end of the last closed fiscal year.

The transfer date can be in the fiscal year that directly follows the last closed fiscal year. This is called "transfer during the fiscal year."

You specify the time of the transfer per company code by setting the transfer date (in Customizing of Asset Accounting , choose Asset Data Transfer → Parameters for Data Transfer → Date Specifications → Specify Transfer Date/Last Closed Fiscal Year .

Remember that the transfer date generally is not the same as the date for the actual transfer of data. Normally, you create (input) legacy data in the System after the transfer date. This could be necessary, for example, if you have to perform a closing in your legacy system between the transfer date and the date of the actual transfer. The consequences of the this difference will be explained later in more detail.

This graphic is explained in the accompanying text.

You can also transfer legacy data to the SAP System before the transfer date. However, you then have to make sure that the transactions that you posted in your legacy system up until the transfer date are also later posted in the Asset Accounting component.

The Transfer Date is the End of the Last Closed Fiscal Year

In this case, you do not need to include any posted depreciation or transactions in the transfer of legacy data. You only need to transfer master data and the cumulative values as of the end of the last closed fiscal year. (In the graphic below, this is the data for time period A). The transfer of balances for the G/L accounts also have to use the balances from this date.

This graphic is explained in the accompanying text.

Transfer at End of Fiscal Year

Any transactions to legacy asset data that have a value date after the transfer date, but before the date of the actual transfer of data (time period C), have to be posted in the System (FI-AA) after the legacy data transfer.

The Transfer Date Is in the Fiscal Year Directly Following the Last Closed Fiscal Year (Transfer During the Fiscal Year)

In the case of a transfer during the fiscal year, all the business transactions up to the date of transfer have been carried out in the legacy system.

This graphic is explained in the accompanying text.

Transfer During the Fiscal Year

Along with the general master data, and the cumulative values from the start of the fiscal year (time period A), you must also transfer the following values:

Depreciation posted

Include the depreciation posted in the legacy system since the end of the last closed fiscal year up to the date of transfer (time period B). To assist in this procedure, you enter the last period before the transfer date that was posted in your legacy system. You enter this information for each company code and depreciation area in Customizing for Asset Accounting . Choose Specify Last Period Posted in Prv.System (Transf.During FY) . The system requires this information in order to determine the first period that should be posted in the System.

If you do not want to transfer depreciation posted from your legacy system, you have an alternative. After the legacy data transfer, you can "catch up" the posting of depreciation by carrying out an unplanned depreciation posting run. This posting run will "catch up" all depreciation in the current fiscal year up to the date of the transfer. The system posts all depreciation that the Asset Accounting component determines for this time period.

Transactions

When transferring legacy data during the fiscal year, you also have to include the transactions from the end of the last closed fiscal year up to the date of transfer (time period B). There are two ways of doing this:

Enter the transactions using the legacy data transfer transaction.

You should be aware, however, that entering these transactions does not result in any updating of General Ledger accounts. When transferring the balances of the G/L accounts, therefore, you need to transfer the balances as they stand on the date of transfer (in Customizing for Asset Accounting , choose Preparing for Production Startup → Transfer Balances ).

Instead of entering the transactions along with the master records, you can enter the master records without transactions, and post the transactions (from time period B) afterward in the System. If you use this method, the G/L accounts in the Financial Accounting (FI) component are automatically posted in the background. In this case, you should transfer the balances of the G/L accounts as they stand at the end of the last closed fiscal year (A).

Any asset transactions in your legacy system that have a value date after the transfer date, but before the date of the physical transfer of data (time period C), need to be posted separately in the Asset Accounting component in any case.

This graphic is explained in the accompanying text.

Current fiscal year YYYY

Last closed fiscal year YYYY - 1

End of the last closed fiscal year 12/31/YYYY - 1

Date of transfer 03/01/YYYY

Date of actual entry 05/01/YYYY

The following values have to be entered in the transfer transaction in Asset Accounting:

Cumulative values as of 12/31/YYYY - 1

Depreciation posted in the year YYYY up to 03/01/YYYY

Transactions from 01/01/YYYY to 03/01/YYYY

In addition you need the following data

Balances of the General Ledger accounts involved as of 03/01/YYYY.

Transactions with asset value dates from 03/01/YYYY to 05/01/YYYY

This graphic is explained in the accompanying text.

You can only transfer acquisitions and down payments to the System using automatic transfer. You have to enter other kinds of transactions (such as retirements) using the manual transfer transaction.