Learn more
 

Ready to get started?

Download a free trial of the Epicor Kinetic ODBC Driver to get started:

 Download Now

Learn more:

Epicor Kinetic Icon Epicor Kinetic ODBC Driver

The Epicor Kinetic ODBC Driver is a powerful tool that allows you to connect with live Epicor Kinetic data, directly from any applications that support ODBC connectivity.

Access Epicor Kinetic like you would a database - read, write, and update Sales Orders, Purchase Orders, Accounts, etc. through a standard ODBC Driver interface.

In this article

Related articles

Epicor Kinetic Reporting and Star Schemas in OBIEE


Create a star schema that shows perspectives on Epicor Kinetic facts in real time.

The CData ODBC Driver for Epicor Kinetic is a standard database driver that can integrate real-time access to Epicor Kinetic data into your data warehouse or directly into your reporting tool. This article shows how to bypass the data warehouse and import operational Epicor Kinetic data into Oracle Business Intelligence Enterprise Edition (OBIEE).

See the knowledge base for ODBC integrations with ETL tools like Informatica PowerCenter. For an ETL solution into Oracle Warehouse Builder, use the driver with the Oracle ODBC Gateway to Access Epicor Kinetic Data as a Remote Oracle Database.

Connect to Epicor Kinetic as an ODBC Data Source

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.

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.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Import Epicor Kinetic Metadata

Follow the steps below to use the OBIEE Client Tools to import Epicor Kinetic metadata into an OBIEE repository. You can then integrate Epicor Kinetic data into your business models.

  1. Open the Administration Tool and click File -> New Repository.

  2. In the Connection Type menu, select ODBC 3.5 and select the CData DSN.
  3. Select the metadata types you want to import under the Relational Sources option and then select Epicor Kinetic tables.
You can now create star schemas based on Epicor Kinetic tables: