Life Cycle Management in SAP Datasphere: Transporting Content between Tenants

[Geetha_Madhuri_Bobbili]

Author: Geetha Madhuri Bobbili
LinkedIn Profile: https://www.linkedin.com/in/geetha-madhuri-bobbili-971268184/

Introduction:

The concept of Life Cycle Management is not exclusive to SAP Datasphere as this process is also done in on-premise systems. The landscape architecture is however slightly different as SAP Datasphere is a Data Warehouse as a Service (DWaaS) solution and runs in the Cloud.

If you have Administrator or Space Administrator role, you can transfer content between tenants/systems in your landscape. For example, you have developed Graphical views, Data Flows, Intelligent Lookups and Analytic Models in your Dev tenant and then move them to a QA tenant when they are ready for Testing.

Typical System Landscape for SAP Datasphere:

Despite being a Cloud-based solution, there is still need to have multiple SAP Datasphere environments (Sandbox, Dev, QA, Prod) to facilitate efficient Life Cycle Management. At a minimum, a configuration with two tenants is recommended for performing Life Cycle Management.

Important Note:

For the seamless promotion of content, it's advisable to ensure that both the source and destination tenants are on the same release version. Transferring content from a higher release version tenant to one with a lower release version is not feasible.

As of the latest release (version 2023.16), the Transport app supports the export and import of the following object types exclusively:

• Local Tables


• Remote Tables: The definition of a remote table contains information about its connection. Before importing, make sure to create the same connection with an identical technical name in the recieving space.


• Views


• Data Flows


• Intelligent Lookups


• Analytic Models


• E/R Models


• Data Access Controls


• Task Chains


• Business Entities / Business Entity Versions


• Fact Models


• Consumption Models


• Authorization Scenarios

Transporting the Content using Export/Import:

To export and import content, you must have Administrator or Space Administrator role to read, maintain, and share Life cycle data.
The exported packages are stored in the cloud, where we can share the packages with other systems in our landscape and import content that is shared with your system.Referring to the above image, the Content is exported as a Package in the Dev Tenant and shared with the QA Tenant. Following this, the shared Content Package is then imported with in the QA Tenant.

Exporting Content for Sharing with Other Tenants:

We can share content across tenants from one or more landscapes and set access rights for each sharing destination. Each tenant can store up to 2048 MB of exported content in the My Content area.

This method has the following advantages:

• Exported files are hosted in the Cloud rather than on the client machine.


• Files can be organized into folders including with folder security options.


• Processing occurs in the background so there is no need to wait for the export to
  complete.


• There is no need to manual download/upload packages for Life Cycle Management.

Procedure:

1. In the side navigation area, click Transport and select Export.

2. Select My Content folder. The My Content page shows a list of packages and folders, including the packages that you have exported and the packages from other systems that you have permission to edit or delete.Let's see some important options on this page before we start exporting our package.

3. Select  New Export. On the Choose content page, select the objects you want to export, and then click Next. If an object depends on other objects, then they will also be selected. Click on Next.

4. On the Set package properties page, complete the properties.

Adding Sharing Destinations:

Select + icon on the Package Properties page, to add your Destination URL and then click Next. From the Access drop down, choose the permissions that you want to grant to the sharing destination. You can add more than one permission.

5. On the Review and export page, review the overview of your package. If there are any problems, select the warning icon to see how to fix them.

6. Click Export to export your package.
You can check the progress of your export in the Notifications list. You'll also receive a message when it is complete.You can check the Export Summary to see the status of all the objects in the package. When the export completes successfully, the package becomes available in the My Content section for the tenants you added.

Importing Content from Another Tenant:

Procedure:

1. Make sure the space or spaces you want to import into are present in your tenant, and each of them has the necessary connections for remote tables used in the import.Example: We can not import content exported from the Sales Space to the Finance Space using Transport App.

Keep in mind that if your content involves objects shared between spaces, both those spaces must be there.

2. On the side navigation, click "Transport" and choose "Import" to see the list of content available for importing.

3.If you don't find the packages you expected to import, hit the "Settings" button and double-check the import settings.

We have the following options:
Enable the Show content shared by all systems option and optionally exclude content from specific tenants by adding them to the Add systems to block content sharing list.

Disable the Show content shared by all systems option and choose specific tenants to import from by adding them to the Add systems to allow content sharing list.
If, after checking these settings, an expected package is still not listed, contact an administrator for help.

4. Click a package to open it and see an overview of its content and review the Import Options section. For more details, and to modify any of the options, click the Import Options tab.

5. Select an option for the Overwrite Preferences. If an object selected for import does not exist on your system, the object will be created and its data will be imported.
For objects that already exist in your system, the Overwrite Preferences determine whether to update the object and its data.Don’t overwrite objects or data: Protects existing objects in your space from being overwritten or having their data updated. You are notified if any of the objects selected for import already exist in your system.
Overwrite data only: Not currently supported for SAP Datasphere.
Overwrite objects and data: Objects on your system can be overwritten and their data can be updated.
Deployment Preference: Check the "Deploy after import" checkbox to automatically deploy objects after import.

6. Select Import. The import process begins. You receive a notification when the process is complete, or if an error occurs.
To view the log of updates and imports for a package, select the package in the content network and choose History.

Conclusion:

By following the outlined steps, you can easily transfer content between tenants/systems in your SAP Datasphere landscape.

If you're looking to boost your expertise in SAP Datasphere, I have authored a comprehensive book, offering readers profound knowledge and valuable insights. Don't miss the opportunity to secure your copy at https://www.sap-press.com/introducing-sap-datasphere_5862/.

[former_member848016]

a0286fd26e1645ac914b04a295fc5777 Did you had any issues transporting the objects between tenants when the space names are different in the tenants. can we have different space names in QA and Prod.

 

 

[MKreitlein]

Hello a0286fd26e1645ac914b04a295fc5777,

very interesting and helpful Blog! 🙂

I have one question regarding e.g. S4 HANA System connections in Datasphere...

This object type is missing on your list of transportable objects above. Does it mean we have to create it in each tenant newly ... and I assume we need to use the same technical name?

If you made the mistake of naming it like the source system is called, like S4D_100 (D for Dev) then you have to use this in the prod. tenant, too, even if your system connection there points to S4P_100 (P for Prod.)? Is my understanding correct?

Thanks a lot, Martin

[Geetha_Madhuri_Bobbili]

Hello Martin,

Instead of transporting the connections, we should create them individually in each Tenant with identical names. That's why I didn't include connections in the above list.

Before importing a remote table, it's essential to establish a corresponding connection with the same name in the receiving Space.

Best regards,
Geetha

[Geetha_Madhuri_Bobbili]

Hello Anil,

The Transport app can not import content into a space with a different technical name than the one it was exported from. Before importing the content in to your target space, please create all the relevant connections and spaces with the identical technical name.

Best regards,

Geetha

[former_member848016]

Thanks for the reply we have used the same identical names for the connections and the spaces in both the datasphere tenants only after that we were able to transport the datasphere objects and SAC objects without any issue.

[amlan_dhow]

Thanks for this document -it should be helpful for the new comers.

I would just like to add one interesting feature of Datasphere here. During the selection of the object there is no need of maintaining any sequence and object list etc. If you choose the final object, it would automatically select all dependent object in package.

This is very interesting feature saving enhancing both productivity (Much faster as no need of maintaining documents of dependency and sequence) and quality of work (Much less error prone specially for a sizable implementation)

 

[Geetha_Madhuri_Bobbili]

Yes Amlan, that’s a fantastic feature, actually. Thank you for bringing it up. It accelerates work and reduces mistakes.

It is also essential to select the overwrite preferences with caution.

Best regards,

Geetha

[yureshino]

Thank you for this document.
Do you know how to transfer objects such as tables created in the Open SQL Schema?

BR,
Yu

[MariannevL]

@yureshino Open SQL schema is not in the span of control of datasphere. The creation of the objects has happened via another tool (like an ETL tool or Postman). Ideally it's that tool that will also create or change the objects in the other tenants.
A normal HANA export/import done via DB explorer or any other tool connected to the Open SQL schema is also possible.

Thanks,
Marianne

[leslie_klinger]

Since this will be a SOX-relevant system for my company, I have a couple questions:

1 - can this be ChaRM enabled for controls and governance?

2 - is the transport mgt process similar to BTP?

3 - what reporting is available for the transport mgt processes?

[danilosouza]

Hello!

I have the same questions and concerns from the leslie_klinger about the SOX. What the options or tools to enable controls and governance? Thank you so much.

1 - can this be ChaRM or CALM enabled for controls and governance?

2 - is the transport mgt process similar to BTP?

3 - what reporting is available for the transport mgt processes?

[virendevi_2]

Hello Marianne and Geetha,

Reg. import/export of HANA side view on datasphere , I didnt quite understand. Is this possible via some out of the box feature?

[puneetc]

Very nice blog and covers almost everything

Understand we would need admin role to move the content between tenants.. also i see there are some pre requisites like same space name, same connection name, admin role etc etc.. how are all these taken care while we move the content from QA to Prod as we might not get the admin role and if the basis team might not be good at export import of the datasphere objects to be precise...

Whats the approach, sap also provides the "Transporting Your Content through SAP Cloud Transport Management". is there a step by step document for the same, which is the better approach for traceability and considering the pre requisites of the transport app by import export.. Appreciate your thoughts and inputs please considering the content to be moved from QA to Prod