Single ICO to single iFlow migration testing

This guide describes the migration of SAP PO Test Cases to SAP Cloud Integration Test Cases that is done for the purpose of the SAP PO to SAP Cloud Integration migration. In case your single ICO is migrated into a single SAP Cloud integration iFlow, please follow the steps below.

Test Scenario

The base scenario we are looking into in this chapter is a single INVOIC ICO migration. The ICO is migrated to a single CPI iFlow with IDOC Sender Adapter. In the scenario above, input and output payloads are taken from the same iFlow.

Migrated CPI iFlow

We have previously created PO Test Cases that are stored in a Test Case folder with an Automation Object of type 20 PI Unit Test PI Unit Test.

PO Test Cases for migration

There are two options in order to migrate these test cases.

Migrate Manually

In order to migrate test cases manually, first, create one Automation Object of type 12 SAP CPI E2E Inbound SAP CPI E2E Inbound , include the migrated iFlow and the blocks for input and output. Make sure to provide also the proper CPI Adapter type.

After creating the Automation Object, head to the Int4 API Tester Cockpit and the folder containing the SAP PO Test Cases. Select the test cases you want to migrate and click on Migrate Selected from the 3-dot menu.

In the popup that appears, fill the target folder for the migrated test cases along with the Automation Object created in the previous step.

After pressing OK, the migrated Test Cases will be at the target folder selected.

Using CPI Migrator

The second option of migrating single ICO to single iFlow Interfaces is by using the CPI Migrator tool.

For the migration from the Automated Migration Tool, select the Migrate Option on the top and choose Assign existing iFlow.

Once selected the Migration Screen pops up, offering two options. Same iFlow for Inbound/Outbound and Different iFlows for Inbound/Outbound, select the first option Same iFlow for Inbound/Outbound

The Automation Object parameter can either be filled with an already existing Automation Object, left empty (This will generate a new Automation Object with a specific name range) or any name can be given and the appropriate Automation Object will be generated. The generated Automation Objects are of type 12 SAP CPI E2E Inbound and needs to be adjusted to each scenario’s needs.

By pressing the continue button, the tool migrates the PO Test Cases to new CPI ones ands puts them in the assigned Target folder.

Leaving the Automation Object name empty or filling it with any Automation Object that does not exist will lead to the creation of a newly generated Automation Object.

Created CPI Test Cases and the new Automation Object can be seen under SAP IS Test Status parameters, after migration.

The same Test Cases are found in the Target Folder in Int4 API Tester Cockpit.

The new Automation Object generated will be empty and needs to be adjusted accordingly by filling the appropriate iFlow block to get the Input/Output payload as well as the Adapter Type necessary.

By clicking Edit, we fill the blocks for the Input/Output payload and fill the IDOC Adapter type. For this specific adapter type there are no extra parameters that need to be used. For any other case these parameters have to be filled as well.

Testing the CPI Test Cases

Upon migrating the Test Cases, the Run CPI Tests button becomes available and enables to easily execute them all together from the Migration Cockpit or directly from the API Tester Cockpit folder.