Most S/4HANA programmes that run late do not fail in the build phase. They slip because a handful of decisions were left open too long. Here are the seven we ask clients to settle early.
1. Greenfield, brownfield or selective
A greenfield implementation lets you redesign processes on standard SAP. A brownfield conversion keeps your current configuration and history. A selective transition moves chosen company codes or data. The right path depends on how much of your current process you still trust.
2. Cloud or on-premise
RISE with SAP, a private cloud or your own data centre each change who manages upgrades, infrastructure and cost. Decide this before you size the project team.
3. Data scope
How many years of history do you really need? Migrating less data reduces risk and cutover time. Archive the rest where it can still be audited.
4. Custom code
Run a custom code analysis early. Many old enhancements are no longer used, and others are replaced by standard S/4HANA features.
5. Fit-to-standard
Hold fit-to-standard workshops before writing specifications. Every gap you close with standard functionality saves build and testing effort later.
6. Integration landscape
List every interface to banks, tax portals, warehouses and other systems. Decide which will move to SAP Integration Suite or another middleware platform.
7. Team and support model
Decide which roles your own team will own and where you need specialist consultants, for implementation and for hypercare after go-live.
How Vinlak helps
Our consultants support S/4HANA programmes across finance, supply chain and technical workstreams, either as a dedicated project team or as specialists who join your existing team.