ERP-COMMANDbatch® Interface

Setup Guide
COMMANDbatch V1.8.8.0 & Later
1/31/14

Command Alkon Inc.

5168 Blazer Parkway
Dublin, Ohio 43017
1.800.624.1872
Fax: 614.793.0608
Part Number: 26215
 © 2003-2014 Command Alkon Incorporated. All rights reserved.
Command Alkon Incorporated believes the statements contained herein are accurate as
of the date of publication of this document. HOWEVER, COMMAND ALKON
INCORPORATED HEREBY DISCLAIMS ALL WARRANTIES EITHER EXPRESSED OR IMPLIED,
INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANT OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. In no event will Command Alkon Incorporated be
liable for any damages, including any lost profits, lost savings, or other incidental or
consequential damage arising out of the use of or inability to use any information
provided through this publication, even if Command Alkon Incorporated has been advised
of the possibility of such damages, or for any claim by any other party. Some states do
not allow the limitation or exclusion of liability or consequential damages, so the above
limitation may not apply.
This information is not intended to be an assertion of future action. The contents of this
document are for informational purposes only and are subject to change without notice.
Command Alkon Incorporated expressly reserves the right to change or withdraw current
products that may or may not have the same characteristics listed in this publication.
Should Command Alkon Incorporated modify its products in a way that may affect the
information contained in this publication, Command Alkon Incorporated assumes no
obligation whatever to inform any user of the modification.
This publication may contain technical inaccuracies or typographical errors. Command
Alkon Incorporated assumes no responsibility for any errors that may appear in this
manual. This publication is intended only for the direct benefit of users of Command
Alkon Incorporated products. This manual may not be used for any purposes other than
those for which it is provided. Information disclosed herein was originated by and is the
property of Command Alkon Incorporated, and, except for rights granted by written
consent, such information shall not be disclosed, disseminated, or duplicated in whole or
in part. Command Alkon Incorporated reserves all patent, proprietary, design,
manufacturing, use, and reproduction rights.

www.commandalkon.com

Command Alkon Incorporated

1800 International Park Drive, Suite 400
Birmingham, AL 35243-4232
(205) 879-3282

5168 Blazer Parkway

Dublin, OH 43017-1339
(614) 799-6650
For a list of all Command Alkon locations, go to:
http://www.commandalkon.com/locations.asp
COMMANDseries (and the names of its components, such as COMMANDconcrete and
COMMANDnetwork), Spectrum, Eagle, and COMMANDbatch are registered trademarks of
Command Alkon Incorporated. All rights reserved.
Windows is a registered trademark of Microsoft Corporation in the United States and
other countries.
Hydro-Control is a registered trademark of Hydronix Limited, United Kingdom.
Verifi is a registered trademark of RS Solutions, Cincinnati, Ohio, USA.

2 1/31/14
 Contents

Contents ........................................................................................ 3

Introduction .................................................................................. 4
Purpose ................................................................................................ 4
Audience ............................................................................................... 4
Revision Summary ................................................................................. 4

ERP-COMMANDbatch Interface ...................................................... 5

Prerequisite Software .............................................................................. 6
EDX Server Installation ........................................................................... 6
EDX Client Installation on COMMANDbatch PC ............................................ 8
ERP User Security ................................................................................ 10
COMMANDbatch Configuration ............................................................... 11
Color Highlighting for Notify or Sync-Allowed Records ................................ 13

1/31/14 3
 Introduction

Topics in This Section

Purpose
Audience
Revision Summary

Purpose
This guide explains how to configure COMMANDbatch and EDX so that
COMMANDbatch can receive Customer, Project and Order data from a master
system such as COMMANDseries, or in the absence of COMMANDseries, from
a third party ERP (Enterprise Resource Planning) system such as SAP.

Audience
This guide should only be used by Command Alkon installation and service
personnel, or plant/management personnel specifically authorized to
configure COMMANDbatch.

Revision Summary
CMDbatch
Date Version Revision
Dec. 10, 2013 1.8.8.0 Document created.
Jan. 31, 2014 1.8.8.0 Revised the screen example of the COMMANDedx
Configuration form to show fewer Outbound Data
options.

4 1/31/14
 ERP-COMMANDbatch Interface

This interface allows COMMANDbatch to receive Customer, Project and Order

data from a master system such as COMMANDseries, or in the absence of
COMMANDseries, from a third party ERP (Enterprise Resource Planning)
system such as SAP.
EDX receives Customer, Project, and Order data in XML messages from the
master system and makes them available to COMMANDbatch which accepts
the messages and updates the corresponding data in its own database.
If there is an issue processing an XML message, COMMANDbatch provides
details to the master or third party system in a response message.

Notes: • Orders can never be deleted, only canceled.

• Future COMMANDbatch releases may be able to publish
Customer, Project and Order data.

1/31/14 5
 Prerequisite Software
• COMMANDbatch 1.8.8.0 or later
• Microsoft .NET 4.0
• EDX 3.2.7.0 or later
• COMMANDbatchPluginCPM-1.8.8.0

EDX Server Installation

If an EDX Server is not currently installed, install it on a separate machine
from the COMMANDbatch PC.

1. Verify that the full version of .NET 4.0 is installed.

Note: The .NET 4.0 installer (dotNetFx40_Full_x86_x64.exe) is available

on the install media under the EDX Integration folder.

2. Run the COMMANDedx installer program.

3. On the Installation Directory window, choose a destination
directory. The default destination is:
Windows XP:

Windows 7:

4. On the Auto Update Selection window, leave “Server” and

“Client” unchecked.

5. On the Component Selection window, select “Server Only”.

6 1/31/14
 6. On the Client Architecture Selection window, check “Force bit
(x86)”.

7. On the Server and History Database Options windows, select the

database and enter the username, password, server name, and
database name (IP Address or Computer Name).
Server Database Options

History Database Options

1/31/14 7
 EDX Client Installation on COMMANDbatch PC
Only the EDX Client is installed on the COMMANDbatch PC.

1. Verify that the full version of .NET 4.0 is installed.

Note: The .NET 4.0 installer (dotNetFx40_Full_x86_x64.exe) is available

on the install media under the EDX Integration folder.

2. Run the COMMANDedx installer program.

3. On the Installation Directory window, choose a destination
directory. The default destination is:
Windows XP:

Windows 7:

4. On the Auto Update Selection window, leave “Server” and

“Client” unchecked.

5. On the Component Selection window, select “Client Only”.

6. On the Client Architecture Selection window, check “Force bit

(x86)”.

8 1/31/14
 7. On the EDX Server Address Selection window, enter the EDX
Server Address or host name. (This address is not validated
during the installation.)

8. On the Client Database Options window, select the client

database (MS SQL or Oracle) and enter the username, password,
and server name for the Client database (either the IP Address or
the Computer Name).
Client Database Options

1/31/14 9
 ERP User Security
The CPM User Security Group can be used with the ERP-COMMANDbatch
Interface.
The CPM User group allows you to set critical fields to read-only on the
following forms to prevent the fields from being edited by local users or
unexpectedly overwritten:
Admix Designs, Customers, Dose Calculation, Drivers, Item Locations,
Materials, Mix Designs, Orders, Project Lines, Projects, and Trucks

To assign a User to the CPM Group:

1. Open the Groups form and select the CPM group.

2. Under the User ID column, select the Users to be added (one user
per row).
3. If you need to add users, close the Groups form and open the
Users form, add the users and then return to the Groups form to
select the users.
4. Save your changes.
When a user is assigned to the CPM User Group, even though specific fields
within a form may be read only, permissions are all defaulted to ‘Granted’ as
far as the ability to Delete and Edit Records within these forms.

To prevent CPM users from deleting/editing CPM data:

1. Open the Groups form and select the CPM group.

2. Click the Group Authorizations button to pull up the “Object

Authorizations for Group” form.
3. Change the Delete Privilege, Edit Privilege, etc. columns, to
‘Revoked’ for each form privilege you do NOT want assigned to
the group.

Caution!
Leave the “Execute Privilege” column set to ‘Granted’ so
that all other granted privileges are valid. If you do not do
this, the user cannot even access the form.

4. Save your changes.

10 1/31/14
 COMMANDbatch Configuration
1. Log in to COMMANDbatch and open the COMMANDedx
Configuration form.

a) On the Configuration tab, check the “Enabled” box and set Inbound
Data entities to match what is shown in the following screen example.

2. On the Interfaces tab, check the “Publish Scope” box.

Note: When “Publish Scope” is checked, the Plant Code on the Plants form
must be set to the Unique Plant Code prior to Plugin Installation.

3. On the Behavior tab, check the “Enable Alerts” box to allow error
messages to be presented to the Batch Operator.

4. Save your changes to the COMMANDedx Configuration form.

5. On the Rules tab of the System Parameters form:
— Uncheck “Allow Changes to Shipped Orders”

1/31/14 11
 — Uncheck “Reset Shipped Qty on Changed Mix”
— Uncheck “Require Reconciliation” (unless the customer wants this
feature)

6. Save your changes on the System Parameters form.

7. On the Plants form, set the Plant Code to a unique plant-specific
number that matches what the third party will use for the site:

a) Right click on the Plant field and select “Rename”. The Plant field
becomes editable.
b) Enter the correct Plant Code and save your changes.
c) Restart COMMANDbatch so your changes take effect.
8. Install the COMMANDbatchPluginCPM:
a) Run the COMMANDbatchPluginCPM executable file from the
COMMANDbatch install CD.
b) Click Next at the Welcome window.
c) Select or change the destination and click Install.
d) When installation is complete, click Next and then Finish.
9. Restart the EDX Client Service in order to publish the Scope to the
EDX Server.

12 1/31/14
 Color Highlighting for Notify or Sync-Allowed Records
Records for entities that are set to “Allow” on the COMMANDedx Configuration
form (see COMMANDbatch Configuration) use the following color scheme.
• Records for synced entities are highlighted in gray.
• Records for synced entities that have been modified are highlighted in
orange.
• Records for non-synced entities are highlighted in blue.
Records for entities that are set to anything other than “Allow” do not use the
above color scheme.

Note: • The Highlight Duration field on the Appearance tab of the

COMMANDedx Configuration form specifies how many days that
records for modified synced entities are highlighted in orange.

1/31/14 13