Analyze Epicor Kinetic Data in R

Access Epicor Kinetic data with pure R script and standard SQL on any machine where R and Java can be installed. You can use the CData JDBC Driver for Epicor Kinetic and the RJDBC package to work with remote Epicor Kinetic data in R. By using the CData Driver, you are leveraging a driver written for industry-proven standards to access your data in the popular, open-source R language. This article shows how to use the driver to execute SQL queries to Epicor Kinetic and visualize Epicor Kinetic data by calling standard R functions.

Install R

You can match the driver's performance gains from multi-threading and managed code by running the multithreaded Microsoft R Open or by running open R linked with the BLAS/LAPACK libraries. This article uses Microsoft R Open 3.2.3, which is preconfigured to install packages from the Jan. 1, 2016 snapshot of the CRAN repository. This snapshot ensures reproducibility.

Load the RJDBC Package

To use the driver, download the RJDBC package. After installing the RJDBC package, the following line loads the package:

Connect to Epicor Kinetic as a JDBC Data Source

You will need the following information to connect to Epicor Kinetic as a JDBC data source:

• Driver Class: Set this to cdata.jdbc.epicorkinetic.epicorKineticDriver
• Classpath: Set this to the location of the driver JAR. By default this is the lib subfolder of the installation folder.

The DBI functions, such as dbConnect and dbSendQuery, provide a unified interface for writing data access code in R. Use the following line to initialize a DBI driver that can make JDBC requests to the CData JDBC Driver for Epicor Kinetic:

You can now use DBI functions to connect to Epicor Kinetic and execute SQL queries. Initialize the JDBC connection with the dbConnect function.

To successfully connect to your ERP instance, you must specify the following connection properties:

• Url:the URL of the server hosting your ERP instance. For example, https://myserver.EpicorSaaS.com
• ERPInstance: the name of your ERP instance.
• User: the username of your account.
• Password: the password of your account.
• Service: the service you want to retrieve data from. For example, BaqSvc.

In addition, you may also set the optional connection properties:

• ApiKey: An optional key that may be required for connection to some services depending on your account configuration.
• ApiVersion: Defaults to v1. May be set to v2 to use the newer Epicor API.
• Company: Required if you set the ApiVersion to v2.

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Epicor Kinetic JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

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

Below is a sample dbConnect call, including a typical JDBC connection string:

Schema Discovery

The driver models Epicor Kinetic APIs as relational tables, views, and stored procedures. Use the following line to retrieve the list of tables:

Execute SQL Queries

You can use the dbGetQuery function to execute any SQL query supported by the Epicor Kinetic API:

You can view the results in a data viewer window with the following command:

Plot Epicor Kinetic Data

You can now analyze Epicor Kinetic data with any of the data visualization packages available in the CRAN repository. You can create simple bar plots with the built-in bar plot function: