SAP consulting

S/4HANA to S/4HANA

Already on S/4HANA does not mean the landscape is finished. Release, database and cloud moves, instance consolidation after an acquisition, and clean-core work on SAP BTP are planned and tested so operations continue.

What you can expect

  • A release upgrade with regression scope you can explain
  • Fewer systems after an acquisition, with a data story finance accepts
  • Custom code moved to the side, onto BTP, where it belongs
  • Interfaces retested against standard APIs rather than copied forward

How the work is shaped

Release upgrade

Fit-to-standard delta, add-on compatibility and a test cycle aimed at what the new release actually changes.

Instance consolidation

Chart of accounts, master data and open documents brought together without a second implementation.

Clean core

Custom logic reviewed and, where it should leave the core, rebuilt on SAP BTP with standard interfaces back into S/4HANA.

Landscape move

Private cloud, RISE or data-centre moves planned around close calendars, not the other way around.