Name: Automating Data Processing in Iflows for the Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud
Uploaded: 2024-8-5
Duration: 622 s
Description: This is the seventh chapter of the microlearning series on the Technical Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud.The session covers the setup and connection of On-Premise and Cloud SFTP servers, the enhancement of iflows, and the testing of automated data processing. Gain insights into the process and look forward to learning how to create your own iflow in future sessions.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div><div><div><div><div>This is the seventh chapter of the microlearning series on the Technical Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud.<br>The session covers the setup and connection of On-Premise and Cloud SFTP servers, the enhancement of iflows, and the testing of automated data processing. Gain insights into the process and look forward to learning how to create your own iflow in future sessions.<br></div></div></div></div></div></div></div></div></div></div></div>  

Automating Data Processing in Iflows for the Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud

Hello and welcome to our Microlearning session on Technical Data Migration from SAP ByD to SAP S/4HANA Cloud. As part of Cloud Migration Factory offered by Cloud ERP team, we have produced a series of sessions to enable you with technical data migration from source ERP to S/4HANA Cloud. In this chapter, I will demonstrate how to automate data processing in the iflows. Agenda for the session is as follows. First, I will provide an overview on the steps on how to automate data processing in iflows. Then, followed by a demo where we will dive into the system. I am Sai Srinath, a Development Specialist in SME Customer and Partner Care team of Cloud ERP unit at SAP based out of Bangalore. The following steps outline the process on how to automate data processing in iflows. Step 1. Set up SFTP server. Step 2. Connect integration suite to SFTP server. Step three, enhance iflows to run on SFTP connection. Step four, finally test the automated data processing. Let's have a detailed look into step one. We have two options for setting up an SFTP server, On-Premise or in the Cloud. For On-Premise SFTP server, we need to install an SFTP application on a local machine and configure the connection parameters. We will define folders to hold input and output files. The connection between the SFTP application and the integration suite is established with the help of cloud connector. For a Cloud SFTP server, neither we have to install anything on local machine nor we need a cloud connector. We can use any preferable vendor who provides this service. The usage shall be same where we define folders to hold input and output files. Let me demonstrate step 1 in the system. In this demo, I will show you On-Premise SFTP server and its parameters. Before we start, make sure you have a BTP account and access to integration suite service. In case of an On-Premise SFTP server, you can choose your preferred SFTP application. For this demo, I will be using Rebex as a local SFTP server. Here you can see the host, port number, username and password. In data folder of Rebex application, we have input and output folders. Input folder will contain extracted files from Business ByDesign. Once the files from input folder are processed by iflow, response files are stored in output folder. To connect SFTP application and integration suite, we need cloud connector. Cloud connector can be downloaded from SAP development tools of cloud section. Depending on your operating system, you can select and download the appropriate file. For successful installation of Cloud Connector, you need to have a JDK installed on your system. In this demo, I will be using SAP Machine and OpenJDK provided by SAP. For instructions, please refer to documentation section. In case of a Cloud SFTP server, once you have the SFTP and user setup ready, you can see the host endpoint and the port number of the SFTP server. Here also define input and output folders similar to On-Premise setup. Let's jump into step 2. For setting up the connection in an On-Premise SFTP server, we use cloud connector between the SFTP server and the integration suite. First, we will connect the integration suite to Cloud Connector, then Cloud Connector to the On-Premise SFTP server. Finally, we will set up authentication details of SFTP in the integration suite and test the connectivity. In case of a Cloud SFTP server, there is no need for a Cloud Connector. Once you setup all the authentication details of cloud SFTP in the integration suite, we can then test the connectivity directly. In this demo, I will guide you on how to setup and connect the integration suite to On-Premise SFTP server. Let's start by logging into SAP Cloud Connector. Open your preferred browser and go to localhost 8443. The default user is administrator and the default password is manage. Click on Login. After logging in, change the password for security reasons. Next, we will connect the SAP Cloud Connector to a sub-account in BTP. Define the sub-account as shown. You can get the sub-account ID and other details from the overview page of BTP sub-account. Give any name to the local ID. Here we will use POC as the local ID. and connect. You should see a successful connection between the cloud connector and the BTP. Now let's connect the SAP cloud connector to local SFTP server. Click on cloud to on-Premise and then click on add. Set the backend system type to non-SAP system and the protocol to TCP. Add the local SFTP server by entering its host and port from the Rebex application. Give a virtual name here. Check the internal host box and click on finish. You should now see that the SFTP server is reachable from the cloud connector. Note to consider, if your connection to Wi-Fi changes, it might result in change of IP address in Rebex. In that case, click on edit and change the host with new IP address from Rebex application. In the next part, we will set up authentication details in integration suite and test the connectivity with on-Premise SFTP server. In the integration suite, navigate to monitor section and select Connectivity Test. Choose SSH option. Hostname will be the virtual hostname in Cloud Connector and do the same for the port. Set proxy type to On-Premise and location ID to POC. Click on send. You should receive a positive response with host key indicating you can reach the host. Next, copy the host key and save it in a notepad. Go back to the monitor section and select security material. Upload the notepad with host key here. Next, we create user credentials of SFTP server. Click on create. Select User Credentials. Give a name for the credentials. The username and password will be your SFTP application user. Navigate back to connectivity test and check the connection to SFTP with authentication details. For authentication, choose user credentials and select the user we created in the security material. Click on send. As you can see, the response is successful. Now the integration suite can access data from SFTP server. When setting up authentication and testing connectivity for a cloud SFTP server in integration suite, the process is similar to On-Premise SFTP server. The key difference is to set the proxy type to Internet. After configuring the settings, you can test the connectivity to ensure everything is working correctly. Step 3 is to enhance the existing iflow. In this step, we will change the adapter of sender and receiver to SFTP and define the parameters like post-processing, message pooling, etc. First, let's start with the On-Premise SFTP server. We need to delete the existing HTTPS connection of sender adapter and change it to SFTP. Enter all the relevant information in the source tab. The directory is where the ByD files are located. The address consists of host and port. The proxy type is On-Premise and the location ID is POC. For authentication, we will use the user credentials we created while testing the connectivity. Next, in the processing tab, for post-processing, select the move file option. This will move the files that are already processed to archive folder. Now let us setup the receiver adapter for SFTP server. The directory is where response files will be saved. For the filename, I am using a header value which will name the response files, same as the ByD file it was executed from. The address, Proxy Type and Authentication details same as we defined in the sender adapter. After making all the changes, save the iflow. Let's discuss about the adapter setup for Cloud SFTP server. The parameter setup for sender and receiver adapter is similar to On-Premise SFTP setup, but the key difference is the Proxy Type is internet. Now that we have set up all the connections and enhanced the iflows, we are ready to test the automated data processing. In this demo, we will use On-Premise SFTP to test the process. In the input folder of customer, I have two extracted files and customer folder in output is currently empty. Now we will deploy the iflow. Once the deployment is successful, we will check the message processing logs. Here we should see two logs representing two extracted files that are being executed. Next we will move to input folder of SFTP server. As we can see the extracted files are moved to archive folder and the response files are in output folder. The same process can be followed for Cloud SFTP server as well. With that, I come to end of the demo. In this session, we have covered how to automate data processing iflows to accelerate your data migration project and here is what you can look forward to in this series of learnings. Learn how to create your own iflow. Thank you and see you in the next chapter.