Access SAP Ariba Procurement Data as a Remote Oracle Database

The Oracle Database Gateway for ODBC and Heterogeneous Services technology enable you to connect to ODBC data sources as remote Oracle databases. This article shows how to use the CData ODBC Driver for SAP Ariba Procurement to create a database link from SAP Ariba Procurement to Oracle and to query SAP Ariba Procurement data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to SAP Ariba Procurement as an ODBC Data Source

Information for connecting to SAP Ariba Procurement follows, along with different instructions for configuring a DSN in Windows and Linux environments.

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.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Note: If you need to modify the DSN or create other SAP Ariba Procurement DSNs, you must use a system DSN and the bitness of the DSN must match your Oracle system. You can access and create 32-bit DSNs on a 64-bit system by opening the 32-bit ODBC Data Source Administrator from C:\Windows\SysWOW64\odbcad32.exe.

Linux

If you are installing the CData ODBC Driver for SAP Ariba Procurement in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData SAPAribaProcurement Source]
Driver = CData ODBC Driver for SAP Ariba Procurement
Description = My Description
ANID = AN02000000280
API = PurchaseOrdersBuyerAPI-V1
APIKey = wWVLn7WTAXrIRMAzZ6VnuEj7Ekot5jnU
AuthScheme = OAuthClient
InitiateOAuth = GETANDREFRESH

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Set Connection Properties for Compatibility with Oracle

The driver provides several connection properties that streamline accessing SAP Ariba Procurement data just as you would an Oracle database. Set the following properties when working with SAP Ariba Procurement data in SQL*Plus and SQL Developer. For compatibility with Oracle, you will need to set the following connection properties, in addition to authentication and other required connection properties.

• MapToWVarchar=False

  Set this property to map string data types to SQL_VARCHAR instead of SQL_WVARCHAR. By default, the driver uses SQL_WVARCHAR to accommodate various international character sets. You can use this property to avoid the ORA-28528 Heterogeneous Services data type conversion error when the Unicode type is returned.

• MaximumColumnSize=4000

  Set this property to restrict the maximum column size to 4000 characters.

• IncludeDualTable=True

  Set this property to mock the Oracle DUAL table. SQL Developer uses this table to test the connection.

Linux Configuration

In Linux environments, Oracle uses UTF-8 to communicate with the unixODBC Driver manager, whereas the default driver encoding is UTF-16. To resolve this, open the file /opt/cdata/cdata-driver-for-saparibaprocurement/lib/cdata.odbc.saparibaprocurement.ini in a text editor and set the encoding.

cdata.odbc.saparibaprocurement.ini

[Driver]
DriverManagerEncoding = UTF-8

Configure the ODBC Gateway, Oracle Net, and Oracle Database

Follow the procedure below to set up an ODBC gateway to SAP Ariba Procurement data that enables you to query live SAP Ariba Procurement data as an Oracle database.

1. Create the file initmysaparibaprocurementdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:

   initmysaparibaprocurementdb.ora

   HS_FDS_CONNECT_INFO = "CData SAPAribaProcurement Sys"

2. Add an entry to the listener.ora file. This file is located in oracle-home-directory/NETWORK/admin.

   If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = mysaparibaprocurementdb)
    (ORACLE_HOME = your-oracle-home)
    (PROGRAM = dg4odbc)
    )
    )
   

   If you are using Heterogeneous Services, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = mysaparibaprocurementdb)
    (ORACLE_HOME = your-oracle-home)
    (PROGRAM = hsodbc)
    )
    )
   

3. Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:

   tnsnames.ora

   mysaparibaprocurementdb =
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
    (CONNECT_DATA=(SID=mysaparibaprocurementdb))
    (HS=OK)
    ) 
   

4. Restart the listener.

5. Test the configuration with the following command:

   tnsping mysaparibaprocurementdb

6. Open SQL*Plus and create the database link with the command below:

   CREATE DATABASE LINK mysaparibaprocurementdb CONNECT TO "user" IDENTIFIED BY "password" USING 'mysaparibaprocurementdb';

You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):

SELECT * from "Orders"@mysaparibaprocurementdb WHERE OrderStatus = 'CHANGED';