Module 24: BW/4HANA Transport Management (BW/4HANA 2.0)
Transport management in BW/4HANA is not just about moving objects —
it is about protecting data consistency, system stability, and business timelines.
Poor transport strategy is one of the top causes of production issues in BW projects.
This module covers:
- CTS basics
- Object dependencies
- Transport strategies
- Retrofit handling
- Production issue resolution
1. CTS Basics (Change & Transport System)
1.1 What is CTS?
CTS manages the movement of:
- BW objects
- ABAP objects
- Configuration changes
Across systems:
DEV → QA → PROD
Only design-time objects are transported — data is not.
1.2 BW Objects Under CTS
| Object Type | Transportable |
|---|---|
| InfoObjects | Yes |
| aDSOs | Yes |
| CompositeProviders | Yes |
| BW Queries | Yes |
| Process Chains | Yes |
| Requests / Data | ❌ No |
2. Object Dependencies (Very Important)
2.1 Why Dependencies Matter
BW objects are highly interdependent.
Example:
InfoObject → aDSO → CompositeProvider → BW Query
If dependency order is wrong:
- Activation fails
- Queries dump
- Loads break
2.2 Common Dependency Chains
| Layer | Depends On |
|---|---|
| aDSO | InfoObjects |
| CompositeProvider | aDSOs / Open ODS |
| BW Query | CompositeProvider |
| Process Chain | DTPs / aDSOs |
Transport bottom-up (foundation → consumption).
3. Transport Strategies (Project-Critical)
3.1 Standard Landscape Strategy
DEV → QA → PROD
- DEV: Development
- QA: Testing / Validation
- PROD: Live system
3.2 Transport Bundling Strategy
Why Bundling?
- Ensures consistency
- Reduces missing dependencies
- Simplifies rollback
Bundle related objects together (model + query + chain).
3.3 Decoupled Transport Strategy (Advanced)
Used in:
- Large programs
- Parallel teams
Approach:
- Foundation transports (InfoObjects, aDSOs)
- Reporting transports (Queries)
- Operations transports (Chains)
Requires strict governance.
4. Retrofit Handling (Advanced & Real-World)
4.1 What is Retrofit?
Retrofit means:
- Applying urgent PROD/QA fixes
- Back to DEV branch
- Without losing future developments
Typical Retrofit Scenario
DEV (ongoing work)
QA
PROD ← Urgent fix
Fix must be:
PROD → QA → DEV (retrofit)
Best Practices for Retrofit
Document emergency fixes
Use dedicated retrofit transports
Synchronize branches quickly
Fixing PROD directly without backport
Multiple untracked emergency fixes
5. Production Issue Resolution (Firefighting)
5.1 Common Production Issues
| Issue | Cause |
|---|---|
| Query dumps | Missing dependency |
| Data load failure | Wrong transport order |
| Authorization issues | Missing roles |
| Performance regression | Unoptimized object |
5.2 Resolution Workflow
Detect Issue
↓
Identify Object & Layer
↓
Fix in DEV
↓
Transport to QA
↓
Validate
↓
Transport to PROD
Never fix directly in PROD unless absolutely unavoidable.
6. BW/4HANA vs Classic BW (Transports)
| Area | Classic BW | BW/4HANA |
|---|---|---|
| Object volume | High | Optimized |
| Dependencies | Cubes-heavy | Layered |
| Transport risk | High | Lower (if LSA++) |
| Retrofit complexity | High | Moderate |
7. Transport Best Practices (VERY IMPORTANT)
Transport in correct order
Validate in QA thoroughly
Bundle logically related objects
Keep transport documentation
Don't transport partially activated objects
Don't mix unrelated changes
Don't bypass QA
8. Interview-Grade Questions
Q1. Why do BW transports often fail in PROD?
Answer: Due to missing dependencies, wrong transport sequence, or insufficient QA validation.
Q2. What is retrofit and why is it needed?
Answer: Retrofit ensures emergency production fixes are synchronized back to development without losing future changes.
9. Summary
- CTS manages BW object movement
- Dependencies define transport order
- Strategy matters more than tools
- Retrofit is essential for live systems
- Discipline prevents production incidents
10. What's Next?
➡️ Module 25: Testing, Quality Assurance & Validation
Good transport discipline is invisible success.