Build SAP Ariba Procurement-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for SAP Ariba Procurement enables users to access live SAP Ariba Procurement data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping SAP Ariba Procurement data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from SAP Ariba Procurement to Google BigQuery,

Upload the CData JDBC Driver for SAP Ariba Procurement to Google Data Fusion

Upload the CData JDBC Driver for SAP Ariba Procurement to your Google Data Fusion instance to work with live SAP Ariba Procurement data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatasaparibaprocurement-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver 👁 Image
   
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.saparibaprocurement) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.saparibaprocurement.SAPAribaProcurementDriver)
   👁 Configuring the driver (Salesforce is shown.)
   
5. Click "Finish"

Connect to SAP Ariba Procurement Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live SAP Ariba Procurement data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver 👁 Adding a database source
   
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-saparibaprocurement)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for SAP Ariba Procurement. For example:
     
     jdbc:saparibaprocurement:RTK=5246...;ANID=AN02000000280;API=PurchaseOrdersBuyerAPI-V1;APIKey=wWVLn7WTAXrIRMAzZ6VnuEj7Ekot5jnU;AuthScheme=OAuthClient;InitiateOAuth=GETANDREFRESH;

     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.

     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.

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     
   • Set Import Query to a SQL query that will extract the data you want from SAP Ariba Procurement, i.e.:
     SELECT * FROM Orders
   👁 Configuring the database source
   
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like saparibaprocurement-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert SAP Ariba Procurement data into
   👁 Configuring the BigQuery sink
   

With the Source and Sink configured, you are ready to pipe SAP Ariba Procurement data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from SAP Ariba Procurement and import it into Google BigQuery. 👁 Image

While this is a simple pipeline, you can create more complex SAP Ariba Procurement pipelines with transforms, analytics, conditions, and more. 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 Google Data Fusion today.