3 Keys To Unlock Your HANA Upgrade

50% of SAP HANA early adapters are migrating to Suite on HANA (SOH)? What are the keys to unlock the upgrade path to your HANA migration?

At SAP TechEd 2016, HANA took center stage. What is the first thing you need to do? What version of ABAP Application Server is required? What about a dual stack environment? One of the best-attended workshops provided these answers and more.

There is a ton of information to consider and multiple paths to follow. In this article, we will focus on the upgrade of ECC to HANA. In later posts, we will focus on Analytics, side-car, and migration to S/4 HANA.

Suite on HANA (SOH) means that you are upgrading from your current DB to the HANA DB. Your core ECC processes, GUI, custom code, and interfaces remain the same.

The keys to unlock your migration path are:

  • General Requisites and Checks;
  • Infrastructure Choices and Sizing;
  • Custom Development and 3rd Party Applications.

All of our customers are long-standing SAP customers. We offer our advice from this perspective, but the information is relevant for new SAP customers as well.

General Requisites and Checks:
The starting point, where are you today; SAP version and EHP release, add-ons, Unicode, support pack, OS/DB and data sizing? We can assist you with this or you can refer to SAP’s OSS Notes packages to guide you through the process steps.

Once you’ve confirmed your starting point, the migration options and tools become clear.

Quick Tips:

  • HANA is dependent upon Unicode. You need to be on Unicode to be on HANA. If you are not Unicode compliant, you must first update your applications to Unicode.
  • Check your add-ons and 3rd party applications to verify if they are HANA certified.

If you are not on Unicode, SAP offers the classic migration path where you first upgrade to Unicode and then perform the HANA migration steps.

Most of our clients that are considering SOH have upgraded to Unicode and are able to perform a one-step migration path.

Infrastructure Choices and Sizing:
The next step is to capture data sizing and decide on the landscape. Many of our clients take this opportunity to decide if the cloud better supports their IT and business objectives.

HANA runs on a variety of platforms including HANA Cloud – public and private. We see a split with larger companies preferring to stay with on-premise for core ERP. Our smaller clients tend to lean more toward a private or hybrid cloud.

Control and security are consistently the main drivers behind this decision.

Data sizing is critical to your migration path. The goal is to trim down the data size. Minimizing and optimizing the data size of your systems is healthy for your path forward. Also, the data volume plays a key role in the outage window.

Reducing your data footprint will improve your processing times. Take this opportunity to assess what data is needed. We recommend the following:

  • Use the Data Volume Management (DVM) tool in Solution Manager.
  • Data Avoidance – consider switching off the creation of specific data.
  • Delete – delete unused or obsolete data.
  • Archive – archive obsolete or irrelevant data.

Quick Tip:

  • Solution Manager – SAP is leveraging Solution Manager for many additional tasks for HANA. We have found that many customers may lack the knowledge or capabilities in SolMan.

Custom Development and 3rd Party Applications:
In our September 2016 newsletter, the 2nd Feature Article titled “An Inconvenient Truth: Migrating to S/4 HANA – Moving Custom Objects to S/4 HANA” goes into detail on how to migrate custom objects to HANA.

The primary takeaway for the migration to HANA, SAP is not supporting the dual-stack. Before migrating, plan on separating the JAVA stack into separate stacks offered by the Software Provisioning Manager. As of SAP NetWeaver 7.5, there are no exceptions to this approach.

As an additional planning step, consider analyzing with runtime tools: long running transactions, reports, and enhancements for performance optimization. Where feasible, condense or re-engineer the code to accommodate the HANA migration.

For a SOH migration from core ECC, the table structures are the same and code changes are not a requirement.

Custom code adaption is required if you are migrating to S/4 HANA. This is due to the simplified S/4 HANA data model.

The 2017 budget cycles are upon us and many of our clients are asking us for guidance and direction on how to get onboard the HANA train. Titan Consulting is here to advise and guide you on the right migration path to take advantage of HANA and S/4 HANA. Contact David Geaslen at 832.422.3251, or david@titanconsulting.net or your Titan Sales Director.