BW/4HANA
BW/4HANA is SAP's next-generation data warehouse product built natively on SAP HANA, replacing classic BW's layered InfoProvider model with simplified objects like Advanced DataStore Objects (ADSOs) and Open ODS Views. This topic covers its architecture, business rationale, modeling simplifications, migration paths from BW-on-HANA/classic BW, and operational differences across on-premise and cloud-adjacent scenarios such as embedded analytics in S/4HANA.
Overview
BW/4HANA is SAP's next-generation data warehouse product built natively on SAP HANA, replacing classic BW's layered InfoProvider model with simplified objects like Advanced DataStore Objects (ADSOs) and Open ODS Views. This topic covers its architecture, business rationale, modeling simplifications, migration paths from BW-on-HANA/classic BW, and operational differences across on-premise and cloud-adjacent scenarios such as embedded analytics in S/4HANA.
Lessons in this topic
- SAP BW/4HANA Tutorial (Part 1)An introduction to BW/4HANA's purpose, its simplified architecture compared to classic BW, and the core objects consultants encounter on day one.
- What BW/4HANA Is and Why Organizations Migrate to It (Part 2)An introduction to BW/4HANA's purpose, simplified architecture, and the business drivers pushing organizations to move from classic BW to this HANA-native data warehouse.
- Modeling with ADSOs, CompositeProviders, and Open ODS Views in BW/4HANA (Part 3)A practical look at how to design a BW/4HANA data model using ADSOs for staging and storage, CompositeProviders for reporting-time combination, and Open ODS Views for virtual access, including transformation and DTP considerations.
- Planning a BW/4HANA Conversion: In-Place vs Remote Conversion and Object Simplification (Part 4)Understand the two primary conversion approaches to BW/4HANA, how classic BW objects map to simplified BW/4HANA objects, and the practical steps and risks involved in planning a conversion project.
- Modeling with ADSOs, Open ODS Views and CompositeProviders in BW/4HANA (Part 5)A practical look at how to design data models in BW/4HANA using Advanced DataStore Objects, Open ODS Views, and CompositeProviders, including layer design and conversion considerations from classic BW.
- BW/4HANA Transfer Toolset: Conversion Paths and Object Readiness (Part 6)How the BW4HANA Transfer Toolset (also called BW4HANA Starter/Transfer Cockpit in SAP guidance) assesses, converts, and migrates classic BW objects to BW/4HANA-compatible equivalents, and what a consultant must plan before running conversion.
- Advanced BW/4HANA: Architecture, Integration and Production Design (Part 7)Advanced capstone for BW/4HANA, connecting the existing lesson areas: Why BW/4HANA Exists and How It Differs from Classic BW; Modeling with ADSOs, CompositeProviders, and Open ODS Views in BW/4HANA; Planning a BW/4HANA Conversion: In-Place vs Remote Conversion and Object Simplification; What BW/4HANA Is and Why Organizations Migrate to It; Modeling with ADSOs, Open ODS Views and CompositeProviders in BW/4HANA; BW/4HANA Transfer Toolset: Conversion Paths and Object Readiness. The goal is to move from feature knowledge to architecture, integration, production support and governance decisions.
Interview questions covered
- What are the core concepts of BW/4HANA, and how would you explain them clearly in an SAP interview?
- How would you apply BW/4HANA in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in BW/4HANA. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in BW/4HANA?
- Suppose you inherit an existing BW/4HANA solution. How would you review it before making a change?
- A senior architect is reviewing BW/4HANA. The project situation is: A retail company running classic BW-on-HANA for ten years has accumulated dozens of InfoCubes and classic DSOs feeding overlapping MultiProviders for sales reporting. What design changes, validation evidence and production controls would you require before approving the solution?
- A project encounters this situation while working on Planning a BW/4HANA Conversion: In-Place vs Remote Conversion and Object Simplification: A retail customer running classic BW 7. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- A project encounters this situation while working on Modeling with ADSOs, CompositeProviders, and Open ODS Views in BW/4HANA: A manufacturing client needs a BW/4HANA model to report on production orders sourced from an S/4HANA system. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- Using this SAP project situation — A retail company running classic BW-on-HANA for ten years has accumulated dozens of InfoCubes and classic DSOs feeding overlapping MultiProviders for sales reporting — explain Why BW/4HANA Exists and How It Differs from Classic BW. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- A project encounters this situation while working on BW/4HANA Transfer Toolset: Conversion Paths and Object Readiness: A retail company running BW 7. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- Using this SAP project situation — A retail company running classic BW 7 — explain What BW/4HANA Is and Why Organizations Migrate to It. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- A project encounters this situation while working on Modeling with ADSOs, Open ODS Views and CompositeProviders in BW/4HANA: During a migration project, a classic InfoSet joining a sales DSO with a customer master DSO is converted into a CompositeProvider. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.