Connect to SAP Concur Data as an External Data Source using PolyBase

PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for SAP Concur, you get access to your SAP Concur data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live SAP Concur data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above.

CData Connect AI provides a pure SQL Server interface for SAP Concur, allowing you to query data from SAP Concur without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to SAP Concur, leveraging server-side processing to return the requested SAP Concur data quickly.

Configure SAP Concur Connectivity for PolyBase

Connectivity to SAP Concur from PolyBase is made possible through CData Connect AI. To work with SAP Concur data from PolyBase, we start by creating and configuring a SAP Concur connection.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection

2. Select "SAP Concur" from the Add Connection panel
👁 Selecting a data source

3. Enter the necessary authentication properties to connect to SAP Concur.

   SAP Concur uses the OAuth 2 authentication standard. obtain the and by registering an app with SAP Concur. See the Getting Started section of the help documentation for an authentication guide.

   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add SAP Concur Connection page and update the User-based permissions. 👁 Updating permissions
   

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create. 👁 Creating a new PAT
   
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to SAP Concur data from Polybase.

Create an External Data Source for SAP Concur Data

After configuring the connection, you need to create a credential database for the external data source.

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to SAP Concur data.

NOTE: Set IDENTITY to your Connect AI username and set SECRET to your Personal Access Token.

CREATE DATABASE SCOPED CREDENTIAL ConnectCloudCredentials
WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';

Create an External Data Source for SAP Concur

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for SAP Concur with PolyBase:

CREATE EXTERNAL DATA SOURCE ConnectCloudInstance
WITH ( 
 LOCATION = 'sqlserver://tds.cdata.com:14333',
 PUSHDOWN = ON,
 CREDENTIAL = ConnectCloudCredentials
);

Create External Tables for SAP Concur

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to SAP Concur data from your SQL Server instance. The table column definitions must match those exposed by CData Connect AI. You can use the Data Explorer in Connect AI to see the table definition.

👁 Table definition in the Data Explorer (Salesforce is shown)

Sample CREATE TABLE Statement

Execute a CREATE EXTERNAL TABLE SQL command to create the external table(s), using the collation and setting the LOCATION to three-part notation for the connection, catalog, and table. The statement to create an external table based on a SAP Concur Departments would look similar to the following.

CREATE EXTERNAL TABLE Departments(
 Id COLLATE [nvarchar](255) NULL,
 OfficeId COLLATE [nvarchar](255) NULL,
 ...
) WITH ( 
 LOCATION='SAPConcur1.SAPConcur.Departments',
 DATA_SOURCE=ConnectCloudInstance
);

Having created external tables for SAP Concur in your SQL Server instance, you are now able to query local and remote data simultaneously. To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect AI today!