Build Data Flows from SAP Ariba Procurement to SQL Server using SSIS

Using SQL Server as a backup for critical business data provides an essential safety net against loss. Backing up data to SQL Server enables business users to more easily connect that data with features like reporting, analytics, and more.

This example demonstrates how to use the CData SSIS Tasks for SAP Ariba Procurement inside of a SQL Server SSIS workflow to transfer SAP Ariba Procurement data into a Microsoft SQL Server database.

Add the Components

To get started, add a new SAP Ariba Procurement source and SQL Server ADO.NET destination to a new data flow task.

Create a New Connection Manager

Follow the steps below to save SAP Ariba Procurement connection properties in a connection manager.

1. In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
2. In the Connection Manager type menu, select SAPAribaProcurement. The CData SAP Ariba Procurement Connection Manager is displayed.
3. Configure connection properties.

   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.
   👁 Configuring a connection (Salesforce is shown).
   

Configure the SAP Ariba Procurement Source

Follow the steps below to specify the query to be used to extract SAP Ariba Procurement data.

1. Double-click the SAP Ariba Procurement source to open the source component editor.
2. In the Connection Manager menu, select the connection manager previously created.
3. Specify the query to use for the data extraction. For example:

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

   👁 The SQL query to retrieve records. (Salesforce is shown.)
   
4. Close the SAP Ariba Procurement Source control and connect it to the ADO.NET Destination.

Configure the SQL Server Destination

Follow the steps below to specify the SQL server table to load the SAP Ariba Procurement data into.

1. Open the ADO.NET Destination and add a New Connection. Enter your server and database information here.
2. In the Data access mode menu, select "table or view".
3. In the Table Or View menu, select the table or view to populate.
4. Configure any properties you wish to on the Mappings screen. 👁 The mappings from the SSIS source component to SQL Server. (Salesforce is shown.)
   

Run the Project

You can now run the project. After the SSIS Task has finished executing, your database will be populated with SAP Ariba Procurement data.