Skip to end of metadata
Go to start of metadata

 

 

This document is written for the person at goodsolutions that installs the standard integration and describes what is needed to be done at the client side of an Standard ERP Integration.

Table of contents

 

Preparation


If you haven't already, familiarise yourself with the document "Guide to RS Production Standard ERP integration".

For Good Solutions to be able to do our work there need to exist a SQL-database which will be used by the integration and that has a username and password to the database that can read and write data to tables mentioned later. When the database is ready, provide Good Solutions with the username and password, as well as the name of the database and IP or URL to the database.

Compatibility

The user has to be a SQL user, a Window user will not work

1. Create database tables

Open file "Create integration tables" in a text editor and replace "XXXXXXXXXXXXXXXXXX" at the first row to the name of your database and execute the query in your SQL-database. The SQL query will create the integration tables where RS Production loads orders and store the ERP reports. For table specifications, see document "How to work with the standard ERP-integration".

Table names

In our definition of "standard integration" the table names has to be "ERPOrders" and "ERPReports" otherwise it will be viewed as a customisation.

2. Installing a integration server

If the RS Production Server can not reach your SQL-database, there also needs to be a Integration Server from Good Solutions installed and configured so it can communicate with the database.

Optional

This may be done by Good Solutions, depending on what has been arranged.

Configure

After the server has been installed, download files StandardERPIntegration.dll and StandardERPDataModel.dll from docs.rsproduction.se:8090/x/pQAQ and put them in the folder called "External dependencies" and then add the <guid> below to the <DataManagers> tag in your installation file.

Case sensitivity

The tags are case sensitive, the characters has to remain lower or upper case otherwise they will not be recognised by the server.

Guid
<guid>5ff13a0b-575f-4c74-bc16-c1291839685c</guid><!-- PythonOrderIntegrationInstance -->
Installation file example
<?xml version="1.0"?>
<SystemConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  ...
  <DataManagers>
    ...
    <guid>5ff13a0b-575f-4c74-bc16-c1291839685c</guid><!-- PythonOrderIntegrationInstance -->
  </DataManagers>
  ...
</SystemConfiguration>

3. Binding planning groups

In order to have articles and orders automatically displayed in Operator Tools, their assigned planning group has to be connected to a measure point. To do this, search for "PlanningGroup" in RS Start, you have come to the right page if it says "PLANNINGGROUP" in the top left corner after you clicked on a search result.

The PlanningGroup page list all planning groups that have been added by the integration, you need to go through all applicable planning groups and select what measure point they belong to.

Note

Planning groups will only be added to RS Productions after the integration is fully up and running.

Attachments

  File Modified
Text File Create integration tables.sql.txt SQL query to create tables in a database. May 24, 2018 by Christoffer Olofsson
PDF File Guide to RS Production Standard ERP integration.pdf How standard integration works. May 24, 2018 by Christoffer Olofsson
PDF File How to work with the standard ERP-integration.pdf SQL tables specifications. May 24, 2018 by Christoffer Olofsson

  • No labels