- SAP Managed Tags:
Administration guide for SAP Ariba Shopping with interactive onboarding diagramHello Ariba community,
I would like to share with you the latest product update: The new SAP Ariba Shopping administration guide is now online!
The administration guide provides you with an interactive onboarding diagram with all required steps and roles for a successful rollout. This blog post helps you with additional screenshots and useful hints in completing the 7 administrative tasks in the administration guide. It was never easier to get started with SAP Ariba Shopping!
Before you start, check the following prerequisites:
You have a valid subscription for one of the following Ariba purchases:
- SAP Ariba Buying or
- SAP Ariba Buying and Invoicing
You have administration rights for the following systems:
- SAP BTP Global Account of your Ariba purchase
- SAP Cloud Identity Services / Corporate IDP
- SAP Ariba Developer Portal
You are aware that the optional integration from guided buying to S/4 is not supported:
The SAP Ariba Shopping mobile app doesn't support requisitions created and submitted in guided buying when guided buying is integrated with SAP S/4HANA or SAP S/4HANA Cloud (2NV and 3EN).
Step 1: Subscribe to SAP Shopping App with SAP Booster
A SAP Booster is a set of guided interactive steps that enable you to select, configure, and consume services on BTP. Search for the SAP Ariba Shopping Booster to subscribe to the BTP application.
You have to start the Booster at the BTP global account of your SAP Ariba purchase to subscribe to SAP Ariba Shopping. You can access BTP global accounts with the SAP BTP cockpit: https://emea.cockpit.btp.cloud.sap
Your company can have multiple BTP global accounts. A global account represents the sales contract and the subscriptions of the purchased solutions. If you don't find the BTP global account of your SAP Ariba purchase, ask your SAP contact person (CSP - Customer Success Partner) or create a support ticket. For more information, see Contacting Support.
Read this section in the administration guide. Click on start.
Check Prerequisites
The Booster starts with checking the prerequisites:
If the authorization check fails, you probably have no global account administrator rights. If the entitlements check fails, the global account does not belong to the Ariba purchase. If you do not find the global account for the Arba purchase, contact your SAP contact or create a support ticket.
Click on Next when the checks are successful.
Select Scenario
You can create or select from existing subaccounts. If you select an existing subaccount you may skip to configure the SAP Identity Authentication Service (IAS) tenant because this step is probably already completed. For this blog post, I select the option to create a new subaccount. Click on Next.
Configure subaccount
Enter now the subaccount details. To minimize network latency, BTP data center and Ariba data center should be in the same region. Click on Next.
Select Identity provider for platform and application and add users
In this step you select the identity provider for the platform and the identity provider for the application. In a productive scenario you would select the identify provider which is used to identify Ariba end users. In a testing scenario you can select the identify provider where you are authorized to create users.
Furthermore, you can add other colleagues (you are already selected per default) to subaccount administrator role and developer role. The developer role is needed to access the SAP Mobile Service cockpit.
Review before automation starts
After reviewing the input, the Booster makes the following manual tasks for you. Click on Finish.
Step 2: Configure Identify Authentication Service
In this step you establish trust between SAP Identity Authentication Service (IAS) of the application and the subaccount with the SAML 2.0 protocol. Read this section in the admin guide to complete on this common task.
To create test users read this sap help section where, you assign the user to Purchasing User and Mobile Shopping user groups at SAP Ariba Buying (P2P). In the IAS you can use the Login attribute to identify the Ariba end user. Then you maintain the SAP Ariba User Id in the login attributes of the test user.
Step 3: Create Application Definitions in SAP Ariba Developer Portal
Sign in to the SAP Ariba APIs developer portal:
Use the recommended namings from this section in the administration guide and create four application definitions.
Note down the generated application keys. You do not have to request API access. You also do not have to link the applications to a public Ariba API. The SAP support team will assign the applications to private APIs when the service request is processed. The service request you will create in the next step 4 will process the next three steps in the process (see screenshot, "What's next"-Section)
Step 4: Create Service request to enable SAP Ariba Shopping APIs
Read this section in the admin guide. Download the the SAML XML file of the BTP destination to add the file as an attachment to the service request:
Create the service request (support component: BNS-ARI-SAS-API) in SAP for Me with the following content:
Dear SAP Support,
The information to enable the SAP Ariba APIs is as follows.
Site Name: The site name (realm) where you want to connect the app with
Data Center: The data center from the Ariba Developer Portal where you have created the four applications
ANID: [Example: AN01037605217-T] - The technical id of the Ariba realm where you want to connect the app with
Application Keys:
SAS Procurement Requisition: [application key]
SAS Procurement Chooser: [application key]
SAS User Schema Information: [application key]
SAS Catalog Search: [application key]
Attached is the SAML XML metadata file from the SAP BTP subaccount.
The processing of the service request takes usually one or two working days. Once completed, you see in the developer portal that the applications are approved for the Ariba Shopping APIs. Request now the oAuth client secrets for the four applications from your Ariba administrator. Note down also the Oauth Client id for the four applications and the real name ("cirrusatlanticsuite" in my example) for later use in step 6.
Step 5: Connect SAP Mobile Services to SAP Ariba Shopping
Read this section in the administration guide. Select the subaccount in the SAP BTP cockpit. Click on SAP Ariba Shopping application:
The URL to access the SAP Mobile Service Cockpit is shown in the browser:
Copy and bookmark the SAP Mobile Service URL and note down the mobile Destination URL for the next step. Open now the SAP Mobile Service URL to access the SAP Mobile Service cockpit, Kernel Service.
The Kernel Service is used for an application like SAP Ariba Shopping that is managed in a single-app cockpit (Software as a Service, or SaaS). The license type is read-only and cannot be selected or edited in the SAP BTP cockpit.
Go to tab "info", select feature "Mobile Connectivity":
You see three mobile destinations:
To configure the three destinations you need first obtain from SAP Ariba Developer Portal the following:
- The value of the host of the Production & Test URL. Example: https://openapi.ariba.com.
- The value of the Token Service URL: Example: https://api.ariba.com/v2/oauth/token
Update all three destinations with the right values from the admin guide. Every destinations requires slightly different information. I selected the images destination as an example:
Basic Info
Custom Headers
In the second step you enter the application key of the Ariba application "SAS Catalog Search":
Annotations
Click on Next.
Destination Configuration
Read the step in admin guide to update the fields with the right values.
Certificate Configuration
Click on Finish. When you have updated all three destinations you should see a similar result:
Click on the row of the requisition-attachment to access the security section. Download SAML metadata file and set expiry date (maximum is 10 years). Update the created Service Report with the SAML metadata file to enable the API for the attachment functionality.
Step 6: Configure SAP BTP Destination To SAP Ariba
Read this section in the admin guide. Go to the Destination section of the subaccount and update the four Destinations:
Here is an example how I updated the first destination. The warning is not applicable for this step.
Check the connection for all four destinations. A green checkmark and a message that says the connection is established indicates that your configuration was successful. The returned response doesn't matter even if it is HTTP Status code 403 or 404.
Step 7: Onboard Users to SAP Ariba Shopping
Read this section in the admin guide. Go to SAP Mobile Service cockpit, navigate to API tab to view the QR code:
SAP Mobile Service Cockpit: API tab- Download (iOS/Android) and open SAP Ariba Shopping app
- Scan QR Code and check connection request
- Agree to end user license agreement (EULA)
- Start shopping!
SAP Ariba Shopping app on iOSFurther References:
- Watch SAP Ariba Shopping app on Youtube.
- Our roadmaps for iOS and Android.
- Blog post from my colleague Jens Trummer about the first release
