New Int4 IFTT testing adapter for simplified interface testing of outgoing messages (EDI, legacy, etc.)
When testing SAP Interfaces (APIs) for different purposes like S/4HANA conversion projects, middleware migrations we often need to take into account that a single SAP interface as a software component is in most cases made of 2 applications (middleware and backend system) as shown in Figure below.
Complete testing of SAP APIs as a single software component
How to customize Int4 IFTT to test ABAP and middleware in a single outbound automation object
Some of them however (as OBJKY) we want to make dynamic so we can use Int4 IFTT message selector to select messages on a massive scale and just repeat those.
Once we run them from Int4 IFTT cockpit they will retrigger the original message on the SAP backend system as shown in the figure below from transaction WE02.
Int4 IFTT will catch the output message (from the middleware – SAP PO/SAP CPI or in the SAP backend system) and compare the original message with the current execution as show in the Figure below.
This means that in a matter of minutes we can test the whole SAP interface (middleware and SAP backend) for any kind of migration or conversion project.
SAP PRESS book: Testing SAP APIs: Strategy and Execution – where testing of SAP APIs for S/4HANA conversion use case is described in detailed
openSAP course: Virtualize and Automate Your SAP Testing Using Int4 IFTT (7200 participants and over 1.000 certified) lesson – Week 2 – Unit 4: SAP S/4HANA Conversion Testing