SAP Launchpad service now available for all RISE with SAP customers
Please note that this blog was published prior to the re-branding related to SAP Build portfolio, which was announced at SAP TechEd 2022. SAP Launchpad service and SAP Work Zone come together under the SAP Build Work Zone brand, with two editions: standard edition (formerly SAP Launchpad service) and advanced edition (formerly SAP Work Zone).
In this blog post, I would like to highlight the importance of SAP Launchpad service and why customers should start looking into its advantages over SAP Fiori launchpad on S/4HANA. Did you know that all RISE with SAP customers get access to the SAP Launchpad service on SAP BTP to use as a default for access to all S/4HANA apps?
Why SAP Launchpad service?
As we see in today’s Business world, achieving agility is important and it requires a unifying process especially when it comes to accessing information spread across various application systems and tools that are fragmented. SAP Launchpad service is a unifying tool on Business Technology Platform that simplifies accessing business applications without the need to login to multiple applications systems, making it convenient for Business end users by providing an intuitive and central access point to all relevant application and services – SAP solutions, custom built, 3rd party applications and extension.
Here are some of the reasons to start considering SAP Launchpad service on SAP BTP over SAP Fiori launchpad on your S/4HANA system
1. Central Entry point of access with harmonized User Experience
The SAP Launchpad service offers a central entry point to access various SAP Solutions on cloud, and on-premises. This enhances the productivity and efficiency of business users by seamlessly accessing relevant apps and content centrally in one place. It provides consistency through harmonized user experience and smooth integrations to different UI technologies and third-party web apps. Many solutions like SuccessFactors, IBP, S/4HANA are tightly integrated and can be accessed within the existing SAP Fiori launchpad shell. Customers can also configure access to 3rd party systems and launch them from a tile on the SAP Fiori launchpad.
Reference: Building a central Launchpad using SAP Launchpad Service – Getting Started | SAP Blogs
2. Connect to multiple SAP S/4HANA systems
When you have more than one SAP S/4HANA system, you will end up with multiple SAP Fiori launchpads and end users would often need to switch between these launchpads. The SAP Launchpad service can help in connecting various S/4HANA systems as well as SAP Business Suite system through content federation by remotely consuming apps from the respective system.
3. Extension Scenario
The SAP Launchpad service makes it convenient for end users to access to all custom applications along with standard apps in the respective SAP systems. SAP Launchpad service includes access to deploy any number of custom Fiori apps in SAP BTP via the Managed HTML5 applications. Hence, customers no longer need to deploy custom apps in their S/4HANA and increase the level of customization. To know more, check out this blog post which talks about 5 key aspects of the SAP Launchpad service that is important for anyone looking to extend their SAP solutions.
4. Extending the reach
During the recent times companies have seen how important it has become to extend the reach and provide access securely, may be to their own employees working from home or giving access to business partner outside their organization. The SAP Launchpad service can provide external access to selected applications to employees or business partners such as suppliers, vendors without the need of VPN.
5. Identity Authentication service
The Identity Authentication service (IAS) provides end users with controlled cloud-based access to business processes, applications, and data. The user experience is made simpler through authentication mechanisms and single sign-on capabilities. IAS is now included as part of the BTP subscription. It is found to be helpful in scenario where customers want to expose Fiori applications to external vendors/suppliers but do not want to manage and maintain those external users in their corporate Identity provider.
Reference: Is SAP Cloud Identity Services for free?
6. SAP Mobile Start
SAP Mobile Start is a native mobile app, which serves as an entry point for users to access various applications and content. It is provisioned automatically with the SAP Launchpad service which means all SAP Launchpad service customers get to use straight away SAP Mobile Start with minimal setup. To get started you just need to download the app from the public App Store and scan a registration barcode from your SAP Launchpad service settings followed by a simple three-step process.
Reference: SAP Mobile Start – the new native entry point to access applications & contents | SAP Blogs
7. BTP Central Notification
Business end users get to receive notifications from custom applications and SAP S/4HANA (cloud and on-premise) applications. These central notifications not only provide updates to the users but also provides direct navigation path to the Fiori Application where it originates from. As of today, notifications from SAP S/4HANA and custom apps are only supported. Hopefully in the future more solutions are added.
Reference: Building a central Launchpad using SAP Launchpad Service – Enabling Notifications | SAP Blogs
8. SAP Task Center
SAP Task Center allows to aggregate approval tasks from multiple SAP solutions like SAP S/4HANA, SAP SuccessFactors, SAP Fieldglass etc. SAP Task Center is provided to the end user via the Task Center application within the SAP Launchpad service sites on SAP BTP that allows end users to handle approval tasks in an efficient way. SAP Task Centre is available only on SAP BTP for customers who are on a consumption-based commercial model. It does require customers to have IAS/IPS as Identity Management system. SAP Task Center is free of charge to integrate tasks from all SAP cloud solutions. Get the details here –
Reference: Handling Tasks in an efficient, integrated and harmonized way using SAP Task Center | SAP Blogs
9. Multiple Fiori Launchpad Sites
It is also possible to create multiple SAP Fiori Launchpad sites on SAP BTP each targeting different personas. For example, one for employees and another for your vendors. This does not require exposing your SAP backend systems to the internet. SAP Cloud Connector installed on your premise securely exposes the content to the SAP Launchpad service for consumption by authorized users. For more details refer to this blog post – SAP BTP Launchpad service: Top 5 reasons to consider using it to extend SAP solutions | SAP Blogs.
10. Evergreen Libraries and Visual Themes
In case of SAP Fiori launchpad, administrators are required to upgrade the SAPUI5 library and component versions to obtain the new features as well as visual themes. For many organizations, upgrades are usually a big activity which involves time and resources. However, with the SAP Launchpad service such overheads are avoided since the upgrades are taken care by SAP and customers get access to the latest SAPUI5 libraries.
Hope this blog post helped you understand the advantages of SAP Launchpad service as compared to SAP Fiori launchpad.
SAP Launchpad service is offered part of the free tier model for SAP BTP to explore and start developing with the SAP Launchpad service. Customers with CPEA / Pay-as-you-go contracts can activate a free service plan for evaluation and PoC projects. Want to get started? Check out this blog post for more details – Start your SAP Launchpad service free trial today! | SAP Blogs
In order to get started and build SAP Launchpad service on BTP you can refer to the following blog series – Building a central Launchpad using SAP Launchpad Service – Getting Started | SAP Blogs .
Please refer here for more information related to SAP Launchpad service .
Note: SAP Launchpad service and SAP Mobile Start are not available for China and NS2 RISE with SAP customers. BTP CPEA Free voucher credits is only applicable to RISE with SAP S/4HANA Cloud & Private Edition customers. You would be able to find the bundled services in the Supplement Guide.
Hello Rai Kamal Saha,
Very informative blog with lots of pointers with regard to SAP BTP Launchpad Service.
As depicted in the first architecture diagram, if we were to try it out with an existing S/4HANA OP system we would need a SAP Webdispatcher to expose some S/4HANA on premise service (likely its gateway service) via the Cloud Connector to the public internet.
Would you have a pointer to documentation regarding the usage of web dispatcher+ cloud connector with on premise S/4HANA ?
kind regards; Piotr
Hi Piotr ,
The architecture diagram shows SAP Launchpad service with Tunneled Access option .
Please refer to this blog SAP Launchpad Service: Understanding Direct and Tunneled Access | SAP Blogs to find details on the connectivity options.
Rai K. Saha
Hello Rai Kamal Saha,,
Nice write up. Would be good to see the possible integration scenarios mentioned too. For instance into Microsoft Teams and with Azure Active Directory.
Find the best-practice guide for SAP Identity Authentication Service integration with Azure AD here.
The statement “importance of SAP Launchpad service and why customers should start looking into its advantages over SAP Fiori launchpad on S/4HANA” seems to imply that by using the SAP Launchpad Service on BTP, the embedded S/4HANA Launchpad/FES can be decommissioned, when in fact it is my understanding that all standard Fiori apps still need to be deployed to the embedded S/4HANA Launchpad/FES because it acts as a federated content provider for the SAP Launchpad Service on BTP.
Can you please clarify this?
First, your understanding is correct. The Fiori apps are deployed on the S/4HANA FES and consumed to the Launchpad service. I believe that what was meant in the quoted sentence is about the additional value that the (BTP) Launchpad service provides. But I will let Rai comment 🙂
That's right , SAP Fiori FES 6.0 supports the exposure of launchpad content so that it can be integrated into the SAP Launchpad service via content federation . Thereby, SAP S/4HANA systems as of release 1610 can serve as content providers and expose their content to the SAP Launchpad service on BTP.
I meant to highlight on what benefits customers get with SAP Launchpad service as opposed to S/4HANA Fiori Launchpad and why they should consider it as their Central entry point for accessing applications.
Hope this helps 🙂
Thanks for the confirmation, Rai Kamal Saha, and Aviad. I am often asked by SAP customers if they can save infrastructure costs by decommissioning their on-premise SAP Fiori FES when they implement the SAP Launchpad service? My answer has been that they still need to keep their FES as a content provider for standard apps, so while they may not save on infrastructure costs they will get the benefit of a Central Entry Point for all of their SAP (and non-SAP) applications via the SAP Launchpad service as well as de-coupling custom Fiori apps from the core by deploying them on SAP BTP.
Side remark: please keep in mind the embedded FES aspect in S/4HANA scenarios that will also impact (positively) costs...
Yes, a very good point Aviad, and a good reason to adopt the SAP recommended approach of embedded FES for S/4HANA instead of a hub FES.
Hello Rai Kamal Saha,,
In point 4 (extending the reasch) SAP CX application is not listed.
Does this means that CX can not be connected / used together with the launchpad?
In our project we are implementing S4HC and CX and want to give the users access via the launchpad
Hi Rai Kamal Saha,
in your blog you write that "SAP Launchpad service and SAP Mobile Start are not available for China and NS2 RISE with SAP"
Does this mean that employees from China can't login to the Launchpad in BTP running in AMS/FRA, or wouldn't we be able to run BTP with launchpad on a BTP in China?
And can you also tell me what NS2 RISE means?