Epicor Kinetic Connector¶
The Jitterbit Harmony Epicor Kinetic Connector establishes access to Epicor Kinetic.
The Epicor Kinetic connector provides an interface for creating an Epicor Kinetic connection, the foundation used for generating instances of Epicor Kinetic activities. These activities, once configured, interact with Epicor Kinetic through the connection.
The Epicor Kinetic connector is accessed from the design component palette's Connections tab (see Design Component Palette).
The Epicor connector was formerly named Epicor ERP.
This connector is used to first configure an Epicor Kinetic connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific Epicor Kinetic connection and its activities are referred to as an Epicor Kinetic endpoint:
Delete: Deletes object data from Epicor Kinetic and is intended to be used as a target in an operation.
Get: Retrieves object data from Epicor Kinetic and is intended to be used as a source in an operation.
Post: Inserts object data into Epicor Kinetic and is intended to be used as a target in an operation.
Put BAQ (UBAQ): Updates object data for a Business Activity Query in Epicor Kinetic and is intended to be used as a target in an operation.
Update: Updates object data in Epicor Kinetic and is intended to be used as a target in an operation.
Get BAQ: Retrieves object data from Epicor Kinetic using a BAQ (Business Activity Query) and is intended to be used as a source in an operation.
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
Prerequisites and Supported API Versions¶
The Epicor Kinetic connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The Epicor Kinetic connector has been verified to be compatible with Epicor Kinetic 10.2.500 and 11.2.400.
The Epicor Kinetic connector uses the Epicor REST API, available in a Swagger UI from
https://<epicor-host-name>/Server/api/help/. Epicor REST Services version 1 is supported. Epicor REST Services version 2 is not supported. Refer to the API documentation for information on the schema fields. (A login to Epicor is required; substitute your Epicor host name in the above URL.)
To use the Put BAQ (UBAQ) and Get BAQ activities, the Epicor Kinetic instance must support Business Activity Queries (BAQs). BAQ support is not required for the other activities (Delete, Get, Post, and Update).
If you experience issues with the Epicor Kinetic connector, these troubleshooting steps are recommended:
Ensure the Epicor Kinetic connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.epicor" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.
The video Jitterbit Basics - Epicor Kinetic to FTP shows how to use the Epicor Kinetic connector as a source for an operation with an FTP target.