Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Asn-Commandbatch Interface Setup Guide

Download as pdf or txt
Download as pdf or txt
You are on page 1of 15

ASN-COMMANDbatch® Interface

Setup Guide
COMMANDbatch V1.8.8.0 & Later
2/3/14

Command Alkon Inc.


5168 Blazer Parkway
Dublin, Ohio 43017
1.800.624.1872
Fax: 614.793.0608
Part Number: 26210
© 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 2/3/14
Contents

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

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

ASN-COMMANDbatch Interface ...................................................... 5


Prerequisite Software .............................................................................. 6
EDX Server Installation ........................................................................... 6
EDX Client Installation on COMMANDbatch PC ............................................ 8
ASN User Security .................................................................................. 9
COMMANDbatch Configuration and Plugin Installation ................................ 10
General Operation ................................................................................ 12
Changes Allowed by APEX after a Shipment is Accepted ............................ 13
Correcting Shipments That Are Accidentally Accepted ................................ 14
Multiple Materials within a Shipment ....................................................... 14
Matching Local Receipts to an APEX Shipment .......................................... 15

2/3/14 3
Introduction

Topics in This Section


Purpose
Audience
Revision Summary

Purpose
This guide explains how to configure COMMANDbatch and EDX so that the
APEX system can send material shipment data to COMMANDbatch, and
COMMANDbatch can acknowledge receipt of the shipments and then process
them as inventory receipts.

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
Sep. 16, 2013 1.8.6.2 Document created.
Sep. 24, 2013 1.8.7.0 • Added notes to the “Prerequisite Software”
section regarding software requirements when
the ASN interface is installed on systems that
are currently running CPM.
• Removed section on configuring the
COMMANDbatch Plugin because the “Publish
Scope” functionality now does this.
• Added step to “COMMANDbatch Configuration”
section for installing the plugin.
Nov. 4, 2013 1.8.8.0 Added a section on “ASN User Security”.
Nov. 6, 2013 1.8.8.0 Revised “COMMANDbatch Configuration” section:
• Added screen shot for renaming Plant Code.
• Changed “RMR” to “CPM” in the plugin name.
Feb. 3, 2014 1.8.8.0 Corrected screen examples of COMMANDedx
Configuration form which no longer shows an
“Enable Shipment Schedule” checkbox.

4 2/3/14
ASN-COMMANDbatch Interface

The ASN (Advance Shipment Notification) feature allows COMMANDbatch and


Apex systems to exchange messages in XML for scheduled deliveries and
actual receipts of materials.
When a material delivery is scheduled, Apex sends a Shipment message to
the COMMANDbatch plant that will receive the delivery. COMMANDbatch
accepts the Shipment notice and presents the information to the operator (as
a Pending Shipment on the Shipments form).

Important!
In order for Apex and COMMANDbatch to communicate correctly,
Material Codes need to be exactly the same on both systems;
otherwise the messages will be rejected.

A Shipment message contains, at a minimum, the following information and


possibly more that is not required:
• Shipment ID
• Ticket Code
• Shipment Date/Time
• PO Code
• Equipment Type
— Truck, train, etc
• Equipment Code
— Truck Code, etc
• Scheduled Delivery Date/Time
• Shipped from information
• Hauler code
• Product Code
• Product Description
• Delivery Amount / UOM
Once a Shipment has been sent to a COMMANDbatch plant (but not
processed), the APEX user can send changes or cancel it entirely.
When the delivery conveyance arrives, authorized COMMANDbatch users can
process the delivery (by changing the Pending Shipment to an Inventory
Receipt on the Shipments form). Once the delivery has been processed,
COMMANDbatch sends an accepted ReceiveDelivery message to Apex to
complete the transaction.

2/3/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 2/3/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

2/3/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 2/3/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

ASN User Security


To restrict users from being able to edit the Qty field on the COMMANDbatch
Shipments form, assign them to the ASN User Group as follows:

1. Open the Groups form and select the ASN 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.

2/3/14 9
COMMANDbatch Configuration and Plugin Installation
1. Log in to COMMANDbatch and open the COMMANDedx
Configuration form.

2. On the Configuration tab, check the “Enabled” box.

3. 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.

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

5. Save your changes to the COMMANDedx Configuration form.


6. Once EDX is enabled, “Require Reconciliation” is automatically
turned on. Unless the customer wants this feature, go to the
Rules tab of the System Parameters form and disable it.

10 2/3/14
7. Save your changes on the System Parameters form.
8. 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.
9. 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.
10. Restart the EDX Client Service in order to publish the Scope to the
EDX Server.

2/3/14 11
General Operation
When APEX sends a Shipment to COMMANDbatch, a record of the transaction
appears on the Shipments form as a "Pending Delivery".

While a Shipment is in the "Pending" state, APEX can cancel the shipment
(which removes it from the Shipments form), or APEX can send a change to
modify the quantity, material, etc.
Once the delivery arrives at the plant, the COMMANDbatch operator can
change the Status of the "Pending Delivery" to an Inventory Receipt using the
dropdown list on the "Status" column and saving the record.
The operator can also assign the inventory to a specific bin, tank or silo using
the Device field’s dropdown list.

After the status of the Shipment record has been changed to "Receipt (+)"
and saved:
• COMMANDbatch sends an Accepted "ReceiveDelivery" message to APEX.
• The Shipment record is cleared from the current view of the form.

Tip!
To view cleared Shipment records for the selected date (defaults
to the current date), click the "Show All" button at the top left of
the Shipments form.

• The cleared Shipment record becomes a record on the Inventory Receipts


form, and the On Hand Qty for the material is updated on the On Hand
Inventory form. (See the following two screen examples.)

12 2/3/14
Changes Allowed by APEX after a Shipment is Accepted
Once a Shipment has been accepted and turned into an Inventory Receipt,
APEX cannot send changes or deletes for the Shipment record. APEX can,
however, change the status back to "In Transit" which changes the Inventory
Receipt back to a Shipment record in a "Pending" status. The following
notification is also presented to the COMMANDbatch operator:

2/3/14 13
Correcting Shipments That Are Accidentally Accepted
If the COMMANDbatch operator accidentally accepts a Shipment (i.e. creates
an Inventory Receipt for a delivery that has not yet been received), the
operator can correct this by:

1. Clicking the Show All button on the Shipments form.

2. Locating the Shipment record.


3. Changing the Status back to "Pending" from "Receipt (+)".
4. Saving the record.
A Notify/Delete message is then sent to APEX so the record can be set back to
“In Transit” from “Received” on that end and the amount can be deducted
from the On Hand total in COMMANDbatch. At this point, APEX will be able to
send changes or delete the record if needed.

Multiple Materials within a Shipment


APEX can send multiple materials on the same Shipment record. In this
scenario, a single material can be accepted (i.e. its Status changed to "Receipt
(+)"), or multiple materials can be accepted at the same time. A separate
Accepted notification is sent to APEX for each material whose Status has been
changed to "Receipt (+)".

14 2/3/14
Matching Local Receipts to an APEX Shipment
If an Inventory Receipt was created locally in COMMANDbatch and a
corresponding Shipment is later received from APEX, the COMMANDbatch
operator can match the receipt with the Shipment as follows:

1. Right click on the pending Shipment item line and select "Match
to Inventory Receipt".

2. When the Inventory Receipts form opens with matching Material


receipts, select the correct Inventory Receipt and close the
Inventory Receipts form.
3. When prompted about matching the Inventory Receipt, click OK.

Once the operator clicks OK, the Status of the Shipment record changes to
"Receipt (+)" and an Accepted message is sent to APEX.

2/3/14 15

You might also like