Before the consumer can access the SaaS application, they need a dedicated URL to access this. To create this, we create a new route and bind it to the approuter as an administrator for the 05 provide subaccount.
For more information refer to the note in the Help Portal.
Navigate to the “Provide” space where the application is deployed. Open the application deployed in previous tutorials and navigate to the “User-Provided Variables” section. Notice the TENANT_HOST_PATTERN. This provides a wildcard that has to match all routes of the applicationTenant host pattern
Now navigate to the “Routes” section in the space “Provide”Application Routes
Create a new route by choosing the domain from the dropdown that matches the TENANT_HOST_PATTERN. The “Host Name” is derived out of the subdomain of the consumer subaccount and the TENANT_HOST_PATTERN we noticed above. The first part of this name is the subdomain of the consumer subaccount. This can be found in the overview section of the consumer subaccount. Consumer subdomainThe second part is the route prefix in the TENANT_HOST_PATTERN. This is the part between the wildcard (.*) and the domain (selected above). The path can be left empty.New Route
Save the newly created route
Step 2Map the newly created route to the application router
+
Next, we need to create a linkage between this new route for the consumer and the application router we created in previous tutorials.
To do this, under “Routes” in the space “Provide”:
Click the “map route” button.
Select the application deployed in previous tutorials.
Save.
Map Route to App
Step 3Subscribe to the SaaS application from consumer subaccount
+
Navigate to the consumer subaccount and go to the “Instances and Subscriptions” tab.
Click “Create” and choose the SaaS application deployed in previous tutorials.Subscribe to App
Wait for the status to change to “Subscribed”. The initial subscription initiates the creation of an ABAP system and the installation of the add-on product in this system. Therefore, this step may take a few hours.Subscribed
Step 4Assign Solution Admin role to user
+
To enable the onboarding of the initial administrator follow the below steps:
Navigate to the consumer subaccount.
Go to the “Role Collections” section.
Add your user to the role collection containing the solution admin role for the application deployed by you in previous tutorials.
Solution Admin
Step 5Onboard initial administrator
+
To access your provider’s SaaS application for the first time, you, as consumer, need to go through an onboarding process.
Open the URL your provider has sent you to get access to their SaaS application. This is the URL added as a route for the consumer subaccount in step 1 of this tutorial.
On the initial administrator onboarding screen, you can see your email address, subdomain and subaccount id. Click Onboard User to start the onboarding process.
Initial administrator onboarding
Click OK in the confirmation dialog
User provisioning confirmation
This might take a few minutes. Once the process is finished, you will be redirected to the Fiori Launchpad of the new ABAP tenant/system. This onboarding process only needs to be done once per consumer.
From now on, the consumer can access the SaaS application via the consumer-specific URL.
Share feedback on this tutorial or join the conversation in SAP Community.
Submit detailed feedbackDiscuss in Community
Steps
Step 1 of 6
1. Create a new route for your consumer2. Map the newly created route to the application router3. Subscribe to the SaaS application from consumer subaccount4. Assign Solution Admin role to user5. Onboard initial administrator6. Test yourself
Joule
AI Notice
Joule is an AI assistant. Generative AI may produce inaccurate, incomplete, or biased information. Always verify important details before acting on them.
Conversations are sent to SAP-hosted large language models for processing. Do not include personal data, credentials, or confidential information in your messages.
Joule's responses are based on the SAP tutorial catalog and may not reflect the latest product changes. For authoritative guidance, consult the linked tutorials and official SAP documentation.