- In SAP S/4HANA, the legacy data transfer posts asset values to the general ledger immediately, against an offsetting account. Decide early which balances come in via asset accounting and which via the general ledger.
- Typical errors are wrong asset classes, equipment records migrated as assets, missing depreciation areas, and incomplete current-year transactions.
- While the legacy data transfer is open, you correct transfer values by reversing and re-posting them. The asset class cannot be changed in the master record; if the asset already has values, you post an asset transfer to a new asset in the correct class.
Why fixed assets are special
Fixed assets carry their history with them. That includes acquisition values, accumulated depreciation, useful lives, and several valuations, for example for financial reporting and for tax purposes. What went unnoticed in the legacy system for years must be correct in every depreciation area after migration.
In SAP S/4HANA, asset accounting follows the logic of new Asset Accounting. Changes to acquisition values go to the general ledger immediately, and each valuation has its own depreciation area that posts in real time. Differences between asset accounting and the general ledger therefore show up earlier.
How the legacy data transfer works in S/4HANA
| Step | Tool or transaction | Watch out for |
|---|---|---|
| Set the transfer date and the last closed fiscal year | Customizing for Asset Accounting | End of the fiscal year or mid-year; decide together with accounting |
| Set the company code status for the legacy data transfer | Customizing | While the legacy data transfer is open, legacy data transfer postings are possible. After completion, they are not |
| Create asset master records | Migration object Fixed asset (incl. balances and transactions) in the Migration Cockpit, individually with AS91 | Class, depreciation areas, useful life, and depreciation start per asset |
| Post transfer values | With the migration object or ABLDT, for large volumes via a BAPI | Each posting creates a general ledger document against the offsetting account |
| Migrate current-year transactions | In the migration object or with AB01 | Acquisitions, retirements, and depreciation posted in the current year |
| Migrate assets under construction | ABLDT_OI for line items | Cumulative values cannot be transferred here, only transactions |
The legacy asset data transfer also posts to the general ledger. The balances of the asset accounts must therefore not be transferred again with the G/L balance transfer. Otherwise the values appear twice on the balance sheet. If you use the same offsetting account for all legacy data transfers, check at the end that its balance is zero.
Typical errors and how to prevent them
| Error | Consequence | Prevention |
|---|---|---|
| Wrong asset class | Wrong account determination and depreciation, wrong presentation on the balance sheet | Agree on the class mapping with asset accounting, spot checks per class |
| Equipment confused with fixed asset | Technical objects appear as assets on the balance sheet, or assets are missing | Clarify the boundary between plant maintenance and asset accounting before the mapping |
| Incomplete depreciation areas | Differences between the book and the tax valuation | Include all depreciation areas in the mapping, reconcile the values per area |
| Wrong useful life or depreciation start | Wrong depreciation from the first month | Cross-check the remaining useful life against the acquisition date |
| Current-year transactions missing | Depreciation and acquisitions of the current year are wrong | For a mid-year transfer date, include transactions and posted depreciation |
| Asset balances migrated twice | Values appear twice on the balance sheet, via the legacy asset data transfer and the G/L balance transfer | Define which accounts are transferred only via the legacy asset data transfer |
| No reconciliation with the general ledger | Differences only surface at closing | Reconcile the asset history sheet and the reconciliation accounts after every test migration |
Keep equipment and fixed assets apart
Equipment belongs to plant maintenance, fixed assets to accounting. An equipment master record can hold an asset number, and one asset can carry several pieces of equipment. If you create every piece of equipment as a separate asset during migration, you inflate the asset base.
Whether a technical object is a separate asset is decided by accounting under the applicable accounting rules. Record this assignment as a rule in the mapping before the first test migration runs.
Choose the transfer date deliberately
The simplest option is a transfer date at the end of a fiscal year. In that case, the closing values of the completed fiscal year are sufficient: acquisition values and accumulated depreciation.
For a mid-year transfer date, you also need the transactions and the depreciation already posted in the current year. This is feasible, but it significantly increases the reconciliation effort.
A go-live at the start of the year, however, coincides with year-end closing. Weigh both options early with your accounting team, together with the schedule from the article on SAP ECC end of maintenance.
Reconcile after every test migration
- Number of assets per asset class and company code against the legacy system
- Acquisition values and accumulated depreciation per depreciation area, for example via the asset history sheet
- Balances of the reconciliation accounts in the general ledger against the asset values
- Balance of the offsetting account for legacy data transfer
- Spot checks of remaining useful life and depreciation start
- Assets under construction with their line items
Asset accounting signs off the reconciliation log. That turns a test migration into evidence that an auditor can read as well.
If it has already happened: correction options
How you correct errors depends mainly on whether the legacy data transfer in the company code is already complete.
| Situation | Correction | Note |
|---|---|---|
| Legacy data transfer open, values wrong | Reverse the legacy data transfer document and post it again correctly | Only without subsequent transactions; reverse those first |
| Legacy data transfer open, master record wrong | Reverse the values, deactivate the asset, and create it again correctly | The cheapest time for any correction |
| Legacy data transfer complete, wrong class | Asset transfer to a new asset in the correct class | The class cannot be changed in the master record; SAP’s intended route is an asset transfer to a new master record |
| Object does not belong in asset accounting | Post a retirement and create the correct objects again | Clarify the balance sheet effect with accounting and your tax advisor beforehand |
Resetting a company code in asset accounting is intended for test systems. For each variant, define the field specifications, test the postings in the test system, and document them for the auditors.
For equipment carried as fixed assets, we drew up a correction concept: asset retirement and re-creation based on field specifications.
How we help
We agree on the class mapping with your asset accounting team and run the test migrations with a reconciliation log. When a migration has gone wrong, we design correction concepts.