Ready to get started?

Download a free trial of the SAP Ariba Procurement Driver to get started:

 Download Now

Learn more:

SAP Ariba Procurement Icon SAP Ariba Procurement JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SAP Ariba Procurement.

How to connect and process SAP Ariba Procurement Data from Azure Databricks



Use CData, Azure, and Databricks to perform data engineering and data science on live SAP Ariba Procurement Data

Databricks is a cloud-based service that provides data processing capabilities through Apache Spark. When paired with the CData JDBC Driver, customers can use Databricks to perform data engineering and data science on live SAP Ariba Procurement data. This article walks through hosting the CData JDBC Driver in Azure, as well as connecting to and processing live SAP Ariba Procurement data in Databricks.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live SAP Ariba Procurement data. When you issue complex SQL queries to SAP Ariba Procurement, the driver pushes supported SQL operations, like filters and aggregations, directly to SAP Ariba Procurement and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze SAP Ariba Procurement data using native data types.

Install the CData JDBC Driver in Azure

To work with live SAP Ariba Procurement data in Databricks, install the driver on your Azure cluster.

  1. Navigate to your Databricks administration screen and select the target cluster.
  2. On the Libraries tab, click "Install New."
  3. Select "Upload" as the Library Source and "Jar" as the Library Type.
  4. Upload the JDBC JAR file (cdata.jdbc.saparibaprocurement.jar) from the installation location (typically C:\Program Files\CData[product_name]\lib).

Connect to SAP Ariba Procurement from Databricks

With the JAR file installed, we are ready to work with live SAP Ariba Procurement data in Databricks. Start by creating a new notebook in your workspace. Name the notebook, select Python as the language (though Scala is available as well), and choose the cluster where you installed the JDBC driver. When the notebook launches, we can configure the connection, query SAP Ariba Procurement, and create a basic report.

Configure the Connection to SAP Ariba Procurement

Connect to SAP Ariba Procurement by referencing the class for the JDBC Driver and constructing a connection string to use in the JDBC URL. Additionally, you will need to set the RTK property in the JDBC URL (unless you are using a Beta driver). You can view the licensing file included in the installation for information on how to set this property.

driver = "cdata.jdbc.saparibaprocurement.SAPAribaProcurementDriver"
url = "jdbc:saparibaprocurement:RTK=5246...;ANID=AN02000000280;API=PurchaseOrdersBuyerAPI-V1;APIKey=wWVLn7WTAXrIRMAzZ6VnuEj7Ekot5jnU;AuthScheme=OAuthClient;InitiateOAuth=GETANDREFRESH"

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the SAP Ariba Procurement JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.saparibaprocurement.jar

Fill in the connection properties and copy the connection string to the clipboard.

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:

  1. The provider obtains an access token from SAP Ariba and uses it to request data.
  2. The provider refreshes the access token automatically when it expires.
  3. The OAuth values are saved in memory relative to the location specified in OAuthSettingsLocation.

Load SAP Ariba Procurement Data

Once the connection is configured, you can load SAP Ariba Procurement data as a dataframe using the CData JDBC Driver and the connection information.

remote_table = spark.read.format ( "jdbc" ) \
	.option ( "driver" , driver) \
	.option ( "url" , url) \
	.option ( "dbtable" , "Orders") \
	.load ()

Display SAP Ariba Procurement Data

Check the loaded SAP Ariba Procurement data by calling the display function.

display (remote_table.select ("DocumentNumber"))

Analyze SAP Ariba Procurement Data in Azure Databricks

If you want to process data with Databricks SparkSQL, register the loaded data as a Temp View.

remote_table.createOrReplaceTempView ( "SAMPLE_VIEW" )

The SparkSQL below retrieves the SAP Ariba Procurement data for analysis.

% sql

SELECT DocumentNumber, Revision FROM Orders WHERE OrderStatus = 'CHANGED'

The data from SAP Ariba Procurement is only available in the target notebook. If you want to use it with other users, save it as a table.

remote_table.write.format ( "parquet" ) .saveAsTable ( "SAMPLE_TABLE" )

Download a free, 30-day trial of the CData JDBC Driver for SAP Ariba Procurement and start working with your live SAP Ariba Procurement data in Azure Databricks. Reach out to our Support Team if you have any questions.