Module 27: BW to BW/4HANA Migration (BW/4HANA 2.0)
Migrating from classic BW to BW/4HANA is not just a technical upgrade —
it is a functional, architectural, and cultural transformation.
This module focuses on execution reality:
- What migration approaches exist
- What must be cleaned
- What breaks
- How to prepare systematically
1. Migration Approaches (Recap + Execution View)
BW to BW/4HANA migration aligns with conversion paths, but with deeper technical focus.
1.1 Migration Approaches Overview
| Approach | Description |
|---|---|
| System Conversion | In-place technical conversion |
| Shell Conversion | System converted, data reloaded |
| Remote Conversion | New BW/4HANA system |
Migration is not redesign by default — unless you choose it.
Migration Approach Selection (Practical View)
Quality of existing BW
Data volume
Downtime tolerance
Redesign appetite
2. Custom Code Adaptation (Critical & Time-Consuming)
2.1 Why Custom Code Breaks
BW/4HANA:
- Removes obsolete tables
- Changes APIs
- Enforces HANA SQL rules
Common Impacted Areas
| Area | Example |
|---|---|
| ABAP routines | SELECT * usage |
| User exits | Obsolete exits |
| Function modules | Deprecated APIs |
| SQL logic | Non-HANA compliant SQL |
Adaptation Strategy
Run SPRO / SUM checks early
Replace SELECT * with explicit fields
Use Open SQL (7.4+ syntax)
3. SPRO Cleanup (Mandatory Before Migration)
3.1 What is SPRO Cleanup?
SPRO cleanup removes:
- Unused configurations
- Obsolete settings
- Legacy extractor definitions
Why SPRO Cleanup is Important
Unclean SPRO = higher migration failure rate.
Key Cleanup Areas
- Source system connections
- Extractor settings
- Old scheduling setups
- Redundant process chains
4. Deprecated Objects (Very Important)
4.1 Objects NOT Supported in BW/4HANA
| Object | Status |
|---|---|
| InfoCubes | ❌ Removed |
| MultiProviders | ❌ Removed |
| 3.x DataFlows | ❌ Removed |
| Transfer Rules | ❌ Removed |
| Update Rules | ❌ Removed |
Replacement Objects
| Legacy Object | BW/4HANA Replacement |
|---|---|
| InfoCube | aDSO |
| MultiProvider | CompositeProvider |
| Transfer Rules | Transformations |
| Update Rules | DTP |
BW/4HANA migration is an object replacement exercise.
5. Migration Checklist (Execution-Oriented)
5.1 Pre-Migration Checklist
Simplification Item Catalog analysis
Custom code scan
SPRO cleanup
Obsolete object inventory
Data volume assessment
5.2 Migration Execution Checklist
- Convert objects
- Activate converted objects
- Fix syntax errors
- Validate data flows
- Adjust process chains
5.3 Post-Migration Checklist
- Functional validation
- Performance benchmarking
- Authorization testing
- Reporting validation
- User sign-off
6. Common Migration Pitfalls
Treating migration as technical upgrade only
Skipping SPRO cleanup
Migrating unused objects
No performance re-baseline
7. BW/4HANA 2.0 vs Classic BW (Migration Reality)
| Area | Classic BW | BW/4HANA |
|---|---|---|
| Object count | High | Reduced |
| Modeling | Cube-centric | aDSO-centric |
| Pushdown | Optional | Mandatory |
| Maintenance | High | Lower (post-cleanup) |
8. Interview-Grade Questions
Q1. Why is SPRO cleanup important before BW/4HANA migration?
Answer: Because obsolete configurations can cause migration failures and increase adaptation effort.
Q2. What is the biggest risk in BW migration?
Answer: Migrating unused or poorly designed legacy objects instead of redesigning or eliminating them.
9. Summary
- Migration is a structured transformation
- Custom code adaptation is critical
- Deprecated objects must be replaced
- Cleanup reduces risk
- Checklists ensure control
10. What's Next?
➡️ Module 28: BW/4HANA Testing, Validation & Cutover
Successful migration is 70% preparation, 30% execution.