Name: Generating CSV Data Load for the Migration from SAP Busines ByDesign to SAP S/HANA Cloud
Uploaded: 2024-6-5
Duration: 715 s

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div>This is the sixth chapter of the microlearning series on the Technical Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud.<br><br>Learn how to enhance your iflow to generate CSV output instead of XML in this micro learning session on technical data migration from SAP Business By Design to SAP S/4HANA Cloud. Explore the benefits of using CSV format for high data volumes and reduce file size and upload time in the SAP S/4HANA Migration Cockpit.</div></div></div></div></div></div></div>

Generating CSV Data Load for the Migration from SAP Busines ByDesign to SAP S/HANA Cloud

Hello and welcome to our microlearning session on Technical Data Migration from SAP Business ByDesign to SAP S/4HANA Cloud. In this chapter, I will demonstrate how to enhance the existing iflow to generate CSV output instead of an XML. SAP S/4HANA Public Cloud Edition also accepts the data in CSV format, which is easy to manage high data volumes. Agenda of the session is as follows. First, I will provide a brief overview of XML and CSV outputs from iflow, which is then followed by a demo where we will dive into the system. My name is Babu Lal Limba, and I am a Customer Engagement Manager in SME Customer and Partner Care Team of Cloud ERP unit at SAP based out of Bangalore. Let's talk about a bit of overview. The iflows provided by SAP generates an XML file that you upload to the migration cockpit in SAP S/4HANA Cloud. However, the XML file size might be too large to be handled in one upload to the cockpit. Either we break the file to bring it to under acceptable size, or we find other data format that can accommodate huge data volumes in lesser file size. This is where SAP S/4HANA Migration Cockpit also supports CSV file as input. CSV format is more condensed and compact in size without missing the relevant information. Hence, it would be worth understanding how the iflows can generate CSV output and help to reduce file size as well as the speed to upload and validate data in migration cockpit. Please check data volumes and XML size, file size at the output of the iflow to decide if you need to enhance iflow to get CSV output. If you have multiple files to upload for an object and each file size is beyond 100 MB, maybe you would like to explore CSV option. In this session, I shall give you hands-on with enhancing the I-flows to generate data load for SAP S/4HANA Cloud in CSV format. Let's get started with the demo and jump into the system. Let's take an example of the object registered product from SAP Business ByDesign, which is mapped to the equipment object in S/4HANA Cloud. This is how the S/4HANA Cloud template looks like. It has three worksheets, master data, partners, and short and long test in which the data will be populated after transforming the data from SAP Business ByDesign Each worksheet will be created as a separate CSV file at the end. And this is the data extract from Business ByDesign registered product. You can see that there are four registered products data that we will map to S/4HANA Cloud Target template. This is the set of data, as you can see when I'm scrolling. I will now jump into the integration suite and start building an iflow. Let's copy an existing iflow and give it a name. Let's call it CSV variant and copy. I have a copied iflow, which I will open now. And it is an XML iflow, as you can see. It generates XML output. So we will start now with the editing of this iflow. Click on Edit. And once the iflow is in edit mode, let's start removing all the components after the message mapping component so that we can now as output generate a CSV file instead of XML. So on the iflow in the edit mode, we will start from the message mapping. Let's create three different targets for from message mapping using a parallel multicast. So I will now put a component called Parallel Multi Cast and connect it to the message mapping component. And I will now draw three branches out of it, one for each XML file. So let me put three content modifiers over here. Content modifier one, content modifier two, and then a content modifier three. Let me just adjust the content modifier appropriately. I would then connect all these content modifiers one by one with the parallel multicast so that each of them receives a feed from the message mapping as an output. So with this, we now are complete with the connections. Now let's go to the equipment template. And here we can see the metadata of this template as well. So we need three worksheets that we need in the iflow. I will give logical names to my content modifiers as per the sheet in the equipment template. So master data, partners and short and long test. So let me give the name for the first content modifier as master data. Then second one, I will name it as partners. And the third one, then I will call it simply text as it provides the information about the text. Now I need to set the message header for each content modifier. So let me go into the message header view, select the first content modifier master data, give a name to it file underscore name and then the source value the source value should be the same as it is provided in the template. So we just copy the metadata the template sheet name technical name and provide it over here as source value followed by hash free text dot CSV. In the same way, we will repeat this activity for the other content modifiers. Let's go to the partner tab, click on add, add a message header, name again, file underscore name source value. We will go to the partners tab and take the technical name of this sheet, S_IHPA and then followed by #FreeText.csv. And then let's do this for the last one, the texts. So again, I will repeat the same activity and then I would go to the S/4 equipment template to find the technical name S_TEXTS_ EQUI and put it over here as a source value. you have to use the same name for the source value as mentioned in the metadata template. We have now to convert the XML data into CSV existing in each of these three containers. So let's put some converters in the iflow. So I will select XML to CSV converter for each of these content modifiers. So XML converter one, then I will again go into the converter and select XML to CSV converter, put another one, and then the same way I will put the third one for the third sheet. And I would connect all these content modifiers to the respective XML to CSV converters. So before proceeding further, we would like to have a look at the target data structure of the message mapping. So let's go into the message mapping, open the data structure, and we can see that in the header of the equipment, we have three child nodes, master data, partners, short, and long text. This is the exact name that we need from the structure, that we will use in the follow-on content in the iflow. So let's go to the XML to CSV Converter part 1, part 2, and give them a name, as I have mentioned. So you can see the path to source element in XSD for the partners would be equipment slash partner, For the text, it would be equipment slash short and long text. At the same time, I specify field separator in CSV as semicolon and include field name as headers for all the three converters. And then save the iflow. Once the iflow is saved, let us now merge the content of three zip files into one. Let us now merge the content of three files into one zip file. So I have added a join here. For that, we need to add a join element and then gather that into one file. So I will connect all my XML to CSV converters to this join. And then I would like to collect this information into one file. Once this is joined, I would then gather this information into one zip file by adding a gather component and connect the join to the gather. Select the gather component that you've created and specify the aggregation strategy. So the incoming format should be any. The aggregation algorithm would be to do a zip and the file name should be header.file name. It is a placeholder and it is a variable that you can see. So it will then give the CSV file the same name that we have specified in XML to CSV converter. Now let's finish this iflow by adding the ending component that is the end message. And I would then connect this gather to the end. We are now ready with the CSV iflow. Let's save this and test the same with some data. To test the iflow, as you have seen in the previous chapter, we first need to deploy the iflow. So we will now click on Deploy. And the deployment process of the iflow would start. Click Yes. Now, once it is triggered for deployment, we would start monitoring the deployment status. So let's go into the monitoring tab and open integration API's view. So after the integration and API tab view is open, you can see manage integration content and you can see one iflow is deployed and you can see it is still starting. Let's refresh to see now it has started and we can see once it is started, there is an endpoint generated for this iflow. I will copy this endpoint so that I can test it via a third party application. I will use Postman for demo purpose. In Postman, let's create a post request, provide the endpoint URL, and then go to the authorization and provide authorization. In the body, select binary, and you select your file, data extract file from business by design, and save this request. Now I will send this request, and the iflow is getting triggered. As I output, the iflow has been processed and I will get a response file. This is how I get a response file as a zip and these are the two CSV files under it. You can see one of the CSV file that I have opened. We see the data only in two CSV files here because there is no data in the short and long text. That's why only two files are generated. With that, I come to the end of the demo. In this session, we have covered how to enhance your iflow to get a CSV output instead of XML. And here is what you can look forward to in this series of learning. Learn how to automate data processing in iflow. Learn how to create your own iflow. Thank you and see you in the next chapter.