View source for Set-up Guide

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=Set-up Guide
|Reference=UG 106181
|Version=7.1
|Date=09 December 2010
|Sysver=3.4
}} 

<!-- TOC --> 
= INTRODUCTION =
This document is intended to show the further set-up possibilities on the WCS. This guide should be used by super-users and testing teams during initial set-up. An alphabetical list of all rules and their values is also included.


This document assumes that the installation has taken place (as described in the document WCS Installation Guide) and that set-up has occurred and a connection established in the WMS.


'''Note:''' A familiarity is required of the use of the WMS with respect to the WCS (as described in the document RDT Training Guide WMS), as well as a reasonable knowledge of the WCS Maintenance functions (as described in the document WCS Maintenance User Guide). See References for more details of the referred documents

= Data sent from WMS =
There are several tables on the WCS that are used to control basic functions. As this data is available on the WMS as well, drip-feed interfaces have been enabled to send this data from the WMS to the WCS. The following section describes which of these tables are set up like this, and for what purpose the information in used.


== Reason Codes ==
Reason codes are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Reason codes are used in a variety of places in the RDT application, for example when picks are cancelled or short-picked, or damaged or additional pallets are received.

The data stored on the WCS is simply the Reason code itself, along with which company and warehouse the codes are associated.

The data stored on the WCS can be seen by running the Reason Codes Enquiry from the Standing Data menu. 


== Pallet Types ==
Pallet types are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Pallet Types are used mainly when entering the details of pallets, for example in goods receipt. Normally, however, the pallet type can be left blank, as the WMS will default the pallet type to that normally received for the stock.

The data stored on the WCS is simply the pallet type itself, along with which company and warehouse the types are associated.

The data stored on the WCS can be seen by running the Pallet Types Enquiry from the Standing Data menu. If a more permanent copy is required, a report can be run from the Reports menu (Pallet Types List)


== Truck Types ==
Truck Types are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Truck Types are used when logging on to the WCS. The type used defines in which areas the driver is allowed. 

The data stored on the WCS is simply the truck type itself, along with which company the trucks are associated.

The data stored on the WCS can be seen by running the Truck Type Enquiry from the Standing Data menu.


== Location Types/Truck Types ==
Location types/Truck types are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Location types (and their associated truck types) are used in nearly every enquiry in the WCS. Every task, to move a pallet from one point to another, defines which location type the associated location is. The data received from the WMS defines which truck types are allowed access to that particular location. This, coupled with the truck type the RDT user enters at log-on, defines where exactly that user is allowed to operate.

The data stored on the WCS is the location type, with all associated truck types, along with which company and warehouse the types are associated.

The data stored on the WCS can be checked by running the Location Truck Type Checker from the Standing Data menu. This is used by entering the location types you want to check in the appropriate combo boxes in the form, the clicking the 'Check' button. The form will show you all the trucks associated with each location types, and which trucks have access to both.

If a permanent copy of the data is required, a report can be run from the Reports menu (Location Type/Truck Types List).


== Receipt Types ==
Receipt Types are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Receipt types are used only in the goods receipt RDT module, and only if they have been enabled. This allows RDT users to define the receipt type that will be passed back and stored on the WMS.

The data stored on the WCS is simply the receipt type itself, along with which company and warehouse the codes are associated.

The data stored on the WCS can be seen by running the Receipt Types Enquiry from the Standing Data menu. 


== Employees ==
Employees (Users) are sent from the WMS to the WCS from a maintenance screen in the WMS. Instructions on how to do this and what is sent are in the WMS Training guide

Employees are used mainly at log-on on the RDT. They can also be used to authorise events on the RDT, if required. The entered employees are stamped as completing their tasks, and this information is stored on the WMS for analysis later.

The data stored on the WCS consists of elements passed from the WMS and also elements that the WCS requires itself.


The Employees will be set up when received as follows:

* Company Code - from WMS
* Warehouse Id - from WMS
* Employee Code - from WMS
* Employee Name - from WMS
* Password - None
* Access Type - RDT
* Group - None

Additionally, one row in this table is created during the initialisation procedure of the database (the user initial admin user ADM is created). This can be seen in the WCS Installation Guide


The data stored on the WCS can be seen by running the Users Maintenance screen from the Standing Data menu. If a more permanent copy is required, a report can be run from the Reports menu (Employees List)


See section 4.1 for details of how to further configure the Employees table.


== Aisles ==
Aisle codes are sent from the WMS to the WCS from a validation process in the WMS. This depends on some very specific system set-up in both the WMS and WCS. However, if this happens, the aisle data is set up as follows:


* Aisle Code - from the WMS tables.
* Availability - Y, N or P
* Company code and Warehouse ID.

Aisle codes are used for two main reasons in the WCS:

* To give the closest next task to an operative
* To allow or disallow putaway in certain aisles.

The data sent automatically above accounts for the operation of the second piece of functionality. Other items on the WCS Aisles table control the first piece.


Apart from these parameters, there is also the option to send over extra aisle information if needed from the Aisles Maintenance screen.

This extra information is as follows:


* Aisle Sequence Code
* Linked Aisle Code, Locs In Aisle and High End Access
* PD Out Location, Type, Check Digits and Max Pallets
* PD In Location, Type, Check Digits and Max Pallets

The data stored on the WCS can be seen by running the Aisles Maintenance screen from the Standing Data menu. If a more permanent copy is required, a report can be run from the Reports menu (Aisles/P&D List). This report, however, links more closely into the further configuration of aisles utilising P&D locations (see sections 3.5 and 4.2)


See section 4.2 for details of how to further configure the Aisles table.


== Stock Parameters and Barcodes ==
Stock configuration and barcode information is sent from the WMS to the WCS from the stock maintenance screen in the WMS and from EDI. 


When stock codes are added or changed and updated, the messages are sent to the WCS. These are not visible within the WCS Maintenance program.


The data sent includes validation items and barcode information, as follows:



{| class="prettytable"
! Item
! Type
! Length
! Description

|-
| Owner Code
| Text
| 3
| Owner Code

|-
| Stock Code
| Text
| 20
| Stock Code

|-
| Description
| Text
| 40
| Description, for display

|-
| Standard Pallet Qty
| Long Integer
| 4
| For validation in Goods Receipt and Stock Take

|-
| Layer Qty 
| Long Integer
| 4
| For layer quantity entry in Goods Receipt

|-
| Shelf Life 
| Long Integer
| 4
| For validation of sell-by dates in Goods Receipt and Stock Take

|-
| Manu Date Required
| Text
| 1
| Whether the stock requires Manufacture dates to be entered. Used in Goods Receipt and Stock Take.

|-
| Sell By Date Required
| Text
| 1
| Whether the stock requires Sell-by dates to be entered. Used in Goods Receipt and Stock Take.

|-
| Cust Batch Required
| Text
| 1
| Whether the stock requires Customer Batches to be entered. Used in Goods Receipt and Stock Take.

|-
| Seals Required
| Text
| 1
| Whether the stock requires a seal to be entered at Goods Receipt. (Bespoke. Oracle Only.)

|-
| Hazardous
| Text
| 1
| Whether the stock is hazardous. Used in Shipment Pallet functionality. (Bespoke. Oracle Only.)

|-
| Chill 
| Text
| 1
| Whether the stock is chill. Used in Shipment Pallet functionality. (Bespoke. Oracle Only.)

|-
| Factor_1_2
| Long Integer
| 4
| The factor used by WMS to determine the number of units in a case, usually. Used for Multi UOM functionality. (C-ISAM only)

|-
| Factor_2_3
| Long Integer
| 4
| The factor used by WMS to determine the number of cases on a pallet, usually. Used for Multi UOM functionality. (C-ISAM only)

|-
| Description 2
| Text
| 30
| Second description line, for display

|-
| Pack Size 
| Text
| 10
| Pack Size, for display

|}
The barcode information is used to determine the elements within a barcode that can be scanned for identification of the stock code. This is usually EAN codes and UCC-EAN codes. When set up in the WMS, this information is sent through to the WCS.

= WCS Internal Data =
Further information is required by the WCS to run. This data is not available from the WMS and must be set up on the WCS itself. This section shows the data that needs to be entered directly.


In all these cases, further details on how to use this screen can be found in the WCSM Users Guide, referenced in 4.2


== Groups ==
This table is used to configure the options individual users can have when accessing RDT or Maintenance functions.

One row in this table is created during the initialisation procedure of the database (the group ADM is created when the initial admin user is created). This can be seen in the WCS Installation Guide

The data can be seen and modified from the Groups Maintenance screen, found on the Standing Data menu.


Users are partially maintained by the WMS, sending data records when an employee is added or deleted. You can add system settings to a user, using the Group ID reference field. This links to records you can maintain in this screen.

The group contains switches to show which users are allowed to use which functions. As such, the screen allows you to enter a unique group id, and a description of the group. You are then given a list of all available functions on the WCS and RDTs. Simply click which functions you require from one list to the other.


The RDT items that can be set up (and their descriptions) are:


{| class="prettytable"
! <center>Rule</center>
! <center>Description</center>

|-
| Enable RDT Receipt
| Allow Blind (Stock level) and Check (Pallet level) Goods Receipt.

|-
| Enable RDT Putaway
| Allow Full-Pallet Putaway.

|-
| Enable RDT Pallet Move
| Allow the user to complete Full-Pallet Movements generated from the WMS.

|-
| Enable RDT Ad Hoc Move
| Allow instigation of a housekeeping Move from the RDT.

|-
| Enable RDT Picking
| Allow the user to complete Full-pallet Picks.

|-
| Enable RDT Part Picking
| Allow the user to complete Case and Unit picks from the RDT.

|-
| Enable RDT Stock Take
| Allow Full (Blind) and Partial (Check) Stock Check.

|-
| Enable RDT Bulk PI
| Allow Perpetual Inventory (ad hoc stock check).

|-
| Enable RDT Shipment Pallet Building
| Allow Shipment Pallet Building. Bespoke.

|-
| Enable RDT Shipment Pallet Despatch
| Allow Shipment Pallet Despatch. Bespoke.

|-
| Enable RDT Shipment Pallet Moves
| Allow Shipment Pallet Moves. Bespoke.

|-
| Enable RDT Pallet Enquiry
| Allow the RDT user to enquire on the contents of a pallet from the WMS.

|-
| Enable RDT Location Enquiry
| Allow the RDT user to enquire on the contents of a location from the WMS.

|-
| Enable RDT Move Enquiry
| Allow the RDT to see where a pallet is going.

|-
| Enable RDT Move Select
| Allow cherry-picking of an individual Move task.

|-
| Enable RDT Select Replenishment
| Allow Select Replenishment. Bespoke.

|-
| Enable RDT Replenishment
| Allow completion (and/or generation) of a Replenishment. Bespoke.

|-
| Enable RDT Stock Move
| Allow Stock Moves (request replenishment of pick face). Bespoke.

|-
| Enable RDT Ad Hoc Putaway
| Allow Ad Hoc Putaway for shelving locations. Bespoke.

|-
| Enable RDT Receipt Serial No Scanning
| Allow entering serial numbers for received items. Bespoke.

|-
| Enable RDT Despatch Serial No Scanning
| Allow entering serial numbers for picked items. Bespoke.

|-
| Enable RDT Loading
| Allow Loading ojnto a vehicle.

|-
| Enable RDT Reject Spur
| Allow Reject Spur Processing. Bespoke to automated conveyor and P&D systems. Bespoke.

|-
| Enable RDT Cherry Picking
| Choose an order to pick from

|-
| Enable RDT Combined Split
| Bespoke: Ad hoc movements of small quantities of stock to other locations

|-
| Enable RDT Stock Enquiry
| Bespoke: Enquire on Stock code

|-
| Enable RDT Mail
| Allow receipt of messages from Maintenance administrators. (Generally, this should always be enabled).

|-
| Enable RDT Reposition
| Allow a task to be repositioned to a different destination location.

|-
| Enable RDT Cancellation
| Allow Moves and Picks to be cancelled, causing the reversion of data on the WMS.

|-
| Enable RDT Damages
| Allow Damage quantity entry during Goods Receipt.

|-
| Enable RDT Receive Additional Pallets
| Allow receipt of extra pallets in Check Goods Receipt.

|-
| Enable RDT Pick Location Error
| Allow a Pick to be cancelled at the initial location stage (for example, if the pick face is unavailable).

|-
| Enable RDT Continuous Part Picking
| Is this module enabled by default for RDT users?

|-
| Enable RDT DC Aisles
| when using Dual Cycling (Interleaving) in Narrow Aisles, allow RDT user to select range of aisles to operate in.

|-
| Enable RDT Marshall
| Not Yet Implemented.

|-
| User Select Pick Location
| Is the user allowed to specify the location from which picking to start?

|-
| Enable RDT Deconsolidation
| Allow deconsolidation of consolidated orders.

|-
| Enable RDT Despatch
| Allow despatch of deconsolidated orders.

|-
| Enable RDT Weighing
| Allow the RDT user to Weight Shipment Packages.

|}
The Admin items that can be set up (and their descriptions) are:


{| class="prettytable"
! <center>Rule</center>
! <center>Description</center>

|-
| Enable Admin Change Warehouse
| Allows the user to change the default warehouse they can see

|-
| Enable Admin Comms
| Allows the user full access to the RDT Comms menu. If this is enabled, the following option need not be.

|-
| Enable Admin Comms Enquiry
| Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.

|-
| Enable Admin Logs
| Allows the user access to the Logs Enquiry screens in the System Tools menu

|-
| Enable Admin Report
| Allows the user access to the Reports menu

|-
| Enable Admin Settings System
| Allows the user access to the System Settings option on the System Tools menu. NOTE: This option should only be enabled for super-users, and even then should only be enabled sparingly.

|-
| Enable Admin Standing Data
| Allows the user full access to all items on the Standing Data menu. If this is enabled, the following option need not be. NOTE: This option will allow users to see other users' passwords, and should therefore be limited only to those users who require it.

|-
| Enable Admin Standing Data Enquiry
| Allows the user access to the Enquiry screens only on the Standing Data menu

|-
| Enable Admin Task Edit
| Allows the user full access to all the screens on the Tasks menu. If this is enabled, the following option need not be.

|-
| Enable Admin Task Enquiry
| Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.

|-
| Enable Admin Utilities Clear Out
| Allows the user access to the Clear-Out options on the System Tools menu. NOTE: This should only be available for super-users.

|-
| Enable Admin Utilities DB Utils
| Allows the user access to the Database Utilities options on the System Tools menu (this is currently being phased out).

|-
| Enable Admin Utilities Repair and Compact
| Allows the user access to the Compact Database option on the System Tools menu.

|}
== System Parameters ==
The values in this table are created during the initialisation procedure of the database. This can be seen in the WCS Installation Guide

Configuration items are grouped into 4 sections. Each is described in detail in the following sections.


=== Rules ===
==== WCS Settings ====
This allows you to modify the communication settings of the WCS, plus settings which directly affect how the system communicates. 


'''Note 1:''' Changing these settings may affect the running of the WCS server. If you are not sure of the consequences of your actions, telephone the support team.

'''Note 2:''' These settings will be enabled during system configuration and in normal circumstances should never be changed. Changes to WCS configuration settings will not take place until after the next stop and start of the WCS Server process. 


Settings common to both connection systems (C-ISAM and Oracle) that may be modified are:


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Default Company Code
| This is the default company code that the RDT will log on to.

|-
| Delete Records
| When this option is checked, completed tasks are deleted from the WCS database. All logging is still in place. When un-checked, the completed tasks are marked for deletion by the cleardown process.

|-
| Enable Hold Priority
| This allows the lowest priority in the WCS to be used as a Held status. When this option is checked, and tasks on priority 9 will not be allocated to RDTs to complete. To release the tasks, re-prioritise the task to a higher level.

|-
| RDT Wait Time
| This is the amount of time that the RDT will wait before re-trying communications.

|-
| Window Caption
| This field changes the displayed name of the WCS Server process, when running. This is useful when running multiple systems on one site or one server.

|-
| RDT_WCS LocalPort
| This is the port that the WCS listens to for communications from RDTs.

|-
| Log Path
| WCS Logging database - When this option is checked, you will be prompted to enter a location for the logging database. THIS OPTION MUST NOT BE CHANGED IF THE WCS SERVER IS RUNNING. When this is done, the logging files in the normal database are no longer used - a new database will be created in the defined area and the WCS server will begin all logging to this database instead. All options in the WCS that use these logging files will now use the new database instead. The logging files are: Error log; Incoming log; Outgoing log; RDT Activities and; Exceptions.

|}
If the system is connecting using socket connections, the following details can be modified:


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| WMS HostName
| This is the IP address or host/DNS name of the WMS machine.

|-
| WMS_WCS LocalPort
| This is the port that the WCS listens to for communications from the WMS.

|-
| WCS_WMS RemotePort
| This is the port that the WMS listens to for communications from the WCS.

|-
| WMS to WCS Try Limit
| This is the amount of times the WCS will try to send a message to the WMS, if the message has been refused, before logging the error and trying the next.

|-
| Use Dummy Checksum
| Used to terminate the interface messages with a dummy checksum value (??)

|}
If the system being linked to is using Oracle Advanced Queues, the following options will be available:


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Ora Database
| The database the WCS connects to for the messages.

|-
| Ora User
| The username for the connection to the Oracle database

|-
| Ora Password
| The password of the user for the connection to the Oracle database.

|-
| Ora Incoming Queue Name
| The Oracle queue on which Incoming messages are stored. Outgoing messages are stored by messages type on the queues defined in the table ORA Type Queues.

|-
| Queue Listener Agent
| The Oracle agent defines which messages to take from the Oracle database queues, and what Agent to write them as. Each instance of the WCS has a unique Agent name, usually per warehouse.

|}
There are also settings for links to an FTP Server. This is a bespoke modification, for the connection to a batch delivery system. The settings are:


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Flat File FTP Server
| Bespoke: The server where flat files are sent.

|-
| Flat File FTP User
| Bespoke: The user for logging into the FTP server.

|-
| Flat File FTP Password
| Bespoke: The password for logging into the FTP server.

|-
| Flat File FTP Location
| Bespoke: The location where files are to be found on the FTP server.

|-
| Flat File Location
| Bespoke: The location where files are to be located on the FTP server.

|}
==== Admin Defaults ====
If a user hasn't been assigned a Group, they have access to Admin functions in the way set up here.

The Admin items that can be set up (and their descriptions) are:


{| class="prettytable"
! <center>Rule</center>
! <center>Description</center>

|-
| Enable Admin Change Warehouse
| Allows the user to change the default warehouse they can see

|-
| Enable Admin Comms
| Allows the user full access to the RDT Comms menu. If this is enabled, the following option need not be.

|-
| Enable Admin Comms Enquiry
| Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.

|-
| Enable Admin Logs
| Allows the user access to the Logs Enquiry screens in the System Tools menu

|-
| Enable Admin Report
| Allows the user access to the Reports menu

|-
| Enable Admin Settings System
| Allows the user access to the System Settings option on the System Tools menu. NOTE: This option should only be enabled for super-users, and even then should only be enabled sparingly.

|-
| Enable Admin Standing Data
| Allows the user full access to all items on the Standing Data menu. If this is enabled, the following option need not be. NOTE: This option will allow users to see other users's passwords, and should therefore be limited only to those users who require it.

|-
| Enable Admin Standing Data Enquiry
| Allows the user access to the Enquiry screens only on the Standing Data menu

|-
| Enable Admin Task Edit
| Allows the user full access to all the screens on the Tasks menu. If this is enabled, the following option need not be.

|-
| Enable Admin Task Enquiry
| Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.

|-
| Enable Admin Utilities Clear Out
| Allows the user access to the Clear-Out options on the System Tools menu. NOTE: This should only be available for super-users.

|-
| Enable Admin Utilities DB Utils
| Allows the user access to the Database Utilities options on the System Tools menu (this is currently being phased out).

|-
| Enable Admin Utilities Repair and Compact
| Allows the user access to the Compact Database option on the System Tools menu.

|}
=== Message Types ===
This tab allows the user to maintain remote queue names for connection to the Oracle WMS. These are not required if the user is running the WCS connected to the C-ISAM WMS.


=== Maintenance Settings ===
This tab controls settings that affect the operation of the WCS Maintenance program directly.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Default Criteria Templates Folder 
| This is the folder where criteria files for the selection of data in certain screens are held. More details on these reprioritisation screens can be found in the WCSM User Guide

|-
| Default Report Files Folder 
| This is the folder where the reports run from the Maintenance program are held. These can be local or remote.

|-
| Default Reports Folder 
| This is the default folder where the output from reports (if requested) is saved.

|-
| Recent Files 
| This is a simple list of the databases opened recently. A button (Clear List) can be clicked to remove all these files from the list.

|-
| Show File List at Startup 
| This controls whether the file list is shown on start-up, or a simple file browser. 

|}
=== Clear Down ===
These parameters control how data is cleared from the WCS database.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Location of Log Files 
| This specifies where the log archive is kept. The Log archive is the area where cleared data is stored.

|-
| Clear Database 
| If checked, any data older than the period entered is removed from the current database and placed in a new archive database.

|-
| Clear Log Archive 
| If checked, and log archives stored are deleted if they are older than the period specified.

|-
| Clear Exceptions 
| If checked, any exceptions older than the period specified is removed from the current database and placed in a new archive database.

|-
| Clear Activities 
| If checked, any Activities records older than the period specified is removed from the current database and placed in a new archive database.

|-
| Clear Deleted Records 
| If checked, any records marked for deletion older than the period specified are removed from the current database and placed in a new archive database. See section 3.2.1.1 for details of how data can be marked for deletion.

|-
| Clear Incoming Log / Outgoing Log /Clear Error Log 
| If checked, any interface log records older than the period specified are removed from the current database and placed in a new archive database.

|}
These settings should be enabled on the WCS Server PC only, as this is the place where any scheduled cleardown procedure would be run from.


== Warehouses ==
The values in this table are created during the initialisation procedure of the database. This can be seen in the WCS Installation Guide


'''Note:''' The values in this section govern how the WCS Server and RDT processes work. Generally, these items have been set up for you in the way that is most conducive to the way you operate in the warehouse. These values should not be changed unless you know how these will change the way the system operates. Changing the values may not have an immediate effect on the operation of the WCS. The safest way to change parameters is to log out all RDTs, the stop the WCS Server before making the changes.


Barcode configuration for the warehouse is available from a button on the form. Configuration items are grouped into seven sections. Each of the above is described in detail in the following sections.


=== General ===
This tab controls the basic operation of the warehouse selected.


{| class="prettytable"
! <center>Rule_Name</center>
! <center>Rule_Description</center>

|-
| Action Password
| The password required when RDT functions are password-protected

|-
| Aisle Length
| The length of the Aisle portion of the Location code.

|-
| Bay Length
| The length of the Bay portion of the Location code

|-
| Level Length
| The length of the Level portion of the Location code.

|-
| Task Identifier
| How the RDT identifies pallets in the warehouse. Normally, this would be set to 'By System Pallet'.

|-
| Check Digits?
| Whether and how check digits are used on the locations in the warehouse.

|-
| Move Efficient
| How tasks are assigned to RDT users. This defaults to 'By Priority' and may only be altered if no stock or pallet ID's are used in the pick face.

|-
| Block Stack
| Whether pallet exchanges operate in the warehouse. Should only be enabled if the warehouse contains Block Stack, Drive-in or Multi-deep locations.

|-
| Exchange Replen
| If the Warehouse is Block Stack, allow Replens to be exchanged as well. NOTE: This should only be enabled if no stock or pallet ID's are used in the pick face.

|-
| Allow Task Exchange
| WCS checks for outstanding tasks to give to the user before asking WMS whether the pallet is available for exchange

|-
| Seamless Exchange
| If this rule is set, the RDT will check whether an exchange can be done immediately, without requiring the user to press the Error function key first.

|-
| Mixed Stock
| whether pallets are allowed to have mixed stock on them in the warehouse.

|-
| WCS Generate Replenishment
| Controls whether the WCS generates the replenishment from Select Replen. For Calidus 3pl, this should always be enabled.

|-
| RDT Pop Up Description
| Whether the RDT automatically pops up the stock description in the main RDT modules.

|-
| Multi UOM processing
| Controls whether the WCS will prompt for 2 UOMs on the RDT when entering quantity. If this is not set, the RDT will just prompt for cases.

|-
| Pallet Enquiry Print Labels
| Controls if pallet label can be printed from a pallet enquiry

|-
| WCS Pallet Enquiry Label Format
| Format of pallet enquiry label

|}
=== RDT Modules ===
For all users that haven't been assigned to a Group, this section configures the options these users can have when accessing RDT or Maintenance functions.


The RDT modules that can be set up (and their descriptions) are:


{| class="prettytable"
! <center>Rule</center>
! <center>Description</center>

|-
| Enable RDT Receipt
| Allow Blind (Stock level) and Check (Pallet level) Goods Receipt.

|-
| Enable RDT Putaway
| Allow Full-Pallet Putaway.

|-
| Enable RDT Pallet Move
| Allow the user to complete Full-Pallet Movements generated from the WMS.

|-
| Enable RDT Ad Hoc Move
| Allow instigation of a housekeeping Move from the RDT.

|-
| Enable RDT Picking
| Allow the user to complete Full-pallet Picks.

|-
| Enable RDT Part Picking
| Allow the user to complete Case and Unit picks from the RDT.

|-
| Enable RDT Stock Take
| Allow Full (Blind) and Partial (Check) Stock Check.

|-
| Enable RDT Bulk PI
| Allow Perpetual Inventory (ad hoc stock check).

|-
| Enable RDT Shipment Pallet Building
| Allow Shipment Pallet Building. Bespoke.

|-
| Enable RDT Shipment Pallet Despatch
| Allow Shipment Pallet Despatch. Bespoke.

|-
| Enable RDT Shipment Pallet Moves
| Allow Shipment Pallet Moves. Bespoke.

|-
| Enable RDT Pallet Enquiry
| Allow the RDT user to enquire on the contents of a pallet from the WMS.

|-
| Enable RDT Location Enquiry
| Allow the RDT user to enquire on the contents of a location from the WMS.

|-
| Enable RDT Move Enquiry
| Allow the RDT to see where a pallet is going.

|-
| Enable RDT Move Select
| Allow cherry-picking of an individual Move task.

|-
| Enable RDT Select Replenishment
| Allow Select Replenishment. Bespoke.

|-
| Enable RDT Replenishment
| Allow completion (and/or generation) of a Replenishment. Bespoke.

|-
| Enable RDT Stock Move
| Allow Stock Moves (request replenishment of pick face). Bespoke.

|-
| Enable RDT Ad Hoc Putaway
| Allow Ad Hoc Putaway for shelving locations. Bespoke.

|-
| Enable RDT Receipt Serial No Scanning
| Allow entering serial numbers for received items. Bespoke.

|-
| Enable RDT Despatch Serial No Scanning
| Allow entering serial numbers for picked items. Bespoke.

|-
| Enable RDT Loading
| Allow Loading ojnto a vehicle.

|-
| Enable RDT Reject Spur
| Allow Reject Spur Processing. Bespoke to automated conveyor and P&D systems. Bespoke.

|-
| Enable RDT Cherry Picking
| Choose an order to pick from

|-
| Enable RDT Combined Split
| Bespoke: Ad hoc movements of small quantities of stock to other locations

|-
| Enable RDT Stock Enquiry
| Bespoke: Enquire on Stock code

|-
| Enable RDT Mail
| Allow receipt of messages from Maintenance administrators. (Generally, this should always be enabled).

|-
| Enable RDT Marshall
| Not Yet Implemented.

|-
| Enable RDT Deconsolidation
| Allow deconsolidation of consolidated orders.

|-
| Enable RDT Despatch
| Allow despatch of deconsolidated orders.

|-
| Enable RDT Weighing
| Allow the RDT user to Weight Shipment Packages.

|}
=== Receipt  ===
The parameters on this tab control how receipt works on the RDT.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Receipt Type
| How the RDT actions the Receipt process - either Blind (stock-level advice) or Check (Pallet-level advice)

|-
| Selection Type
| How to find the receipt on the RDT - via Advice Note or GRN no.

|-
| Damages
| Allow Damage quantity entry during Goods Receipt

|-
| Enter WMS Rotation
| Allow the user to enter Rotation during Goods Receipt

|-
| Default Pallet Type
| during Goods Receipt, whether the RDT user is prompted for a valid Pallet Type at the start of the receipt. This will then be the default for all pallets subsequently received during that session for that user. Without this item being enabled, pressing 'RETURN' in the pallet type field against a received pallet will tell WMS to default to its Default Pallet Type.

|-
| Enter Receipt Type
| Allow the user to enter the receipt type in RDT Goods Receipt

|-
| RDT Echo Putaway Location
| If enabled, this parameter makes the RDT Receiving process display the suggested putaway location after successfully receiving a pallet.

|-
| Print Labels
| Controls where/if pallet labels are printed during the receipt process

|-
| WCS Receipt Label Format
| Format of the receipt label printed, if printed from the WCS.

|-
| Additional Pallets
| Allow additional pallets to be received during the RDT receipt process

|-
| Single Scan Entry for Additional Pallets
| Allow users to scan single barcode for entry of some required elements for adding additional pallets

|-
| Receipt Non-advised Stock Codes
| Is the user allowed to receive stock codes that have not been preadvised for that receipt?

|-
| Receipt Pallet Count Check
| If the number of pallets on a received stock item exceeds that preadvised, this parameter details the action the RDT is to take.

|-
| Receipt Total Qty Stock Check
| If the quantity of a stock item exceeds the total preadvised, this parameter details the action the RDT is to take.

|-
| Receipt Pallet Qty Check (Pallet)
| If the pallet quantity for a stock item is different to the pallet quantity preadvised, this parameter details the action the RDT is to take. Only for preadvices at a pallet level.

|-
| Receipt Standard Qty Check (Stock)
| If the pallet quantity for a stock item is different to the standard pallet quantity, this parameter details the action the RDT is to take. Only for preadvices at stock level.

|-
| Enter Eurodate
| Bespoke: Enter Eurodate rather than Manufacture Date

|-
| Enter Layers
| Enter Layers and Bits at Goods Receipt

|-
| Enable Pack Size Entry
| If this rule is enabled, pack size will be prompted for when entering pallet details for impression stock

|-
| Receipt Impressions Check
| If the impressions quantity for a stock item is different to the impressions quantity preadvised, this parameter details the action the RDT is to take. Only for preadvices at pallet level.

|-
| Purchase Order Entry
| Enable Purchase Order entry during RF goods receipt, if the receipt contains lines from multiple Purchase Orders.

|-
| Close GRN
| Allow RDT users to close GRNs at the end of the receipt process, by asking them to confirm that the GRN is now complete.

|}
=== Putaway ===
The parameters on this tab control how putaway works on the RDT.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Multi-Pallet Putaway
| Allow several pallets to be picked up during putaway

|-
| Extended Reposition Validation
| Whether the WCS performs extended checks when a reposition location is chosen.

|-
| Request Putaway Details at Scan
| Require the WMS to decide on a putaway location at the time of putaway scan, rather than at receipt

|-
| RDT Reposition
| Allow reposition on the RDTs? This option can be over-ridden by the Group setting

|-
| RDT Cancellation
| Allow cancellation on the RDTs? This option can be over-ridden by the Group setting

|}
=== Picking/Post-Picking Activities ===
These parameters control how the RDT acts during the picking modules. Also, some of these flags control how the WCS receives picking tasks, and how it assigns them to RDT users.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Pick By
| Controls what the RDT prompts for as confirmation that the correct item has been found for picking

|-
| Continuous Part Picking
| When part picking, asks the user whether they want to continue part picking (i.e. build a despatch pallet from several pick lines).

|-
| Pick Into Containers
| Controls whether RDT Part Picking prompts for Picking Container IDs

|-
| Lost Label
| Controls whether a user is allowed to identify a pallet during picking from its stock information (stock code, batch, etc) rather than entering the pallet ID

|-
| Pick Location Error
| Allow the RDT picker to cancel an pick at the point of confirming the location code.

|-
| Residual Stock Balance Enquiry
| Controls whether the RDT user is prompted to enter the amount of remaining stock in the pick face after a part pick. The WCS requests the WMS to find the current quantity of stock in the pick face.

|-
| Use WMS Rotation 
| If this rule is set, wherever Customer Batch is displayed or entered during Picking or Deconsolidation, the RDT will display or request the entry of WMS Rotation instead.

|-
| Picker Replens
| Allow pickers to perform their own replens at the point of picking the part picks.

|-
| Pick Dependencies
| Ensure part picks are not released for picking until any outstanding replenishment has been completed first

|-
| Replen Dependencies
| This rule controls whether the number of replenishment moves into a pick face are limited. Also, that the replen associated with the highest priority pick is released first, whilst all others are held.

|-
| Pick In Sequence
| If picks have been placed on a Load, what sequence should orders be released for picking?

|-
| Pick Page Allocation
| This controls how the WCS allocates picks to pickers.

|-
| Concurrent Picking
| Allow loads to be picked concurrently with other loads, when picking by aisle. This stops new loads being started by pickers until the current load has been fully allocated to pickers.

|-
| Lock Pick Header
| Lock the picking header record for full pallet picking/load building

|-
| Consolidation Group
| For Consolidated picking: How to create groups of picks.

|-
| Force Sky Picking
| Are part pick tasks from bulk treated as sky picks?

|-
| Print Despatch Labels
| Whether the RDT attempts to print despatch labels for picked stock.

|-
| WCS Despatch Label Format
| Format of the despatch label

|-
| Pick Label Prompt
| Where should pick labels be prompted for?

|-
| User Select Pick Location
| Is the user allowed to specify the location from which picking to start?

|-
| Deconsolidation Method
| Whether Deconsolidation tasks are processed by the WCS

|-
| Ad Hoc Deconsolidation
| Are deconsolidation tasks sequenced manually or by the system?

|-
| Loading Method
| Loading Method in use for the warehouse

|-
| Loading Selection Type
| Controls whether the RDT initially asks the user to load stock by Route/Load or Order Number. This can be changed by the user when loading.

|-
| PC Generation Algorithm
| Algorithm to generate Picking Containers

|-
| PC Prefix
| Prefix for automatically-generated Picking Container

|-
| Weigh Shipment Package
| Allow the entry and validation of the Catch Weight during the Shipment Pallet Building process

|-
| Ship Pack Weight Check
| If a weight entered during the Shipment Package Weight function is outside the tolerance value, what action should the RDT take?

|-
| Weight Tolerance
| If weights are being checked by the Shipment Package functions, what tolerance is allowed (plus or minus, in kilograms)?

|-
| Display Order Summary
| Defines when the order summary screen is displayed on the RDT during part picking.

|-
| Load before Pick Confirmation
| Controls whether the WCS will allow loading to be done before the entire order has been Pick Confirmed in the WMS

|}
=== Dual Cycling ===
This section controls how the RDT is allocated DC tasks, and how the RDT responds to the user requests.


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Enable Dual Cycling
| If this is enabled, the RDT logon procedure allows users to choose whether they work in Bulk (NA areas) or not. Depending on this choice, the RDT displays Dual Cycling options for the users.

|-
| NADC Crossover Method
| The method by which the RDT NA drivers are moved to another aisle in their range during Dual Cycling.

|-
| NADC Threshold Priority
| If using the Threshold crossover method, this parameter details the level at which tasks are considered urgent, to be actioned immediately.

|-
| Send Aisle Status to WMS
| For NA areas: Inform the WMS that the aisle has a truck in it.

|-
| NADC Aisle Lock
| The point at which an aisle is locked to prevent other RDTs using the aisle

|-
| RDT DC Aisle Selection
| If using Dual Cycling, this parameter controls whether the user is allowed to select a range of Aisles in which to work, or simply accept the default aisle range entered against the user.

|-
| NADC Skip Putaway
| Allow full NADC users to skip putaways in aisles, and do the next pick immediately.

|-
| Exclude Blocked Moves from Priority Calc
| Whilst calculating the priority of moves within an aisle, exclude moves which cannot currently be completed, due to blocked P&D locations.

|-
| Exclude Source to Dest moves from WA DC
| Ensures WA DC (interleaving) focuses more on emptying P&D locations rather than completing housekeeping moves.

|}
=== Default Locations ===
This set of options is generally used with a conveyor system (bespoke). However, the first parameter (Default Receiving Location) also controls whether the RDT Receipt module prompts for a receiving location for a pallet. This can then be reflected on subsequent putaways.


=== Bespoke ===
This set of options controls what bespoke development can be enabled or disabled. '''Note:''' functionality in this section is generally very specific to a particular operation and should only be enabled with a system that is configured exactly as that operation. 


{| class="prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Bespoke Site Rule
| Site identity defining which bespoke rules are to apply

|-
| Bespoke Kraft Batch
| Remove non-alphabetic characters from the start of the Batch

|-
| Pick By Carton
| Pick a quantity of stock by scanning individual cartons.

|-
| Encoded Sell By Dates?
| Use encoded sell by dates?

|-
| Allow Overpicking
| Allow the RDT user to enter a picked quantity which is greater that that required by the order.

|-
| Batch Delivery Process
| Enable creation of flat files for the Batch Carton Delivery process.

|-
| Bespoke BHS No Mixed Stock
| Disables some of the generic Mixed Stock functionality in the warehouse

|-
| Picks by Quantity
| Allocates pick tasks to the RDT users by quantity, largest first.

|-
| Enter Pick Station
| Identify the picking station at the start of part picking

|-
| Enter Pack Type
| Prompt for the pack type when picking. This is for the carton sizes when pack records are created.

|-
| Bespoke No Batch Prompt
| If this rule is enabled, no customer's batch will be prompted when entering pallet details, even if the WMS has requested that one is entered.

|-
| Picker Replen by Quantity
| Allow pickers, when doing their own replenishments, to replenish areas by stock moves, not pallet moves.

|-
| Nokia Barcodes
| This rule controls whether the RDT will expect to scan Nokia barcode labels

|-
| Stock Take Enter GRN
| When adding pallets during Stock Take or Perpetual Inventory, request the user to enter a GRN number

|-
| Bespoke Nokia Stock Take Imps
| If this rule is enabled, only the impression quantity will be prompted for when checking impression stock

|}
=== Barcode Fields ===
In this screen, the fields the RDT will decode from UCC/EAN-128 barcodes can be defined. These items are used in Goods Receipt.


== Owners ==
The values in this table are created when the user logs on to the RDT for the first time. The WCS will check for the existence of the WCS and create an owner record, indicating whether the owner requires customer pallet IDs to be entered. 


The WCS can also create rules at an owner level, which will supersede the rules at the Warehouse level. This can be done by checking the Restricted box. At this point, the WCS will create rules for the Owner.


'''Note:''' The values in this section govern how the WCS Server and RDT processes work. Generally, these items have been set up for you in the way that is most conducive to the way you operate in the warehouse. These values should not be changed unless you know how these will change the way the system operates. Changing the values may not have an immediate effect on the operation of the WCS. The safest way to change parameters is to log out all RDTs, the stop the WCS Server before making the changes.


Barcode configuration for the warehouse is available from a button on the form. Configuration items are grouped into seven sections. In general, the rules at Owner level are the same as the rules at warehouse level. Each of the above is described in detail in the warehousing section.


== P&Ds ==
P&D locations are staging areas or racks at the end of a narrow aisle to allow pallets to be dropped off mid-move, and then picked up by the next truck available to do that job.


Items that can be entered on this screen are:

* Location Code - The P&D Location Code.
* Location Type - This can be chosen from the drop-down list. This is only important if the client is using Reject Spur functionality in the warehouse, which is bespoke.
* Check Digits - As above. Can be left blank.
* PnD Type - Affects the order in which NA trucks pick up pallets from P&Ds in NADC. Choose from 3 types:
** FIFO - First on to the P&D will be first suggested off the P&D
** LIFO - Last on to the P&D will be first suggested off the P&D
** Random - User scans pallet to take off P&D.
* Actual/Max Pallets - by setting the max pallets, you can limit the number of tasks that are allowed to each P&D.
* To recalculate the number of pallets actually at the P&D, click the Recalculate button. You will be asked to confirm your selection. There is no need to save the data once recalculated, as the program will do this automatically.

Company code and Warehouse ID will default from the user's default company and warehouse.


See section 4.2 for the use of P&D locations set up in the WCS.


== RDT ==
This is an optional set-up item.

An RDT that make connections to the WCS create a record on this table. The WCS stores a unique key number and the RDT identifier, which is normally the IP address of the RDT. The data can be seen on the RDT ID Maintenance screen, found on the Standing Data menu.

The table also contains a description, and this screen can be used to change this to a more user-friendly description of the RDT. Additionally, this allows you to keep a list of all RDTs and their IP addresses.

When descriptions have been entered of the RDTs, this can be displayed against any activities or exceptions on the WCS.


== Printers ==
Printers can be either networked windows printers, or direct TCP/IP connections. The screen allows entry of either type.

A toolbar is included on the screen for ease of use.

To add new records, press the new button on the toolbar. Once you have entered your new printer, press the save button or OK button. Your data will be saved.

To find an existing record, press the find button on the toolbar. You will be taken to a lookup screen. Once you have selected your printer, the data will be displayed.

To navigate to other printers sequentially, use the scrollbar at the bottom of the screen. The status bar will show you which record you are on. 

Once you have found a printer, you may wish to change some parts of it. Simply click on your chosen field and edit it. Once you have made all your changes, press the save or OK button to save your data.

To delete a record, press the delete button on the toolbar, then confirm through the popup dialogue. 


To enter a wireless printer:

[[Image:Pic1.png]]

# Press the New button.
# Give the printer a name.
# Enter the IP address and port number of the printer.

You can then use the Printer Tests section to send through sample print files directly to the printer to ensure that the IP address and port number are set correctly.

'''Note:''' For mobile printers, the port is usually 515, for Zebra printers the port is usually 9100. However, this is not guaranteed, and should be confirmed utilising the configuration options on your printer.


To enter a Windows printer or queue:


[[Image:Pic2.png]]

# Press the New button.
# Give the printer a name.
# Choose the Windows printer from the drop-down box.

'''Note: '''The printers must be set up directly from the RDT or WCS Servers the RDT Applications are running from.


For details of how to set up Windows printers for the WCS, see 4.2


It is possible to print a test print to the printers from this screen, if you have a test print document. This can be achieved by putting the name of the test print document into the 'Data File' section on the form, or using the Browse (...) button to find the test print. Then click the Test Print button - the printer should then print the document.


= Modification of Sent Data =
In some instances, data that has been sent from the WMS doesn't have enough detail for the WCS. In this instance, further information must be entered on the WCS for records that already exist. This section describes the data that may need modifying, and what can be entered.


For these screen, further details on how to use this screen can be found in the WCSM Users Guide

== Employees ==
As mentioned in section 2.6, the Employee data comes partially pre-populated from the WMS. The rest of the settings can be manipulated in the Users Maintenance screen in the Standing Data menu.


Data that can be amended in this screen:

* Password - this can be set here. The password is encrypted in the WCS database and can only be read from this screen. Only certain users have access to this screen, controlled by the user's assigned Group.
* Group ID - A group can be assigned, controlling the user's access to RDT and Admin modules. See section 3.1 for details

* Works Only in Aisle - These parameters effect the areas the user is given tasks, when operating System-directed tasks in the bulk areas. These will act as defaults for the user, or their defined range, depending on certain warehouse flags.
* Supervisor - Employees who are marked as Supervisor can use their username and password to unlock other RDT terminals. Locking occurs in some RDT modules as a result of some defined rule (for example, in Goods Receipt). See section 3.3 for details of some locking functions.
* Access Type - shows how the user is able to log on to the system - admin and/or RDT. This can be modified, and will take effect the next time the user logs on. 
* Logged on shows how the user is currently logged on to the system. This can be reset using the reset button. N.B. this directly affects the users. USE WITH CARE.

== Aisles ==
As mentioned in section 2.7, the Aisle data comes partially pre-populated from the WMS. The rest of the settings can be manipulated in the Aisles Maintenance screen in the Standing Data menu.


Data that can be amended in this screen:

* Sequence - This shows the order in which tasks from different aisles will be given to an RDT user, if moves are given in a location-efficient manner.
* Narrow Aisle - This controls whether this aisle can be selected in the NADC aisles selection. 
* High End Access - This also controls the order in which tasks are given to users in DC. If set, tasks within an aisle are given in reverse order.
* Locs in Aisle - Future development.
* Linked Aisle Code - If this is populated, the WCS sees this aisle and the parent aisle code as one aisle, for NADC and aisle locking.
* Split Faces - If this is checked, the WCS splits tasks from odd and even bays separately.
* MHE-Fed - For Automated conveyor-fed aisles.
* PD Out/In - Controls whether the aisle utilises P&D locations for inbound and outbound tasks. The P&Ds can be chosen from a lookup.
* Display Info - This button displays some further information about the aisle:
** Availability - Set from the WMS.
** PD Weighting/Total Priority/IN/Out - Future development.
** Truck In - If a truck is currently in the aisle, the RDT will be shown here. 
* Reset Status - Clears the aisle of any locks, allowing other RDT users to work in the aisle. Included for support purposes.

Alternatively, the WMS has the ability to send some of these additional settings from the Aisles Maintenance screen.

=Appexdices=

==Rules And Categories ==


{| class="prettytable"
! <center>Name</center>
! <center>Type</center>
! <center>Description</center>
! <center>Category</center>
! <center>Default</center>

|-
| Action Password
| WHSE, OWNER
| The password required when RDT functions are password-protected
| 03
| FRAGGLEROCK

|-
| Ad Hoc Deconsolidation
| WHSE, OWNER
| Are deconsolidation tasks sequenced manually or by the system?
| 01
| N

|-
| Aisle Length
| WHSE, OWNER
| The length of the Aisle portion of the Location code.
| 33
| 2

|-
| Exchange Replen
| WHSE, OWNER
| If the Warehouse is Block Stack, allow Replens to be exchanged as well
| 01
| N

|-
| Allow Overpicking
| WHSE, OWNER
| Allow the RDT user to enter a picked quantity which is greater than that required by the order.
| 02
| N

|-
| Allow Task Exchange
| WHSE, OWNER
| WCS checks for outstanding tasks to give to the user before asking WMS whether the pallet is available for exchange
| 01
| Y

|-
| Batch Delivery Process
| WHSE, OWNER
| Enable creation of flat files for the Batch Carton Delivery process.
| 01
| N

|-
| Bay Length
| WHSE, OWNER
| The length of the Bay portion of the Location code
| 34
| 2

|-
| Bespoke BHS No Mixed Stock
| WHSE, OWNER
| Disables some of the generic Mixed Stock functionality in the warehouse
| 01
| N

|-
| Bespoke Kraft Batch
| WHSE, OWNER
| Remove non-alphabetic characters from the start of the Batch
| 01
| N

|-
| Bespoke No Batch Prompt
| WHSE, OWNER
| If this rule is enabled, no customer's batch will be prompted when entering pallet details, even if the WMS has requested that one is entered.
| 01
| N

|-
| Bespoke Nokia Stock Take Imps
| WHSE, OWNER
| If this rule is enabled, only the impression quantity will be prompted for when checking impression stock
| 01
| N

|-
| Bespoke Site Rule
| WHSE, OWNER
| Site identity defining which bespoke rules are to apply
| 9001
| 

|-
| Block Stack
| WHSE, OWNER
| Enables some RDT functions to exchange pallets
| 01
| N

|-
| Close GRN
| WHSE, OWNER
| Allow RDT users to close GRNs at the end of the receipt process, by asking them to confirm that the GRN is now complete.
| 01
| N

|-
| Concurrent Picking
| WHSE, OWNER
| Allow loads to be picked concurrently with other loads, when picking by aisle. This stops new loads being started by pickers until the current load has been fully allocated to pickers.
| 01
| Y

|-
| Conveyor Input Spur
| WHSE, OWNER
| Bespoke: Conveyor Input Spur Location. Required for RDT Reject Spur Processing
| 03
| 

|-
| Conveyor Input Spur CD
| WHSE, OWNER
| Bespoke: Conveyor Input Spur Check Digits. Required for RDT Reject Spur Processing
| 03
| 

|-
| Conveyor Input Spur Type
| WHSE, OWNER
| Bespoke: Conveyor Input Spur Type. Required for RDT Reject Spur Processing
| 28
| 

|-
| Conveyor Reject Spur
| WHSE, OWNER
| Bespoke: Conveyor Reject Spur Location. Required for RDT Reject Spur Processing
| 03
| 

|-
| Conveyor Reject Spur CD
| WHSE, OWNER
| Bespoke: Conveyor Reject Spur Check Digits. Required for RDT Reject Spur Processing
| 03
| 

|-
| Conveyor Reject Spur Type
| WHSE, OWNER
| Bespoke: Conveyor Reject Spur Type. Required for RDT Reject Spur Processing
| 28
| 

|-
| Deconsolidation Method
| WHSE, OWNER
| Whether Deconsolidation tasks are processed by the WCS
| 31
| N

|-
| Default Company Code
| SYS
| This is the default company code that the RDT will log on to.
| 03
| 

|-
| Default Putaway Location
| WHSE, OWNER
| 
| 03
| 

|-
| Default Putaway Location CD
| WHSE, OWNER
| 
| 03
| 

|-
| Default Putaway Location Type
| WHSE, OWNER
| 
| 28
| 

|-
| Default Receiving Location
| WHSE, OWNER
| Default Receiving Location. If entered, the RDT Receipt Module allows the user to choose a receiving location, which defaults to this parameter.
| 03
| 

|-
| Default Receiving Location CD
| WHSE, OWNER
| Default Receiving Location Check Digits
| 03
| 

|-
| Default Receiving Location Type
| WHSE, OWNER
| Default Receiving Location Type
| 28
| 

|-
| Delete Records
| SYS
| When this option is checked, completed tasks are deleted from the WCS database. All logging is still in place. When un-checked, the completed tasks are marked for deletion by the cleardown process.
| 01
| N

|-
| WCS Despatch Label Format
| WHSE, OWNER
| Format of the despatch label
| 25
| 

|-
| Display Order Summary
| WHSE, OWNER
| Defines when the order summary screen is displayed on the RDT during part picking.
| 42
| S

|-
| Change Warehouse
| SYS, GRP
| Allows the user to change the default warehouse they can see
| 01
| N

|-
| Comms
| SYS, GRP
| Allows the user full access to the RDT Comms menu. If this is enabled, the following option need not be.
| 01
| N

|-
| Comms (Enquiry Only)
| SYS, GRP
| Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.
| 01
| N

|-
| Logs
| SYS, GRP
| Allows the user access to the Logs Enquiry screens in the System Tools menu
| 01
| N

|-
| Report
| SYS, GRP
| Allows the user access to the Reports menu
| 01
| N

|-
| System Settings
| SYS, GRP
| Allows the user access to the System Settings option on the System Tools menu. NOTE: This option should only be enabled for super-users, and even then should only be enabled sparingly.
| 01
| N

|-
| Standing Data
| SYS, GRP
| Allows the user full access to all items on the Standing Data menu. If this is enabled, the following option need not be. NOTE: This option will allow users to see other users' passwords, and should therefore be limited only to those users who require it.
| 01
| N

|-
| Standing Data (Enquiry Only)
| SYS, GRP
| Allows the user access to the Enquiry screens only on the Standing Data menu
| 01
| N

|-
| Task Edit
| SYS, GRP
| Allows the user full access to all the screens on the Tasks menu. If this is enabled, the following option need not be.
| 01
| N

|-
| Task (Enquiry Only)
| SYS, GRP
| Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.
| 01
| N

|-
| Clear-down options
| SYS, GRP
| Allows the user access to the Clear-Out options on the System Tools menu. NOTE: This should only be available for super-users.
| 01
| N

|-
| Compact Database
| SYS, GRP
| Allows the user access to the Compact Database option on the System Tools menu.
| 01
| N

|-
| Check Digits?
| WHSE, OWNER
| Does the warehouse use check digits, or just location codes?
| 11
| Y

|-
| Customer Pallet No
| WHSE, OWNER
| Display customer pallet number on the RDT
| 01
| N

|-
| Enable Dual Cycling
| WHSE, OWNER
| If this is enabled, the RDT logon procedure allows users to choose whether they work in Bulk (NA areas) or not. Depending on this choice, the RDT displays Dual Cycling options for the users.
| 01
| N

|-
| Encoded Sell By Dates?
| WHSE, OWNER
| Use encoded sell by dates?
| 01
| N

|-
| Lock Pick Header 
| WHSE, OWNER
| Lock the picking header record for full pallet picking/load building
| 01
| Y

|-
| Enable Hold Priority
| SYS
| This allows the lowest priority in the WCS to be used as a Held status. When this option is checked, and tasks on priority 9 will not be allocated to RDTs to complete. To release the tasks, re-prioritise the task to a higher level.
| 01
| Y

|-
| Mixed Stock
| WHSE, OWNER
| Do you have mixed-stock pallets?
| 01
| N

|-
| Multi-Pallet Putaway
| WHSE, OWNER
| Allow several pallets to be picked up during putaway
| 02
| N

|-
| Multi-UOM processing
| WHSE, OWNER
| Whether the WCS deals with multiple UOMs
| 01
| N

|-
| Enable Pack Size Entry
| WHSE, OWNER
| If this rule is enabled, pack size will be prompted for when entering pallet details for impression stock
| 01
| N

|-
| Pick Dependencies
| WHSE, OWNER
| Ensure part picks are not released for picking until any outstanding replenishment has been completed first
| 01
| Y

|-
| Picker Replens
| WHSE, OWNER
| Allow pickers to perform their own replens at the point of picking the part picks.
| 02
| N

|-
| Ad Hoc Move
| WHSE, OWNER
| Allow instigation of a housekeeping Move from the RDT.
| 02
| Y

|-
| Ad Hoc Putaway
| WHSE, OWNER, GRP
| Allow Ad Hoc Putaway for shelving locations. Bespoke.
| 02
| N

|-
| Bulk PI
| WHSE, OWNER, GRP
| Allow Perpetual Inventory (ad hoc stock check).
| 02
| Y

|-
| RDT Cancellation
| WHSE, OWNER, GRP
| Allow cancellation on the RDTs? This option can be over-ridden by the Group setting
| 02
| N

|-
| Enable RDT Cherry Picking
| WHSE, OWNER, GRP
| Choose an order to pick from
| 01
| N

|-
| Combined Split (Bespoke)
| WHSE, OWNER GRP
| Bespoke: Ad hoc movements of small quantities of stock to other locations
| 02
| N

|-
| Continuous Part Picking
| WHSE, OWNER, GRP
| When part picking, asks the user whether they want to continue part picking (i.e. build a despatch pallet from several pick lines).
| 01
| Y

|-
| Damages
| WHSE, OWNER, GRP
| Allow Damage quantity entry during Goods Receipt
| 01
| N

|-
| RDT DC Aisle Selection
| WHSE, OWNER, GRP
| If using Dual Cycling, this parameter controls whether the user is allowed to select a range of Aisles in which to work, or simply accept the default aisle range entered against the user.
| 01
| Y

|-
| RDT Deconsolidation
| WHSE, OWNER, GRP
| Allow deconsolidation of consolidated orders.
| 02
| N

|-
| RDT Despatch
| WHSE, OWNER, GRP
| Allow despatch of deconsolidated orders.
| 02
| N

|-
| Despatch Serial No's 
| WHSE, OWNER, GRP
| Allow entering serial numbers for picked items. Bespoke.
| 02
| N

|-
| RDT Echo Putaway Location
| WHSE, OWNER
| If enabled, this parameter makes the RDT Receiving process display the suggested putaway location after successfully receiving a pallet.
| 19
| N

|-
| Enter Eurodate
| WHSE, OWNER
| Bespoke: Enter Eurodate rather than Manufacture Date
| 01
| N

|-
| Enter Layers
| WHSE, OWNER
| Enter Layers and Bits at Goods Receipt
| 01
| N

|-
| Loading
| WHSE, OWNER, GRP
| Allow Loading onto a vehicle.
| 02
| N

|-
| Location Enquiry
| WHSE, OWNER, GRP
| Allow the RDT user to enquire on the contents of a location from the WMS.
| 02
| Y

|-
| Mail
| WHSE, OWNER, GRP
| Allow receipt of messages from Maintenance administrators. (Generally, this should always be enabled).
| 02
| Y

|-
| Marshalling
| WHSE, OWNER, GRP
| Not Yet Implemented.
| 02
| N

|-
| Measure Qty
| WHSE, OWNER
| Allow Measure Quantity to be entered on the RDT
| 01
| N

|-
| Move Enquiry
| WHSE, OWNER, GRP
| Allow the RDT to see where a pallet is going.
| 02
| Y

|-
| Select Movements
| WHSE, OWNER, GRP
| Allow cherry-picking of an individual Move task.
| 02
| Y

|-
| Pallet Enquiry
| WHSE, OWNER, GRP
| Allow the RDT user to enquire on the contents of a pallet from the WMS.
| 02
| Y

|-
| Pallet Move
| WHSE, OWNER, GRP
| Allow the user to complete Full-Pallet Movements generated from the WMS.
| 02
| Y

|-
| Part Picking
| WHSE, OWNER, GRP
| Allow the user to complete Case and Unit picks from the RDT.
| 02
| Y

|-
| Lost Label 
| WHSE, OWNER
| Controls whether a user is allowed to identify a pallet during picking from its stock information (stock code, batch, etc) rather than entering the pallet ID
| 02
| Y

|-
| Pick Location Error
| WHSE, OWNER, GRP
| Allow the RDT picker to cancel a pick at the point of confirming the location code.
| 02
| N

|-
| Picking
| WHSE, OWNER, GRP
| Allow the user to complete Full-pallet Picks.
| 02
| Y

|-
| RDT Pop Up Description
| WHSE, OWNER
| Pop up description of stock on RDT screen
| 38
| N

|-
| Putaway
| WHSE, OWNER, GRP
| Allow Full-Pallet Putaway.
| 02
| Y

|-
| Receipt
| WHSE, OWNER, GRP
| Allow Blind (Stock level) and Check (Pallet level) Goods Receipt.
| 02
| Y

|-
| Receipt Serial No's
| WHSE, OWNER, GRP
| Allow entering serial numbers for received items. Bespoke.
| 02
| N

|-
| Additional Pallets
| WHSE, OWNER, GRP
| Allow additional pallets to be received during the RDT receipt process
| 02
| Y

|-
| Reject Spur Processing
| WHSE, OWNER, GRP
| Allow Reject Spur Processing. Bespoke to automated conveyor and P&D systems. Bespoke.
| 02
| N

|-
| Stock Moves
| WHSE, OWNER, GRP
| Allow completion (and/or generation) of a Replenishment. Bespoke.
| 02
| N

|-
| RDT Reposition
| WHSE, OWNER, GRP
| Allow reposition on the RDTs? This option can be over-ridden by the Group setting
| 02
| N

|-
| Select Replen
| WHSE, OWNER, GRP
| Allow Select Replenishment. Bespoke.
| 02
| N

|-
| Shipment Pallet Building
| WHSE, OWNER, GRP
| Allow Shipment Pallet Building. Bespoke.
| 02
| N

|-
| Shipment Pallet Despatch
| WHSE, OWNER, GRP
| Allow Shipment Pallet Despatch. Bespoke.
| 02
| N

|-
| Shipment Pallet Moves
| WHSE, OWNER, GRP
| Allow Shipment Pallet Moves. Bespoke.
| 02
| N

|-
| Stock Enquiry (Bespoke)
| WHSE, OWNER, GRP
| Bespoke: Enquire on Stock code
| 02
| N

|-
| Stock Move
| WHSE, OWNER, GRP
| Allow Stock Moves (request replenishment of pick face). Bespoke.
| 02
| N

|-
| Stock Take
| WHSE, OWNER, GRP
| Allow Full (Blind) and Partial (Check) Stock Check.
| 02
| Y

|-
| RDT Weighing
| WHSE, OWNER, GRP
| Allow the RDT user to Weight Shipment Packages.
| 02
| N

|-
| Weight
| WHSE, OWNER
| Allow Weight to be entered on the RDT
| 01
| N

|-
| Replen Dependency
| WHSE, OWNER
| This rule controls whether the number of replenishment moves into a pick face are limited. Also, that the replen associated with the highest priority pick is released first, whilst all others are held.
| 01
| N

|-
| WCS Generate Replen
| WHSE, OWNER
| Let WCS Generate Replenishments
| 01
| Y

|-
| Enter Pack Type
| WHSE, OWNER
| Prompt for the pack type when picking. This is for the carton sizes when pack records are created.
| 41
| N

|-
| Enter Pick Station
| WHSE, OWNER
| Identify the picking station at the start of part picking
| 01
| N

|-
| Enter WMS Rotation
| WHSE, OWNER
| Allow the user to enter Rotation during Goods Receipt
| 01
| N

|-
| Exclude Blocked Moves from Priority Calc
| WHSE, OWNER
| Whilst calculating the priority of moves within an aisle, exclude moves which cannot currently be completed, due to blocked P&D locations.
| 01
| Y

|-
| Extended Reposition Validation
| WHSE, OWNER
| Whether the WCS performs extended checks when a reposition location is chosen.
| 01
| N

|-
| Flat File FTP Location
| SYS
| Bespoke: The location where files are to be found on the FTP server.
| 24
| 

|-
| Flat File FTP Password
| SYS
| Bespoke: The password for logging into the FTP server.
| 26
| 

|-
| Flat File FTP Server
| SYS
| Bespoke: The server where flat files are sent.
| 03
| 

|-
| Flat File FTP User
| SYS
| Bespoke: The user for logging into the FTP server.
| 03
| 

|-
| Flat File Location
| SYS
| Bespoke: The location where files are to be located on the FTP server.
| 24
| 

|-
| Force Sky Picking
| WHSE, OWNER
| Are part pick tasks from bulk treated as sky picks?
| 01
| N

|-
| Residual Stock Balance Enquiry
| WHSE, OWNER
| Controls whether the RDT user is prompted to enter the amount of remaining stock in the pick face after a part pick. The WCS requests the WMS to find the current quantity of stock in the pick face.
| 02
| N

|-
| Level Length
| WHSE, OWNER
| The length of the Level portion of the Location code.
| 35
| 2

|-
| Load before Pick Confirmation
| WHSE, OWNER
| Controls whether the WCS will allow loading to be done before the entire order has been Pick Confirmed in the WMS
| 01
| N

|-
| Loading Method
| WHSE, OWNER
| Loading Method in use for the warehouse
| 20
| N

|-
| Loading Selection Type
| WHSE, OWNER
| Controls whether the RDT initially asks the user to load stock by Route/Load or Order Number. This can be changed by the user when loading.
| 37
| R

|-
| Log Path
| SYS
| WCS Logging database - When this option is checked, you will be prompted to enter a location for the logging database. THIS OPTION MUST NOT BE CHANGED IF THE WCS SERVER IS RUNNING. When this is done, the logging files in the normal database are no longer used - a new database will be created in the defined area and the WCS server will begin all logging to this database instead. All options in the WCS that use these logging files will now use the new database instead. The logging files are: Error log; Incoming log; Outgoing log; RDT Activities and; Exceptions.
| 25
| 

|-
| Move Efficient
| WHSE, OWNER
| Location or priority efficiency
| 05
| L

|-
| NADC Aisle Lock
| WHSE, OWNER
| The point at which an aisle is locked to prevent other RDTs using the aisle
| 32
| L

|-
| NADC Crossover Method
| WHSE, OWNER
| The method by which the RDT NA drivers are moved to another aisle in their range during Dual Cycling.
| 18
| T

|-
| NADC Skip Putaway
| WHSE, OWNER
| Allow full NADC users to skip putaways in aisles, and do the next pick immediately.
| 02
| Y

|-
| NADC Threshold Priority
| WHSE, OWNER
| If using the Threshold crossover method, this parameter details the level at which tasks are considered urgent, to be actioned immediately.
| 17
| 4

|-
| Nokia Barcodes
| WHSE, OWNER
| This rule controls whether the RDT will expect to scan Nokia barcode labels
| 01
| N

|-
| Ora Database
| SYS
| The database the WCS connects to for the messages.
| 03
| 

|-
| Ora Incoming Queue Name
| SYS
| The Oracle queue on which Incoming messages are stored. Outgoing messages are stored by messages type on the queues defined in the table ORA Type Queues.
| 03
| 

|-
| Ora Password
| SYS
| The password of the user for the connection to the Oracle database.
| 26
| 

|-
| Ora User
| SYS
| The username for the connection to the Oracle database
| 03
| 

|-
| WCS Pallet Enquiry Label Format
| WHSE, OWNER
| Format of pallet enquiry label
| 25
| 

|-
| Pallet Enquiry Print Labels
| WHSE, OWNER
| Controls if pallet label can be printed from a pallet enquiry
| 01
| N

|-
| PC Generation Algorithm
| OWNER
| Algorithm to generate Picking Containers
| 9002
| 

|-
| PC Prefix
| OWNER
| Prefix for automatically-generated Picking Container
| 03
| 

|-
| Pick By
| WHSE, OWNER
| Controls what the RDT prompts for as confirmation that the correct item has been found for picking
| 23
| N

|-
| Pick By Carton
| WHSE, OWNER
| Pick a quantity of stock by scanning individual cartons.
| 01
| N

|-
| Consolidation Group
| WHSE, OWNER
| For Consolidated picking: How to create groups of picks.
| 10
| N

|-
| Pick In Sequence
| WHSE, OWNER
| If picks have been placed on a Load, what sequence should orders be released for picking?
| 36
| N

|-
| Pick Into Containers
| WHSE, OWNER
| Controls whether RDT Part Picking prompts for Picking Container IDs
| 39
| N

|-
| Pick Label Prompt
| WHSE, OWNER
| Where should pick labels be prompted for?
| 29
| P

|-
| Pick Page Allocation
| WHSE, OWNER
| This controls how the WCS allocates picks to pickers.
| 12
| P

|-
| Picker Replen by Quantity
| WHSE, OWNER
| Allow pickers, when doing their own replenishments, to replenish areas by stock moves, not pallet moves.
| 01
| N

|-
| Picks by Quantity
| WHSE, OWNER
| Allocates pick tasks to the RDT users by quantity, largest first.
| 01
| N

|-
| Print Despatch Labels
| WHSE, OWNER
| Whether the RDT attempts to print despatch labels for picked stock.
| 30
| N

|-
| Purchase Order Entry
| WHSE, OWNER
| Enable Purchase Order entry during RF goods receipt, if the receipt contains lines from multiple Purchase Orders.
| 01
| N

|-
| Queue Listener Agent
| SYS
| The Oracle agent defines which messages to take from the Oracle database queues, and what Agent to write them as. Each instance of the WCS has a unique Agent name, usually per warehouse.
| 03
| 

|-
| RDT Wait Time
| SYS
| This is the amount of time that the RDT will wait before re-trying communications.
| 04
| 20

|-
| RDT_WCS LocalPort
| SYS
| This is the port that the WCS listens to for communications from RDTs.
| 04
| 15002

|-
| Default Pallet Type
| WHSE, OWNER
| During Goods Receipt, whether the RDT user is prompted for a valid Pallet Type at the start of the receipt. This will then be the default for all pallets subsequently received during that session for that user. Without this item being enabled, pressing 'RETURN' in the pallet type field against a received pallet will tell WMS to default to its Default Pallet Type.
| 01
| N

|-
| Enter Receipt Type
| WHSE, OWNER
| Allow the user to enter the receipt type in RDT Goods Receipt
| 01
| N

|-
| Receipt Impressions Check
| WHSE, OWNER
| If the impressions quantity for a stock item is different to the impressions quantity preadvised, this parameter details the action the RDT is to take. Only for preadvices at pallet level.
| 22
| N

|-
| WCS Receipt Label Format
| WHSE, OWNER
| Format of the receipt label printed, if printed from the WCS.
| 25
| 

|-
| Receipt Non-advised Stock Codes
| WHSE, OWNER
| Is the user allowed to receive stock codes that have not been preadvised for that receipt?
| 22
| E

|-
| Receipt Pallet Count Check
| WHSE, OWNER
| If the number of pallets on a received stock item exceeds that preadvised, this parameter details the action the RDT is to take.
| 22
| N

|-
| Receipt Pallet Qty Check (Pallet)
| WHSE, OWNER
| If the pallet quantity for a stock item is different to the pallet quantity preadvised, this parameter details the action the RDT is to take. Only for preadvices at a pallet level.
| 22
| A

|-
| Print Labels
| WHSE, OWNER
| Controls where/if pallet labels are printed during the receipt process
| 21
| N

|-
| Selection Type
| WHSE, OWNER
| How to find the receipt on the RDT - via Advice Note or GRN no.
| 08
| A

|-
| Single Scan Entry for Additional Pallets
| WHSE, OWNER
| Allow users to scan single barcode for entry of some required elements for adding additional pallets
| 01
| N

|-
| Receipt Standard Qty Check (Stock)
| WHSE, OWNER
| If the pallet quantity for a stock item is different to the standard pallet quantity, this parameter details the action the RDT is to take. Only for preadvices at stock level.
| 22
| I

|-
| Receipt Total Qty Stock Check
| WHSE, OWNER
| If the quantity of a stock item exceeds the total preadvised, this parameter details the action the RDT is to take.
| 22
| E

|-
| Receipt Type
| WHSE, OWNER
| How the RDT actions the Receipt process - either Blind (stock-level advice) or Check (Pallet-level advice)
| 07
| B

|-
| Request Putaway Details at Scan
| WHSE, OWNER
| Require the WMS to decide on a putaway location at the time of putaway scan, rather than at receipt
| 01
| N

|-
| Seamless Exchange
| WHSE, OWNER
| If this rule is set, the RDT will check whether an exchange can be done immediately, without requiring the user to press the Error function key first.
| 01
| N

|-
| Send Aisle Status to WMS
| WHSE, OWNER
| For NA areas: Inform the WMS that the aisle has a truck in it.
| 01
| N

|-
| Ship Pack Weight Check
| WHSE, OWNER
| If a weight entered during the Shipment Package Weight function is outside the tolerance value, what action should the RDT take?
| 22
| N

|-
| Stock Take Enter GRN
| OWNER
| When adding pallets during Stock Take or Perpetual Inventory, request the user to enter a GRN number
| 01
| N

|-
| Task Identifier
| WHSE, OWNER
| Which field to use to identify pallets
| 06
| P

|-
| Use Dummy Checksum
| SYS
| Used to terminate the interface messages with a dummy checksum value (??)
| 01
| N

|-
| Use WMS Rotation 
| WHSE, OWNER
| If this rule is set, wherever Customer Batch is displayed or entered during Picking or Deconsolidation, the RDT will display or request the entry of WMS Rotation instead.
| 01
| N

|-
| User Select Pick Location
| WHSE, OWNER, GRP
| Is the user allowed to specify the location from which picking to start?
| 01
| N

|-
| Vendor Managed Inventory
| WHSE, OWNER
| If this flag is enabled, supplier will be displayed and entered during standard RF modules
| 01
| N

|-
| Exclude Source to Dest moves from WA DC
| WHSE, OWNER
| Ensures WA DC (interleaving) focuses more on emptying P&D locations rather than completing housekeeping moves.
| 01
| Y

|-
| WCS_WMS RemotePort
| SYS
| This is the port that the WMS listens to for communications from the WCS.
| 04
| 

|-
| Weigh Shipment Package
| WHSE, OWNER
| Allow the entry and validation of the Catch Weight during the Shipment Pallet Building process
| 01
| N

|-
| Weight Tolerance
| WHSE, OWNER
| If weights are being checked by the Shipment Package functions, what tolerance is allowed (plus or minus, in kilograms)?
| 40
| 

|-
| Window Caption
| SYS
| This field changes the displayed name of the WCS Server process, when running. This is useful when running multiple systems on one site or one server.
| 03
| Warehouse Control Server

|-
| WMS HostName
| SYS
| This is the IP address or host/DNS name of the WMS machine.
| 03
| <nowiki>*****</nowiki>

|-
| WMS to WCS Try Limit
| SYS
| This is the amount of times the WCS will try to send a message to the WMS, if the message has been refused, before logging the error and trying the next.
| 04
| 3

|-
| WMS_WCS LocalPort
| SYS
| This is the port that the WCS listens to for communications from the WMS.
| 04
| 

|}
Categories:


{| class="prettytable"
! <center>Category</center>
! <center>Value</center>

|-
| 01
| N-Disabled

|-
| 
| Y-Enabled

|-
| 02
| N-Disabled

|-
| 
| P-Password-Protected

|-
| 
| Y-Enabled

|-
| 03
| Plain Text

|-
| 04
| Plain Numeric

|-
| 05
| L-By Location

|-
| 
| P-By Priority

|-
| 06
| C-By Cust Pallet ID

|-
| 
| P-By Pallet ID

|-
| 
| S-By Stock

|-
| 07
| B-Blind Receipt

|-
| 
| C-Check Receipt

|-
| 08
| A-By Advice No

|-
| 
| G-By GRN No

|-
| 09
| L-By Load Number

|-
| 
| O-By Order Number

|-
| 10
| N-None

|-
| 
| S-By Stock/Batch

|-
| 11
| C-Combo Check

|-
| 
| N-Disabled

|-
| 
| Y-Enabled

|-
| 12
| A-By Aisle

|-
| 
| L-By Load/Aisle

|-
| 
| P-By Order Page

|-
| 
| R-By Reference

|-
| 13
| Date

|-
| 14
| E-Error

|-
| 
| I-Information

|-
| 
| W-Warning

|-
| 15
| F-Full/Blind

|-
| 
| P-Preadvised/Partial

|-
| 16
| A-Area (m2)

|-
| 
| I-Impressions

|-
| 
| L-Length (m)

|-
| 
| Q-Quantity

|-
| 
| V-Volume (m3)

|-
| 
| W-Weight (kg)

|-
| 17
| Priority Values

|-
| 18
| M-Manual

|-
| 
| T-Threshold

|-
| 
| W-Weighting

|-
| 19
| 0-Disabled

|-
| 
| 1-Fetch Details

|-
| 
| 2-Display Location

|-
| 20
| C-By Carton

|-
| 
| F-By Final Media Number

|-
| 
| I-By Picking Container

|-
| 
| N-Disabled

|-
| 
| P-By Pick

|-
| 
| V-By Vehicle/Store/Picking Container

|-
| 21
| C-WCS

|-
| 
| M-WMS

|-
| 
| N-Neither

|-
| 22
| A-Authorisation Required

|-
| 
| E-Error

|-
| 
| I-Informational Message

|-
| 
| N-None

|-
| 23
| B-By Stock and Batch

|-
| 
| P-By Pallet ID

|-
| 
| S-By Stock Code

|-
| 
| V-By Pallet/Stock/Supplier

|-
| 
| X-By Pallet and Stock

|-
| 24
| Plain Text (with directory Browser)

|-
| 25
| Plain Text (with File browser)

|-
| 26
| Plain Text (password text)

|-
| 27
| Date (with Date Picker)

|-
| 28
| Plain Text (with Location Type lookup)

|-
| 29
| M-Marshalling

|-
| 
| P-Pick

|-
| 30
| D-Per Despatch Pallet

|-
| 
| N-Disabled

|-
| 
| P-Per Pick

|-
| 
| R-Request Quantity

|-
| 
| W-WMS

|-
| 31
| D-Deconsolidate Only

|-
| 
| N-Disabled

|-
| 
| P-Deconsolidate and Pack

|-
| 32
| A-At Allocation

|-
| 
| L-At Location

|-
| 33
| Aisle Length

|-
| 34
| Bay Length

|-
| 35
| Level Length

|-
| 36
| A-By Drop Sequence

|-
| 
| D-By Reverse Drop Sequence

|-
| 
| N-Disabled

|-
| 37
| O-By Order Number

|-
| 
| R-By Route/Load

|-
| 38
| N-Disabled

|-
| 
| P-Pick Only

|-
| 
| R-Goods Receipt Only

|-
| 
| Y-Enabled

|-
| 39
| G-Generate

|-
| 
| N-Disabled

|-
| 
| P-Password_Protected

|-
| 
| T-Pre-Set Tray Values

|-
| 
| Y-Enabled

|-
| 40
| Decimal

|-
| 41
| M-At Marshalling

|-
| 
| N-Disabled

|-
| 
| S-At Start

|-
| 42
| E-At Each Dispatch Pallet

|-
| 
| N-Disabled

|-
| 
| S-At Start Only

|-
| 9001
| -Standard site (No bespoke rules)

|-
| 
| BIBBY-Bibby

|-
| 
| CERT-Cert

|-
| 
| FWLMA-XKO Sites

|-
| 
| NIJ-DHL EXEL Healthcare

|-
| 
| SCH-Schenker

|-
| 
| TBI-DHL EXEL Dublin RHR

|-
| 
| TBW-DHL EXEL Whitwood

|-
| 
| TNT-TNT

|-
| 
| JJD-JJD

|}
==Printing from the WCS==

There are many ways in which printers can be set up for WCS use.

* The printers can be fixed or wireless.
* They can be Windows printers (networked or direct connect), UNIX queues or Wireless (via TCP/IP settings).

For all except wireless, this requires the set-up of a Windows printer (or queue). The WCS is then informed of the printerâ€™s existence using the WCS Maintenance Printers Maintenance form.

'''Note:''' Although these methods can be used for standard network printers, it is recommended that the printer then be used exclusively for WCS printing.

=== '''Setting Up Wired Windows Printers'''===

The printer must first be set up on the RDT or WCS server. This should be done following your network administration policy.

Once this is completed in Windows, the printer must then be set up for the WCS to recognise. To do this, use the WCS Maintenance Printers Maintenance screen. 

=== '''Wireless Printing''' ===

You can set up a Windows printer for the wireless printer, using the TCP/IP settings or, more commonly, the WCS can be set up for direct printing.

=== '''Windows Queue''' ===

This method is extremely similar to setting up Windows printers (see 4.2), but the method for setting up the Windows queue is different. You should follow your network administration policy for setting up printer queues. The following demonstrates how the printer would be set up:

Add a new printer from the Control Panel. Choose to set up a local printer, and choose the option to create a new port, as below:

[[Image:Pic3.png]]

Choose Standard TCP/IP port. At this point, you will be taken through the following wizard.

[[Image:Pic4.png]]

When this port is added, the first Windows Printer wizard will be completed, and allow you to test print.


Once this is completed in Windows, the printer must then be set up for the WCS to recognise. To do this, use the WCS Maintenance Printers Maintenance screen, choosing the queue from the drop-down list of Windows printer queues. 


=== '''UNIX Queue''' ===

This is similar to the Windows Queue setup (above).


Add a new printer from the Control Panel. Choose to set up a local printer, and choose the option to create a new port, as below:

[[Image:Pic5.png]]

Choose LPR port. At this point, you will be taken through the following wizard.

[[Image:Pic6.png]]

Enter the name or IP address of the UNIX machine hosting the queue, followed by the name of the printer queue on that server. Click OK when this is completed.


You will then be prompted through the standard 'Install Printer Software' dialogue - choose 'Generic/Text Only' as the Manufacturer/Printer.


Once this is completed in Windows, the printer must then be set up for the WCS to recognise. To do this, use the WCS Maintenance Printers Maintenance screen, choosing the queue from the drop-down list of Windows printer queues. 


=== '''Direct Connect''' ===

'''Note: '''This is the normal set-up for wireless printing in the WCS.

In this option, the printer merely needs to be set up within the WCS Maintenance Printers Maintenance screen.

[[Category:WCS Training Guides]][[Category:Documents]]