Phases in SAP BW/4HANA Conversion

When you choose any of the SAP BW/4HANA conversion approaches, there are multiple phases.

Though there are many activities in each phase, the overall process can be divided into two phases: the conversion prepare phase, and the conversion realization phase, which we’ll discuss in the following sections.

Conversion Prepare Phase

The figure below illustrates the intricate tasks associated with each phase of the SAP BW/4HANA migration.

The following list acts as a precursor, setting the stage for a detailed examination of the migration process and its integral components:

• System requirements: Before staring any SAP BW/4HANA migration project, the first step is to understand the system requirements for SAP BW/4HANA. This will cover the sender system SAP BW version and target system SAP BW version and consider the database platform and release.
• Maintenance planner: To perform the technical system conversion to SAP BW/4HANA, it’s imperative to use the maintenance planner. As part of this process, it’s recommended to execute the maintenance planner in the early stages of the SAP BW/4HANA system conversion project. The maintenance planner assesses and verifies the supportability of various items for the conversion, ensuring that all necessary prerequisites are met.
• Prechecks: There are tools from SAP that facilitate your conversion project by furnishing prechecks designed to pinpoint crucial measures required to guarantee the compatibility of your system with the conversion process. It’s advisable to execute these checks prior to commencing the realization phase to allow ample time for resolving any identified issues before initiating the conversion processes. These prechecks, delivered to customers intending to migrate to SAP BW/4HANA in the form of SAP Notes, serve as valuable resources. Customers can use these prechecks to discern the essential steps they must undertake before transitioning to SAP BW/4HANA. The outcome of these checks provides a comprehensive list of instances that necessitate attention before embarking on the conversion process.
• Custom code: Before moving to SAP BW/4HANA, you check for custom code that needs to be adapted. To support you in detecting this code, SAP provides a code scan tool as part of the SAP BW/4HANA transfer cockpit. For example, you can verify whether custom code that has been developed long back in ABAP, and which is embedded in transformations and other objects, will be compatible with the SAP BW/4HANA data structures. This step needs the active involvement from the ABAP experts as there might be a requirement to retire and remove the obsolete custom code.
• Simplification and readiness check: SAP has provided the detailed documentation on the simplification items for each classical SAP BW object and how that can be handled.

Conversion Realization Phase

This is the phase where the actual SAP BW/4HANA migration will happen. Based on the detailed analysis, the organization can choose the best possible options for its SAP BW to SAP BW/4HANA conversion.

During the realization phase of the in-place conversion, as depicted in the figure below, it’s essential to have the necessary starter add-on and transfer cockpit. Once the custom code adjustments are completed, SUM is employed for the actual system conversion. Subsequently, post-conversion steps are undertaken, leading to the emergence of the SAP BW/4HANA system.

In the realization phase of the remote conversion, depicted in the next figure, a pivotal prerequisite is the installation of the SAP BW/4HANA system within the target landscape. Subsequently, the deployment of the Conversion Cockpit tool, an integral part of the Data Migration Integration Server (DMIS) add-on in both sender and target systems, becomes crucial. This tool serves as a cornerstone in orchestrating a smooth transition from the existing system to the advanced SAP BW/4HANA architecture. Prior to initiating the conversion, it’s imperative to conclude the custom code adjustments, ensuring seamless compatibility with the new environment.

Within this process, the focus is on data migration, which is the important task preserving and transferring critical information accurately. Post-conversion, a series of steps are executed that culminate in the successful realization of the SAP BW/4HANA system. These post-conversion measures ensure the integration of advanced functionalities and complete the remote conversion.

During the realization phase of the in-place conversion, as depicted in the next figure, it’s essential to have the SAP BW/4HANA target system installed, the transfer cockpit, and the adjusted custom code. The data load isn’t possible in this case, so the post-conversion steps are directly undertaken, leading to the SAP BW/4HANA system in the target landscape.

Editor’s note: This post has been adapted from a section of the book Migrating to SAP BW/4HANA by Renjith Kumar Palaniswamy.