The problem
When moving from ECC to S/4HANA, or to a new server, attention goes mainly to the data and the processes. But all the integrations with other systems have to come along too: the functions, queries and views that webshops, apps and reports run on. If something goes wrong when moving integrations, the outside world notices first.
The approach
- First know what is there. Which integration objects exist on the old system, which version, and do they match the design? Only objects that are known to be in order are moved.
- Know what the new system can do. The target system is read: which release, which technologies are available? Sometimes an integration can take a more modern form on the new system.
- Move in layers. First the foundation that other objects depend on, then the rest. The next layer only starts when the previous one is fully in place.
- Check on arrival. On the new system, every object is read back and compared with the register.
An overview in three columns
Source, move, target: for each object you can see where it is. That way it is clear at any moment what has already moved, what still needs to be done and what needs attention.
What to watch out for
- Start the inventory of integrations early in the migration, not at the end. Integration migration is not a final step.
- Clean up what is no longer used; it does not need to move.
- Test integrations on the new system together with the systems that connect to it.
Would you like advice on moving SAP integrations along? Request a free advice conversation.
Updated on