Skip to Content

SAP S/4 HANA Migration best practice

Mar 10, 2017 at 06:01 AM


avatar image

Dear All,

We have some query regarding S/4 HANA migration option,please clear up with our doubts,please find below for the que.

que.1.:-Which is the best way for migration? option 1.New implementation option.2.System conversion option 3.Landscape transformation

Que.2.Which is the best way for migration of production system with minimal downtime?

option.1.New implementation option.2.System conversion option.3.Landscape transformation

Que.3.One scenario i am working on it but struck at one point:- Here you go about the scenario below:-

We have on ERP system with hardware configuration of 64 Gb RAM 1 TB hard disk,We need that system to get convert for the SAP S/4 HANA in place.As per my knowledge S/4 HANA have different hardware configuration of minimal 0f 128 GB RAM,so i think the current hardware it wont suit for system conversion. So how i have to proceed further i know system conversion using sum and DMO and other procedure,but using this tool i cant do in same hardware because S/4 HANA needs high level hardware.So my concern how i have to proceed further , and what are the steps to follow for the system conversion.



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Michael Hu Apr 27, 2017 at 03:34 AM

Hi Sanjeev,

I'd like to share some information about the ERP 6.0 to S/4HANA OP migration project.

It's very hard to answer your first two questions, because it all depends on the situation, for example, if the customer have already did huge modification or development tasks of the existing ERP system, then the system conversion might not be a good idea, cause you'll have to spend a lot of time to do the customer code check and migration preparation, plus, lots of system configuration may have to be redone. And sometimes not all source ERP system are suited for system conversion. In this case a new implementation with business data migration may be a better choice, the same applies to landscape transformation, it all depends on system and business complexity.

Regarding system downtime, as a normal system conversion, it may take few days for the final production system migration (not including sandbox testing, DEV, QAS etc), depends on the existing system database size and hardware, also the target platform hardware and HANA size. For new implementation of landscape transformation, you can just install the new S/4HANA system and there'll be minimum system downtime for that part, but your team have to spend a lot of time to do the data migration work, although the final cut over downtime is less compare to system conversion, but it certainly requires more work hour and human resources.

Now for the last question, if you're going to using S/4HANA, you'll have to using HANA DB, typically the vendor will help to install and configure the HANA appliance after you've made the purchase, so your target database won't running on the existing hardware, you can still run the SAP application server on the existing hardware if it's supported, you can check that in PAM. But I'd say 128GB RAM for HANA is very small, I don't think S/4 supports running on such a small HANA appliance, I would suggest at least go with 256GB.

The basic procedure for system conversion would be like this:

1. Install the HANA DB

2. Check / Upgrade source platform OS or hardware, sometimes a system migration to new hardware or OS might be required

3. Using Maintenance Planner to generate the relevant support package and xml file, you'll also need Solution Manager and some required notes applied, the source system must be configured as managed system in Solution Manager, and the RFC connection (at least read RFC) should be working. Notice not all system are suited for the system conversion, like if you've some third party add-ons, some unsupported component install in the source system.

4. Schedule the time and resource for Sandbox migration task using SUM, so you can get a better idea and get your self familiar with the migration tasks, which will involve pre-migration check, apply few notes and run some report to check the configuration on source system. You'll have to configure/adjust the CVI, MRP, and some FI related tasks.

5. Start the actual system conversion in Sandbox, you'll spend a lot of time with SUM, some task may take hours or days, this's also the time you may encounter lots of errors, if you have the time and resource, you may do this twice, one for DEV system, and one for PRD system, but our main gold is focusing on PRD system.

6. Now you can schedule and start the actual system conversion, simply put from DEV, QAS, to PRD, but there'll also be a lot of team work, like schedule the code freeze time, dealing with the urgent change, dictionary objects modification etc.



Show 1 Share
10 |10000 characters needed characters left characters exceeded

Dear Michael.

Thank you for your valuable suggestion.Above answer is very helpful to me regarding S/4 Hana to get through with the things.

So can i decide with final step to go for new implementation method than system conversion.

or else we can go for side by side conversion.

Do you have any idea about side by side conversion.