Getting Ready for S/4HANA

Moving to S/4HANA may seem intimidating and, therefore, quickly leads to procrastination in making strategic decisions.

The fundamental choice you have to make:

1. Transition to standard SAP (“Clean Core“) or
2. Like-for-like move and keep all the custom developments (“Lift and Shift“)?

Both choices have pros and cons.

What if you can apply the best of both worlds, combining “Clean Core” with “Lift and Shift”?

It is an option hardly discussed but very feasible. Read on to find out why.

Why Fixes Cause Trouble

SAP systems can get messy. Companies add special fixes to make things work. These “Z-programs” become key. This makes moving to S/4HANA scary. Leaders fear messing things up.

But, these fixes can cause issues.

• Hard to Fix: Custom code needs work all the time.
• Stops Updates: Custom code can stop SAP from updating.
• Slows New Ideas: Time spent on old code can’t be used for new tech.

The problem is not the fixes. It is how they are used and documented. Often, we forget why we made the fix. Many users even think that a custom solution is standard SAP!

SAP adds new functionality that makes old fixes not needed. They often get ignored because companies have spent so much money on the custom solution. They do not want to lose the investment by moving to standard. However, keeping a custom solution alive can be more expensive and less stable.

Before we start the S/4HANA work, we must look at these fixes. Ask the IT support team which custom solution puts the biggest burden on their resources. Ask the business users which custom solutions are the least stable. Find the documentation for these solutions. You quickly get an idea of the magnitude of the issue at hand.

Paving the Clean Core Pathway

The Clean Core Pathway starts with small tasks. These are not big jobs. You can already apply them to your ECC system today.

Here is how to do it:

1. Find Key Areas: Pick fixes that cause many tickets or stop updates.
2. Make Small Teams: Use IT staff and key users. Get tech skills and process smarts.
3. Set Clear Goals: Know what the fix does. See if SAP can do the same.
4. Test in a Safe Place: Try SAP in a test system. Find problems early.
5. Write Down What You Find: Report on if it fits, what’s missing, and what needs to change.

Using SAP’s Biggest Secret

Many custom fixes use rules in the code. These rules say how the system acts. Finding these rules can become impossible to understand. Replacing these rules can be tricky. Many companies do not dare to touch it, like not disrupting the dust. It keeps you hostage in your own system.

This is where the Business Rule Framework (BRF+) can offer a way out.

BRF+ moves rules from code to configuration.

• Easy to Change: Users can change rules without coding.
• Easy to See: Rules are clear and easy to get.
• Easy to Move: Rules can be transported from ECC to S/4HANA.

The Business Rule Framework is available in your ECC and S/4HANA standard licence. So it is FREE!

BRF+ can become a bridge. It lets you use custom fixes on ECC. It gets ready for Clean Core in S/4HANA. You can “lift and shift” BRF+ rules to S/4HANA. Over time, SAP may add better stuff, and you can stop using these BRF+ rules.

The key takeaway is to start today by converting custom code into business rules.

Good Things in ECC

The Clean Core Pathway helps more than S/4HANA. It helps the SAP ECC system, too. By finding and replacing fixes, you cut IT costs. You make the system work better. You make jobs easier. For example, BRF+ lets users control rules, not IT. These small wins make the S/4HANA move easier. They show leaders why it is good.

What If They Say No?

Some leaders may not like the Clean Core Pathway. They think it costs too much. We must answer these fears.

• “Why fix it if it works?” Explain that fixes cause tech debt. This debt slows progress.
• “We have no time.” Do small tasks. Show how they help both systems.
• “Users won’t change.” Show the plan to help users. Show they are involved.

The key takeaway is the decision of whether to keep on adding custom code in SAP ECC with a low ROI or replace them with business rules, and you have this BRF+ configuration moved to S/4HANA to establish a high ROI.

A Plan for S/4HANA

The Clean Core Pathway is done step by step, using BRF+ when you cannot replace a custom development with a standard SAP solution.

Each step helps the next:

1. Check: Ask IT, check reports, and find fixes that cause problems.
2. Small Tasks: Make teams, test SAP, and write down what you find.
3. BRF+: Move rules from code to settings.
4. Help Users: Get users involved, say why it’s good, train them, and give help.
5. S/4HANA: Move to S/4HANA using SAP’s method. Focus on Clean Core rules.

This plan is not set in stone. It can change to fit your needs. Start early, stay focused, and think about business goals.

AI and Clean Core

The Clean Core Pathway gets ready for new tech. AI, learning machines, and robots are changing work. These need good data and easy jobs. A Clean Core helps. By cutting tech debt and making jobs easy, you get your SAP system ready for what’s next.

How Clean Core Fits with the Fast Implementation Track

The Fast Implementation Track (F.I.T.) speeds up S/4HANA projects. The Clean Core Pathway methodology is fully integrated into this FIT methodology.

• Faster Moves: Converting custom code into BRF+ configuration accelerates your S/4HANA deployment.
• Less Fixes: Moving to standard S/4HANA means less burden on your IT support after deployment.
• AI Ready: A Clean Core S/4HANA is the best basis for implementing AI solutions for your business.

Make the Fast Implementation Track Your Purpose. See the comment below to ready more about the Fast Implementation Track.

Conclusion

The Clean Core Pathway helps you move to S/4HANA. It cuts risks and makes things better. It is not just about cleaning code. It is about setting the stage for what’s next.