Post Transfer Values - For Legacy Asset (ABLDT)

Steps with the Manual Transfer of Legacy Data

The manual legacy data transfer includes the following steps:

1. Create the asset master records for the legacy data transfer.

   Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Create Master Data for Legacy Asset (transaction AS91)

2. Post the transfer values.

   Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Post Transfer Values (transaction ABLDT)

   A journal entry is posted for the asset with this. The G/L accounts are also updated. For each asset a transfer document is created that posts the transfer values, for example, on the APC and accumulated depreciation account and against the offsetting account for the legacy data transfer.

3. With a data transfer during the year, you transfer asset-related business transactions that occurred before the transfer date in the current fiscal year (transfer using transaction AB01L).

   If a posting date in the current fiscal year is entered that is before the transfer date, the system recognizes this business transaction as a transfer document; no depreciation is calculated, the document is posted against the offsetting account for the legacy data transfer.

4. For assets under construction that are line item-managed, transfer the open items.

   Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  AUC with Line Item Management: Transfer Line Items, transaction ABLDT_OI)

More Functions with the Manual Legacy Data Transfer

You can also use the following functions with the manual legacy data transfer:

• You can display the master data.

  Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Create Master Data for Legacy Asset (transaction AS93)

• You can modify the master data.

  Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Display Master Data for Legacy Asset (transaction AS92)

• You can create subnumbers for the asset master record.

  Customizing activity: Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Create Master Data for Subnumber for Legacy Asset (transaction AS94)

Master Data

You create master data for legacy assets exactly the same way as you create regular asset master data. However, take into account the following special features of legacy assets:

• The capitalization date is always a required entry. Using the capitalization date, the system determines the depreciation start date and the expired useful life, based on the period control in the depreciation key.

  If the asset was acquired at a time when the company code had a different fiscal year variant, this determination of the useful life will be correct only if the period calendar assignments have been maintained historically.

• The planned useful life is a required entry when a depreciation key for automatic depreciation calculation has been entered.

  You can also account for increased wear and tear on an asset in the past as the result of multiple shift use. You do this by manually correcting the expired useful life that was automatically calculated by the system.

• Time-dependent data (such as the assignment to a cost center) can only be transferred with the values current on the transfer date. To create new time intervals, you have to use the function for changing master data.

Post Asset Values (Transfer Values).

Take into account the following special features when transferring legacy asset values:

• Depreciation areas:

  You must take all active depreciation areas for the asset into account, and enter the historical acquisition costs.

• Posted depreciation (for a transfer during the year)

  If you transfer legacy data during the fiscal year, you can enter the depreciation that was already posted in the legacy system in the current fiscal year.

  Specify the last depreciation period posted (in the legacy system) (field FAA_DEPR_PERIOD) when entering the depreciation posted in the transfer year. The system requires this information to determine the first period for the depreciation that should be posted in the SAP system.

  Manual depreciation first generates a statistical noted item in Asset Accounting and, depending on the posting indicator for the depreciation area, is posted to the FI accounts with the following depreciation run. Make sure then that, for a transfer during the year of depreciation posted manually (for example, with transaction type 640), the respective amount (depending on the posting indicator and on whether postings to FI accounts took place in the legacy system or not) has to be a partial amount of the posted depreciation transferred during the year (transaction type 500).

• Transactions (for a transfer during the fiscal year)

  With a legacy data transfer during the fiscal year, the transfer date of the given company code is not the end of the fiscal year (see Transfer During the Year). You can transfer the transactions from the current fiscal year up to the date of the transfer for legacy data transfer during the fiscal year.

  Make the following entries when transferring transactions:

  • Asset value date

    Note that the asset value date has to be in the current fiscal year, and it must lie before the transfer date.

  • Transaction type

  • Posting Amount

• Posted revaluations:

  Posted revaluations are first entered in Asset Accounting as statistical items and are only then transferred (posted) to the FI accounts with the next depreciation run. Depending on the Customizing settings for the depreciation area, it is therefore necessary to specify the revaluations within the framework of the depreciation posted during the year as both a statistical line item as well as a “posted value”.

The values you enter are also checked against the positive/negative sign rules of the depreciation area (positive/negative net book value, positive/negative ordinary depreciation, and so on).

Change Transfer Values Subsequently

If wrong transfer values were posted, you must reverse the journal entry and then enter the transfer values again.

You can only change transfer values by reversing the posted transfer document and making a new posting. To be able to reverse a transfer document, subsequent transactions are not allowed to exist on the fixed asset.

If follow-on transactions were already posted on the fixed asset, we recommend you proceed as follows:

1. Reverse all transactions in reverse chronological order.

2. Reverse the transfer transaction.

3. Post the new transfer values.

4. Enter the follow-on transactions again individually.

Depreciation Areas in Foreign Currencies

With the manual data transfer, you must transfer the historical values from the feeder system. The foreign currency amounts cannot be determined using an exchange rate by a specified key date. The system therefore does not support historical currency translations; in fact you must enter the values.

Line Item-Managed Assets under Construction (AuC)

To ensure that the line item-managed assets under construction are included, the transfer values are not allowed to be entered as accumulated values in Customizing activity Asset Accounting  Asset Data Transfer  Manual Data Transfer  Legacy Fixed Asset  Post Transfer Values (transaction ABLDT).

You must enter the values individually instead using transaction ABLDT_OI. You must use the specific transaction types 900 and 910 for the transfer.

If you have the special case of proportional depreciation on the AuC, then enter this as proportional depreciation from the previous years using the transaction.