Golden Rules For SAP Suite On Migration Of HANA & S/4HANA

Categories: Cloud Computing

SAP S/4HANA is an intelligent SAP’s next generation ERP suite, which is explicitly designed for in-memory computing. It provides an adapted, consumer-grade user experience with SAP FIORI without any concern about the industry or business size. It also helps to drive immediate value to the business across all lines. With the help of SAP HANA in-memory platform, the developers of SAP have prudently personalized the solution in order to meet the requirements and challenges of the digital economy. Along with the innovative processes the companies can improve the existing processes to declare their advantage in the digital struggle.

Depending on the needs of the individuals, SAP S/4HANA can be deployed either on on-premise or in the cloud platform. The on-premise deployment option, provide you with a great amount of flexibility and control, whereas with the help of cloud platform you can deploy with a lower total cost of ownership quickly. SAP S/4HANA has been developed to empower your business to transform.

Get quality help now
checked Verified writer

Proficient in: Cloud Computing

star star star star 4.7 (657)

“ Really polite, and a great writer! Task done as described and better, responded to all my questions promptly too! ”

avatar avatar avatar
+84 relevant experts are online
Hire writer

In SAP S/4HANA the processes can run more quickly, with the help of real-time analytics the businesses can take more accurate and better decisions, and also it offers an enhanced user experience for your team. On the other hand, the SAP HANA database offers you unbeatable speed and performance, that allows jobs and transactions to run in a more adequate time frame. The prediction engine of SAP HANA offers the businesses the different ways to work with programming the complex calculations and enhancing the accuracy around the decision making.

Get to Know The Price Estimate For Your Paper
Number of pages
Email Invalid email

By clicking “Check Writers’ Offers”, you agree to our terms of service and privacy policy. We’ll occasionally send you promo and account related email

"You must agree to out terms of services and privacy policy"
Write my paper

You won’t be charged yet!

When these key areas of process are combined it provides the organization with the relevant benefits.

Since the last year, the huge number of increase in the customers has been observed, which are adopting suite on HANA.There has been some skills transferability from BW to Suite migrations and also there are certain differences. This article presents some excellent rules and guidelines for migration toward the SAP HANA and S/4HANA suite.

Define scope of the project

In order to migrate towards SAP S/4HANA or suite on HANA, it is required to define the scope of the project. Most of the clients are looking for a technical migration initially on SAP S/4HANA or HANA suite. Then perform the code changes and start S/4HANA extensions. The necessary technical migration activities have to be covered. If it is required, then the customer will move towards the Unicode conversion and upgrade to ECC 6.0.

Build the Integrated schedule

This activity is imperative for any project, likewise it is essential with a suite on HANA. There are different types of associated systems such as forecasting systems like BPC, Supply Chain Management,reporting systems like BW, third party interfaces and integration. Also, there are a number of front end tools, for example, SAP GUI, Portals, Web stores, etc. The integration of cloud to the SuccessFactors or Ariba or Salesforce. It is required to involve teams from Basis, Architecture, Infrastructure, Networking, Custom Development, Test Management, Finance, HCM etc. It is required to include the entire business. An integrated schedule is developed that defines the project in a manner which can be presented on a single monitor screen so that everyone should know about the happening of the event and the time as well. It has to be make sure that the integrated schedule should also include a reference to further issues or projects which will run simultaneously and which would be trackable and if there is any change it can be frozen. It is equally important in an integrated schedule, to ask the teams for the accurate estimations about the time taken by a task to complete it instead of asking them to pay their times. The a project manager, a contingency would be added, which let some slippage for resolution of different problems.

Develop mid-level and comprehensive plans

There are three levels of plans that have to be built for a migration project. The very first is the integrated schedule that defines the project on a weekly basis. Secondly, there should be detailed plan, which is at the level of task-time-resource. Only the experienced project managers are able to work with the detailed plan and interpret them, as it is very difficult to read and understand. It includes development of a Gantt chart with multifaceted dependencies, resource costing, WBS and allowing burn down charts and computation of grossed value. Usually, the detailed plan is utilized by the PMO only.

The third level of the plan is the mid-level plan, which is created at the task-day-team level. The mid-level-plan permits you to elucidate to the project team everyday about their work, that is what work they have to do and when. With the help of the mid-level-plan you are able to squeeze the plan, and the smaller projects will have improved time to value and lower cost.

Have a stakeholder map and communication plan

It is required to decide that who, when and how the communication should take place on a regular basis, as from different places everyone will have an eye on the suite on HANA project. The senior leaders and CIOs frequently require a short update on a weekly basis, which should be readable with one swipe on a smart phone. If the communication with the stakeholders takes place regularly, the probabilities of scattering misinformation and triggering interruption to the project may decrease.

Have a production-sized sandbox and prototype

It will totally depend on the organization, landscape and complexity that how this will going to take place, however, once you have arrived in the chief development system, you will have a change freeze. It is required to prepare this change freeze and to keep it short and this can’t be prepared unless there has earlier completed production-sized migration. In order to carry out this it is required to have a system copy of the production integration environment such as BW or ECC etc. and then we can migrate from the ECC system to HANA. It can be done two to three times by the basis team, before its release to the technical and functional teams so that they can enhance their process. Also, this can carry out early, before purchasing of all the hardware. If this can be done, you can easily validate the sizing so that there is a confidence in you for your bill of material and to perform the other activities like archiving to reduce the hardware requirements.

Consider to some skin in the game from SAP

There is a system called ONE support, which will combine the SAP’s Active, Global Support and Professional Services Organizations i.e PSO. This system can be contracted so that they can be included in the planning and support of the project, irrespective of whether you are of maximum consideration, active entrenched or Enterprise support customer. In general, there is a service catalog available in which contains service for planning and custom code management.Even there are free services for Pre and post go live checks which can booked within six weeks. With the help of SAP architecture, it is easy to size and plan, as this service is a huge bonus and also a good quality of resources are available to carry out this work. Also, there is a HANA Ambassador program which can be accessible in North America, this program delivers a resource which reports into the Global customer Office at SAP. By utilizing this program your project can obtain the required attention.

Join the customer advisory council

A customer advisory council exist for a HANA run by Scott Feldman which meets occasionally. This service is available without any charge for senior IT people and project sponsors , so that they can talk to other customer and can hear about the on-going changes in the ground and obtain some extra confidence.

Make Numerous change, Test Once

There is an excellent tool provided for HANA migration called DMO, which will upgrade, cover and carry out a Unicode conversion and can migrate to HANA in a single step, without touching the source system. This increases the amount of effort in root cause analysis of a problem,however, it gives a single test landscape. If enough testing is not performed in the project, this may lead to a major risk. The test management activity is crucial and has to be revised, that is test automation,strategies ,coverage has to be revised.

Solution Manager is your friend

During HANA migration, the solution manager is your friend. There is a solution manager, web page which contains a lot of useful pages, including the tools for the HANA migration. This involves a Custom Code Management Cockpit i. CDMC which tells about the code that has been customized and will break down, Usage and Procedure Logging i.e. UPL, which specifies that what code is used and the last one is the Clonefinder, which specify about the transactions have been duplicated to custom and how much they are modified. These codes can be utilized in combination with testing and process prioritization by business users.

Carry out enough testing

It is required to have a conversation with the test manager and confirms that you have developed a good test strategy. There are few questions like: Is there any separate phases for unit, integration and performance testing? Is there any tool are used for test automation like HP quality center? How broad is the test coverage? Some kind of effort would be included in custom code recompense. Though HANA is a wonderful database, it is a columnar database some custom code may not run effectively if not written properly. The row-based databases are more lenient as compared to columnar databases.


Thus, these are the few rules which can be followed for migration of SAP HANA and S/4HANA. Moreover, it is required to develop an integrated cutover plan, which is utilized by many teams, it involves all the teams and their activities. In this the plan should be numbered properly, which can be aligned with cutover document.

Updated: Feb 02, 2024
Cite this page

Golden Rules For SAP Suite On Migration Of HANA & S/4HANA. (2024, Feb 09). Retrieved from

Live chat  with support 24/7

👋 Hi! I’m your smart assistant Amy!

Don’t know where to start? Type your requirements and I’ll connect you to an academic expert within 3 minutes.

get help with your assignment