An Overview on

Asset Legacy Data Transfer in SAP

S/4 HANA.

Ravi Surya, PhD (Finance)

 Overview ECC Vs SFIN
As Classic Asset Accounting converted as New Asset Accounting,
Documents directly posts to Universal Journal Entry Table ( ACDCOCA).
Sub-ledger specific Asset Accounting tables like ANLC, ANLP,ANEA, ANEP
. have been abolished. So it is no longer required to handle the General
Ledger and Asset Sub ledger separately during Fixed Asset Legacy Transfer.
In ECC : Up to now, you could maintain master data and takeover values in
one transaction (AS91). The G/L account balances in the transfer G/L
account were then manually written in summarized form in a separate
step.
In Simple Finance : In the new solution, the master data continues to be
created in AS91 and/or changed in AS92. However, the takeover values are
posted separately in the new 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
Takeover values" button no longer available in transaction AS91

As per new design in SAP S/4 HANA Finance, we must create and save the fixed asset in
Transaction AS91 first. Then you can use Transaction ABLDT to post Takeover Values. Or you
can also use Transaction AS92, it will navigate directly to Transaction ABLDT. However, it is
important that the Legacy asset must exist first in HANA system. When you post Takeover Values
in ABLDT, the values are, with immediate effect, posted as separate transfer documents and
update Asset Master and GL Accounts. Consequently, the design is such that reconciliation
problems between totals and line items in Asset Accounting are avoided.
Refer Next Slide for Configuration.
With SAP Simple Finance On-Premise Edition 1503, the universal journal entry Table (
ACDOCA) was introduced; therefore, the legacy data transfer for asset accounting also
had to be adjusted accordingly
Removed Customizing Activities in SAP S/4 HANA Finance

The following automatic transfer options from the past are no longer available:

Automatic transfer using direct input (RAALDT01, RAALTD11, RAALTD11_UNICODE)

Transfer using BATCH (batch session to AS81..AS84 or AS91..AS94). We can no longer enter any takeover values in these
transactions.
 How can I make retroactive changes to the takeover values
of a fixed asset?
In the past, it was possible to change subledger-specific information directly in the table
ANLC and therefore manipulate, as required, the takeover values already entered.
Unfortunately, this option was also frequently misused outside the legacy data transfer,
which resulted in reconciliation errors and a considerable support effort because these
manipulations could be reproduced only to a limited extent.
For greater transparency, and due to the fact that 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. In order 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.
See also SAP Note 2217275, which corrected various errors associated with reversing
transfer transactions.
Does the new transaction ABLDT support batch input?

Transaction ABLDT uses an input-enabled ALV grid control. Therefore,

according to SAP Note 311440, it does not support batch input. As an
alternative, you can use BAPI_FIXEDASSET_OVRTAKE_CREATE.

The LSMW recording is based on the batch input recorder and

therefore has the same restrictions as described in SAP Note 311440.
Therefore, it is not possible to create an LSMW recording for
transaction ABLDT. For more information, see SAP Note 554635.As an
alternative, you can use BAPI_FIXEDASSET_OVRTAKE_CREATE
Which alternative option is available in relation to uploading mass data?

In the past, batch input was frequently used to transfer legacy assets in large quantities.
This option is no longer available (see point [6]). Furthermore, direct input is no longer
available. See SAP Note 2014219.
To transfer mass data, use either transaction AS100 or the BAPI
BAPI_FIXEDASSET_OVRTAKE_CREATE for the legacy data transfer (or the method
CreateInclValues for the business object BUS1022). Transaction AS100 can process a
maximum of 5,000 assets in one file upload. However, you can split the file, if required.
When LSMW is used in combination with BAPI_FIXEDASSET_OVRTAKE_CREATE, it is
also possible to process, for example, an Excel file with more than 5,000 assets whereby
one fixed asset is always represented by a (very wide) line in the Excel file. To do this, you
must maintain the field mapping accordingly and define internally which depreciation areas
or depreciation-area-specific information are stored in which columns (fixed assignment;
for example: column BK - BZ contains, by convention, the ANLB information for area 20).
In particular, this procedure is very useful if the feeder system from which the data is to be
transferred supports an Excel download.
What do I need to bear in mind when transferring old subnumbers?
For the transfer of sub-numbers, you must implement SAP Notes 2245187 and 2243637.
Otherwise, depending on the data constellation, you might find that the transferred
documents are posted but the corresponding asset sub numbers are missing.
For a mass upload via LSMW with sub-numbers, it is important to know that:A sub-number
can only be created if the main asset number already exists. & Each number must also
lock the main asset number when it is created
You should therefore split the upload as follows:
Upload of all main asset numbers (completely without sub numbers) You can use the
standard LSMW parallelization mechanisms for this. For more detailed information about
this, see the LSMW documentation and SAP Note 752194.
Upload of sub numbers following successful completion of step 1 To do this, you should
split the sub numbers into multiple files so that the corresponding main asset numbers can
never occur in two files at the same time. You then start each of these files without parallel
processing. However, you can upload the files at the same time, thus achieving a kind of
manual parallelization
AW01N : Screen from Simple Finance System
Transaction: AB03
Accounting Document : FB03
Thank you!

Thank you!
Ravi Surya, PhD(Finance),