Additional depreciation area and second migration

[djwafelap]

Hello SAP experts,

My customer has been using SAP S/4HANA on Premise for asset accounting since 2018. At that time, assets were migrated and have since been posted to. An additional legally required valuation view with a different depreciation (with start either on 1.1. or 1.7.) was previously supplied by a service provider via Excel. However, this is to be discontinued and this valuation is to be mapped via a new depreciation area in SAP.

The customizing of a new depreciation area is clear so far. During the transfer, we initially thought of migrating the values supplied in Excel to the new depreciation area of the existing assets only as of 31.12.2020 and then continuing the asset values with a different depreciation key. However, initial tests have revealed two problems:

1. The system wants to migrate at the earliest to a financial year that lies directly before the current one, i.e. 2021.

2. The system reports an error FAA_POST210 ("New transfer of accumulated values not possible"). Even if it only affects one additional valuation area that does not post to the general ledger, the system requires the reversal of all transactions including the migration from 2018 and a legacy data transfer for all valuation areas.

Do any of you know how we could get the data into SAP? Reversing thousands of transactions is almost impossible. We would like to avoid creating new master records because this would result in chaos with the many assets.

I would be grateful for any tips!

Best regards

Rado

[jganz]

3401627 - Check for multiple value transfers to the same legacy asset as part of different legacy data transfers

[jganz]

Hi to all,

here the answer from SAP:

Solution provided:
Dear Mr. Ganz,
actually, it is a quite unusual approach to use ABLDT successively for partial transfer of legacy values per ledger group.
However, from technical perspective this is possible as long as these separate transfers are being executed within the same legacy data transfer segment in FAA_CMP.
In such a scenario the legacy values of the depreciation areas which are assigned to different ledger groups all refer to the same legacy transfer date stored in ANLA-LDT_DATE, which is correct.
However, this does not apply in case of multiple value transfers to the same fixed asset as part of different legacy data transfer dates in FAA_CMP.
Best regards,
Marco Herhuth
Application Innovation Services – AIS, Customer Solution Support and Innovation | Asset Accounting
SAP Development Support

[jganz]

Hi all,

we have the same a big issue with the new asset accounting in S/4. We are therefore looking for a broad response from similar cases in order to persuade SAP to find a solution.

At the time of the live migration and go-live, our customer decided to be creating a legacy data transfer and posted the transfer values with restriction to depreciation area for the local gaap. The data transfer took place in 2021. In 2023, a new value transfer for tax gaap is to take place for the 2022 financial year. The postings with transaction ABLTD could also be carried out by the customer without any problems. Subsequently, the situation arose to reverse incorrect documents, which failed due to the error message “AA422 ("Contact your system administrator (table error)”. Then we opened an SAP service incident and received the SAP note "3401627 - Check for multiple value transfers to the same legacy asset as part of different legacy data transfers".

However, this note does not provide a solution to the basic issue.
Our research into the new asset accounting under S/4 has shown that subsequent migration should not be possible even in depreciation areas without an initial value transfer. Only the copying of new depreciation areas with identical values from the source depreciation area should be possible. However, this situation and functionality does not meet the legal auditing requirements for accounting. There, it must also be possible to subsequently map an asset history sheet as "historic values" without acquisition postings and with deviating values. Furthermore, no subsequent reversals or changes to the balance sheet or the valuation areas under local gaap can be required.

These restrictions compared to the ERP release with the classic asset accounting with account solution completely question the functionality of the new asset accounting under S/4 regarding a correct multiple valuation approach?

With best regards

Jens

[pinkster]

Hi there,

I am experiencing the same issue has anyone come up with a resolution for this.

Regards

Tracy

[mb92]

Hello Rado,

I encounter the same issue. Did you find any solution?

Regards,

Maryem

[djwafelap]

Hi Maryem,

Unfortunately, there doesn't seem to be a solution except of reversing all transactions. That's what SAP told me. I am going to work on this in a few weeks/months. If I find any solution, I will tell you about this.

If you find something, I would appreciate reading from you 🙂

Best regards

Rado