S/4HANA Implementation: What Actually Happens#
Implementing SAP S/4HANA is one of the most complex technology projects an organisation can undertake. This guide walks through what actually happens during implementation—from preparation through go-live and beyond.
---
Phase 1: Preparation (2-4 Months)#
Project Setup#
Governance establishment: - Executive steering committee formation - Project team assembly (internal + partner) - Decision rights documentation - Communication plan
Technical setup: - Development environment provisioning - Access management setup - Integration landscape planning - Security framework establishment
Requirements Gathering#
What this really means: - Documenting current processes (as-is) - Defining target processes (to-be) - Identifying gaps between standard SAP and requirements - Prioritising requirements (must-have vs. nice-to-have)
Common mistakes: - Documenting what systems do, not what business needs - Missing edge cases and exception processes - Underestimating reporting requirements - Ignoring integration requirements
Fit-Gap Analysis#
Comparing requirements against standard SAP functionality:
Fit: Standard SAP meets requirement.
Gap - Configuration: Can be addressed through SAP configuration.
Gap - Development: Requires custom code (ABAP, Fiori).
Gap - Process Change: Requirement may need to change to fit SAP.
Gap - Third-Party: External solution needed.
---
Phase 2: Realisation (6-12 Months)#
Configuration#
Foundation: - Organisational structure (company codes, plants, sales orgs) - Master data setup (customers, vendors, materials) - Financial configuration (GL, AP, AR, AA) - Control configuration (controlling, profit centres)
Functional: - Sales and distribution - Materials management - Production planning - Quality management
Technical: - Authorisations and roles - Output management - Workflow configuration - Integration setup
Development#
When development is needed: - Custom reports and interfaces - Enhancements to standard transactions - Fiori applications for custom processes - Integration components
Development principles: - Minimise custom code - Use SAP extension points - Document everything - Plan for upgrade compatibility
Data Migration Preparation#
Migration object identification: - What data must migrate? - What historical data is needed? - What data can be archived?
Data cleansing: - Master data deduplication - Reference data standardisation - Historical data quality assessment
Migration tooling: - SAP Data Services - LTMC (Legacy Transfer Migration Cockpit) - Custom extraction programs
---
Phase 3: Testing (3-4 Months)#
Unit Testing#
Testing individual transactions and processes.
Conducted by: Functional consultants.
Focus: Does each transaction work correctly?
Integration Testing#
Testing end-to-end business processes across modules.
Conducted by: Business users with consultant support.
Focus: Do processes work across organisational boundaries?
Example: Order-to-cash: Sales order → Delivery → Invoice → Payment → GL posting
User Acceptance Testing (UAT)#
Business validation of configured system.
Conducted by: Business users.
Focus: Does the system meet business requirements?
Critical success factor: Realistic test scenarios with actual business data.
Performance Testing#
System performance under expected load.
Conducted by: Technical team.
Focus: Response times, batch processing duration, concurrent user capacity.
Regression Testing#
After fixes or changes, ensure nothing else broke.
Automation: Consider test automation for regression scenarios.
---
Phase 4: Final Preparation (2-3 Months)#
Training#
End-user training: - Role-based training programs - Transaction-level instruction - Scenario-based exercises - Quick reference guides
Super-user training: - Deeper system knowledge - Troubleshooting capability - Training delivery capability
Cutover Planning#
Cutover activities: - Final data migration schedule - Master data freeze timing - Legacy system shutdown plan - SAP system availability schedule - Contingency plan if cutover fails
Rehearsal: - Execute cutover in test environment - Measure actual timing - Identify bottlenecks - Refine plan
Go-Live Preparation#
Technical readiness: - Production system ready - Infrastructure capacity confirmed - Integration connections tested - Monitoring in place
Organisational readiness: - Users trained - Support team ready - Communication sent - Escalation paths clear
---
Phase 5: Go-Live and Stabilisation (2-3 Months)#
Go-Live Execution#
Day 1: - System goes live - Support team available - Escalation paths active - Issue tracking rigorous
Week 1: - Hypercare support - Rapid issue resolution - Daily stakeholder calls - Usage monitoring
Stabilisation Period#
Weeks 2-4: - Transition from hypercare to normal support - Issue volume tracking - Performance monitoring - Training reinforcement
Months 2-3: - Process optimisation - Report refinement - Enhancement requests prioritised - Lessons learned documentation
---
Common Implementation Failures#
Scope Creep#
What happens: Requirements expand during implementation.
Why: Poor initial requirements gathering, stakeholder pressure, "while we're at it" thinking.
Prevention: Rigorous change control, strong governance, clear scope documentation.
Data Migration Problems#
What happens: Data doesn't migrate correctly, causing post-go-live issues.
Why: Underestimated data quality issues, insufficient testing, compressed timelines.
Prevention: Early data assessment, thorough cleansing, extensive migration testing.
Inadequate Testing#
What happens: Issues appear in production that should have been caught in testing.
Why: Compressed testing timeline, inadequate test coverage, limited business involvement.
Prevention: Protected testing timeline, comprehensive test scenarios, business accountability for sign-off.
Change Management Failure#
What happens: Users resist new system, work around it, or simply don't use it.
Why: Insufficient communication, inadequate training, lack of user involvement.
Prevention: Comprehensive change management programme, user involvement throughout, visible executive support.
---
ANZ-Specific Considerations#
Partner Availability#
Limited local partner resources mean: - Book partner resources early - Have backup plans for key roles - Build internal capability
Time Zone Challenges#
Global SAP resources may operate in different time zones: - Plan communication windows - Consider follow-the-sun support models - Document handoffs carefully
Integration Complexity#
ANZ-specific integrations (banking, government) may require: - Custom development - Local middleware - Extended testing
---
Monday Morning Action Plan#
If you're starting S/4HANA implementation:
- Document Your Current Processes: Before consultants arrive, document what you actually do—not what documentation says you do.
- Identify Your Non-Negotiables: What requirements cannot change? These drive customisation decisions.
- Assess Your Data: How good is your master data? How much historical data must migrate?
- Assemble Your Team: Who internally will work on this project? Do they have time?
- Establish Governance: Who makes decisions when conflicts arise? How quickly can they decide?
---
Conclusion: Implementation Is a Marathon#
S/4HANA implementation is not a sprint—it's a marathon requiring sustained commitment, realistic planning, and disciplined execution. The organisations that succeed are those that prepare thoroughly, execute rigorously, and adapt thoughtfully when challenges arise.