ETL SAP Ariba Source in Oracle Data Integrator

Leverage existing skills by using the JDBC standard to read and write to SAP Ariba Source: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for SAP Ariba Source connects real-time SAP Ariba Source data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with SAP Ariba Source just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the SAP Ariba Source APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- SAP Ariba Source to Oracle. After reverse engineering a data model of SAP Ariba Source entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR (cdata.jdbc.saparibasource.jar) and .lic file (cdata.jdbc.saparibasource.lic), located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: ~/.odi/oracledi/userlib and $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\odi\oracledi\userlib and %APPDATA%\odi\agent\lib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of SAP Ariba Source data. After reverse engineering, you can query real-time SAP Ariba Source data and create mappings based on SAP Ariba Source tables.

1. In ODI, connect to your repository and click New -> Model and Topology Objects.
2. On the Model screen of the resulting dialog, enter the following information:
   • Name: Enter SAPAribaSource.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter SAPAribaSource.
   • Context: Select Global.
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter SAPAribaSource.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.saparibasource.SAPAribaSourceDriver
   • URL: Enter the JDBC URL containing the connection string.

     In order to connect with SAP Ariba Source, set the following:

     • API: Specify which API you would like the provider to retrieve SAP Ariba data from. Select the Supplier, Sourcing Project Management, or Contract API based on your business role (possible values are SupplierDataAPIWithPaginationV4, SourcingProjectManagementAPIV2, or ContractAPIV1).
     • DataCenter: The data center where your account's data is hosted.
     • Realm: The name of the site you want to access.
     • Environment: Indicate whether you are connecting to a test or production environment (possible values are TEST or PRODUCTION).

     If you are connecting to the Supplier Data API or the Contract API, additionally set the following:

     • User: Id of the user on whose behalf API calls are invoked.
     • PasswordAdapter: The password associated with the authenticating User.

     If you're connecting to the Supplier API, set ProjectId to the Id of the sourcing project you want to retrieve data from.

     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 Source JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.saparibasource.jar

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

     Below is a typical connection string:

     jdbc:saparibasource:API=SupplierDataAPIWithPagination-V4;APIKey=wWVLn7WTAXrIRMAzZ6VnuEj7Ekot5jnU;Environment=SANDBOX;Realm=testRealm;AuthScheme=OAuthClient;InitiateOAuth=GETANDREFRESH
4. On the Physical Schema screen, enter the following information:
   • Name: Select from the Drop Down menu.
   • Database (Catalog): Enter CData.
   • Owner (Schema): If you select a Schema for SAP Ariba Source, enter the Schema selected, otherwise enter SAPAribaSource.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for SAP Ariba Source, enter the Schema selected, otherwise enter SAPAribaSource.
5. In the opened model click Reverse Engineer to retrieve the metadata for SAP Ariba Source tables.

Edit and Save SAP Ariba Source Data

After reverse engineering you can now work with SAP Ariba Source data in ODI. To edit and save SAP Ariba Source data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes.

Create an ETL Project

Follow the steps below to create an ETL from SAP Ariba Source. You will load Vendors entities into the sample data warehouse included in the ODI Getting Started VM.

1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

   Alternatively you can use SQLPlus. From a command prompt enter the following:

   sqlplus / as sysdba
2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Vendors table in SAP Ariba Source: CREATE TABLE ODI_DEMO.TRG_VENDORS (CATEGORY NUMBER(20,0),SMVendorID VARCHAR2(255));
3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
4. Click Reverse Engineer. The TRG_VENDORS table is added to the model.
5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
6. Drag the TRG_VENDORS table from the Sales Administration model onto the mapping.
7. Drag the Vendors table from the SAP Ariba Source model onto the mapping.
8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
9. Open the Physical tab of the Mapping Editor and click VENDORS_AP in TARGET_GROUP.
10. In the VENDORS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load SAP Ariba Source data into Oracle.