Three weeks after the IT go-live, the cyberattack hit.
At that point, the system was technically live — but functionally unusable. The logistics modules in SAP S/4HANA were installed, yet there had been no real testing, no structured training, no proper ERP or EDI usage.
The old system was gone. And 13,000 materials were being managed manually. Every day was escalation day. Shipments were reprioritized hour by hour. Customers were calling constantly. OEM lines were stopping. Inside the plant, planners were downloading demand manually, retyping data, double-checking stock that no one fully trusted.
It wasn’t a system problem anymore — it was a business survival problem.
Our mandate was clear: make SAP work — functionally — and do it fast.
First: Create Transparency, Not More Activity.
Before touching configuration, we needed clarity. We mapped backlog, customer call-offs, shipment priorities, and master data gaps. It became obvious that the system wasn’t failing — the foundation was.
Master data was inconsistent. MRP couldn’t run reliably. Inventory accuracy was questionable. And the organization was greenfield — no one had ever used SAP before.
So we rebuilt from the ground up.
Fix the Basics So the System Can Think.
We validated and corrected material masters, BOMs, routings, MRP parameters, and warehouse data. Only once the basics were stable did we structure work packages across MM, PP, SD, EWM, TM, PM and QM.
No big bang. No theory workshops.
Step-by-step functional readiness. At the same time, we introduced cycle counting immediately. There’s no point running MRP if your stock data is fiction. That single move reduced risk dramatically and created the trust planners needed to rely on the system.
Eliminate Manual Work — Fast.
The real breakthrough came when we reactivated automated EDI. Customer demand and ASN confirmations were no longer handled manually. Within eight weeks, demand flowed directly into SAP again.
The noise dropped instantly.
MRP started running with less than ±2% deviation on both FG and WIP levels. Training was completed in 7.5 weeks — not in a classroom, but in real daily scenarios. People stopped fearing the system and started using it.
Three Months Later:
- Full functional implementation completed
- Automated EDI restored
- Reliable inventory through cycle counting
- 50% overtime reduction in indirect areas
- Headcount reduction in planning
- No more OEM line stops
What started as chaos became structured execution.
This experience reinforced something I strongly believe: installing SAP is not implementing SAP. Technology doesn’t stabilize operations — disciplined processes and trained people do.