Name: Overseeing the Transition from SAP Business ByDesign to SAP S/4HANA Cloud
Uploaded: 2024-3-19
Duration: 546 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><p>Welcome to the first chapter of the microlearning series on the technical data migration from SAP Business ByDesign to SAP S/4HANA Cloud. In this series, we will provide a detailed overview of the motivation, approach, tools, and architecture involved in this migration process.</p><p>In this initial session, we'll delve into the fundamentals of the migration process, including the rationale behind it, the recommended approach by SAP, and the tools and accelerators utilized to streamline the migration. Specifically, we'll explore the Extract, Transform, Load approach advocated by SAP and the use of standard tools such as iFlows to facilitate a smooth transition.</p></div></div></div></div>

Overseeing the Transition from SAP Business ByDesign to SAP S/4HANA Cloud​  ​

Hello and welcome to our microlearning session on Technical Data Migration from SAP Business ByDesign 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 the Technical Data Migration from source ERP to SAP S/4HANA Cloud. In the chapters that follow, you will see more details on migration path and demos on on our accelerators, that is, the iflows. Agenda for the session is as follows. First, I will talk about the motivation for transition from your ERP system to SAP S/4HANA Cloud. Then we will cover the data migration approach. As we proceed, we will take a deep dive into the architecture behind the suggested migration approach. And finally, I will talk about where we stand today, what's the roadmap, and what you can expect in the series of learning. 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. So let's get started with the overview. The message from SAP is loud and clear that our customers cannot outgrow the ERP portfolio of SAP. Hence, SAP has offered multiple products in its ERP stack, starting from SAP Business One to SAP S/4HANA. SAP S/4HANA Cloud Public Edition is also positioned in SME segment, and it has its priorities set to deliver the intelligent enterprise for SMEs. Hence, the customer who have outgrown with their current ERP system, like SAP Business ByDesign or SAP Business One, could be a suitable fit for SAP S/4HANA Public Cloud. With that context in mind, we are offering a migration path to SAP S/4HANA Cloud via Greenfield implementation. Let me quickly touch upon some key drivers for this transition. First, the fast growing businesses are reaching the limits of their ERP system, like SAP Business ByDesign or SAP B1 in terms of sizing and volumes. Second, SAP S/4HANA business ecosystem has much higher scalability and flexibility. Third, appealing innovations areas in SAP S/4HANA Cloud that attract specific customer segments, like subscription billing, group reporting, et cetera. Fourth, more people in the labor market of SAP S/4HANA are available. And lastly, the customers use extensive enhancements and customizations and want to transform back to standard. And this is a chance for them to move to SAP S/4HANA Public Cloud. Transition to S/4HANA Public Cloud is a Greenfield implementation project. It is a brand new implementation starting from scratch, which involves defining your processes, systems, and landscapes. It also involves full load of data migration and re-engineering of processes. You map the business processes to new ERP, redefine them, and orchestrate them. Let's come to the core topic of this session that touches the hefty task of data migration. SAP recommends an ETL approach for data migration that involves extraction of data, cleansing, transformation, and upload to the target system. SAP provides standard tools and accelerator to facilitate the ETL approach. SAP offers the following tools in this context. Number one, provide standard tools for extraction and standard tools for upload. Number two, provide mapping of key objects between SAP Business ByDesign and SAP S/4HANA objects. Partner can utilize these mappings to transform data from SAP Business ByDesign to SAP S/4HANA Cloud Migration Template files. Number three, provide tools called iflows to automate filling of SAP S/4HANA Cloud migration template files. This will reduce the overall effort and reduce the cost of implementation as well. This slide gives a high level architecture and overview of how ETL approach must be realized. On the left, we have source ERP, that is our SAP Business ByDesign system, and where we extract the data from required object into Excel templates. These data files are then transformed and massaged by the middle piece to convert them into S/4HANA migration template file. The S/4 migration template file is then uploaded to SAP S/4HANA system on the right. The middle piece consumes the integration suite service on BTP to execute this transformation. In nutshell, SAP provides tools for extraction, and SAP provide tools for upload. And in between, SAP is additionally developing and delivering iflows using BTP service that do the data transformation job and reduce overall effort for partners in migration activity. You may note that partners can use the mappings and develop their own tools for transformation. Also, the partners using the SAP-delivered iflows can customize them as per their need on top. Let's talk about the first piece, that is extraction. And specifically, extraction from SAP Business ByDesign. Extraction is supported for most of the common objects in SAP Business ByDesign. Data is extracted into XML files in the same form as the data files migrated into Business ByDesign. You can apply packaging parameters while extracting to avoid failures of heavy load extraction. You can apply filtering to extract only the needful data for migration. And extraction is a background job and can be executed in non-productive hours to avoid burdening the system unnecessarily. The second piece in ETL is transformation. Transformation tools, that is the iflows, are available for most common master data objects like material services, customers, suppliers, et cetera. These iflow act as an accelerator for your migration project and comes with standard field mappings. The output from a iflow can be XML or a CSV file, as both are supported by S/4HANA migration cockpit. These accelerators are quite performant and can do a processing of 135 MB file in less than two minutes. As mentioned earlier, you need integration suite service activated in your BTP sub account so that you can load these iflows and execute to get the output files. There is no connection required between the integration suite and the S/4HANA Public Cloud system. This is a quick glimpse into the mapping in an iflow that shows how the data fields from Business ByDesign are mapped to SAP S/4HANA corresponding object. The visual just shows the drag and drop mappings. However, many mappings involve data merging, splitting, or complex logic that is written in the script file as a program. You will hear more details in next chapters. Coming to the last piece, that is load in ETL. This step is executed in S/4HANA Cloud system. Output generated from transform step is fed into load step, and data is pushed to the target system. The migration cockpit in SAP S/4HANA is similar to what was available in SAP Business ByDesign, and it provides a step-by-step guidance on pushing the data into S/4HANA Public Cloud system. The migration cockpit is included in the license of SAP S/4HANA Cloud. The task of value mapping to map the code values from SAP Business ByDesign to SAP S/4HANA Cloud is done as a part of this project in Migration Cockpit before pushing the data into the system. Once these value mappings are defined, they can be reused in further migration projects. Let me provide you a quick view of where we are currently. We have published blogs called Data Migration Accelerator and a child blog on how to consume an iflow on SAP Community, providing details on our ETL architecture and iflow guide. You can find the blog by navigating to the path mentioned on the slide here. In the blog, you will find the link to the repository where we have the iflows uploaded. Partners can download these iflows file and upload to their integration suite system for hands-on and for use in their data migration project. As on March, 2024, we have published iflows for 13 key objects that are most common across our Business ByDesign customer base. For example, customers, suppliers, materials, services, inventories, et cetera. iflow for more objects are in progress, and stay tuned to our blog for more updates on that. With this, I come to the end of this session. In this session, we have covered SAP's data migration approach to accelerate your transition projects. And here is what you can look forward to in this series of learning. Learn what are the prerequisites to prepare for this data migration. Learn how to customize standard iflows. Learn how to consume standard iflows and update these iflows with new data structure. Learn how to enhance iflows for CSV output. And learn how to automate data processing using SFTP in iflows. You will also learn how to create your own iflow. Thank you, and see you in the next chapter.

Overseeing the Transition from SAP Business ByDesign to SAP S/4HANA Cloud​ ​

Overseeing the Transition from SAP Business ByDesign to SAP S/4HANA Cloud