You need to upgrade to S/4HANA…

A ten-year journey from legacy environment to Standard S/4HANA

But you have complex SAP enhancements that manage critical processes.

Don’t worry, its very common. And there is a path!

I spent over ten years at an Oil & Gas Major and supported them through their entire SAP journey, from initial implementation to a successful S/4HANA upgrade.

The first SAP implementation followed a common path - build complex custom processes to reflect how the business ran pre-SAP.

This resulted in hundreds of thousands of lines of custom ABAP code, and incredibly complex business processes that users found very hard to learn and retain.

We had to build sophisticated web applications to front-end SAP and keep our users out of the GUI.

Then we doubled in size overnight after the acquisition of a major competitor. Fortunately our web applications allowed us to onboard thousands of new users and get them following our business processes thanks to integrations to a second SAP environment.

The decision was taken to upgrade to a single S/4HANA environment with the ambitious goal of eliminating the hundreds of thousands of lines of custom code.

So we had to engineer-out the custom code without losing business process capability. We did this by transferring the complexity to our software partners who are much better suited to manage and support this.

Now we have an S/4HANA environment that is ready for cloud, AI and whatever else the future holds.

You are not alone. There is a process.

Take an inventory of your most complex custom processes and ask yourself if they can be standardized or passed to a software partner to maintain.

Then find an experienced system integration partner to help you with you project and maintenance process and data migration.

Xytalis has worked with many companies that have complex legacy project and maintenance processes, and coordinating the migration of these solutions from custom code to partner enabled integration.

Go to xytalis.com/consult and request a free one hour call today!

Previous
Previous

Orphaned Project Materials: A Persistent Challenge in Every S/4H Upgrade

Next
Next

Connecting STO to SAP? Here are the must-have integrations