Tips on how to get a Hana doing off a ground

The problem for SAP business is that determining either and how to pierce to S/4 Hana is by no means easy. Sebastian Grady, boss of eccentric support dilettante Rimini Street, that supports program from SAP, Oracle and a series of other suppliers, says: “This is not as elementary as flicking a switch – it can be a really dear re-implementation, rather than a elementary upgrade. SAP’s stream flagship product set, built over 40 years ago, has 400 million lines of code. Customers have millions invested in endless customisations that might have to be rewritten in a pierce to S/4 Hana.

“Frankly, we don’t know how organisations can make a essential calculation about a cost or lapse on investment since they do not have all of a information they need. And because would a patron take on a risk of an unproven complement that is expected to be in growth for many years?”

Others, though, trust a ongoing digital mutation of business creates a contingent pierce to S/4 Hana unavoidable for many SAP stalwarts. Robin Webster, executive of record during Centiq, that provides managed services for SAP Hana, says: “SAP is really penetrating to get people onto a platform. It’s a bit early in a cycle for many organisations – subsequent year should be engaging – though it is going to happen.

“There was always going to be a need to redesign how SAP works underneath a covers to take advantage of a full capabilities of Hana. SAP talks a lot about simplification, though that simplification is contingent on S/4. For many customers, it’s only a doubt of when to pierce – and that will be when a business functionality in S/4 is so distant modernized that businesses confirm they can’t do though these new tools.”

Hillarys’ Bond says it is vicious to plan any pierce early. “When we done a switch, it was a large architectural change,” he says. “We used to run HP-UX, though for Hana, we indispensable Linux, so we changed to SuSe. That concerned retraining all a in-house staff. We even migrated some of a non-SAP systems opposite to give us a bit of knowledge using prolongation systems in that environment. Hana also assumes we will be operative in a virtualised world, so we had to get adult to speed with that virtualisation layer.”

Picking a right partner for a pierce is also vital. “We used Panaya,” says Bond, “whose collection were means to analyse all a tradition formula to discern how most would need to be rewritten, that sped adult doing considerably.”

Hana also requires a opposite proceed to normal relational databases, says Bond. “When we pierce to a column/in-memory database, we need to retrain. Rules that had served me good for 30 years are no longer appropriate. For example, Hana archiving is really different. As a database is already dense in memory, archiving doesn’t make it smaller and can indeed make it bigger,” he says.

Lewis Marston, CEO during SAP supply sequence and digital mutation dilettante Rocket Consulting, recommends that organisations take a holistic perspective of their focus landscape and roadmap so that a vital preference can be done with fixing to a SAP focus roadmap. “A clearly tangible information plan is a contingency before relocating to S/4 Hana,” he says. “Data though value will, even with a high storage application that is accessible in Hana, expostulate adult infrastructure costs significantly.”