Executive summary
A manufacturing company running SAP ECC 6.0 faced growing operational risk because its database platform and server hardware had reached end of life. Candent moved the SAP landscape to SAP HANA on modern, SAP-certified infrastructure, removing the support risk, improving performance and laying the foundation for a future move to SAP S/4HANA.
Customer background
- Industry: manufacturing.
- More than 1,500 SAP users.
- Landscape: SAP ECC 6.0, SAP BW and SAP Solution Manager on Oracle Database 11g, running on physical servers.
Business challenge
- Database end of life. Oracle 11g support had ended, security patches were no longer available, audit and compliance concerns were growing and maintenance costs were rising.
- Hardware end of life. Servers were more than seven years old, vendor support contracts had expired and hardware and storage failures were frequent, with a real risk of a long outage.
- Performance. Month-end processing took 8 to 10 hours, batch jobs overran their windows and BW reports were getting slower.
- Strategy. The company wanted a platform ready for SAP S/4HANA, with a smaller infrastructure footprint and lower running costs.
Objectives
| Objective | Target |
|---|
| Remove end-of-life hardware risk | 100% |
| Upgrade the database platform | Supported, current platform |
| Improve performance | At least 30% |
| Prepare for SAP S/4HANA | Yes |
Solution
| Layer | Before | After |
|---|
| Database | Oracle Database 11g | SAP HANA |
| Servers | Physical servers, 7+ years old | SAP-certified servers on virtualised infrastructure |
| Storage | Legacy SAN | All-flash storage |
| Operating system | Legacy | SUSE Linux |
| Resilience | Single servers | High availability configuration |
Approach
- Assessment: SAP Quick Sizer review, hardware sizing validation, database growth analysis and custom code assessment, with workload analysis from ST03N and EarlyWatch reports.
- Preparation: new servers provisioned, SUSE Linux installed, the SAP target landscape built and backups validated.
- Migration: export and import with SAP Software Provisioning Manager (SWPM), database and application migration, and interface validation.
- Testing: functional, performance, user acceptance and disaster recovery testing.
- Cutover: final data synchronisation, production migration over one weekend, then hypercare.
Timeline
| Activity | Duration |
|---|
| Assessment and planning | 3 weeks |
| Infrastructure build | 4 weeks |
| SAP migration testing | 6 weeks |
| User acceptance and performance testing | 3 weeks |
| Production cutover | 1 weekend |
| Hypercare | 2 weeks |
Risks and how they were managed
| Risk | Mitigation |
|---|
| Data loss | Multiple backup validation cycles |
| Extended downtime | Mock cutovers and rehearsals |
| Performance issues | Benchmark and load testing |
| Interface failures | End-to-end integration testing, including PI/PO, EDI and third-party applications |
| User acceptance | Early business involvement |
Results
| Measure | Before | After |
|---|
| SAP response time | 3.5 seconds | 2.0 seconds (about 40% faster) |
| Batch processing duration | Baseline | 60% shorter |
| Database backup | 6 hours | 2 hours |
| Availability | 98.5% | 99.9% |
| Storage utilisation | Baseline | 35% better |
| Infrastructure support cost | Baseline | About 25% lower per year |
| Vendor support | Expired | Fully supported |
Month-end closing and reporting are faster, infrastructure-related incidents have fallen and the security and compliance position has improved.
Lessons learned
- Run at least two mock migrations before the production cutover.
- Validate every SAP interface (PI/PO, EDI and third-party applications) early.
- Base sizing on real workload data from ST03N and EarlyWatch reports.
- Involve business users in user acceptance testing to avoid issues after go-live.
- Align the migration architecture with the long-term SAP S/4HANA roadmap.
Delivery
About four months from assessment to the end of hypercare, with production moved over a single weekend.