418122, 242 PM Case Study of Transtion to SAP SIAHANA | SAP Blogs System Conversion Process Steps ‘System conversion is a guided process supported by several tools (such as Software Update Manager) and utilities provided by SAP for analysis. Software Update Manager (SUM) is a tool used for software maintenance (installing ‘support packages). It also converts an SAP ERP system into an SAP S/4HANA system. It combines the migration of the system to the SAP HANA database (if you are not on HANA), conversion of data, and software upgrade into one single step. Majority of the data conversion (transfer into the new data model) is carried out by SUM; however, the conversion of financial data is a follow up activity after the data conversion You can use the prerequisite check extended mode of SUM before your first conversion cycle, The tool will execute the same checks however, instead of stopping at issues, it will collect all of the issues in a single list (@ CVS file). This gives you the ability to analyze the issues and work on them and prepares you better for the first conversion SAP S/4HANA is anew product, and not an incremental update, System conversion is significantly more than an upgrade. In our case, we chose System Conversion but that doesn't preclude you from using some of the best features in SAP S/4HANA. The SAP Fiori provides an innovative user experience. You should introduce the new Fiori UX for one or more business roles. This will help showcase its value and to stakeholders and users Ultimately, system conversion not only increases your readiness to innovate, but also carves your path for future business transformation. Now that we have taken this first step to migrate to SAP S/4HANA, we'll continue to leverage the new functionality and innovation Some other lessons learnt: + We chose System Conversion but please explore, and leverage SAP standard content. It helps remove lot of redundant processes and harmonize them + Redesign your business processes for in-memory computing. This is not about doing the same things faster so think outside the box, Remember it's not a faster horse, it's new car and perhaps a Ferrari, Make good use of it + Ensure your development team fully understands the new software development concepts and technologies, ABAP has evolved over the past decade and core data services (CDS) are available for data centric applications, + SAP Fiori is more than a new Web user interface (UI). Embrace it. Don't stick with the old GUI + Clean your master data prior to the transition. Make this a priority. This is critical hitps: blogs sap.com2022/01/03/case-stuey-oftranstion-to-sap-s-thanal ete415722, 242 PM (Case Study of Transition to SAP SIAHANA | SAP Blogs + System performance is important. Make sure this is part of your testing cycles. Volume testing is the best way to ascertain that the solution is ready for production + Manage your financial data and understand the plans of your finance team to leverage the new G/L and document split capabilities. This may have a major influence on your project, + Conversion test cycles are the key to success of your project. © Test your first conversion with a copy of the production with the standard SUM procedure, It will almost definitely take longer than you are expecting. © Use a copy of the production system as a source in the first conversion cycle. Don't compromise with a subset of data or an old copy. © Use a production-like hardware for the target SAP S/4HANA system in this first cycle. This will give you realistic execution times and a good estimate of the expected downtime. If you do this on a DEV system, the team will understand only the technical procedure and steps and not much in the way of resolution or execution times. © Plan for at least two (three would be better) additional conversion test cycles with production data and production hardware. © Two of of these cycles should also include tests on the connected third-party systems to validate the integration. Don't underestimate the effort required to correct some of the interfaces. It takes time to get to the root cause and then get the appropriate resources from third party vendors © Check the compatibility of the third-party systems prior to your first cycle © We found some of these third-party tools incompatible with S/4HANA. This must be resolved and, in some cases, would mean looking for alternatives and tough business decisions. + Remove unused code. You'll inevitably find some of the code is never executed. Use ABAP call monitor statistics + Clean-up your custom code. Over the years, we had extended our solution and found several thousands of lines of custom code, Take this opportunity to reassess and clean + System Conversion sounds like a technical upgrade but change management cannot be an after thought and rushed. Using innovation and harmonized processes means “educating” the users to do things differently. Don't underestimate this effort. + Explore your options to archive historical data that may be perceived as useful but can be accessed as “read-only’. Archive prior to conversion to SAP S/4HANA as a pre-conversion activity + Other factors that will influence your project timeline © Data cleansing © Change Management © External interfaces hitps: blogs sap.com2022/01/03/case-stuey-oftranstion-to-sap-s-thanal me