Module 22: BW/4HANA Data Integration (BW/4HANA 2.0)
Data integration defines how clean, timely, and scalable your BW/4HANA system will be.
Modern BW integration is ODP-first, selective about replication, and designed for hybrid landscapes.
This module covers:
- SAP S/4HANA integration
- ODP-based extraction
- SLT integration
- External data sources
- Data provisioning strategies
1. SAP S/4HANA Integration (Primary Source)
1.1 Integration Philosophy
BW/4HANA integrates with S/4HANA using:
- Standardized extractors
- CDS-based data models
- ODP framework
S/4HANA is the system of record; BW/4HANA is the system of analytics.
1.2 Integration Options from S/4HANA
| Method | Usage |
|---|---|
| ODP extractors | Default & recommended |
| CDS views | Operational & semantic reuse |
| SLT | Real-time replication |
| File-based | Rare / legacy |
2. ODP-Based Extraction (Strategic Standard)
2.1 What is ODP?
ODP (Operational Data Provisioning) is SAP's unified framework for:
- Data extraction
- Delta handling
- Queue management
2.2 ODP Contexts
| Context | Source |
|---|---|
| SAP | ECC / S/4 standard extractors |
| CDS | CDS-based extraction |
| BW | BW-to-BW |
| SLT | Real-time replication |
ODP is mandatory for future-proof BW/4HANA integration.
2.3 Why ODP Replaced Legacy Extraction
| Aspect | Legacy | ODP |
|---|---|---|
| Delta stability | Medium | High |
| Monitoring | Fragmented | Central |
| Scalability | Limited | Strong |
| Future support | Deprecated | Strategic |
3. SLT Integration (Real-Time Scenarios)
3.1 What is SLT?
SLT (SAP Landscape Transformation):
- Replicates tables in near real-time
- Uses triggers or logging tables
- Replicates to HANA
3.2 Use Cases for SLT
- Real-time reporting
- Operational analytics
- Low-latency dashboards
SLT replicates tables, not business semantics.
3.3 SLT + BW/4HANA Architecture
S/4 Tables
↓ SLT
HANA Tables
↓
Open ODS / aDSO
↓
BW Query
3.4 When NOT to Use SLT
Business logic is complex
Historical snapshots are required
Data volumes are very large
4. External Data Sources
4.1 Types of External Sources
BW/4HANA can integrate:
- Non-SAP databases
- Cloud data (via SDA / SDI)
- Flat files
- APIs (indirectly)
4.2 Integration Techniques
| Technique | Usage |
|---|---|
| Open ODS Views | Virtual access |
| SDA | Federated queries |
| SDI | Data replication |
| File-based | Batch ingestion |
Virtualize first, persist only when required.
5. Data Provisioning Strategies (Very Important)
5.1 Batch Provisioning
Characteristics:
- Scheduled loads
- Stable & scalable
- Default choice for BW
5.2 Near Real-Time Provisioning
Technologies:
- ODP
- SLT
- Event-driven
5.3 Virtual Provisioning
Characteristics:
- Open ODS Views
- No persistence
- Real-time access
5.4 Strategy Selection Matrix
| Requirement | Best Choice |
|---|---|
| Historical analysis | Batch (aDSO) |
| Real-time insight | SLT / ODP |
| External access | Open ODS |
| Large volumes | Persisted aDSO |
| Low latency | Virtual / SLT |
6. Hybrid Integration Architecture (Real Projects)
S/4HANA (ODP + CDS)
↓
Staging aDSO
↓
Harmonized aDSO
↓
CompositeProvider
↓
BW Query / SAC
7. BW/4HANA vs Classic BW (Integration)
| Area | Classic BW | BW/4HANA |
|---|---|---|
| Extraction | LO / Custom | ODP-first |
| Real-time | Limited | Strong |
| External data | Batch-heavy | Virtual + Hybrid |
| Scalability | Moderate | High |
8. Common Integration Mistakes
Ignoring ODP
Using SLT everywhere
Over-persisting external data
Mixing extraction strategies randomly
9. Interview-Grade Questions
Q1. Why is ODP preferred in BW/4HANA?
Answer: ODP provides a unified, stable, and scalable extraction and delta framework, making BW/4HANA integration future-proof.
Q2. When should SLT be used?
Answer: When near real-time data replication is required and business semantics can be applied downstream.
10. Summary
- ODP is the integration backbone
- S/4HANA is the primary source
- SLT enables real-time replication
- External data can be virtualized
- Strategy depends on latency, volume, and semantics
11. What's Next?
➡️ Module 23: Security, Auditing & Compliance in BW/4HANA
Good integration design prevents 90% of downstream issues.