We are proud to share our inclusion in the 2024 Gartner Magic Quadrant for Data Integration Tools. We believe this recognition reflects the differentiated business outcomes CData delivers to our customers.
Get the Report →Connect to SAP Ariba Procurement Data in RunMyProcess through Connect Cloud
Use CData Connect Cloud to create on OData API for SAP Ariba Procurement Data and connect to SAP Ariba Procurement data in Akorbi Digital RunMyProcess.
Akorbi Digital RunMyProcess makes it easy to create applications for complex business applications, such as budget application and contract management. CData Connect Cloud creates a live connection to SAP Ariba Procurement and can be used to generate an OData API (natively supported in RunMyProcess) for SAP Ariba Procurement. By pairing RunMyProcess with CData Connect Cloud, you get true cloud-to-cloud connectivity to all your SaaS and cloud-based Big Data and NoSQL sources - no need to migrate your data or write your own integrations. Simply connect to Connect Cloud from RunMyProcess as you would any other REST service and get instant, live access to your SAP Ariba Procurement data.
In this article, we walk through connecting to SAP Ariba Procurement from CData Connect Cloud and accessing SAP Ariba Procurement data through an OData feed in RunMyProcess.
Connect to SAP Ariba Procurement from RunMyProcess
To work with live SAP Ariba Procurement data in RunMyProcess, we need to connect to SAP Ariba Procurement from Connect Cloud, provide user access to the connection, and create OData endpoints for the SAP Ariba Procurement data.
(Optional) Add a New Connect Cloud User
As needed, create Users to connect to SAP Ariba Procurement through Connect Cloud.
- Navigate to the Users page and click Invite Users
- Enter the new user's email address and click Send to invite the user
- You can review and edit users from the Users page
Add a Personal Access Token
If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.
- Click on your username at the top right of the Connect Cloud app and click User Profile.
- On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
- Give your PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Connect to SAP Ariba Procurement from Connect Cloud
CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.
- Log into Connect Cloud, click Connections and click Add Connection
- Select "SAP Ariba Procurement" from the Add Connection panel
-
Enter the necessary authentication properties to connect to SAP Ariba Procurement.
In order to connect with SAP Ariba Procurement, set the following:
- ANID: Your Ariba Network ID.
- ANID: Specify which API you would like the provider to retrieve SAP Ariba data from. Select the Buyer or Supplier API based on your business role (possible values are PurchaseOrdersBuyerAPIV1 or PurchaseOrdersSupplierAPIV1).
- Environment: Indicate whether you are connecting to a test or production environment (possible values are TEST or PRODUCTION).
Authenticating with OAuth
After setting connection properties, you need to configure OAuth connectivity to authenticate.
- Set AuthScheme to OAuthClient.
- Register an application with the service to obtain the APIKey, OAuthClientId and OAuthClientSecret.
For more information on creating an OAuth application, refer to the Help documentation.
Automatic OAuth
After setting the following, you are ready to connect:
-
APIKey: The Application key in your app settings.
OAuthClientId: The OAuth Client Id in your app settings.
OAuthClientSecret: The OAuth Secret in your app settings.
When you connect, the provider automatically completes the OAuth process:
- The provider obtains an access token from SAP Ariba and uses it to request data.
- The provider refreshes the access token automatically when it expires.
- The OAuth values are saved in memory relative to the location specified in OAuthSettingsLocation.
- Click Create & Test
- Navigate to the Permissions tab in the Add SAP Ariba Procurement Connection page and update the User-based permissions.
Configure SAP Ariba Procurement Endpoints for RunMyProcess
After connecting to SAP Ariba Procurement, create a workspace and virtual dataset for your desired table(s).
- Navigate to the Virtual Datasets page and click Add to create a new Workspace (or select an existing workspace).
- Click Add to add new assets to the Workspace.
- Select the SAP Ariba Procurement connection (e.g. SAPAribaProcurement1) and click Next.
- Select the table(s) you wish to work with and click Confirm.
- Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
Sample URLs for OData Feeds
Once you have configured a connection to SAP Ariba Procurement, created a user, and created OData endpoints in Connect Cloud, you can access OData feeds for SAP Ariba Procurement data. Below, you will see the URLs to access tables and the list of tables. For information on accessing the tables, you can navigate to the OData page for Connect Cloud. For the URLs, you will need the URL of Connect Cloud: https://cloud.cdata.com/api/odata/{workspace_name}.
Table | URL | |
---|---|---|
Entity (table) List | https://cloud.cdata.com/api/odata/{workspace_name}/ | |
Metadata | https://cloud.cdata.com/api/odata/{workspace_name}/$metadata | |
Orders | https://cloud.cdata.com/api/odata/{workspace_name}/Orders |
As with standard OData feeds, if you wish to limit the fields returned, you can add a $select parameter to the query, along with other standard OData URL parameters, such as $filter, $orderby, $skip, and $top. See the help documentation for more information on supported OData queries.
With the connection and Workspace configured, you are ready to connect to SAP Ariba Procurement data from RunMyProcess.
Retrieve SAP Ariba Procurement Data from RunMyProcess DigitalSuite Studio
With the connection to SAP Ariba Procurement and OData endpoints created, we are ready to add SAP Ariba Procurement data to RunMyProcess for Retrieval.
Create a Provider
- Log into RunMyProcess and open DigitalSuite Studio.
- Click Resources to bring up the Resources page, then select then the CONNECTORS tab.
- Click the + (New Provider) button to create a new provider, choose the account to use, then click Confirm.
- In the provider settings page, configure the following properties.
- URL: Set the OData endpoint in the Connect Cloud OData page: https://cloud.cdata.com/api/odata/{workspace_name}.
- Authentication Schema: Select Login/Password.
- Login: Specify a CData Connect Cloud username (e.g. [email protected]).
- Password: Specify the PAT of the Connect Cloud user.
- Fill in the same properties in the ACCEPTANCE and TEST tabs. Note: You can copy the configured settings by clicking 'Copy this configuration button,' then pasting the content in the new tab by clicking 'Paste previously copied configuration.'
- Click Save to save the properties.
Retrieve SAP Ariba Procurement Data by Creating a Connector
- In the CONNECTORS tab, click the button with three dots to create the provider, then select Add connector from the menu.
- In the following page, set Connector URL to the OData endpoint configured in Connect Cloud (e.g. https://cloud.cdata.com/api/odata/{workspace_name})
- Click Save then Launch to test the connector execution. Click Launch test to execute. The process is successful if you get the JSON response of your configured table information.
More Information & Free Trial
Now, you have created a provider and connector to retrieve SAP Ariba Procurement data. For more information on creating OData feeds from SAP Ariba Procurement (and more than 100 other data sources), visit the Connect Cloud page. Sign up for a free trial and start working with live SAP Ariba Procurement data in RunMyProcess.