Entering Legacy Data

Data transfer from a legacy system is the first activity you perform in a new production system after configuration and asset classification. You can transfer asset data automatically from the legacy system, or, if there is only a small amount of asset data in the legacy system, you can enter the asset master data manually using the transaction AS91. However, the takeover values are posted separately in the posting transaction ABLDT. When you do this, a posting is made to the transfer clearing account immediately. In other words, the manual step for the summary write-off is no longer required.

Transaction ABLDT uses an input-enabled ALV grid control. Therefore, according to the SAP Note 311440, it does not support batch input. Therefore, it is not possible to create an LSMW recording for transaction ABLDT. For more information, see the SAP Note 554635.

Programs for transferring legacy data automatically are as follows:

• For a large to very large quantity of legacy data, use the BAPI interface BAPI_FIXEDASSET_OVRTAKE_CREATE. The BAPI also supports the creation and transfer of legacy asset values in a single step. The transfer of values to existing legacy assets is not supported. If you change existing migration values, you must first reverse the transfer transaction(s) before you can use BAPI_FIXEDASSET_OVRTAKE_POST to post new values. To cancel transfer transactions, use BAPI_ASSET_REVERSAL_POST (SAP Note 2481644).
• For several hundred assets, use Microsoft Excel (transaction AS100) Transaction AS100 can process a maximum of 5,000 assets in one file upload. However, you can split the file, if required.

For greater transparency, and because transfer documents are posted in the new solution, the only way to change takeover values is to reverse the posted transfer document and then repost it. To be able to reverse a transfer document, a fixed asset must not have any subsequent transactions because the legacy data transfer provides the value foundation for this fixed asset. If follow-on transactions have already been posted to the fixed asset, you must first reverse all transactions (preferably in reverse sequence), then reverse the transfer transaction, and finally, post the new takeover values. You can then create the follow-on transactions again individually.

In the case of assets under construction (AuCs), you cannot transfer cumulative APC or accumulated depreciations. The transfer must take place using the transfer of transactions, as follows:

• In the manual case, not using transaction ABLDT but using AB01 or, as of the SAP Note 2294012, using the new transaction ABLDT_OI.

• In the case of a transfer using BAPI_FIXEDASSET_OVRTAKE_CREATE, do not enter the values into the table CUMULATEDVALUES; instead, enter them into the table TRANSACTIONS.

Start the legacy data transfer by setting the status of the company code to Asset data transfer not yet completed in Customizing for Financial Accounting under Asset Accounting→Asset Data Transfer→Parameters for Data Transfer→Define Transfer Date and Additional Parameters.

You can transfer legacy data in FI-AA with the Ongoing status, but you cannot post-normal transactions.

You can transfer legacy data for any date in the past from a legacy system. However, you cannot create any legacy data in the SAP system before the transfer date. Therefore, the data is transferred from the legacy system on the transfer date.

The transfer date can be either at the end of the last closed fiscal year or any date within the fiscal year following the last closed fiscal year during the same year.

You can transfer the following data:

• Legacy data transfer at the end of the last closed fiscal year:

  Master data, a historical asset under construction, APC values, and accumulated depreciation as they stood at the last closed fiscal year.

• Legacy data transfer during fiscal year:

  In addition, you transfer the depreciation and asset transactions posted during the current year.

If the transfer time is at the end of the last closed fiscal year, transfer the master data, APC values, and accumulated depreciation as given at the end of the last closed fiscal year.

With the app Migrate Your Data - Migration Cockpit, you can migrate business data to SAP S/4HANA. You can migrate data directly from certain SAP source systems, or you can use staging tables to migrate data.

You can use this app to do the following:

• Create migration projects to migrate data, and to monitor the status of the migration.

• Select the migration objects that are relevant for your migration scenario (the app uses migration objects to identify and transfer the relevant data).

• Process any mapping tasks for the migration objects.

• Simulate the migration before migrating your data to SAP S/4HANA, and monitor the status of the simulation process.

• Migrate your data to SAP S/4HANA, and monitor the status of the migration.

• Legacy asset master data can be entered manually or transferred automatically.
• With the app Migrate Your Data - Migration Cockpit, you can migrate business data to SAP S/4HANA.
• BAPI interface supports creation and transfer of legacy asset values.
• The transfer date can be at the end of the last closed fiscal year or any date within the following fiscal year.