Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Testing of S/4 HANA conversions is a challenge because:

  • Limited business involvement due to unchanged business requirements (compared to greenfield implementations

  • Limited access to vendors and customers systems and the manual testing – already live system

  • Technically driven nature of conversion

In many cases, business processes on SAP ECC are not started in SAP ECC but in the external systems (B2B-EDI, Legacy systems). Those systems communicate with the use of integration technologies (like IDOCs, etc.).
In order to To validate and test the system after conversion to S/4HANA, we need to simulate many external systems (service virtualization).
Int4 IFTT with the use of it’s REPEATER function , using its REPEATER function, can automatically repeat all messages which that existed in the system after the conversion process is finished and compare the business documents created before the S/4HANA conversion with the reference documents created before the S/4HANA conversion. Using this approach can eliminate the need to connect external systems for S/4HANA validation and at the
same test more examples using the existing messages.

Testing process

Below The below description is limited to the API Backend testing. However, but of course it can be extended to the full entire SAP environment together with the integration platform.

Step 1:
Convert your existing SAP ECC
Convert your ECC system to S/4 HANA and select the existing IDOC messages/Business
documents as references which can be repeated by Int4 IFTT using the
REAPETER REPEATER functionality.
Step 2:
Rerun
With the use of Int4 IFTT, automatically repeat your existing messages/business documents
in order to create new business objects on the converted system.
Step 3:
Compare
Using an Int4 IFTT automatic comparison report, compare objects created before the
S/4HANA conversion with the new objects created after the conversion.

Business Value to customer

Presented The presented approach will lead to:

  • Cost reduction due to low involvement of external partners (customers, vendors) and business resource

  • Meeting all business requirements by automated testing for
    thousands of cases

  • Improved efficiency of the migration process thanks to Test Driven Development (TTD) approach