{"id":27176,"date":"2026-11-11T16:58:53","date_gmt":"2026-11-11T15:58:53","guid":{"rendered":"https:\/\/scheer-pas.com\/en\/?post_type=post_type_article&p=27176"},"modified":"2026-11-12T09:05:14","modified_gmt":"2026-11-12T08:05:14","slug":"sap-s4hana-migration-integration-layer-blogpost","status":"publish","type":"post_type_article","link":"https:\/\/scheer-pas.com\/en\/blog\/article\/sap-s4hana-migration-integration-layer-blogpost\/","title":{"rendered":"How to Keep Enterprise Integrations Stable During an SAP S\/4HANA Migration"},"content":{"rendered":"
<\/div>
\n
\n \"Five <\/div>\n\n<\/div><\/div>
\n\t

BLOG<\/p>\n<\/div><\/div><\/div><\/div>

\n\n\t
\n\t\t

How to Keep Enterprise Integrations Stable During an SAP S\/4HANA Migration<\/h1>\t<\/div>\n\n<\/div><\/div>
\n\t

11 November 2026 | Lukas Peter<\/p>\n<\/div><\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t

Replacing SAP ECC with SAP S\/4HANA affects every system that exchanges data with the ERP platform. In one migration from SAP ECC on-premise to SAP S\/4HANA in the RISE with SAP (SAP RISE) cloud environment, 18 systems and external parties exchanged data through 180 interfaces in Scheer PAS. 30 of these interfaces already existed and had to keep their data structures, although the SAP system underneath was replaced.<\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t
\n\t\t
<\/div>\n\t\t\t\t
<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

TL;DR <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

An SAP migration is also an integration project. When connected systems talk to SAP through an integration layer, that layer can absorb much of the change. For most of the 30 existing interfaces (roughly 80%) adjusted mappings kept each interface exactly as it was, and the calling systems did not notice the switch.<\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\t
\n\t\t
<\/div>\n\t\t\t\t
<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>
<\/div><\/div>
<\/div>
\n\t

SAP migrations are usually planned around SAP itself: data migration, custom code, new processes. The systems around it get less attention, although every change to SAP’s data structures reaches them. In this project, those included dealer systems, an enterprise data platform, banks, insurance companies, public authorities, and an online shop.<\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n\n\t
\n\t\t

Why is an SAP S\/4HANA migration also an integration project? <\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

An SAP S\/4HANA migration is also an integration project because every system that exchanges data with SAP depends on its data structures and interfaces. Replace the ERP system, and each of those connections must be checked, adapted, or rebuilt.<\/p>\n

 <\/p>\n

In this project, 18 systems and external stakeholders exchanged data through Scheer PAS, including SAP S\/4HANA itself, the enterprise data platform (formerly the data warehouse), databases, dealer systems, parent and national companies, agencies, public authorities, service providers, HR and user-management systems, blob storage, job scheduling, an online shop, banks, insurance companies, and mobility service providers.<\/p>\n

 <\/p>\n

Few of them can adapt to the migration’s schedule. A bank, an authority, or an external agency rarely adapts its interface because one of its partners migrates its ERP system.<\/p>\n<\/div><\/div><\/div><\/div>

<\/div><\/div>
<\/div>
\n
\n \"Five <\/div>\n\n<\/div><\/div>
\n\n\t
\n\t\t

What did this SAP S\/4HANA migration involve?<\/h2>\t<\/div>\n\n<\/div><\/div>
\n\t

This SAP S\/4HANA migration moved the ERP platform from SAP ECC on-premise to SAP S\/4HANA in the SAP RISE cloud environment. Master data was migrated and synchronised, and the integration and interfaces were implemented with Scheer PAS. The master data transfer was first used for the migration itself and is still running today: it keeps master data from SAP S\/4HANA in sync with the enterprise data platform.<\/span>\u00a0<\/span><\/p>\n

 <\/p>\n

In total, 180 interfaces were implemented, 30 of which already existed before the migration. The 150 new interfaces connected a wide range of systems directly with SAP S\/4HANA. That is a figure from this project, not a benchmark. How many interfaces a migration involves depends on how many systems a company connects and how it scopes its interfaces.<\/span>\u00a0<\/span><\/p>\n<\/div><\/div><\/div>

\n\n\t
\n\t\t

The project at a glance<\/h2>\t<\/div>\n\n<\/div><\/div>
\n\n
\n\t\n
\n \n \n \n \n
Aspect<\/th>\n In this project<\/th>\n <\/tr>\n <\/thead>\n
Migration<\/th>SAP ECC on-premise to SAP S\/4HANA (SAP RISE)<\/td><\/tr>\n
Systems and external parties<\/th>18<\/strong><\/td><\/tr>\n
Interfaces implemented<\/th>180<\/strong><\/td><\/tr>\n
Interfaces built before the migration<\/th>30<\/strong>. For most of them (roughly 80%), adjusted mappings kept the interface unchanged.<\/td><\/tr>\n
Communication<\/th>REST, OData, SOAP, JMS, SQL, RFC<\/td><\/tr>\n
Data formats<\/th>XML, JSON, flat files<\/td><\/tr>\n
Robotic process automation<\/th>UiPath<\/td><\/tr>\n <\/tbody>\n <\/table>\n<\/div>\n\n