In Migrating to SAP BW/4HANA, Renjith Kumar Palaniswamy, SAP BW/4HANA architect, leverages more than 15 years of experience to offer readers a comprehensive guide that blends technical insights with strategic advice, helping organizations navigate the complexities of the migration process from SAP Business Warehouse (BW) to SAP BW/4HANA. His expertise includes native and mixed SAP BW/4HANA data modeling, as well as greenfield implementations and system conversions.
In this SAP Press bestseller, Palaniswamy explores the evolution of data warehousing from the 1970s to the present, emphasizing the need for modern solutions like SAP BW/4HANA, while also discussing advancements in in-memory computing through SAP HANA that enable real-time analytics.
Aimed at IT decision-makers, professionals, and project managers, his hands-on guide is intended to help SAP users plan system conversions, evaluate which option— remote, shell, or in-place—best suits their business needs, and gain the knowledge required to make informed choices during the migration journey.
Along the way, Palaniswamy highlights the transition of cloud-based data warehouse systems and SAP BW/4HANA’s alignment with the growing demand for scalable, flexible, and cost-effective data solutions. Ultimately, he aims to ensure that readers think about their potential transition to SAP BW/4HANA as not simply a technology upgrade but also a strategic move toward sustained business excellence.
In this interview, ASUG discusses the various areas of focus in Migrating to SAP BW/4HANA, discussing a range of implementation options and scenarios, conversion and consolidation approaches, and related solutions such as SAP HANA Composite Providers and SAP BW Bridge for SAP Datasphere.
This interview has been edited for brevity and clarity.
ASUG: What is SAP BW/4HANA, and how does it differ from previous versions of this technology, such as Business Warehouse (BW) on SAP HANA?
Palaniswamy: BW/4HANA is SAP's next-generation data warehouse solution, optimized exclusively for the SAP HANA platform. Unlike previous versions, such as BW on HANA, BW/4HANA has been completely redeveloped to leverage the full capabilities of the HANA platform. This includes significant performance enhancements, and a streamlined architecture designed to run exclusively on HANA, leading to more efficient data processing and management.
BW/4HANA offers several benefits, including improved performance, reduced data processing times, and simplified data management. By being fully optimized for SAP HANA, BW/4HANA can take full advantage of in-memory computing, leading to faster query responses and enhanced online analytic processes (OLAP) functionality. Additionally, the platform supports advanced analytics and provides a modern user interface, making it easier for businesses to gain insights from their data.
ASUG: What are the core design principles behind SAP BW/4HANA?
Palaniswamy: The core design principles of BW/4HANA include simplicity, openness, a modern interface, and high performance.
ASUG: What does the principle of simplicity in SAP BW/4HANA refer to, and how does it impact development and costs?
Palaniswamy: The simplicity principle in BW/4HANA aims to streamline the entire development process and reduce associated costs. This is accomplished by eliminating many persistent objects used in previous versions, such as InfoCubes and standard days sales outstanding (DSO), which have been replaced by more efficient and advanced DSO. The result is a more straightforward architecture that reduces complexity and accelerates the development cycle.
ASUG: What does the openness principle in SAP BW/4HANA mean in terms of data integration and consumption?
Palaniswamy: The openness principle in BW/4HANA refers to the platform's ability to easily integrate with various data sources and allow for broad data consumption. This means that BW/4HANA can interact with different types of data, whether structured or unstructured, from a variety of external sources. It also ensures that the data can be consumed and utilized by different applications and tools, providing greater flexibility for businesses.
ASUG: What’s changed in terms of user interaction?
Palaniswamy: BW/4HANA enhances user interaction through a modern interface that includes tools like the BW Modeling tool, which is integrated into Eclipse, and SAP UI5-based tools and Web cockpits. These interfaces provide a more intuitive and efficient user experience, allowing developers and users to interact with the system more effectively and with greater ease.
ASUG: How does SAP BW/4HANA improve performance, particularly in OLAP functionality and computational tasks?
Palaniswamy: BW/4HANA improves performance through its optimized architecture that leverages the SAP HANA platform's in-memory computing capabilities. This leads to faster OLAP functionality and more efficient computational tasks. Additionally, BW/4HANA employs a “push down” approach, where computational tasks are executed directly on the SAP HANA database, further enhancing performance by reducing data movement.
ASUG: You refer in the publication to SAP HANA Composite Providers as valuable resources for merging information in SAP BW/4HANA. Can you elaborate on the significance of these objects?
Palaniswamy: HANA Composite Providers in BW/4HANA are advanced virtual objects that replace older objects like MultiProviders and InfoSets. They offer a more flexible and powerful way to combine and query data from different sources. By consolidating these virtual objects into a single, optimized solution, HANA Composite Providers improve both performance and usability, making data integration and analysis more efficient.
ASUG: In what scenarios would a business choose to implement SAP BW/4HANA over previous versions? Can you provide a case study?
Palaniswamy: A business might choose to implement BW/4HANA over previous versions when they require faster data processing, a simplified architecture, and advanced analytics capabilities. For instance, a retail company that needs real-time insights into customer behavior might benefit from BW/4HANA's enhanced performance and modern interface, allowing them to respond quickly to market changes. A case study could involve a company that successfully reduced data processing times by 50% and improved decision-making speed by implementing BW/4HANA.
ASUG: How would you explain the advantages of BW/4HANA to a stakeholder unfamiliar with SAP systems?
Palaniswamy: I would explain that BW/4HANA is a powerful data warehousing solution that enables businesses to analyze large amounts of data quickly and efficiently. It offers a modern, user-friendly interface and integrates easily with various data sources, providing valuable insights that can drive better business decisions. The platform is designed to reduce complexity and costs, making it an ideal choice for companies looking to optimize their data management processes.
ASUG: What are the key factors an organization should consider when deciding on a migration strategy to SAP BW/4HANA?
Palaniswamy: Overall database size, the current BW 7.X version, the total number of BW objects, and whether data migration is necessary. The existing system landscape and data migration requirements are also crucial in determining the most appropriate approach. There is no one-size-fits-all strategy, because each organization's needs and circumstances differ. Factors like database size, the complexity of the existing BW environment, and future data modeling requirements all influence the choice of migration approach. Therefore, strategies must be tailored to meet the specific needs of each organization.
ASUG: In your book, you write extensively about the different implementation options available to customers. I'd love to dig into those. Let's start with greenfield. Can you describe this approach as it relates to SAP BW/4HANA?
Palaniswamy: With a greenfield implementation strategy, enterprises start from scratch by developing new data models using the new modeling options provided by BW/4HANA. This approach is ideal for organizations that want to create a fresh system without carrying over any legacy data or objects. It allows for the complete re-design of data models, leveraging BW/4HANA’s advanced capabilities.
ASUG: What is an in-place conversion and when would an organization choose this option?
Palaniswamy: An in-place conversion involves migrating the existing system to SAP BW/4HANA while retaining the same system landscape and system ID. This approach is chosen when an organization prefers to keep their current system environment intact but wants to upgrade to BW/4HANA. Before conversion, the system must be migrated from a non-HANA to a HANA database. This method is suitable for organizations looking to minimize disruption during the migration process.
ASUG: How does a shell conversion differ from other migration approaches, and in what scenarios is it most suitable?
Palaniswamy: This involves migrating to a completely new BW/4HANA system within a new system landscape and system ID, without migrating the existing data. Only the BW objects are converted, and no data is moved. This approach is suitable for organizations that want to create a new system environment while retaining the flexibility to design the data migration process separately, if needed. It’s ideal when the focus is on optimizing the data models and system performance without the immediate need to carry over old data. This approach is ideal for re-designing data models and optimizing system performance. However, its limitation is that it doesn’t include data migration, which means any necessary data migration must be handled separately, potentially adding complexity to the overall project.
ASUG: What is a remote conversion and why would an organization choose this method? Can you provide a case study?
Palaniswamy: A remote conversion involves migrating to a new SAP BW/4HANA system with a new system ID while also migrating data from the old BW system to the new BW/4HANA objects. This approach is chosen when there is a need to preserve historical data while transitioning to a new system landscape. For example, a large multinational company with extensive historical data might choose a remote conversion to ensure all valuable data is retained during the migration process, while still benefiting from BW/4HANA’s advanced features.
ASUG: When should an organization consider a consolidation approach during their SAP BW/4HANA migration?
Palaniswamy: An organization should consider a consolidation approach when it has multiple BW systems across different regions or business units and wishes to unify them into a single BW/4HANA system. This approach helps reduce system complexity, improve data consistency, and streamline maintenance efforts. It is particularly beneficial for large enterprises looking to centralize their data warehousing operations.
ASUG: How should the size of an organization influence its choice of SAP BW/4HANA migration strategy?
Palaniswamy: Significantly. Smaller organizations with less data might opt for a migration approach without data, focusing on a fresh start with new data models. Medium-sized organizations might prefer an in-place conversion to retain their existing system landscape while upgrading to BW/4HANA. Large organizations with extensive data and complex landscapes might choose a Remote Conversion to ensure all critical data is migrated while optimizing the new system environment.
ASUG: What challenges might a large organization face when choosing to migrate to SAP BW/4HANA with data, and how can they be mitigated?
Palaniswamy: A large organization might face challenges such as long migration times, data integrity issues, and the complexity of ensuring all relevant data is migrated accurately. These challenges can be mitigated by thorough planning, conducting a detailed assessment of the current BW environment, and using tools and methodologies designed to handle large-scale data migrations. Additionally, running pilot tests and involving experienced consultants can help address potential issues before they become critical.
ASUG: What role does the existing system landscape play in determining the most appropriate SAP BW/4HANA migration approach?
Palaniswamy: The existing system landscape plays a crucial role in determining the most appropriate BW/4HANA migration approach. Factors such as the current database type, system architecture, and integration with other systems must be considered. For instance, if an organization is already using HANA, an in-place Conversion might be more straightforward. In contrast, organizations with a more complex or outdated landscape might benefit from a remote conversion or shell conversion to modernize their infrastructure.
ASUG: What is the SAP BW Bridge for SAP Datasphere, and what purpose does it serve?
Palaniswamy: The SAP BW Bridge for SAP Datasphere is a solution designed to bridge the gap between traditional BW systems and the new SAP Datasphere. It allows organizations to integrate their existing BW systems with SAP Datasphere, enabling a more seamless data management experience. This approach is suitable for organizations that are transitioning to SAP Datasphere while still relying on their BW systems.
ASUG: Finally, what are the key factors an organization should consider when deciding on a migration strategy to SAP BW/4HANA?
Palaniswamy: When planning a migration to BW/4HANA, an organization should consider several key factors, such as the overall database size, their current BW 7.X version, and the total number of BW objects that need to be migrated. Additionally, the organization must evaluate its landscape strategy—whether they intend to migrate within the existing landscape or move to a new one. Finally, it's crucial to determine whether data migration from old BW objects is required, as this will significantly influence the chosen migration approach.