Skip to Content

Why SAP S/4 HANA :

By 2020, 5 billion people will enter the middle class and come online, while 50 billion devices will be connected to the Internet of Things, creating a digital network of virtually everything

Data is the new Oil and for enterprise application will have to process huge amount of data in real time, requires business to consume the next generation of Business Suite. R3  is not capable to do such colossal task. Hence moving to SAP S/4 HANA is the real need of business application.


Short quick facts one should consider based on timeline, complexity, system requirements.



S4 HANA Suitable Scenario:

There are more than one way to move your business to SAP S/4 HANA . System conversion or new implementation are usually the most know scenario. Landscape transformation is another way to run business on S/4 HANA. Will try to explain which scenario is best suited for your business.

As per system requirement:

Release type:

If a Business Suite System is on an older release, you have to execute several steps to move to SAP S/4HANA.

You first have to move to SAP ERP 6.0 EHP7 / SAP HANA, adapt to this release, and then move to SAP S/4HANA. In this case, a New Implementation might have advantages because this in-between step is not required.

Can you move to SAP S/4 HANA On Premise edition in one step procedure

System conversion looks better option in this case.

Business Add-on and function Pre-check: If you have identified un-supported add-ons and business function and they are still not available on the roadmap- Such case will postpone S/4 Project to certain point of time and usually independent from transition scenario.

As Per Business Process:

Business process fits to current and future requirement: Performing system conversion is better option. Based on the simplification list approach, the conversion project is guided where things are different in SAP S/4HANA

Business process does not fit to current and require redesign: Complete re-design require performing new implementation. New process based on Best practice content and migrate your application data to new process.


As per custom Code: Custom code need to be identified while planning to migrate to S/4 HANA.

Want to take over custom code: If you business needs to take over existing custom code , then system conversion might have advantages. Using Custom code migration worklist, customer is guided to compile custom code to data structures and scope of S/4 HANA

Want to replace custom code: If S/4 HANA already contains replacement of your custom code as standard S/4 HANA functionality, then you can choose any transition scenario.


As per Timeline:

How fast you want to move to S/4 HANA: If your customer is global and wants all business residing in different countries to be migrated to S/4 HANA, system conversion would be better choice as complete re-design is going to take longer time.

Risk Mitigation: If customer wants to mitigate risk and move only one application to SAP S/4 HANA, then landscape scenario is not the one should be considered. Landscape transformation will be better given choice. Landscape transformation allows you to move your application phase wise like SAP S/4 HANA central finance, SAP S/4 HANA cloud version or SAP S/4 HANA core.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

    1. Naveen Kumar Post author

      Hello Michelle, Moving to SAP S4 HANA is and moving to HANA are different.

      Though moving to Sap S4 HANA include moving to HANA also.  Have performed system conversion and new implementation both. Experience including lots of learning but end of day customer was happy.





Leave a Reply