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

[guest9]

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 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 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 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 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.

SAP HANA Studio: Object Transferred

Success!

 

---

Thank you for making it this far. We do expect to have a demo for you soon so do check back.

 

As we mentioned in the overview, this blog is part of a series. You can find the additional parts below:

Part 1: Creating Simple Objects Using SAP BW bridge for SAP Datasphere (Demo)

Part 2: Combining Data from SAP BW bridge and SAP Datasphere (Demo)

Part 3: Using SAP Analytics Cloud on top of SAP BW bridge and SAP Datasphere (Demo)

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

 

Do have a look at our additional articles for more information:

Introducing SAP BW bridge for SAP Datasphere

SAP Datasphere, SAP BW bridge: Overview and Technical Deep Dive

[former_member759402]

Hi Jonathan,

This is really nice descriptive blog and will definitely help everyone!

We are wondering, do you know when this shell conversion option will be released and available for customers to use?

Thanks,

Ankur

[guest9]

Hi Ankur,

Thanks for the comment and for pointing this out.

The "Shell Conversion" is planned for release 2202 (19/20 February) and the "Remote Conversion" is planned for BW bridge release 2205 (21/22 May). You can find the latest dates in this note as well - 2984828

Thanks again!

[former_member759402]

Hi Jonathan,

That's good to know that it will be available soon. Could you also suggest which version of 'Transfer Tool' will be required on BW system?

If you can refer any SAP note for pre-requisite as well will be helpful.

Thanks,

Ankur

[guest9]

Hi Ankur,

I would recommend checking out these notes. You will notice it mentions the "Shell Conversion" is only available in 2202 which would tie in with the previous release date.

You should be able to find the different minimum system requirements here: 3141688
And you can also check out some of the supported functionality and limitations here: 3117800

Hope that helps!

[paulvatter]

hi Jonathan

do you know when 3141688 will be released?

Thanks and best regards Paul

[guest9]

Hi Paul,

Thanks for pointing this out. Just noticed this note is still in a processing state.

I can't find a fixed date for the release just yet although I expect it to be soon. I will reply here as soon as I do notice it is released for customers.

There is also a good blog post on Maintenance Windows and Major Upgrades for the SAP BTP ABAP Environment. The "Shell Conversion" which we refer to in this blog post is planned for Release 2202 on the 19/20th of February 2022. It is likely the notes will follow shortly.

Thanks!

[MC]

Hi Jonathan

 

Is the RFC Setup documented in the SAP BW Bridge official guide (currently for me not loading) ?

Would it be possible to add a few screenshots and a direct link to the sap help section ?

Is there anything special to keep in mind whilst performing the RFC setup ?

 

Best regards

Marian

[doubroff_oliviier]

Hello Jonathan

 

in others blogs, I understood that Sap bw bridge do not contain any olap component so no query at all. So I am astonish to learn that the conversion toll should move query as well.

Can you explain ?

rgds

Olivier

[cjfaurie_1616]

Hi Jonathan,

Hope all is well?

For a shell conversion from SAP BW to SAP DWC, SAP BW Bridge, can a user run the task list SAP_BW4_TRANSFER_CLOUD_SHELL multiple times at the same time? Will it cause issues or table locks in SAP BW?

 

Thanks

Kind regards

Neels Faurie

 

 

[felipe_capano]

Hi Neels,

It is possible to run different task list runs in parallel for the task list type SAP_BW4_TRANSFER_CLOUD_SHELL. What can happen is different open task list runs having objects in common (overlapping objects). When this situation happens, such objects are locked in the original task list run and that will prevent the subsequent task list to run.

The system will then display an error message "Run SAP_BW4_TRANSFER_CLOUD_SHELL_XXXXXXXXX contains objects of current scope".

An overlapping situation can also happen between different task list types, for example SAP_BW4_TRANSFER_CLOUD_SHELL and SAP_BW4_TRANSFER_CLOUD_REMOTE.

For such cases, the options to proceed are either to complete the original task list or to finalize/delete it.

 

Kind regards,

Felipe

[felipe_capano]

Hi Olivier,

Queries objects can be transferred to BW bridge via the Shell Conversion but these BW bridge queries are not accessible/executable. SAP plans to offer a query transfer capability which, after the query objects are transferred, will allow such objects to be imported as entities/artifacts to SAP Data Warehouse Cloud.

This is planned for Q1.2023.

https://roadmaps.sap.com/board?PRODUCT=73555000100800002141&range=FIRST-LAST#;INNO=000D3ABE772D1EDCA...

Kind regards,

Felipe

[felipe_capano]

Hi Marian,

Please see the section 4.1 of the Shell Conversion Guide:

https://help.sap.com/doc/6467461ba122491da38f00c3e432fdf7/2211/en-US/SAP_DWC_BWbridge_Conversion_Gui...

And also the Getting Started:

https://help.sap.com/docs/SAP_DATA_WAREHOUSE_CLOUD/ecce5bb08ae24ed089497fc00c2320d8/18d69431efb34a71...

Kind regards,

Felipe

 

[cjfaurie_1616]

Good morning Felipe,

 

Thanks very much for your reply, noted.

Kind regards,

Neels Faurie

[Saket_S]

Hi Jonathan,

Suppose if we are working in a Greenfield implementation and want to use standard ODP based extractors in BW Bridge. In that case can we directly connect BW Bridge with source S/4HANA and start building models inside BW Bridge. Will we still need a BW or BW/4Hana sender system in background as in case of brownfield? Technically, is it a prerequisite to have BW sender system even in case of Greenfield implementation on BW Bridge?

Regards

Saket

[guest9]

Hi Saket,

For a Greenfield implementation there is no need for additional BW or BW/4HANA systems as your start point. Your case here would be what we discussed in the first part of this series - Part 1: Creating Simple Objects Using SAP BW bridge for Datasphere Cloud (Demo)

Regards,
Jonathan

[Saket_S]

Thank You Jonathan to confirmed that BW sender system like BW/4HANA or BW 7.5 etc. is not a prerequisite for BW Bridge when doing a Greenfield implementation.

Your reply will help me to get started on the Greenfield project with DataSphere, BW Bridge connected to S/4HANA cloud(Private version) without bothering about the availability BW sender system.

Regards

Saket