Jonathan Francis

January 31, 2022 6 minute read

Using SAP BW bridge for SAP Datasphere (Part 4: Shell Conversion – Walkthrough)

15 6 2,881

Overview

This blog post is part of a series where we will be looking at a few simple use cases and basics when using SAP BW bridge for SAP Datasphere. The purpose of this series is for you to have a walkthrough of how SAP BW bridge, SAP Datasphere, and SAP Analytics Cloud can work together.

In Part 4, we will have a walkthrough of the Shell Conversion to transfer data models from legacy SAP BW to SAP BW bridge for SAP Datasphere

General Availability

The Shell Conversion transfer tool will be available in the Wave 5 release scheduled for the 23rd of February 2022. Updated dates can be found in note: 2984828

Introduction to SAP BW bridge for SAP Datasphere

SAP BW bridge is the latest feature to be released for SAP Datasphere. The main benefit is being able to leverage existing on-premise designs in SAP BW, while also having access to the latest cloud-based functionality in SAP Datasphere. For a detailed breakdown, please head over to the Overview and Technical Deep Dive blog.

Pre-requisites

In the following section, we will be using SAP GUI and SAP HANA Studio or Eclipse.

SAP BW GUI

SAP HANA Studio

Note: SAP BW bridge for SAP Datasphere connects to legacy SAP BW systems via RFC so that connection should already have been set up before running through the steps below.

Part 4: Shell Conversion to SAP BW bridge for SAP Datasphere

Walkthrough

In today’s walkthrough, we will be looking at how to use the Shell Conversion to transfer data models from a legacy SAP BW system. In our example, we will transfer a single Infocube to SAP BW bridge for SAP Datasphere

SAP BW GUI: Infocube Use Case – ZBRI_DEMO

Step 1:

First, we navigate to the Transaction Code STC01 in SAP GUI. We will then select the task list SAP_BW4_TRANSFER_CLOUD_SHELL and execute. This of course is similar to the shell conversion from SAP BW to SAP BW/4HANA

SAP BW GUI: STC01

Step 2:

We will then be looking at our Task List page. The first thing we need to do is select the objects we want to transfer which we do by selecting the “Fill Parameter” as highlighted.

SAP%20BW%20GUI%3A%20Maintain%20Task%20List

SAP BW GUI: Maintain Task List

Step 3:

Next, we will be given the object list page. Here we go to “Add New Object” as highlighted.

SAP BW GUI: Add Objects

Step 4:

We will then be given a search window that is similar to that we have seen in BW and BW/4HANA. We then fill in our example Infocube which is ZBRI_DEMO and select search.

SAP BW GUI: Search

Step 5:

Once we have selected our object(s), we will be brought back to the list of objects.

SAP BW GUI: List of Objects

Additional information

Similar to settings in SAP BW for transports or business content installation, we are able to control the scope of selection as highlighted here. In our example, we will not be transporting all related info objects and limit the scope to only the Infocube so we have selected “Minimal Scope“. This will however transfer objects like the InfoArea automatically.

Additional Information: Only Mandatory Objects

We also have an option to create Composite Providers automatically. This option becomes important when the object we are transferring has queries built on top of it. In such scenarios, this will create an additional Composite Provider and it will move the queries to the Composite Provider in the new environment.

Additional Information: Create HCPR

Step 5:

Next, we need to select our target system by selecting “Shell Transfer Target System”

SAP BW GUI: Target System

Step 6:

Here we need to select the predefined target system for migration. This is an RFC connection so it would have been maintained in SM59

SAP BW GUI: Target System

Step 7:

Once we are back on the task list page, we can start our task list. We can do this either directly or in the background as shown below.

Note: We would recommend triggering them as background jobs since runtimes can vary depending on the number of objects selected.

SAP%20BW%20GUI%3A%20Start%20Task%20List%20Run

SAP BW GUI: Start Task List Run

Step 8:

The task list will automatically stop asking us to maintain the package and transport mapping of our selected objects. We then select the “Fill Parameters” on the second task as seen below.

SAP BW GUI: Fill Parameter

Step 9:

In the “Maintain Object List” page, we need to select “Assign Receiver Package and Transport” which will allow us to do just that

SAP BW GUI: Assign Package

Step 10:

We then enter our “Package” and “Request/Task” and select enter.

Note: The package and transport request are not in the source system but rather in the target system. They need to be created and maintained in the target system prior to this step.

SAP%20BW%20GUI%3A%20Package%20and%20Transport

SAP BW GUI: Package and Transport

Step 11:

We then “Resume” our run either directly or in the background.

Note: We would recommend triggering them as background jobs since runtimes can vary depending on the number of objects selected.

SAP BW GUI: Run Job

Step 12:

Our last stop will be the “Checklist for Usage of Involved Objects“. This is a custom coding and authorization check. We need to resolve issues if any by selecting the “Fill Parameters” of the task.

SAP BW GUI: Check Usage

Step 13:

We need to confirm that we have both “BADI” and “AUTH” marked as resolved. There is no further action required.

Note: If we do have objects which are actually flagged and shown under “Where used”, that will need to be resolved manually outside of this task list

SAP BW GUI: Customer Coding

Step 14:

For the final time, we then “Resume” our run either directly or in the background.

Note: We would recommend triggering them as background jobs since runtimes can vary depending on the number of objects selected.

SAP BW GUI: Run Job

Step 15:

We see that the task list is complete and the object has been successfully transferred.

SAP%20BW%20GUI%3A%20Task%20List%20Complete

SAP BW GUI: Task List Complete

Step 16:

Finally, we log in to our HANA Studio to confirm that the Infocube has been transferred. As we can see below, our Infocube [ZBRI_DEMO] has been migrated as a DSO [ZBRI_DEMO]. The Info Area has also been automatically been transferred.