Are you ready for 2020 SAP PO migration? 

SAP PO 7.5 – migration project  

Due to the end of support for Process Orchestration (SAP PO) versions < 7.5 at the end of 2020 most of the customers will have to migrate to SAP PO 7.5. The migration project is purely technical and depending on the complexity of the original landscape it may or may not require a lot of effort. 

Read More

SAP API testing with Int4 IFTT runs integrated with Tricentis Tosca

In his latest book “Enterprise Continuous Testing: Transforming Testing for Agile and DevOps” Wolfgang Platz mentions that API testing is the future of automated testing as it is the only part of enterprise system testing where in reality you can automate >85% of test cases.


Read More

Int4 IFTT Integration with ALM

Int4 IFTT – Simple Integration with ALM

Are you using Micro Focus ALM (formerly HP ALM/Quality Center) to manage application delivery, lifecycle and testing in your company?

We have great news for you – Int4 IFTT can be easily integrated with ALM without installing additional components or libraries. Test execution is automated using VAPI-XP test script and doesn’t require Unified Functional Testing (UFT) to be integrated with ALM.

Read More

Int4 IFTT – Reduced data footprint of test cases

In Int4 IFTT installations with large number of test cases or test cases with big payloads speed of data growth can become a challenge.
To reduce the data footprint of test cases database we are introducing payload compression.
This feature, available from Int4 IFTT SP12, transparently compresses new test cases payload at saving time and decompresses it on demand when payload is displayed or used during test case execution. Read More

Long-awaited feature in Int4 IFTT – SAP PO Wizzard

As you remember in order to create test cases you had to create configuration object manually per tested interface, where you would define all rules and parameters. Not anymore! As of Service Pack 11 release 006 you will be equipped with SAP PO Wizzard which would handle this task automatically.

Read More

SAP PI 7.XX dual stack to SAP PO 7.5 migration – lessons learned


SAP Process Integration is the most common SAP middleware platform so far. Its widely used to connect various SAP and non-SAP systems, providing a single point of integration. According to SAP PI dual stack installations (ABAP and JAVA) will be supported by SAP only until the end of 2020. Very likely in the next couple of years there will be an increase in the number of SAP PI migration projects as SAP XI/PI dual stack installations will need to be migrated to a single stack JAVA only SAP PO architecture.

Read More

Int4 IFTT integration with Solution Manager

In the previous blog “Int4 IFTT Change Management Integration” you can find general information about new features in Int4 IFTT related to integration with change management software. In this blog you will learn more about integration with SolMan.

Read More

Int4 IFTT gets even more automated!

Since SP11 integration with change management software is available. Int4 IFTT will create automatically incidents regarding particular test case, update their status, close existing and creating new ones. You will be also enabled to manage incidents directly from test cockpit manually.
With this feature Continuous Testing implementation is easier and there is not chance to overlook the defect. Check this blog to learn more!

Read More

SAP Test Tool (PIT) – SAP PO 7.5 SP14


SAP has prepared a first version of a SAP PO upgrade testing tool – PIT. It’s being shipped with SP14 to SAP PO which is currently released.  The tool perfectly complements Int4 IFTT testing tool in one scenario the so please have a look how you can configure it to help you perform an SAP PO upgrade more easily.   

Use cases

SAP Test Tool primarily focuses:

  • help with SAP PO dual stack (ABAP & JAVA) to single stack migrations (JAVA only)



In order to use SAP Test Tool you need to have SAP PO 7.5 SP14 (where you can install it or run test scenarios) but if you just want to feed the SAP Test Tool with data you can use a system from 7.31 SP17 or 7.5 SP06 or higher.

For each message used as a source you need to enable logging on BI, MS, AM.

Current limitations (this may be subject to change)

  • ICOs with sender/receiver wild cards
  • Sync/async, async/sync bridges
  • Mapping splits
  • Flows with Decentralized adapter engines
  • No adapter modules are tested


Terminology used in SAP Test Tool

Test system – SAP PO system in the landscape which is used for testing – either as source (feeding the Test tool with messages) , target (where sender’s messages are executed) – those are used in dual stack to single stack migrations or both (sender and target) which is a typical use case for regression testing on a single system.

Test Case – SAP PO routing configuration which is being tested (ICO, etc.)

Test Data Set – a set of messages (successfully processed) which is a subject for testing.

Run configuration – specifies on which landscape should the test case be executed


In order to be able to create the configuration and run it you’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.


Currently SAP Test Tool is using NWDS as a main configuration tool. The scenario below will describe how to do regression testing on a single SAP PO system. We will find a successfully processed message, do a mapping change and see what will happen once we reprocess the same message via the same ICO. Ideally it should display all of the differencies between the two runs.

Step 1

Open NWDS and find the new perspective: SAP Process Integration Test.

Step 2

Open preferences and insert connection data to your SAP PO were the SAP Test Tool is installed.

Step 3

In the next step you need to define the systems (source and target) where you need to run your tests. In this case it’s the same system where SAP Test Tool is installed.

Step 4

In the next step we can start creating Test Cases.

Select the type of the flow you want to test.

In the next step it’s time to select the routing object itself (ICO).

Step 5

In the next step the Test case is created so we can populate it with test data. In order to do that select the Test Data tab of the Test Case.

Then select the “Add” button to add messages to the test data where you can specify the source system from which you want to fetch the data.

Next select the time range when the message was created and the message itself.

On the Verification tab of the Test case you can also define which parts of the message should not be checked (dates, etc.).

This step finishes the configuration/customizing part of the SAP Test Tool.

Run and validation

In order to run the test you need to create a new run configuration.

Where you need to specify the Test Case and the landscape of the execution.

What you can also select here is the checkbox “Stop message before delivering to Receiver” which will automatically cancel the Test message after processing so it will not overload the receiver system.

Once you press Run the Test Case will get executed and the TestRun is executed you can send it for Verification which will compare the old (original) target message with the new one created by executing the Test Case.

As I’ve changed the mapping before running the Test Case what we can see is that there are some differences found.

In the Error Overview section we can see a more detailed description talling us the what is different between the original message and the one from the Test Run.

Complementary tools:

SAP Test Tool is a free test tool provided by SAP which can help in some SAP PO Use types mentioned in this article. In case you’d need to Test some other use cases like the ones mentioned below fell free to contact us about a demo of the Int4 IFTT (the only SAP certified tool for testing all SAP middleware scenarios).

SAP Test Tool – PIT and Int4 IFTT scenario coverage

Use Case Support
SAP PO dual stack to single stack migrationsYesYes
3rd party middleware to SAP PO migrationsNoYes
SAP PO to 3rd party middleware migrationsNoYes
SAP EDI migrations (B2B add on)NoYes
SAP Cloud Platform Integration (CPI) testingNoYes
Service VirtualizationNoYes
S4/HANA conversions testingNoYes
SAP Backend validations (document field level)NoYes
SAP Backend (IDOC, Proxy) testing, SAP eCATT
SAP AIF TestingNoYes
Test Driven DevelopmentNoYes
Continuous testing/DevOpsNoYes
Integration test documentationNoYes
SAP PO Features
Use of successful messages as reference messagesYesYes
XML comparison (including exceptions)YesYes
EDIFACT/ flat files comparison (incl. exceptions)NoYes
Exchanging test cases between environmentsYesYes
SAP PO adapter module testingNoYes
SAP PO multimappingsNoYes
Background (scheduled) validationsNoYes
Solman integration, incident managementNoYes
NWDS requiredYesNo
SAPGUI requiredNoYes
SAP PO only (after 7.31 SP17)YesNo
SAP PO (also versions prior to 7.31 SP17) , SAP CPI,
SAP Backend interface implementation,
3rd partymiddleware


More videos on the SAP PO upgrades topic – How to upgrade you SAP PO landscape




int4 booth at SAP Teched Barcelona 2018!

We’re happy to announce that we’ve been approved to become an official exibitor at SAP Teched Barcelona in 2018 (23rd-25th October).

We will be presenting our SAP certified automated regression testing and service interface virtualization software – IFTT.

With the use of int4 IFTT you can fully automate testing of all your SAP PO/AIF/CPI/IDOC flows in both the middleware and at the SAP backend system. All will happen without source system access as we provide an unique service interface virtualization concept without the need for additional hardware or software.

With this great news we also have a suprise for you. Two of our experts and SAP Press book authors SAP Mentor – Michal Krawczyk and Mateusz Nowak will be available for you at our booth everyday from 13:00-14:00 to answer all of your SAP PI and SAP AIF related queries. Please come to our booth to have a chat about SAP integration anytime during the day and have an amazing teched experience.

Invitation for SAP Teched 2018