Asn-Commandbatch Interface Setup Guide
Asn-Commandbatch Interface Setup Guide
Asn-Commandbatch Interface Setup Guide
Setup Guide
COMMANDbatch V1.8.8.0 & Later
2/3/14
www.commandalkon.com
2 2/3/14
Contents
Contents ........................................................................................ 3
Introduction .................................................................................. 4
Purpose ................................................................................................ 4
Audience ............................................................................................... 4
Revision Summary ................................................................................. 4
2/3/14 3
Introduction
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
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.
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
Windows 7:
6 2/3/14
6. On the Client Architecture Selection window, check “Force bit
(x86)”.
2/3/14 7
EDX Client Installation on COMMANDbatch PC
Only the EDX Client is installed on the COMMANDbatch PC.
Windows 7:
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.)
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.
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.
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.
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:
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".
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