In case you your single ICO is migrated into multiple SAP Cloud integration iFlows (iFlow chains, where one iFlow is used to inject the message, e.g. the dispatcher and another one produces an output), please follow the steps below to perform a proper test cases migration from SAP PO to SAP Cloud Integration.
Test Scenario
As test scenario we will use an INVOIC IDOC to HTTP ICO migrated to multiple CPI iFlows. One iFlow contains the input payload and another iFlow contains the output payload. The two iFlows are linked with the ProcessDirect Adapter.
Previously created PO Test Cases are stored in a Test Case folder with Automation Object of type 20 PI Unit Test PI Unit Test.
There are two options in order to migrate these test cases.
Migrate Manually
For this specific scenario at least two iFlows are required and two Automation objects, one for Inbound and one for Outbound.
Create one Automation Object of type 12 SAP CPI E2E Inbound SAP CPI E2E Inbound. Include the iFlow, the block to get the input payload and fill out the Output Automation Object parameter (this is the Automation Object from which the output payload will be taken).
In this scenario we are using the IDOC Adapter type which does not have any extra parameters. If the Adapter type you use has required parameters, please make sure to fill them as well.
Create the Outbound Automation Object with type 13 SAP CPI E2E Outbound SAP CPI E2E Outboundwith the same name you used as the Output Automation Object parameter in the previous automation object. Include the migrated iFlow and the block for the output payload.
After creating the Automation ObjectS, 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 Inbound 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 multiple iFlows 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 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 Inbound Automation Object generated will be empty and needs to be adjusted accordingly by filling the appropriate iFlow block to get the Input payload as well as the Adapter Type necessary.
By clicking Edit, we fill the blocks for the Input/Outpup 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.
An Outbound Automation object has to be created manually like shown in the previous paragraph. This Automationj Object will be assigned to the Output Automation Object parameter.
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.
