Manual Migration

Manual migration process

1. Create the new iFlow

2. Assign it to the migrated ICO

3. Configure details for Automation Object

Create the new iFlow

For manual migration, the work starts with a manual creation of SAP CPI iFlow that will be implementing the migrated interface. Once that is ready, the next step is in Migration Cockpit.

Assign the iFlow to migrated ICO

First, navigate to the ICO that is migrated. Then go to Migrate and choose Assign existing iFlow activity.

Open

Choose the target landscape for operation. It could be Development at this stage.

Open

Next, use the dropdown to find the newly created iFlow.

Enter Automation Object name to reuse existing object. If Automation Object with provided name doesn’t exist it will be created during the process. If Automation Object field is left blank system generates the object using predefined name and sequence number.

Finally, choose a folder (might need to be created from APITester first) where to place the migrated test cases dedicated to the iFlow. Click on the box on the left of the scenario name to select it.

Click Continue

After a moment, the screen refreshes, offering details of the migration artifacts and a view to the migrated test cases.

Configure details for the Automation Object

The automatically created Automation Object might not have all the details needed for properly testing the CPI iFlow. From the SAP IS Test status section, click on the Automation Object name to open the Automation Object and further edit it from there. Please read on in the SAP IS Testing section of the manual how to further configure the Automation Object.

At a minimum, these settings need to be configured

• CPI: Block in iFlow to get input payload

• CPI: Block in iFlow to get output payload

• CPI: Adapter type

Following the correct Automation Object configuration, the migration is ready for testing.