|Philip MUGGLESTONE from the SAP HANA Academy and the Partner Innovation Lab just uploaded two new hands-on video tutorials to the playlist
In this blog post you will find the videos embedded with references and some additional information.
To be informed when new posts are published about partner-related content in the video tutorials series, follow tag
Questions? Please post as comment.
Useful? Give us a like and share on social media.
Hands-On Video Tutorials
What You Will Learn
The first part of the SAP Business Technology Platform Multitenant Business Application playlist on the SAP HANA Academy YouTube channel covers the basics of developing multitenant business applications
The second section revisits similar topics but this time using CAP, the SAP Cloud Application Programming model
The two videos of the blog cover the Subscription Management Dashboard recently added to SAP BTP and a video about troubleshooting and best-practices.
To bookmark or directly access the playlist, go to
Subscription Management Dashboard
In this video tutorial, Philip Mugglestone introduces the Subscription Management Dashboard available in the BTP Cockpit.
0:00 – Introduction
0:30 – SAP BTP Cockpit
1:00 – Add role collection with roles and assign user
2:00 – Navigating the Subscription Management Dashboard
4:15 – New subscription
5:15 – Unsubscribe
6:00 – Documentation
To access the documentation, visit
In this video tutorial, Philip Mugglestone shows how to troubleshoot SaaS multitenant applications. Philip covers how to avoid the XA Advanced login screen and how to configure the TENANT_HOST_PATTERN setting and ensure subscription and dependency URLs are compatible.
0:00 – Introduction
0:40 – SAP HANA XS Advanced log on window
1:40 – Subscription Management Dashboard
2:20 – Subscription failed
4:20 – Update MTA YAML configuration file
7:00 – Build and deploy project to Cloud Foundry
8:00 – Subscription Management Dashboard
8:20 – Subscription successful
9:30 – Best practices
- Use lowercase for
- provider subaccount subdomain
- provider org name
- provider space name
- app name
- Do not use any spaces (use dash – if needed)
- Configure provider subaccount subdomain = provider org name
- Using a wildcard custom domain is more flexible and less sensitive
As a last resort you can workaround some of these issues by specifying the URL compatible org/space/app name directly in the mta.yaml before build & deploy.
Note that for subscribers, we do not have to configure Org and Space.
Share and Connect
Questions? Post as comment.
Useful? Give us a like and share on social media. Thanks!
If you would like to receive updates, connect with me on