WCS - User contributions [en-gb]

C-TMS Automotive RF Process

2026-02-19T10:24:12Z

Anw: Minor formatting change

'''Automotive RF Process'''

== Messages ==

{| class="wikitable prettytable"
! '''Message'''
! '''From > To'''
! '''Description'''

|-
| 404
| TMS > WCS
| Order Preadvice Message which creates the TMS_Preadvice_Header and TMS_Preadvice_Detail records.

|-
| 804
| WCS > TMS
| Order Creation module sends these as each item is scanned onto the order.

|-
| 441
| TMS > WCS
| Item/Load Creation message. Should get one of these for each 804 message. I think this creates the TMS_Load* records.

|-
| 442
| TMS > WCS
| Trip ready to load message which I presume updates the TMS_Load* records to ‘Ready to Load’ status (!).

|-
| 841
| WCS > TMS
| Load Confirmation

|-
| 431
| TMS > WCS
| Unload/Receipt message (only if x-docked)

|-
| 432
| TMS > WCS
| Trip ready to unload.

|-
| 831
| WCS > TMS
| Unload Confirmation.

|-
| 441
| TMS > WCS
| Item/Load Creation message again. The process loops around again to the 3<sup>rd</sup> message above.

|-
| 851
| WCS > TMS
| Asset (Item) Enquiry

|-
| 451
| TMS > WCS
| Asset (Item) Enquiry Response

|-
| 471
| TMS > WCS
| DU (Media) Type Updates

|-
| 472
| TMS > WCS
| New Depot

|}
== Standing Data ==
Whenever DU Type information is changed in C-TMS then 471 messages are sent to WCS for all of the depots requiring WCS RF Cross-Docking containing this information for WCS to maintain its own Media Types against the corresponding depots.

Whenever a depot is marked as requiring WCS RF Cross-Docking functionality then a 472 messages is sent from C-TMS to create this new depot in WCS.

A button (Re-Send ALL) can then be pressed to send all of the DU Types to WCS for all of the appropriate depots including the newly marked one.

== Order Creation ==
404 messages arrive at around 00:10 each night, showing the next 24 hours of orders to be fulfilled. There should be one per destination location.

Order Creation starts. This process is used to associate pallets/cages (i.e. containers or assets) to an order.

First, a label printer is requested.

Then a media type:

If re-usable Asset, the process requests the user to scan the Asset code (barcode on the cage). This is validated as being the right media type by passing a 851 message to CTMS and getting a 451 message from C-TMS in response.

If non-reusable, ID is generated by WCS.

RDT prompts for destination – WCS matches this to a destination and order on the Preadvice tables.

If OK, a label is printed (even if it’s a reusable Asset with a barcode), a Preadvice Item record is created, 804 message is sent.

{{Note}} In CTMS, this associates the item to the order. If this is an asset, and Asset History record is NOT created at this stage, so there’s no audit that the Asset was ever put on the order until Loading.

{{Note}}''If this is a reusable Asset, the item is added by with a sequence (generated from the number of times the asset has been used) to keep the item unique.''

== Loading ==
Once the order reached a certain status in CTMS {{warning}}INFO REQUIRED, the order is planned on a trip and that trip is allocated a marshalling location (outbound bay) in CTMS, the system generates loading messages (441 or 442 messages – {{warning}}INFO REQUIRED.

This creates Load* records for the orders, trips and items at status C (Load Checked, or Ready For Loading, if you prefer).

{{Note}} This refers to a previous process that was designed into Dunelm for Load Checking before Loading proper – this is no longer used.

User blind enters the trip ID.

User scans each item on the trip.

{{Note}} ''For Assets: Although the barcode scanned contains only the asset code without the unique sequence, and the messages sent to WCS contain this sequence, the RDT identifies these as checking for an asset on the trip that matches what we have of the ID. There should only be one, but if not, the system sorts them in reverse sequence and selects the top 1.''

An 841 message sent for each item scanned (''for Assets: the whole ID plus sequence is sent back'').

'''Note:''' There is some functionality to Unload an item on RDT – {{warning}}INFO REQUIRED

Once complete, trip is marked as En Route.

{{Note}} For Assets, at scanning, an Asset History record is created showing the Asset as In Transit at this stage.

== Delivery ==
At this stage, CTMS generates messages to Microlise.

''For Assets: Only the Asset ID (not the sequence) is sent to Microlise for delivery.''

Microlise scans each item at destination and sends back a message to CTMS upon completion.

Order is marked as Complete.

== Unloading ==
At that depot, Receipt could now start:

{{warning}}INFO REQUIRED

[[Category:Documents]][[Category:Technical Guides]]

RDT Functionality

2025-12-19T12:23:24Z

Anw: Minor formatting change

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = RDT Functionality Guide
| Reference = UG 106181
| Version = 11.02
| Date = 30th October 2025
| Sysver = 3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client.

Function keys are standardised throughout the RDT system, consisting of:

* <code>F1</code>- Confirm Key - in most modules, this key is generally the key that you would press to confirm anything you have entered.
* <code>F2</code>- Amend Key
* <code>F3</code>- Add Key - in some modules (for example, Goods Receipt, Stock Take), you use this key to start the process of adding a new record (pallet, product, etc). When complete, generally you use the F1 key above to confirm that you have finished.
* <code>F4</code>- Error Key - in most modules, you use this key to state that there has been an exception. You will either be take to the exception screen for this particular process, or you might be shown a menu of exceptions that you can choose from.
* <code>F5</code>- Special/Zero Key
* <code>F7</code>- Enquiries menu - in some modules, you can press this key to open up a quick menu which has access to any enquiries that your user has access to. You can use them here to check/problem solve, and then back out to return to the task that you were in.
* <code>F8</code>- Additional Information Key - in some modules (for example picking), you can press this key to show additional information on the task. For example, in Picking, this might show you some order/address information at one point, or show you some stock information at a different point. The system keeps track of where you are up to and shows you the most pertinent information. This is so that the main screen is kept uncluttered (which is important on a limited screen display size).
* <code>F9</code>- Help Key - this will show you which function keys can be pressed at this time.
* <code>F10</code>- Return to Main Menu Key
* <code>CLEAR</code>/<code>ESC</code>- Backup key
* <code>CRSRUP</code>- Previous Key
* <code>CRSRDN</code>- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

==Multi-part movements==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="wikitable"
| 1
| Source
|
|
| Destination
|-
| 2
| Source
| Interim1
|
|
|-
| 3
| Source
|
| Interim2
|
|-
| 4
|
| Interim1
| Interim2
|
|-
| 5
|
| Interim1
|
| Destination
|-
| 6
|
|
| Interim2
| Destination
|}

== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="wikitable"
! Truck Type (Code)
! Tasks to be done

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="wikitable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

* Wide Area Dual Cycling
* Narrow Aisle Dual Cycling
* Pallet Moves
* Pallet Replens
* Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':
* Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="wikitable"
! Aisle
! Sequence

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="wikitable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="wikitable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="wikitable"
! Task
! From
! To
! Aisle Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:
* OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.
* SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

==Owner Restrictions==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="wikitable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

==Movement Exceptions==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

If the 'Extended Reposition Validation' rule is set to enabled on the WCS then when a user tries to reposition a pallet, the system will perform extra validation with the WMS.

The following checks are made:
* Check that the pallet exists.
* Check that the location exists.
* Check that the pallet type of the pallet being repositioned is allowed in the location.
* Check the bonded flags of the pallet and location.
** If the pallet is bonded, check that the location is also bonded.
** If stock already exists in the location, check that the bonded flags match the bonded flag of the pallet being repositioned.
* Check that the location is available for the pallet type.
* If the location is a multi-deep location then check whether there are other pallets in the location and that they match the location validation flag setting.
* Check that the location is either a bulk location (Loc Use Type '1'), receipt location ('3'), returns location ('4'), damaged stock location ('5') or a multi-pallet location ('M') and there are no pallets which do not satisfy the location validation (Use) flag setting.
** 4 - Valid pallets contain the same stock, batch number and owner batch
** 5 - Valid pallets contain the same stock.
** 6 - Valid pallets contain the same stock and sell-by date.
** 7 - Check the last receipt location for pallets containing the same GRN and stock.
** 8 - Valid pallets contain the same stock and manufacturing date

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

==Multi-Pallet Locations==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:
* Product Code
* Batch
* Manufacture Date
* Sell-by date
* GRN number
* Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:
* Task Exchange
* Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Enhanced Pick Exchange ===
The rule 'Enhanced Pick Exchange' controls whether part pick tasks can be exchanged and also whether pick tasks can be exchanged for pallets from different locations. This also affects full-pallet picking pallet exchange.

If the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. If the ‘Enhanced Pick Exchange’ rule is set to ‘Disabled’ then the RDT will not prompt the user to enter the location of the new pallet and a ‘651’ pallet exchange enquiry message will be sent to the Calidus ''3pl'' system in the present format after the new pallet has been entered.

During full-pallet picking, if the ‘Enhanced Pick Exchange’ rule is set to ‘Enabled’, then the RDT will prompt the user to enter the location of the new pallet after entering a pallet value. This will validate the exchanged pallet with the existing one and may display errors depending on WMS validation configuration.

During part-pallet picking, if the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. After identifying the new pallet, the RDT will prompt the user to enter the location of the new pallet as the 'Enhanced Pick Exchange' rule must be set to 'Enabled' for part pallet pick tasks to be exchanged. This will validate the exchanged pallet in the same way.

The validation errors that may be displayed are:

* unknown pallet.
* pallet under stock take.
* unable to exchange replen.
* location is not a multi pallet location.
* exchanged pallet unknown.
* pallet is unavailable.
* bonded flags do not match.
* stock codes do not match.
* customer batch values do not match.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<pre>
<TEMPLATE>
ABC Pick Label

Marshalling Location:

{MarshLoc}

</TEMPLATE>
</pre>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:
<pre>
ABC Pick Label

Marshalling Location:

MAR01A
</pre>

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="wikitable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="wikitable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet. Enhanced pick exchange may also be enabled - see the section above for details.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

Note that, if Sky Pick is enabled, sky picks at P&D locations can be picked up, moved and completed using this module in the wide areas.

When this module is used in the Narrow Aisle areas when Sky Picking is enabled "At PND", then these sky picks will also be completed here. the process is:

* Narrow aisle truck driver retrieves the pallet from the narrow aisle bulk location and takes the pallet to the PND out location.
* Narrow aisle truck driver removed the required amount of stock from the pallet onto another pallet, entering a unique id for the new pallet so that it can be identified, and leaves this new pallet at the PND out location.
* Narrow aisle truck driver returns the remaining original pallet back to the narrow aisle source location.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="wikitable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:
* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

Note that, if Sky Pick is enabled "At PND", sky picks at P&D locations can be picked up, moved and completed using this module.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:
* FPP- P&D to MARSH
* Replen- P&D to PICK
* Sky Pick
** P&D to SPLIT
** SPLIT to P&D
* Move - P&D to P&D
* Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:
* FPP- BULK to MARSH
* Replen- BULK to PICK
* Sky Pick- none required - only in NA
* Move - BULK to BULK
* Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

==Logging==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

==Parameter-controlled Functions==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

==RDT Messages==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
===RDT Log-on Procedure.===

[[Image:FunctionalityFlowChart1.png]]

===Receipts.===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

===Putaways.===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

===Full Pallet Picking.===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

===Part-pallet Picking.===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

===Pallet Moves.===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

===Stock Take.===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

===Pallet Enquiry.===

[[Image:FC26.PNG]]

===Location Enquiry.===

[[Image:FC27.PNG]]

===Movement Enquiry.===

[[Image:FC28.PNG]]

===Ad Hoc Movements.===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

===Bulk PI.===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

===Select Moves.===

[[Image:FC33.PNG]]

===Loading by Carton.===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

===Shipment Pallet processes.===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

===Select Replenishment.===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

===Serial Number Capture at Goods Receipt.===

[[Image:FC40.PNG]]

===Serial Number Capture at Despatch.===

[[Image:FC41.PNG]]

===Combined Split.===

[[Image:FC42.PNG]]

===Ad Hoc Putaway.===

[[Image:FC43.PNG]]

===Cherry Picking.===

[[Image:FC44.PNG]]

===Deconsolidation.===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

===Despatch by Order.===

[[Image:FC49.PNG]]

===Loading (by Picking Container).===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

Did You Know

2025-12-19T12:04:34Z

Anw: Updated

This guide is intended to help you discover features delivered with your ''CALIDUS'' system.

== ''CALIDUS'' WCS ==

=== Mobile Device Function Keys ===
Function keys are standardised throughout the RDT system, consisting of:

* <code>F1</code>- Confirm Key - in most modules, this key is generally the key that you would press to confirm anything you have entered.
* <code>F2</code>- Amend Key
* <code>F3</code>- Add Key - in some modules (for example, Goods Receipt, Stock Take), you use this key to start the process of adding a new record (pallet, product, etc). When complete, generally you use the F1 key above to confirm that you have finished.
* <code>F4</code>- Error Key - in most modules, you use this key to state that there has been an exception. You will either be take to the exception screen for this particular process, or you might be shown a menu of exceptions that you can choose from.
* <code>F5</code>- Special/Zero Key
* <code>F7</code>- Enquiries menu - in some modules, you can press this key to open up a quick menu which has access to any enquiries that your user has access to. You can use them here to check/problem solve, and then back out to return to the task that you were in.
* <code>F8</code>- Additional Information Key - in some modules (for example picking), you can press this key to show additional information on the task. For example, in Picking, this might show you some order/address information at one point, or show you some stock information at a different point. The system keeps track of where you are up to and shows you the most pertinent information. This is so that the main screen is kept uncluttered (which is important on a limited screen display size).
* <code>F9</code>- Help Key - this will show you which function keys can be pressed at this time.
* <code>F10</code>- Return to Main Menu Key
* <code>CLEAR</code>/<code>ESC</code>- Backup key
* <code>CRSRUP</code>- Previous Key
* <code>CRSRDN</code>- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

== ''CALIDUS'' Assist ==
=== Searching for Help ===
Although all pages from your ''CALIDUS'' system link directly to the appropriate page in this ''CALIDUS'' Assist guide, you can search for help on anything in the system using the search bar. It depends on how you have ''CALIDUS'' Assist configured, but this search bar is normally either in the title at the top of the screen or in the toolbar on the left.

Did you know that you can activate this search at any time using a shortcut key combination? Hover over the Search bar now and you will see it tells you the hot-key combination, typically ALT-F or ALT-SHIFT-F. Hitting those keys together will activate the search box and you can type in what you're looking for. Be aware that these shortcuts are dependent on the browser that you are using, so check for compatibility first.

If you know the name of the page, just type it there and click the '''Go''' button. If you want to search for any text in the page, click the '''Search''' button instead, or just hit enter for ''CALIDUS'' Assist to do it for you. Typically, as you type, the search bar will quickly offer you some matches that might be what you're looking for - if it is, just click the suggestion and Assist will take you there.

Some tips on searching:

* If you enter multiple words (like "fixed drop scheduling") without quotes, the search routine will find you pages that match any of the words, but ordered in the most likely order (i.e. with most matches of most words)
* If there is a page called "fixed drop scheduling", you will be taken straight to it.
* If you enter your search with quotes i.e. "fixed drop scheduling", it will find that specific phrase in the pages, rather than any of the words.
* If you enter plus instead of space i.e. fixed+drop+scheduling, you will only get pages in the results that have all 3 words in them, anywhere in the page, in any order.
* You can also control partial word matching with as asterisk. So let's say you are searching for a parameter called AUTO_SCHED something-or-other. Searching for AUTO_SCHED will not bring back any results, as there are no full words or phrases like that. But if you enter AUTO_SCHED_* instead, it will search for words ''starting with'' "AUTO_SCHED" and bring you back some matches.

=== Searching Tables ===
A lot of the pages have tables of data on them - this can be a bit difficult to see what you're after. So, in the cases where there is a large amount of data in tables, we have made the tables searchable.

On top of the table will be a search box. Type in what you're looking for and the table will be filtered to show all of the matching rows - that is, rows where any column contains that text at all, anywhere. This filters as you type.

Note that some data will be always be shown, like headers, or rows that the writers of the page have decided must always be shown.

You can clear the text out of the search box and this will display everything again - do this by either deleting it or use the provided clear button to the right of the search box.

Have a go below - maybe try entering "ap", then "app", or enter "fruit" and see the way it works.

{| class="wikitable apt-searchable" id="dyk-search-table"
|-
! Fruit !! Some Text - this header row is always shown
|-
| Apple || Green apples
|-
| Orange || Not an apple
|-
| Pineapple || Also not
|-
| Grapefruit || Very big!
|- class="non-searchable"
| Banana || I like bananas, so I'm always going to show them
|-
| Kumquat || Interesting fruit
|-
| Grape || Small fruit
|-
| Tomato || Is this a fruit or a vegetable?
|}

=== Translating ===
The toolbox contains a link to Google Translate to translate the page into a language of your choice. Select the language from the drop-down list, and Google will translate the whole page for you.

There will be a banner at the top showing the translation options after you have selected a language - simply click the X on the banner to return to the standard page.

=== Printing and Exporting ===
You can export pages from ''CALIDUS'' Assist using the ''Print as PDF'' or ''Download as PFD'' link. Where this appears depends on the style the Assist is configured with, but by default this link will be in the ''Toolbox'' menu on the left of the screen, or on the tabs at the top right of the screen.

You can export categories as a full document in the same way - all pages in that category will be included in the PDF in the order in which they are listed in the category.

We've typically also included a link in the description of categories where this will export as a document, and we also add the {{DocLink|Did You Know}} button next to documents that you can download from the first page of Assist.

Main Page

2025-12-19T11:53:10Z

Anw: Updated

<div style="text-align: center;">[[Image:Calidus-Mobile.JPG]]</div>

<center><font size="5">Welcome to the ''CALIDUS'' WCS Mobile Assist help pages.</font></center>

Here you will find all kinds of guides, from simple to advanced, from user guides to technical implementation guides, all to provide as much information on how to get the best out of your ''CALIDUS'' WCS implementation.

Assuming you are now up and running with your system, why not try to find something you didn't know? Try clicking the 'Did You Know' link below.

<center><font size="5">[[Did You Know]]</font></center>

That's how Assist works - help broken down into bite-sized chunks, designed to help you make the most of your system. If you're familiar with the web and familiar with Wiki, you're going to find it easy to get around in Assist.

If you're coming here as a new user without a clear idea of how ''CALIDUS'' WCS works or what it does, you should start with the overview and glossary of terms - that will give you enough information so that you're clear on what we're achieving with this application. You'll find them first in the list below.

If you're more comfortable with documents rather than web pages, we've got you covered.

Every page here can be downloaded as a PDF (including this one) by clicking the ''Print as PDF'' or ''Download as PDF'' link in the toolbar, typically on the left of your browser window, or on the tabs at the top right of the window. That will give you the PDF of just that page, but if you want something more formal, see the heading below called [[#Documents|Documents]] - downloading those as PDFs will give you the formal Aptean document. On this page, we've also provided direct links to those document versions - click the {{DocLink|Main Page}} link next to the page.

As you can see, some of the guides are multi-page, so we organise those into categories of pages. Where those pages form a guide themselves (like the C-TMS Key Functionality), you can use that ''Download as PDF'' or ''Print as PDF'' link again from the category to get all the pages in one handy guide.

We keep these pages up to date based on the latest available version of ''CALIDUS'' WCS - if you see something you like here, but aren't sure whether your version supports it, why not give our team a call? We can advise you on the steps you need to take to upgrade your system to the latest and greatest.

We're constantly updating the system, and that means that we're constantly updating the documentation too. One of the great things about Wiki pages is that the history is kept, so you can click the ''View History'' link (usually at the top of the page) to see all previous versions of the help page. So, although all the guides are the latest version, you can still access the older pages for reference.

The same is true of any of the pictures that we've uploaded in these guides - click on them and you can see the whole history of that picture. You can download them as well, if you like.

Of course, we also keep PDF copies of the previous version of the documentation when we've finished it, so we can always provide them to you. We've generated them from these Assist pages just like you can - because it's that easy to use.

Below you'll find links to all of the guides in this Assist system.

==Overview==
* [[Template:WCS Glossary|WCS Glossary]]
* [[WCS System Overview]]

==Documents==
* [[:Category:Documents]]

* [[:Category:WCS Training Guides]]
**[[Installation Guide]]
**[[Set-up Guide]]
**[[WCS Maintenance]]
**[[RDT Functionality]]
**[[Using WCS from WMS]]
**[[External Data Access]]
** [[Label Formats]]
** [[Common Activities Guide]]

== Mobile Devices ==
* [[:Category:Android|Android]]
** [[Installing Barcoders Android Server]]
** [[Android Setup Guide]]
** [[Android Usage Guide]]
** [[Android Development Guide]]
** [[Android Support Guide]]
* Wavelink (Windows Mobile)
** [[Wavelink Virtual Client]]
** [[Wavelink Client Support]]

== FAQ ==
* [[:Category:FAQ]]
* [[Did You Know]]

== Technical Guides ==
* [[:Category:Technical Guides]]
**[[C-TMS Automotive RF Process]]
**[[ctms:Putway Algorithm Summary|Putway Algorithm Summary]] (external)
**[[Network Diagrams]]
** [[Remote System Connectivity]]

Using WCS from WMS

2025-12-19T11:49:03Z

Anw: Split into separate pages

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=Using WCS from WMS Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= System Overview =

{{:WCS System Overview}}

= RDT Control Processes =
== Menus ==
[[Image:Img1.png]]

The menu is normally located on the top flexible menu.

== System Parameters ==
In order to send RDT messages or tasks to Calidus 3''pl''-Mobile, the Calidus 3''pl'' system must be informed that the Interface to Calidus 3''pl''-Mobile is present. This is enabled via the 'RDT Interface' flag on system parameters.

[[Image:Img2.png]]

Click on the Default Locations tab to identify the default locations required.

[[Image:Img3.png]]

Build up location 3 (Q/A) is the default putaway location, if the putaway algorithm finds no locations. Location 6 is a Default Marshalling Location, used by pick list and allocation.

== Owner parameters ==
An RDT Interface flag also exists per Owner or Stockist. With this flag, we are able to determine whether, even if the warehouse allows RDT operations, the owner allows RDT operations.

[[Image:Img4.png]]

In all ways, this bank of screens operates in the same way as the System parameters screens, described above.

== RDT Status Maintenance Screen ==
This screen is the major control screen for RDTs in Calidus 3''pl''

[[Image:Img5.png]]

Each line controls not only the running of the update process in Calidus 3''pl'', but also the availability of the functions to standard Calidus 3''pl'' processing. So, for example, if the Pallet Receipt Update availability flag is 'Y', you have the ability to send receipt preadvice messages to WCS. If it is 'N', you can't send those messages.

The use of the availability flags in the system will be explained for each sending process described in the next section.

Use 'Start Interface' to start the RF interface programs.

Use 'Stop Interface' to stop the RF interface programs.

The light below these buttons indicates whether the interface is on or off.

'''The use of this screen should be limited to System Administrators only.'''

= SENDING DATA =
== Standing Data tables ==
See the C3PL-M Setup guide, for details of how this data is used in the Calidus 3''pl''-Mobile.

Various data tables on Calidus 3''pl'' need to be sent to Calidus 3''pl''-Mobile. These tables are:

* Employees
* Truck Types
* Pallet Types
* Location Types
* Reason Codes
* Receipt Types
* Aisles Status/Aisles
* Stock information

The maintenance screens for these tables can be found (by default) on the Warehouse maintenance menu. The exception to this is the Stock Maintenance screen, normally found on the Stock menu.

To perform an initial send of the data to Calidus 3''pl''-Mobile, enter the form and find data. Once found, click the Send button on the form, which will only be visible if the Interface flags for the owner and warehouse are enabled. The whole file will be sent.

Also, during normal use of the screens, any added or deleted data is sent to Calidus 3''pl''-Mobile, to keep the files accurate. Simply use the screen as normal, and the data will be sent, as long as the interface flags are turned on.

== Preadvices ==
Enter the preadvice as normal, either with or without pallet details.

Once all details have been entered, click the 'Send' button on the main preadvice screen. Tasks per pallet will be sent to Calidus 3''pl''-Mobile. You can only send preadvice records this way if the availability flag of the Pallet Receipt Update process is set to 'Y'.

[[Image:Img6.png]]

Sending the preadvices to Calidus 3''pl''-Mobile need only be done this way if the Goods had not been preadvised via EDI. In this process, all messages will be automatically sent to Calidus 3''pl''-Mobile on receipt of the EDI.

Once pallets have been received on Calidus 3''pl''-Mobile and sent back to Calidus 3''pl'' they will automatically be updated.

'''Note:''' In unexpected scenarios (e.g. unexpectedly received pallets) the Goods Receipt Note will NOT be automatically confirmed as received. The pallets, which have processed correctly, will have been confirmed but no action will have been taken on other pallets. You will still be able to put the correctly processed pallets away. In order to confirm the GRN fully, you must access the GR Confirmation screen and use the Confirm process there. Until this action is taken, the GRN will continue to appear on diagnostic reports. See section 5.2 for more details.

== Putaways ==
When the Goods Receipt has been processed on Calidus 3''pl''-Mobile, update messages are sent back to Calidus 3''pl''. The Pallet Receipt Update program, controlled by the RDT Start/Stop screen processes these. When the program processes the receipt messages, it will generate a putaway location for the pallet automatically. This is sent through to Calidus 3''pl''-Mobile as a putaway task.

If a location cannot be found for the pallet, the putaway location will default to the third build-up location on system parameters, the Q/A location.

If, however, you have the availability flag of the Pallet Receipt Update process set to 'N' and the flag for Movement/Putaway Update process set to 'Y', you can send putaway messages a different way.

When the flags are set up this way, preadvice messages can't be sent to WCS, but putaway messages can. When you have created the goods receipt in Calidus 3''pl'', enter locations as normal in Goods receipt confirmation.

[[Image:Img7.png]]

When the 'Confirm' option is chosen, the receipt is confirmed and then putaway messages are sent to Calidus 3''pl''-Mobile, with the locations that you specified.

Once the putaway messages have been processed, the pallets will be available in the system.

== Pallet Moves ==
Pallet movements sent to Calidus 3''pl''-Mobile are processed in almost exactly the same way as normal. Pallet movements are raised via the Pallet Movement Request screen as normal. In the Ticket Print screen, you will be prompted for two extra items:

[[Image:Img8.png]]
If you do not want to print the move ticket, enter 'No' at the appropriate prompt. You must then enter a priority for the messages. This priority will indicate how quickly the messages are processed in Calidus 3''pl''-Mobile. The values range from 2 (the highest) to 9 (the lowest).

After this entry, the request is processed as normal, but with movement messages being sent to Calidus 3''pl''-Mobile.

== Replens ==
Replenishments are processed in the same way as pallet movements.

== Picks ==
Pick tasks are sent to the RDTs at the normal pick list stage. This stage can be reached through a number of screens, the most common being the Pick Wave screen.

=== Pick Wave ===
Orders can be found and allocated to a Pick Wave, using this screen.

[[Image:Img9.png]]

Enter a default load then click 'Find Orders' to display the orders. Criteria can be entered here to narrow down the orders to be found.

Once found, assign the orders to the Load using the check box next to the order, then save.

[[Image:Img10.png]]
Click the 'Send to Alloc' button to allocate the load.

Once allocation is complete, the order can be pick listed using the 'Send To Pick' button.

[[Image:Img11.png]]

If the load is to be pre-assigned to one picker, the employee ID of this picker can be entered in the Picker field before sending to pick.

[[Image:Img12.png]]

The Marshalling location is the lane to which you wish the picked pallets to go. If one is not entered, the system will default the location to the Default Marshalling Location in the system parameters screen. The RDT priority affects how quickly the pick tasks will be allocated to a picker. As with other RDT process priorities, this can be set from 2 to 9, 2 being the highest priority.

When you have chosen the parameters, click the 'Generate Pick List' button. This will produce a paper pick list if desired, and will also transfer the pick tasks to Calidus 3pl-Mobile for completion.

=== Pick List ===
If you allocate and pick list by separate processes in the menus, you will be prompted to enter the extra parameters at the Pick List stage:

[[Image:Img13.png]]

The Marshalling location is the lane to which you wish the picked pallets to go. If one is not entered, the system will default the location to the Default Marshalling Location in the system parameters screen. The RDT priority affects how quickly the pick tasks will be allocated to a picker. As with other RDT process priorities, this can be set from 2 to 9, 2 being the highest priority.

When you have chosen the parameters, click the 'Generate Pick List' button. This will produce a paper pick list if desired, and will also transfer the pick tasks to Calidus 3pl-Mobile for completion.

== Pick Modifications ==
If you have short-picked an item or the pickers have not found some pallets, these tasks will be sent back to Calidus 3''pl'', and will reduce the amount picked. The shortfall must be appended onto the order. This is achieved by adding lines at pick confirmation, but without confirming the order.

First, find the order in the Pick confirmation by route/load/order screen:

[[Image:Img14.png]]

Select the required page of the order. You will be taken to the confirm screen.

[[Image:Img15.png]]

From here, append lines to the order as normal, but do not confirm the page. When saved, the appended pick task will be sent to Calidus 3''pl''-Mobile for processing. When completed, the task will be returned and updated automatically by Calidus 3''pl''.

Pick tasks that have been manually short-picked or confirmed will also be interfaced to Calidus 3pl-Mobile, to reduce or remove the pick tasks outstanding.

== Stock Check ==
Generate the stock check cycle as normal in the generation screen. For messages to be sent to Calidus 3''pl''-Mobile, the interface flag (either from owner or system parameters) must be set, and the stock check availability flag and owner check flags must also be set in the RDT start/stop screen.

[[Image:Img16.png]]

The cycle will either be a full stock check or a partial stock check. If neither, the stock check will be assumed to be a partial, or pre-advised, check.

Once stock details have been checked on the RDTs, the information is sent back to Calidus 3''pl'' and updated into the stock take count input screen.

[[Image:Img17.png]]

Once the data is checked for consistency, the cycle can be confirmed (using the 'Confirm' button), making it ready for updating, using the Stock Take Update screen.

[[Image:Img18.png]]

Good counts should be confirmed. If unsure about the counts, the cycle can be rejected or partially confirmed. In a partial confirmation, any records that were correct are confirmed, and any with modifications are left on the stock cycle.

= Receiving Procedures =
== Receipt Transaction Exceptions ==
[[Image:Img19.png]]
Message types allow you to choose which processes' messages you want to see on the report. A full list will be shown.

The error type allows you to choose from a range of message levels:

* Informational (type 'I') - Some processes write away messages to the report, showing successful completion of update. These are informational messages.
* Warning (type 'W') - Warnings show data that may need to be fixed, but the line has been updated anyway.
* Error (type 'E') - Errors show records that cannot be updated. The reason will be shown in the description. Data with errors must be entered and updated manually through the normal manual update screens.
* Debug messages (for support)
* All (type 'A') - All of the above.

You are prompted to choose a Date From. This will default to today's date.

[[Image:Img20.png]]

The 'Cleardown' button shows the parameters required so that the exceptions log can be cleared. This should be done on a regular basis. By default, no clear-down is done. If you choose to do the clear-down, you are prompted to enter a date. All data before this data will be deleted. Take care using this function as, once deleted, the exceptions data cannot be recovered.

== Diagnostics processes ==
In addition to the above report, several diagnostics reports exist that will aid in identifying possible problems:

* For GRNs:
* GRN's not putaway confirmed
* GR Discrepancies Report
* GRN's advised not confirmed
* For Orders:
* Order (status) report
* Unconfirmed Orders
* Unconfirmed Pick Pages Report
* For Moves:
* Unconfirmed Movements
* Outstanding Movements Report

Additionally, the Data Extraction Suite allows the user to design reports to examine all of this data.

Various enquiries exist in the system, which will also aid identification:

* All stock movements enquiries
* Customer Pallet ID Enquiry
* Pallet Enquiry
* Order Enquiry

WCS System Overview

2025-12-19T11:48:33Z

Anw: Split into separate pages

[[File:WCS-Overview.png|800px]]

== Operation ==
As can be seen from the diagram, Calidus 3''pl'' runs on a UNIX server, while Calidus 3''pl''-Mobile runs on a Windows Server in this implementation.

In the diagram, Calidus 3''pl'' has been split into three areas.

The non-shaded area is the manual Calidus 3''pl'' system, being the screens and methods currently used to enter and confirm tasks.

The wavy shaded area shows the portion of Calidus 3''pl'' that sends messages to the WMS interface. These are covered in great detail in following sections.

The dotted area contains Calidus 3''pl'' RDT update programs that automatically do the work of the confirmation processes in manual Calidus 3''pl''. For example, one of these processes might confirm movements; another might confirm orders as picked. They work by receiving confirmation of tasks completed from Calidus 3''pl''-Mobile. Those messages (of tasks to be completed, and confirmation of tasks completed) are sent by the interface.

Both systems have an interface; Calidus 3''pl''''s is referred to as the WMS interface, Calidus 3''pl''-Mobile's as the WCS interface. Both need transmitters (to send their messages) and receivers to get messages back. As can be seen from the diagram, Calidus 3''pl ''sends messages to Calidus 3''pl''-Mobile's receiver program, WCS Server through an Oracle Advance Queue. When messages are being sent back to Calidus 3''pl'', Calidus 3''pl''-Mobile's transmitter program, also WCS Server, sends messages to Calidus 3''pl ''by enqueuing messages on Oracle Advance Queues in the WMS database.

The third part of the interface consists of the Merge processes. In Calidus 3''pl'', these consists of many processes which we route messages to using the Queue Reader processes. These route the messages to the Merge processes (dotted area of the RDT update programs).

So, let's look at the progression of tasks through this system from start to finish. For this example, we'll use a simple housekeeping pallet movement.

When the task (move pallet 1 from A to B) is raised, the message is passed to the WMS Interface Queue. The Queue passes the information to the WCS Server. Note: Only when the message is fully processed is this removed from the queue, ensuring messages are never lost).

Once WCS's receiver has the message, merges the message to the database. This identifies the type of message (a pallet movement), and checks that everything is OK about the message''s contents. When satisfied of the contents, the task is put in the main WCS database, ready for use.

When an RDT user requests a task, and they are to be allocated movement tasks, WCS will allocate the closest movement to that user's location, or in priority order. In our example, this means they are given the movement we raised on Calidus 3''pl''. They are told to get the pallet 1 from location A and take it to location B, there scanning the check digits of the destination for confirmation.

Once they have completed the task, Calidus 3''pl''-Mobile sends a completion message to the Calidus 3''pl'' receiver queue.

The Queue Reader associated to the queue identifies the type of message, in our example, a movement completion message. The message is then routed to the correct RDT update process. Again, messages are only removed from the queue when correctly processed.

The RDT update process examines the contents of the message for validity, and then updates all the Calidus 3''pl'' data files that you would expect if it was confirmed manually in the Pallet Move Confirmation screen.

Main Page

2025-12-16T11:54:16Z

Anw: Updated

<div style="text-align: center;">[[Image:Calidus-Mobile.JPG]]</div>

* [[:Category:Documents]]

* [[:Category:WCS Training Guides]]
**[[Installation Guide]]
**[[Set-up Guide]]
**[[WCS Maintenance]]
**[[RDT Functionality]]
**[[Using WCS from WMS]]
**[[External Data Access]]
** [[Label Formats]]
** [[Common Activities Guide]]
* Wavelink (Windows Mobile)
** [[Wavelink Virtual Client]]
** [[Wavelink Client Support]]

* [[:Category:FAQ]]
* [[Did You Know]]

* [[:Category:Android|Android]]
** [[Installing Barcoders Android Server]]
** [[Android Setup Guide]]
** [[Android Usage Guide]]
** [[Android Development Guide]]
** [[Android Support Guide]]

* [[:Category:Technical Guides]]
**[[C-TMS Automotive RF Process]]
**[[ctms:Putway Algorithm Summary|Putway Algorithm Summary]] (external)
**[[Network Diagrams]]
** [[Remote System Connectivity]]

WCS Labels Changes

2025-12-16T11:20:42Z

Anw: Initial Creation

The page is intended to provide a guideline on the construction and layout of the WCS Label formats.

= Latest versions =
<code><template></code>

<code><parameters version=”2”></code>

<code>Carton : <item name="Carton" format="trim" /></code>

<code>Packing Date: <item name="SysDate" type=”date” format="DD/MMM/YYYY" /></code>

<code>Order : <item name="OrderNo" len="15" /></code>

<code>Customer: <item name="Customer" format="trim,ucase" /></code>

<code><item name="AddrLine1" /></code>

<code><item name="AddrLine2" /></code>

<code><item name="Town" /></code>

<code><item name="County" /></code>

<code><item name="PostCode" /></code>

<code><item name="Country" /></code>

<code>---------------------------------</code>

<code>Contents:</code>

<code>Stock Batch Qty</code>

<code><group name="details" repeat="20"></code>

<code><item name="Stock" len="15" /> <item name="Batch" len="8" /> <item name="Qty" type=”numeric” format="####0" /></code>

<code></group></code>

<code>Label <item name="LabelNo" type=”numeric” format="####0" /> of <item name="BoxCount" type=”numeric” format="####0" /></code>

<code></template></code>

Version on TEMPLATE tag determines whether we are using old method with curly brackets or new method.

== Groups ==
There is a requirement to use Deconsolidation for some promotional materials.

The process fits what they want to do for these items exactly, but this is only a small percentage of the stock being picked.

Need to check that Despatch Confirm cleans up Picking Container and Deconsolidation records for orders effectively, when using Final Media functionality.

Would require ‘labels’ produced from this process, which are more like mini packing lists:

<code>Carton : XXXXXXXXXXXXXXXXXXXX</code>

<code>Packing Date: DD/MMM/YYYY</code>

<code>Order : XXXXXXXXXXXXXXXXXXXX</code>

<code>Customer: XXXXXXXXXXXXXXXXXXXX</code>

<code>Addr1</code>

<code>Addr2</code>

<code>Town</code>

<code>County</code>

<code>Country</code>

<code>Postcode</code>

<code>---------------------------------</code>

<code>Contents:</code>

<code>Stock Batch Qty</code>

<code>XXXXXXXXXXXXXXXXX XXXXXXXXXXX XXXXX</code>

<code><repeating up to X times></code>

<code>Label X of Y</code>

So we would produce as many labels as required to show the contents of the box, for the order.

Would need to extend label picking class so that you could specify sub groups, and how many times they could be printed.

<code><template></code>

<code><parameters version=”3”></code>

<code><text>Carton : </text><item name="Carton" format="trim" /></code>

<code><text>Packing Date: </text><item name="SysDate" type=”date” format="DD/MMM/YYYY" /></code>

<code><text>Order : </text><item name="OrderNo" len="15" /></code>

<code><text>Customer: </text><item name="Customer" format="trim,ucase" /></code>

<code><item name="AddrLine1" /></code>

<code><item name="AddrLine2" /></code>

<code><item name="Town" /></code>

<code><item name="County" /></code>

<code><item name="PostCode" /></code>

<code><item name="Country" /></code>

<code><text>---------------------------------</text></code>

<code><text>Contents:</text></code>

<code><text>Stock Batch Qty</text></code>

<code><group name="details" repeat="20"></code>

<code><item name="Stock" len="15" /> <item name="Batch" len="8" /> <item name="Qty" type=”numeric” format="####0" /></code>

<code></group></code>

<code><text>Label </text><item name="LabelNo" type=”numeric” format="####0" /><text> of </text><item name="BoxCount" type=”numeric” format="####0" /></code>

<code></template></code>

Need to design the tags fully, to decide what formatting details we can use.

Need MaxLen, Len, Format (Dates, Text and Numbers), mid and trim functions, etc.

Note: Have extended this to full XML, even the plain text bit.

Problem with this: if this isn’t plain text, but printer language, each item print location is defined in the plain text. So:

<code>^FO16,780^A0,30,26^FDProduct Code^FS</code>

<code>^FO310,780^A0,30,26^FDLot No^FS</code>

<code>^FO560,780^A0,30,26^FDCtns^FS</code>

<code>^FO656,780^A0,30,26^FDPces^FS</code>

<code>^FO16,830^A0,30,26^FD12345678901234567890^FS</code>

<code>^FO310,830^A0,30,26^FD12345678901234^FS</code>

<code>^FO560,830^A0,30,26^FD00010^FS</code>

<code>^FO656,830^A0,30,26^FD00100^FS</code>

This is ZPL to print some label headers, then print out the 4 items. The “830” bit in the FO statement shows the y coordinate, where the line is printed. In our group, we need to specify the start (830) and the ‘height’ to be added to each line (lets say 80):

<code><template></code>

<code><parameters version=”3”></code>

<code><text></code>

<code>^FO16,780^A0,30,26^FDProduct Code^FS</code>

<code>^FO310,780^A0,30,26^FDLot No^FS</code>

<code>^FO560,780^A0,30,26^FDCtns^FS</code>

<code>^FO656,780^A0,30,26^FDPces^FS</code>

<code></text></code>

<code><group name="details" repeat="5" ystart=”830” yspacing=”80”></code>

<code><text>^FO16,</text><item name=”ypos” /><text>^A0,30,26^FD</text><item name=”StockCode” /><text>^FS</text></code>

<code><text>^FO310,</text><item name=”ypos” /><text>^A0,30,26^FD</text><item name=”Batch” /><text>^FS</text></code>

<code><text>^FO560,</text><item name=”ypos” /><text>^A0,30,26^FD</text><item name=”Cases” /><text>^FS</text></code>

<code><text>^FO656,</text><item name=”ypos” /><text>^A0,30,26^FD</text><item name=”Units” /><text>^FS</text></code>

<code></group></code>

<code></template></code>

So, ystart defines the start y coordinate, yspacing defines how much to add on though each group, ypos defines the dictionary item which will be set by the previous 2 parameters.

This could also be expanded to xstart, xspacing and xpos, for producing lists. We would maybe also have to define the directionality – horizontal or vertical.

== 1.3 Barcodes ==
Need to include some information regarding barcode types. Most are just plain text producers e.g. CODE-39, but CODE-128 and EAN-128 allow changes based on content. For example:

12345678 can be codes as 128C

SSN12345678 can be coded as 128A or B, but the barcode is twice the length.

The barcode can be set to be in 128C, but the alpha portions can be set to be in 128A or B, with control sequences.

The language property on the parameters tag could control the characters used to change code type:

<code><parameters version=”3” language = “ZPL”></code>

For example, a UCC barcode in zebra format:

<code>^FD>;>802123456789012341501020310>6ROT45678>8>5370224^FS</code>

So the format could be:

<code><text>^FD>;>802</text></code>

<code><item name=”StockCode” /></code>

<code><text>15</text></code>

<code><item name=”SellBy” /></code>

<code><text>10>6</text></code>

<code><item name=”CustBatch” /></code>

<code><text>>8>537</text></code>

<code><item name=”Qty” fomat=”9999” /></code>

<code><text>^FS</text></code>

That could cause problems to the parser though, so it might be better if:

<code><text>^FD</text></code>

<code><text type=”EAN128C”>02</text></code>

<code><item type=”EAN128C” name=”StockCode” /></code>

<code><text>15</text></code>

<code><item name=”SellBy” /></code>

<code><text>10</text></code>

<code><item type=”EAN128C” name=”CustBatch” /></code>

<code><text>37</text></code>

<code><item name=”Qty” fomat=”9999” /></code>

<code><text>^FS</text></code>

The property “EAN128C” or “CODE128C” on text tags will start the barcode “>;” and set the code type C “>8”

The property “EAN128C” or “CODE128C” on item tags will check the element for alphabetic characters and encapsulate the alpha text with “>6” at the start and “>8” at the end.

Still need some mechanism of terminating variable-length items though. Possibly send AI through as property, as follows:

<code><text>^FD</text></code>

<code><text type=”EAN128C” /></code>

<code><item type=”EAN128C” ai=”02” name=”StockCode” /></code>

<code><item type=”EAN128C” ai=”15” name=”SellBy” /></code>

<code><item type=”EAN128C” ai=”10” name=”CustBatch” /></code>

<code><item type=”EAN128C” ai=”37” name=”Qty” format=”9999” /></code>

<code><text>^FS</text></code>

AI property would control putting the AI at the start of the printed field.

Could do same when checking for lowercase characters as well (change from B to A, etc).

Possibly would need a similar label printed from WMS (Pick Container Enquiry screen).

== 1.4 Optional Sections ==
I can see a need to modify this so that sections or items are only printed if certain criteria are met.

So:

<code><template version="3" language="ZPL"></code>

<code><text>Carton : </text><item name="Carton" format="trim" /></code>

<code><text>Packing Date: </text><item name="SysDate" type=”date” format="DD/MMM/YYYY" /></code>

<code><text>Order : </text><item name="OrderNo" len="15" /></code>

<code><text presentif=”customer”>Customer: </text></code>

<code><item name="Customer" format="trim,ucase" presentif=”customer” /></code>

<code><item name="AddrLine1" /></code>

<code><item name="AddrLine2" /></code>

<code><item name="Town" /></code>

<code><item name="County" /></code>

<code><item name="PostCode" /></code>

<code><item name="Country" /></code>

<code><text>---------------------------------</text></code>

<code><text>Contents:</text></code>

etc

or

<code><template version="3" language="ZPL"></code>

<code><text>Carton : </text><item name="Carton" format="trim" /></code>

<code><text>Packing Date: </text><item name="SysDate" type=”date” format="DD/MMM/YYYY" /></code>

<code><text>Order : </text><item name="OrderNo" len="15" /></code>

<code><group name=”address” presentif=”customer”></code>

<code><text>Customer: </text></code>

<code><item name="Customer" format="trim,ucase" /></code>

<code><item name="AddrLine1" /></code>

<code><item name="AddrLine2" /></code>

<code><item name="Town" /></code>

<code><item name="County" /></code>

<code><item name="PostCode" /></code>

<code><item name="Country" /></code>

<code></group></code>

<code><text>---------------------------------</text></code>

<code><text>Contents:</text></code>

etc

The “presentif” parameter controls whether the item or group contents should be displayed at all. Specifying a field name simply checks if there is a value in that string (or zero). Or you could specify a condition (“qty<>0”).
[[Category:Technical Guides]]

Main Page

2025-12-16T11:14:24Z

Anw: Updated

<div style="text-align: center;">[[Image:Calidus-Mobile.JPG]]</div>

* [[:Category:Documents]]

* [[:Category:WCS Training Guides]]
**[[Installation Guide]]
**[[Set-up Guide]]
**[[WCS Maintenance]]
**[[RDT Functionality]]
**[[Using WCS from WMS]]
**[[External Data Access]]
** [[Label Formats]]
* Wavelink (Windows Mobile)
** [[Wavelink Virtual Client]]
** [[Wavelink Client Support]]

* [[:Category:FAQ]]
* [[Did You Know]]

* [[:Category:Android|Android]]
** [[Installing Barcoders Android Server]]
** [[Android Setup Guide]]
** [[Android Usage Guide]]
** [[Android Development Guide]]
** [[Android Support Guide]]

* [[:Category:Technical Guides]]
**[[C-TMS Automotive RF Process]]
**[[ctms:Putway Algorithm Summary|Putway Algorithm Summary]] (external)
**[[Network Diagrams]]
** [[Remote System Connectivity]]

Wavelink Virtual Client

2025-12-16T11:12:15Z

Anw: Initial Creation

This page is intended to show the installation and usage of the Wavelink Virtual Client.

The latest Wavelink Virtual Client is contained within the file WinCEWLC.zip

To install:

* Unzip the file to a location of your choice

To Start:

* Enter the folder above and double-click on WLClientShell.exe.

To Configure:

* To change the device ‘skin’, right-click on the window background and choose a device layout from the Skins sub-menu.
* To add a new connection, Right-click on ‘Add New’ and enter the name (e.g. WCS Test), Address and Port (for example, 172.198.45.166 and 2001 respectively). Click '''Update'''.

To Use:

* Click the added shortcut and you should connect to the system.
* All functionality should work as in the RF device itself.
* You can use the Scan button on the device skin to pop up a scan dialogue to emulate scanning.
* You can use the key buttons on the skin for their normal purpose, as well as the computer keyboard.
* To Exit the client when finished with the system, click the power (0/1) button on the skin.

Remote System Connectivity

2025-12-16T11:08:43Z

Anw: Initial Creation

This guide is intended to show the configuration, setup and support of a remote WCS installation.

== RDC Configuration ==
Each server has a capability of supporting 1 console session and 2 remote sessions through Remote Desktop Connection (RDC).

A remote session is initiated by a connection to the machine through RDC from a remote machine. To initiate this, you provide a domain, username and password for the connection, which must be set up as a remote user on the server.

When this user connects, a session is started under this username. The session consists of the Windows desktop and all associated client processes required for this user.

Sessions in this state can be seen clearly by using the Task Manager, as sessions for the remote user provided, with status 'Active'. Additionally, the screen will show the machine that is connected to the remote session (i.e. the machine name on the remote or local network).<center>
[[File:WCS-TaskMgr.png|800x800px]]
</center>In the example above, we can see that there are 3 sessions:

* Session 0 is the Console session. It is running (i.e. status Active)
* Session 1 is the first remote session. It was logged on with user FWL_Support, from machine UKATH-1LPD024 and is active.
* Session 2 is the second remote session. It was logged on with user FWL_Support, from machine WALKERT-S1 and is active. This is the session that I connected to, to get this screenshot.

When the remote session is closed, the local session is left running by default, so any programs that were started during the session are left running on the server, within the local session. RDC will warn you of this fact when you close the remote session (using the X on the top right of the window).

Sessions in this state can be seen clearly by using the Task Manager, as sessions for the remote user provided, but with status 'Disconnected'.

If the remote session is terminated using the start menu (''Start/Log Off''), the local session is terminated with the remote session, stopping all programs running.

Sessions that have been terminated in this way do not show as connected session on the Task Manager.

If 1 or more sessions exist on the machine at disconnected status for the provided Domain and username, RDC will connect to these sessions rather than create a new one.

If there is 1 only, this will be connected to immediately.

If there are more than 1, the client will ask the user to choose which of the session to which they would like to connect.

== RDC with WCS ==
One remote session is used to run the WCS Server, the server-side component of the Calidus 3PL-Mobile application. This must be running for the RF system to be active.

This is not run as a service, but as an application.

If the session that runs the WCS Server is closed (but not logged off), the application continues to run.

If the session that runs the WCS Server is logged off, the application will be terminated and the RF application will no longer work.

== Operational Considerations ==
The site users are connecting to the server using RDC, in order to run the WCS Maintenance application (the Calidus 3PL-Mobile application that allows the user to see and manage RF tasks).

They connect using the FWL_Support account.

If 2 users open a session on a server and stay connected to this session, there are no available sessions for OBS support.

If the users disconnect from the session (and do not terminate the session), the session will be available for OBS to use, when we connect for support purposes.

If users log off the session, there is a chance that the WCS Server application will also be terminated, and so will affect the running of the system – this is not recommended.

As the only purpose of connecting to the server is to run the WCS Maintenance application, all of the above potential issues can be mitigated by installing the application locally (see section 1.4), or running the application over the network (see section 1.5). An installer exists for this purpose.

== Installing WCS Maintenance Locally ==

=== Prerequisites ===
In this instance, it is assumed that the WCS has been set up on a WCS Server PC, and that the user has access to this PC over the network. The PC should have some shared folders, as specified in section 2.3:

* '<code>''{Installation Path}''\Database</code>' shared as '<code>\\''{WCS Server}''\WCSDB$</code>' (required)
* '<code>''{Installation Path}''\Bin\Reports</code>' shared as '<code>\\''{WCS Server}''\WCSRPT$</code>' (optional)
* '<code>''{Installation Path}''\</code>' shared as '<code>\\''{WCS Server}''\WCS$</code>' (optional)

It is further assumed that all required standing data has been set up on the WCS and that the user has been provided a valid username and password for access to the WCS.

=== Run Installer ===
Run the WCS installer and install the WCS Maintenance package only.

Follow the on-screen instructions.

Default working directory for the install is:

<code>C:\Program Files\Warehouse Control Server</code>

=== Run WCS Maintenance ===
Start WCS maintenance from the shortcut on the start menu under the group 'Warehouse Control Server'.

Choose the appropriate database from the file list or the Browser.

You will be accessing the central WCS database remotely. There are several ways to do this:

* Browse for the appropriate database using the 'More Files' option on the File List. You should be browsing through your Network, looking for the machine on which the WCS has been installed, and choosing the shared Database folder '<code>\\''{WCS Server}''\WCSDB$</code>';
* Set up a network drive (for our example, we will choose the driver letter “W”), pointing to the 'Database' shared folder on the WCS Server PC. Use this driver letter to find the database (rdt1.mdb) in the Browser.

Once you have selected the database once, the database will remain on the file list for you to select.

Log in using your provided WCS username and password.

Once in, go to the System Settings screen, using either the toolbar or the menus (''System Tools/System Settings'').

Click '''Apply''', then '''OK''' in this form. That sets up the settings for Maintenance, as well as an 'INI' file for the maintenance functions, with the normal default values for certain areas.

== Installing Network WCS Maintenance ==

=== Prerequisites ===
As section 4.1

=== Run Installer ===
Run the WCS installer and install the WCS Maintenance (Network Install) package only.

Follow the on-screen instructions.

Default working directory for the install is:

<code>C:\Program Files\Warehouse Control Server</code>

Once completed, this installer will have installed all the required libraries for WCS Maintenance to run and will have created a shortcut on the start menu. This shortcut must be modified to point to the network WCS Maintenance application.

If the site want the users to use the central installation of WCS Maintenance (for ease of release and support), the following steps must be taken:

# Change the 'Target' field to point to the network shared WCSMaintenance.exe file in the format <code>'\\{WCS Server}\WCS$\WCSMaintenance.exe</code>' where '{WCS Server}' is the network name of the WCS Server Machine.
# Save the changes to this shortcut.

=== Run WCS Maintenance ===
Start WCS maintenance from the shortcut on the start menu under the group 'Warehouse Control Server'.

Choose the appropriate database from the file list or the Browser.

You will be accessing the central WCS database remotely. There are several ways to do this:

* Browse for the appropriate database using the 'More Files' option on the File List. You should be browsing through your Network, looking for the machine on which the WCS has been installed, and choosing the shared Database folder '<code>\\''{WCS Server}''\WCSDB$</code>';
* Set up a network drive (for our example, we will choose the driver letter “W”), pointing to the 'Database' shared folder on the WCS Server PC. Use this driver letter to find the database (rdt1.mdb) in the Browser.

Once you have selected the database once, the database will remain on the file list for you to select.

Log in using your provided WCS username and password.

Change ''<nowiki/>'Default Report Files Folder''' location (found from the menu ''System Tools/System Settings'', Maintenance settings tab) to the shared name of the WCS Reports folder on the WCS PC which is usually '<code>\\{WCS Server}\WCSRPT$</code>'.

Click '''Apply''', then '''OK''' in this form. That sets up the settings for Maintenance, as well as an 'INI' file for the maintenance functions, with the normal default values for certain areas.

File:WCS-TaskMgr.png

2025-12-16T11:02:12Z

Anw:

Task Manager

Main Page

2025-12-16T10:54:53Z

Anw: Updated

<div style="text-align: center;">[[Image:Calidus-Mobile.JPG]]</div>

* [[:Category:Documents]]

* [[:Category:WCS Training Guides]]
**[[Installation Guide]]
**[[Set-up Guide]]
**[[WCS Maintenance]]
**[[RDT Functionality]]
**[[Using WCS from WMS]]
**[[External Data Access]]
** [[Label Formats]]
** [[Network Diagrams]]

* [[:Category:FAQ]]
* [[Did You Know]]

* [[:Category:Android|Android]]
** [[Installing Barcoders Android Server]]
** [[Android Setup Guide]]
** [[Android Usage Guide]]
** [[Android Development Guide]]
** [[Android Support Guide]]

* [[:Category:Technical Guides]]
**[[C-TMS Automotive RF Process]]
**[[ctms:Putway Algorithm Summary|Putway Algorithm Summary]] (external)

Network Diagrams

2025-12-16T10:51:31Z

Anw: Initial Creation

Key:

* ABS - Android Barcoders Server - the application that handles communication between the Aptean App and the Android mobile device.
* WLS - Wavelink Server - the application that handles communication between the Aptean App and the Windows mobile device.
* WCS - the Aptean Calidus WCS Server, which handles communication to/from the RDTs (Android or Windows mobile devices) and also communication to/from the WMS.
* WMS - The Aptean Calidus 3PL WMS.
* RDT - the mobile device.
* RDT App - the application that is run upon connection of those devices to the WCS, through ABS or WLS.

=== Single Site 1: Local WCS Server ===
<center>[[File:WCS-NETWORK-Local.png|800x800px]]
</center>

=== Single Site 2: Central WCS Server ===
<center>
[[File:WCS-NETWORK-Central.png|800x800px]]
</center>

=== Second Site 1: Remote RDTs ===
<center>
[[File:WCS-NETWORK-RemoteRDT.png|800x800px]]
</center>

=== Second Site 2: Remote RDT Server ===
<center>
[[File:WCS-NETWORK-RemoteRDTSvr.png|800x800px]]
</center>

=== Second Site 3: Remote RDT Servers/Central WCS Server ===
<center>
[[File:WCS-NETWORK-RemoteCentral.png|800x800px]]
</center>

=== Second Site: External RDT Server ===
<center>
[[File:WCS-NETWORK-External.png|800x800px]]
</center>

=== Two Systems on One Server ===
<center>
[[File:WCS-NETWORK-Multiple.png|800x800px]]
</center>

File:WCS-NETWORK-Multiple.png

2025-12-16T10:51:13Z

Anw:

Two Systems on One Server

File:WCS-NETWORK-External.png

2025-12-16T10:50:17Z

Anw:

Second Site: External RDT Server

File:WCS-NETWORK-RemoteCentral.png

2025-12-16T10:49:20Z

Anw:

Remote RDT Servers/Central WCS Server

File:WCS-NETWORK-RemoteRDTSvr.png

2025-12-16T10:48:07Z

Anw:

Remote RDT Server

File:WCS-NETWORK-RemoteRDT.png

2025-12-16T10:46:53Z

Anw:

Remote RDT

File:WCS-NETWORK-Central.png

2025-12-16T10:46:03Z

Anw:

CEntral WCS

File:WCS-NETWORK-Local.png

2025-12-16T10:42:18Z

Anw:

Local WCS

Set-up Guide

2025-10-30T14:13:01Z

Anw: Minor formatting change

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = Set-up Guide
| Reference = UG 106181
| Version = 7.03
| Date = 30th October 2025
| Sysver = 3.4
}}


= 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 and whether the truck type is considered intrinsically safe.

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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! 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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</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.
|-
|Enable RDT Daily Cycle Check
|The Daily Cycle Check functionality will be available to the users if this rule is enabled
|-
|Enable RDT Part Replenishments
|Allow completion of Part Replenishment tasks
|-
|Trolley IDs
|Allow loading of orders into trolleys
|-
|Pre-Receipt Sort (Bespoke)
|Allow Pre-Receipt Sortation (Bespoke)
|-
|Blind Receipt (Bespoke)
|Allow pallets to be received and putaway at the same time (Bespoke)
|-
|Blind Return (Bespoke)
|Allow pallets to be returned and putaway at the same time (Bespoke)
|-
|Enable RDT Stock Adjustment
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|-
|Ad Hoc Stock Move
|Allow Ad Hoc Stock Movements via RF
|-
|Enable Stock Transfers
|Allow completion of Stock Transfer tasks
|-
|Enable Packing
|Allow the RDT user to pack orders
|-
|Enable Stock Putaway
|Allow the RDT user to Stock Putaway
|-
|Ad Hoc Location Move
|Allow Ad Hoc Location Movements via RF
|-
|Update CPID
|Allow the user to update the customer pallet id value. Bespoke
|-
|Picking Container Adjustment
|Allow the user to adjust Picking Containers. Bespoke
|}

The Admin items that can be set up (and their descriptions) are:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</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.
|-
|OBS Menu
|Controls access to the OBS Support 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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
|-
|WMS System
|Version of WMS that the WCS is connecting to.
|}

If the system is connecting using socket connections, the following details can be modified:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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 (??)
|-
|Connection Logging
|Level of logging for System Connections (OBS USE ONLY)
|}

If the system being linked to is using Oracle Advanced Queues, the following options will be available:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
|-
|Ora Priority Incoming Queue
|The Oracle queue on which high priority messages are stored.
|}

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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.

|}

There are also settings for the RDT client. These settings are:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
!<center>Name</center>
!<center>Description</center>
|-
|RDT Wait Time
|This is the amount of time that the RDT application will wait before re-trying communications to the WCS.
|-
|RDT Box Drawing
|What style of box-drawing the RDT's connected to this WCS will use.
|-
|RDT Logging
|Whether the RDT's connected to this system log messages sent to and received from the server, for diagnostic purposes.
|-
|RDT Non Fatal Retry Count
|When the RDT application encounters a non-fatal Wavelink error this number specifies how many times it will retry before bombing out. A value set too low could result in application failures where they would normally be recoverable. CHANGE WITH CAUTION.
|}

==== 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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</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.
|-
|OBS Menu
|Controls access to the OBS Support Menu
|}

=== Bespoke ===
This is bespoke functionality and should only be enabled by your Aptean system implementation team.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</center>
! <center>Description</center>

|-
| Regroup Order by Stock
| Allow WCS Maintenance users to re-group an order's picks by the number of stock picks on the order, then by location.
|-
|Dummy Loc Enq Location
|Controls whether the WCS sends a dummy location enquiry to the WMS
|-
|Dummy Loc Enq Duration
|Sets the duration of time in minutes without a message before a dummy location enquiry is sent to the WMS. Default is 30 min.
|-
|Dummy Loc Timer Duration
|Sets the duration of time for the dummy location check in minutes. Default is every 2 min.
|-
|Dummy Loc Trigger
|Controls the trigger checks of the dummy location enquiry to the WMS. Default is Incoming only.
|-
|Priority Change Audit
|Controls whether an Exceptions record is created to capture when a user changes the priority of a task
|}
=== 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.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</center>
! <center>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.
|-
|Enable RDT Measure Qty
|Allow Measure Quantity to be entered on the RDT
|-
|Enable RDT Weights
|Allow Weight to be entered on the RDT
|-
|Enable Multi UOM processing
|Whether the WCS deals with multiple UOMs
|-
|Pallet Enquiry Print Labels
|Controls if pallet label can be printed from a pallet enquiry
|-
|Pallet Enquiry Label Format
|Format of pallet enquiry label
|-
|Vendor Managed Inventory
|If this flag is enabled, supplier will be displayed and entered during standard rf modules
|-
|Display UOM
|Display UOM on RDT when user prompted to enter a quantity value.
|-
|Zero Negative Quantities
|Zero negative values on enquiries. Default Enabled
|}
=== 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:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</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.
|-
|Enable RDT Part Replenishments
|Allow completion of Part Replenishment tasks
|-
|Enable RDT Stock Adjustment
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|-
|Trolley IDs
|Allow loading of orders into trolleys
|-
|Pre-Receipt Sort (Bespoke)
|Allow Pre-Receipt Sortation (Bespoke)
|-
|Blind Receipt (Bespoke)
|Allow pallets to be received and putaway at the same time (Bespoke)
|-
|Blind Return (Bespoke)
|Allow pallets to be returned and putaway at the same time (Bespoke)
|-
|Ad Hoc Stock Move
|Allow Ad Hoc Stock Movements via RF
|-
|Enable Stock Transfers
|Allow completion of Stock Transfer tasks
|-
|Enable Packing
|Allow the RDT user to pack orders
|-
|Enable Stock Putaway
|Allow the RDT user to Stock Putaway
|-
|Ad Hoc Location Move
|Allow Ad Hoc Location Movements via RF
|-
|Update CPID
|Allow the user to update the customer pallet id value. Bespoke
|-
|Picking Container Adjustment
|Allow the user to adjust Picking Containers. Bespoke
|}
=== Receipt ===
The parameters on this tab control how receipt works on the RDT.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
|-
|Cross Docking
|Is cross-docking enabled for this operation?
|-
|Enter Delivery Reference
|Allow the user to enter a delivery reference in RDT Goods Receipt.
|-
|Change Damage Qty
|If Damaged Pallet Receipt is allowed, is the quantity allowed to be changed from the full pallet quantity? Note: This functionality is supported in the Oracle WMS only.
|-
|Enter Putaway Location
|Allow users to receive and putaway items in a single process
|-
|Receipt Expected Quantity Check
|If enabled, this parameter makes the RDT compare the received quantity entered with the expected quantity pre-advised
|-
|Generate Customer Pallet Id
|If enabled, this rule allows users to determine whether the WMS generates a customer pallet id value.
|-
|Weight Volume Check
|Check stock dimensions and weight are populated during Goods Receipt.
|-
|Enter Vintage
|Controls whether the Goods Receipt module prompts for a vintage value
|-
|Redundant Stock Check
|If enabled, products marked as redundant are rejected when scanned at receipt
|-
|Temperature Recording
|Controls whether Temperature Recording is required at Pre-Advice
|-
|Receipt Intake Stock Check
|Controls Issue Life Check at Receipt
|-
|Allow Receipt Detail Backout
|Controls whether user can back out of Receipt Detail
|-
|Latest Sell By Date Check
|Controls whether input of SellByDate is checked against latest date
|-
|Minimum Pallet ID Length
|Controls the minimum length of SSCC entered in Receipt
|-
|Customer Pallet Validation
|Controls whether an enquiry message is sent to the WMS to validate if a customer pallet value can be received
|-
|Goods Receipt Vehicle Checks
|Controls whether an enquiry message is sent to the WMS to validate if a GRN has been Vehicle Checked
|-
|Capture EAN
|Controls whether users are allowed to enter EAN values for a stock code
|-
|Blind Receipt Data Format
|Controls what the RDT displays in the Blind Receipt/Return modules when displaying the pallet details
|-
|Capture Original SSCC
|Controls whether the Goods Receipt module prompts the user to enter the original SSCC value when generating a new SSCC value.
|}
=== Putaway ===
The parameters on this tab control how putaway works on the RDT.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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
|-
|Print Part Replen Labels
|Whether the RDT attempts to print labels for Part Replenishments
|-
|Part Replen Label Format
|Format of the Part Replen label
|-
|Display Ad Hoc Putaway Locations
|If enabled, this parameter ensures a location enquiry is sent to the WMS from Ad Hoc Putaway to find location assigned to the stock code
|-
|Print Ad Hoc Putaway Labels
|Whether the RDT attempts to print labels for Ad Hoc Putaways
|-
|Ad Hoc Putaway Label Format
|Format of the Ad Hoc Putaway label
|-
|Ad Hoc Putaway Case Scan
|Controls whether the Ad Hoc Putaway module requires case scanning or accepts quantity entry
|-
|Print Ad Hoc Stock Move Labels
|Controls whether the Ad Hoc Stock Move module prompts the user to print a label
|-
|Ad Hoc Stock Move Label Format
|Format of the Ad Hoc Stock Move Label
|-
|Select Stock Move by Stock
|Allow selection of stock moves by Stock before Pallet
|-
|Default Ad Hoc Pallet Move Reason
|Controls the default reason code value for use with the Ad Hoc Pallet Move module
|-
|Multiple Putaway Tasks Prompt
|Controls whether the RDT prompts the user to complete one or all of the putaway tasks when multiple putaway tasks exist for the customer pallet id
|-
|Ad Hoc Pallet Move Reason Prompt
|Controls whether a reason code value is prompted within the Ad Hoc Pallet Move module
|-
|Ad Hoc Pallet Move Change Pallet Type
|Controls whether the user is allowed to change the pallet type within the Ad Hoc Pallet Move module
|-
|Ad Hoc Pallet Move Suggest Location
|Controls whether the WCS request a suggested location from the WMS within the Ad Hoc Pallet Move module
|}
=== 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.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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
|-
|Log Postponement
|Whether pick postponements are recorded in the Exceptions Log
|-
|Pick for On-time Delivery
|If enabled, this rule will ensure that picks are assigned to pickers in Priority, then OTD Date and Time sequence
|-
|Split Pick Quantities
|If enabled, allows large picks to be split into more than one pack
|-
|Pick Multiple Containers
|If enabled, allows creation of several containers in sequence
|-
|Num Picks before RSBE
|The number of picks to elapse between residual stock balance enquiries
|-
|Choose Marshalling Location
|Allow the pickers to choose a marshalling location when taking a picked pallet to marshalling
|-
|Cherry Picking Selection Type
|Controls how Cherry Picked tasks are assigned to users
|-
|Default Short Pick Reason
|Default reason code for short and zero picks (Bespoke)
|-
|Force Source Confirmation
|Force the confirmation of the source picking location for each pick even if it is the same as the previous pick.
|-
|Full Pick Despatch Labels
|If disabled, Despatch labels will not be printed for full pallet picks.
|-
|Authorise Pick Shortage
|When enabled, this rule will ensure that, when part picks are cancelled or otherwise have their quantity changed, the user will be forced to obtain supervisor authorisation before continuing.
|-
|Calculate Packs
|If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks
|-
|Enhanced Pick Exchange
|Allow pick exchanges from different locations and for part pallet pick tasks
|-
|Add Miscellaneous Charges
|Allow users to add miscellaneous charges to orders
|-
|Shipment Pallet Build Validation
|Controls what validation is followed when assigning shipment packages onto shipment pallets
|-
|Always Display Order
|If enabled, the full pick screen will always display order number rather than route/load
|-
|Combined Part Pick Sequence
|Controls whether full pallet picks are assigned to the RDT before part pallet picks when using the Part Picking module
|-
|Additional Pick Sequence
|Controls whether additional conditions are required for sequencing pick tasks
|-
|Marshalling Method
|Controls whether orders are to be marshalled or not
|-
|Additional Pick Instructions
|Controls whether RDT users can view the additional pick instructions
|-
|Print Stock Despatch Label
|Controls whether the Part Picking module allows stock level despatch labels to be produced
|-
|WCS Stock Despatch Label Format
|Format of the stock despatch label
|-
|Single Picker Per Order
|Assign related picks to user on first pick. Default Disabled
|-
|Pick Catch Weight Per Case
|Controls whether Catch Weights are entered at Case instead of Stock/Pick level. Default Disabled.
|-
|Check Duplicate Serial Numbers
|Controls whether Duplicate serials are checked during Pick. Default Disabled.
|-
|Pick By Order
|Controls whether a picker is locked to task for a single order
|-
|Full Pallet Task Exchange
|Controls whether Full Pallet TASK exchange is allowed between orders
|-
|Use WMS Pick Sequence
|Controls whether pick tasks are assigned to a picker in WMS location pick sequence order
|-
|Display Multi UOM
|Controls the display of Multiple UOM Descriptions when entering Pick Quantity
|-
|Largest Task Next Sequence
|Set the sequence of picks after selection by Largest Qty
|-
|Check EAN on Case Serial
|Controls whether an error is issued if an EAN barcode is scanned as a serial number
|-
|Serial Minimum Length
|Controls the minimum length of a scanned case serial number in Picking. Default 0 (disabled)
|-
|Serial Maximum Length
|Controls the maximum length of a scanned case serial number in Picking. Default 0 (disabled)
|-
|Default Pick Exchange Reason
|Controls the default reason code value for use with pick exchanges
|-
|Enter Despatch Pallet Type
|Controls whether pickers are prompted to enter the pallet being picked or picked onto
|-
|Part Pick Pallet Count
|Controls whether Part Picking prompts users to enter a pallet count
|}
=== Dual Cycling ===
This section controls how the RDT is allocated DC tasks, and how the RDT responds to the user requests.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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.
|-
|Multi-Pallet WADC
|Determines whether the WADC modules allow multiple pallets to be picked at the same time
|-
|Multi-Pallet Picking Sequence
|Controls whether the first pallet picked or last pallet picked via WA Dual Cycling is taken to marshalling first
|}
=== 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.
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Name</center>
! <center>Description</center>

|-
| Default Receiving Location
| Default Receiving Location. If entered, the RDT Receipt Module allows the user to choose a receiving location, which defaults to this parameter.
|-
|Default Receiving Location CD
|Default Receiving Location Check Digits
|-
|Default Receiving Location Type
|Default Receiving Location Type
|-
|Conveyor Input Spur
|Bespoke: Conveyor Input Spur Location. Required for RDT Reject Spur Processing
|-
|Conveyor Input Spur CD
|Bespoke: Conveyor Input Spur Check Digits. Required for RDT Reject Spur Processing
|-
|Conveyor Input Spur Type
|Bespoke: Conveyor Input Spur Type. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur
|Bespoke: Conveyor Reject Spur Location. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur CD
|Bespoke: Conveyor Reject Spur Check Digits. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur Type
|Bespoke: Conveyor Reject Spur Type. Required for RDT Reject Spur Processing
|-
|Default Putaway Location
|
|-
|Default Putaway Location CD
|
|-
|Default Putaway Location Type
|
|-
|Default Problem Resolution Location
|
|-
|Default Problem Resolution Location CD
|
|-
|Default Problem Resolution Location Type
|
|}

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

{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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
|-
|Force Default Manu Date
|Bespoke: If this rule is enabled and manufacture dates are required at goods receipt, the RDT will not prompt for this but will instead default the value to the current date.
|-
|New Stock Take Message Layout
|BESPOKE: Changes the Stock Take message to WMS to a different extended format. USE WITH CAUTION
|-
|Pre-Reposition
|Bespoke: Pre-reposition all pending putaways for a stock code when a pallet of the same stock is repositioned
|-
|Display PO Number
|Display the PO Number associated with the pick
|-
|Blind Receipt Label (Bespoke)
|RDT label for the Blind Receipt module (Bespoke)
|-
|Blind Return Label (Bespoke)
|RDT label for the Blind Returns module (Bespoke)
|-
|Maximum Putaway Quantity
|Maximum quantity allowed to be received and putaway by UPC code (Bespoke)
|-
|BHS Short Picking
|Bespoke:short picking mechanism that automatically creates a replacement pick
|-
|Goods Receipt Lookup
|Allow Goods Receipt lookup in RDT Goods Receipt
|-
|Split Tote
|Allow the user to choose to split a picked line over several totes.
|-
|Stock Take Batch Check
|When checking pallets during Stock Take, request the user to check the customer batch value
|-
|Stock Take Sell By Date Check
|When checking pallets during Stock Take, request the user to check the sell by date value
|-
|Display Default Receipt Values
|Controls whether the RDT displays the pallet details of the previous pallet as the default values of the pallet being received
|-
|RF Use Estimated Pallets
|If enabled, then the new estimated pallets message will be sent to the Calidus-3pl Mobile system
|-
|Tote to Carton Standardise
|If enabled, the RDT screens will be amended to display Carton in place of Tote
|-
|Duration Measurement
|Controls whether the duration value is sent to the WMS in seconds or minutes
|-
|Multi Stage Confirmation Message
|Controls whether confirmation messages are sent to the WMS for multi stage tasks
|-
|Loose Item Serial Number
|Controls whether serial number entry is required when picking loose cases and units
|-
|Confirm Take To Marshalling
|Bespoke: Require Confirmation before Take To Marshalling
|-
|Buk PI By
|Bespoke: Perform Bulk PI by Task Identifier or Stock/Sell-By-Date. Default is Task Identifier
|-
|Write RPM Logs
|Bespoke: Write RPM record to Error Log. Default Disabled
|-
|GS1-128 Scan Sequence
|Bespoke: Determines preferred sequence of fields on GS1-128 Scan
|-
|Split Face Sequence
|Controls the sort sequence when Split Faces enabled
|-
|Ad Hoc Stock Move Multi Action
|Controls what additional information is required for the Ad Hoc Stock Move functionality to identify individual pallets. Default Error.
|-
|Select Move Allow Held
|Allow Select Move Function to include Held Movements
|-
|Pallet Case Label Threshold
|Controls whether receipt labels are produced at pallet level or case level based on quantity
|-
|Original Priority Audit
|Controls whether an Exceptions record is created to capture the original priority of the pick / movement task
|-
|Update CPID Print Labels
|Controls if a pallet label can be printed from the Update CPID module
|-
|Update CPID Label Format
|Format of Update CPID Label
|}
=== 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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

== 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 ==
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <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
| NOPASSWORD
|-
|Ad Hoc Deconsolidation
|WHSE, OWNER
|Are deconsolidation tasks sequenced manually or by the system?
|01
|N
|-
|Ad Hoc Location Move
|WHSE, OWNER
|Allow Ad Hoc Location Movements via RF
|02
|N
|-
|Ad Hoc Pallet Move Change Pallet Type
|WHSE, OWNER
|Controls whether the user is allowed to change the pallet type within the Ad Hoc Pallet Move module
|01
|N
|-
|Ad Hoc Pallet Move Reason Prompt
|WHSE, OWNER
|Controls whether a reason code value is prompted within the Ad Hoc Pallet Move module
|01
|Y
|-
|Ad Hoc Pallet Move Suggest Location
|WHSE, OWNER
|Controls whether the WCS request a suggested location from the WMS within the Ad Hoc Pallet Move module
|01
|N
|-
|Ad Hoc Putaway Case Scan
|WHSE, OWNER
|Controls whether the Ad Hoc Putaway module requires case scanning or accepts quantity entry
|01
|Y
|-
|Ad Hoc Putaway Label Format
|WHSE, OWNER
|Format of the Ad Hoc Putaway label
|25
|
|-
|Ad Hoc Stock Move
|WHSE, OWNER, GRP
|Allow Ad Hoc Stock Movements via RF
|02
|N
|-
|Ad Hoc Stock Move Label Format
|WHSE, OWNER
|Format of the Ad Hoc Stock Move Label
|25
|
|-
|Ad Hoc Stock Move Multi Action
|WHSE, OWNER
|Controls what additional information is required for the Ad Hoc Stock Move functionality to identify individual pallets. Default Error.
|76
|E
|-
|Add Miscellaneous Charges
|WHSE, OWNER
|Allow users to add miscellaneous charges to orders
|01
|N
|-
|Additional Pick Instructions
|WHSE, OWNER
|Controls whether RDT users can view the additional pick instructions
|67
|N
|-
|Additional Pick Sequence
|WHSE, OWNER
|Controls whether additional conditions are required for sequencing pick tasks
|9003
|B
|-
|Aisle Length
|WHSE, OWNER
|The length of the Aisle portion of the Location code.
|33
|2
|-
|Allow Exchange of Replens
|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 Receipt Detail Backout
|WHSE, OWNER
|Controls whether user can back out of Receipt Detail
|01
|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
|-
|Always Deconsolidate
|WHSE, OWNER
|When enabled, the system will always deconsolidate, even when not strictly necessary (i.e. for single orders)
|55
|N
|-
|Always Display Order
|WHSE, OWNER
|If enabled, the full pick screen will always display order number rather than route/load
|01
|N
|-
|Authorise Pick Shortage
|WHSE, OWNER
|When enabled, this rule will ensure that, when part picks are cancelled or otherwise have their quantity changed, the user will be forced to obtain supervisor authorisation before continuing.
|01
|N
|-
|Automatic Despatch
|WHSE, OWNER
|Automatically despatch confirm an order when it has been deconsolidated
|01
|N
|-
|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
|
|-
|BHS Short Picking
|WHSE, OWNER
|Bespoke:short picking mechanism that automatically creates a replacement pick
|01
|N
|-
|Blind Deconsolidation
|WHSE, OWNER
|When enabled, the user will be prompted to deconsolidate blind
|55
|N
|-
|Blind Receipt (Bespoke)
|WHSE, OWNER, GRP
|Allow pallets to be received and putaway at the same time (Bespoke)
|01
|N
|-
|Blind Receipt Data Format
|WHSE, OWNER
|Controls what the RDT displays in the Blind Receipt/Return modules when displaying the pallet details
|82
|Q
|-
|Blind Receipt Label (Bespoke)
|WHSE, OWNER
|RDT label for the Blind Receipt module (Bespoke)
|49
|B
|-
|Blind Return (Bespoke)
|WHSE, OWNER, GRP
|Allow pallets to be returned and putaway at the same time (Bespoke)
|01
|N
|-
|Blind Return Label (Bespoke)
|WHSE, OWNER
|RDT label for the Blind Returns module (Bespoke)
|49
|B
|-
|Block Stack
|WHSE, OWNER
|Enables some RDT functions to exchange pallets
|01
|N
|-
|Buk PI By
|WHSE, OWNER
|Bespoke: Perform Bulk PI by Task Identifier or Stock/Sell-By-Date. Default is Task Identifier
|69
|I
|-
|Calculate Packs
|WHSE, OWNER
|If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks
|61
|N
|-
|Capture EAN
|WHSE, OWNER
|Controls whether users are allowed to enter EAN values for a stock code
|01
|N
|-
|Capture Original SSCC
|WHSE, OWNER
|Controls whether the Goods Receipt module prompts the user to enter the original SSCC value when generating a new SSCC value.
|01
|N
|-
|Change Damage Qty
|WHSE, OWNER
|If Damaged Pallet Receipt is allowed, is the quantity allowed to be changed from the full pallet quantity? Note: This functionality is supported in the Oracle WMS only.
|01
|Y
|-
|Check Duplicate Serial Numbers
|WHSE, OWNER
|Controls whether Duplicate serials are checked during Pick. Default Disabled.
|74
|N
|-
|Check EAN on Case Serial
|WHSE, OWNER
|Controls whether an error is issued if an EAN barcode is scanned as a serial number
|01
|N
|-
|Cherry Picking Selection Type
|WHSE, OWNER
|Controls how Cherry Picked tasks are assigned to users
|51
|R
|-
|Choose Deconsolidation
|WHSE, OWNER
|Allow the RDT user to choose which Marshalling lane to deconsolidate from
|01
|N
|-
|Choose Marshalling Location
|WHSE, OWNER
|Allow the pickers to choose a marshalling location when taking a picked pallet to marshalling
|65
|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
|-
|Combined Part Pick Sequence
|WHSE, OWNER
|Controls whether full pallet picks are assigned to the RDT before part pallet picks when using the Part Picking module
|64
|M
|-
|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
|-
|Confirm Take To Marshalling
|WHSE, OWNER
|Bespoke: Require Confirmation before Take To Marshalling
|01
|N
|-
|Connection Logging
|SYS
|Level of logging for System Connections (OBS USE ONLY)
|80
|D
|-
|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
|
|-
|Cross Docking
|WHSE, OWNER
|Is cross-docking enabled for this operation?
|01
|N
|-
|Customer Pallet Validation
|WHSE, OWNER
|Controls whether an enquiry message is sent to the WMS to validate if a customer pallet value can be received
|01
|N
|-
|Decon Exceptions
|WHSE, OWNER
|If enabled, this will allow supervisors to immediately resolve discrepancies found at Deconsolidation
|01
|N
|-
|Deconsolidation Logging Level
|WHSE, OWNER
|This rule indicates the detail level of Deconsolidation activity logging
|48
|D
|-
|Deconsolidation Method
|WHSE, OWNER
|Whether Deconsolidation tasks are processed by the WCS
|31
|N
|-
|Deconsolidation Pack ID
|WHSE, OWNER
|This rule indicates which pack size identification field is displayed during deconsolidation
|46
|C
|-
|Deconsolidation Stock ID
|WHSE, OWNER
|This rule indicates which stock identification fields are displayed during deconsolidation
|45
|C
|-
|Default Ad Hoc Pallet Move Reason
|WHSE, OWNER
|Controls the default reason code value for use with the Ad Hoc Pallet Move module
|53
|
|-
|Default Company Code
|SYS
|This is the default company code that the RDT will log on to.
|03
|
|-
|Default Pack Type
|WHSE, OWNER
|Default Pack Type for Pick
|9007
|STD
|-
|Default Pick Exchange Reason
|WHSE, OWNER
|Controls the default reason code value for use with pick exchanges
|53
|
|-
|Default Problem Resolution Location
|WHSE, OWNER
|
|03
|
|-
|Default Problem Resolution Location CD
|WHSE, OWNER
|
|03
|
|-
|Default Problem Resolution Location Type
|WHSE, OWNER
|
|28
|
|-
|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
|
|-
|Default Short Pick Reason
|WHSE, OWNER
|Default reason code for short and zero picks (Bespoke)
|53
|
|-
|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
|-
|Despatch Label Format
|WHSE, OWNER
|Format of the despatch label
|25
|
|-
|Despatch Note Printer
|WHSE, OWNER
|Where the Despatch Note Printer is defined
|47
|M
|-
|Display Ad Hoc Putaway Locations
|WHSE, OWNER
|If enabled, this parameter ensures a location enquiry is sent to the WMS from Ad Hoc Putaway to find locations assigned to the stock code
|02
|N
|-
|Display Decon Summary
|WHSE, OWNER
|This rule controls whether the deconsolidation process displays a summary screen with Order Information at the start of deconsolidating each order
|01
|Y
|-
|Display Default Receipt Values
|WHSE, OWNER
|Controls whether the RDT displays the pallet details of the previous pallet as the default values of the pallet being received
|01
|N
|-
|Display Multi UOM
|WHSE, OWNER
|Controls the display of Multiple UOM Descriptions when entering Pick Quantity
|01
|N
|-
|Display Order Summary
|WHSE, OWNER
|Defines when the order summary screen is displayed on the RDT during part picking.
|42
|S
|-
|Display PO Number
|WHSE, OWNER
|Display the PO Number associated with the pick
|01
|N
|-
|Display UOM
|WHSE
|Display UOM on RDT when user prompted to enter a quantity value.
|01
|N
|-
|Dummy Loc Enq Duration
|SYS
|Sets the duration of time in minutes without a message before a dummy location enquiry is sent to the WMS. Default is 30 min.
|04
|30
|-
|Dummy Loc Timer Duration
|SYS
|Sets the duration of time for the dummy location check in minutes. Default is every 2 min.
|04
|2
|-
|Dummy Loc Trigger
|SYS
|Controls the trigger checks of the dummy location enquiry to the WMS. Default is Incoming only.
|70
|I
|-
|Duration Measurement
|WHSE, OWNER
|Controls whether the duration value is sent to the WMS in seconds or minutes
|66
|M
|-
|Enable Admin Change Warehouse
|SYS, GRP
|Allows the user to change the default warehouse they can see
|01
|N
|-
|Enable Admin 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
|-
|Enable Admin Comms Enquiry
|SYS, GRP
|Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.
|01
|N
|-
|Enable Admin Logs
|SYS, GRP
|Allows the user access to the Logs Enquiry screens in the System Tools menu
|01
|N
|-
|Enable Admin Report
|SYS, GRP
|Allows the user access to the Reports menu
|01
|N
|-
|Enable Admin Settings System
|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
|-
|Enable Admin 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
|-
|Enable Admin Standing Data Enquiry
|SYS, GRP
|Allows the user access to the Enquiry screens only on the Standing Data menu
|01
|N
|-
|Enable Admin 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
|-
|Enable Admin Task Enquiry
|SYS, GRP
|Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.
|01
|N
|-
|Enable Admin Utilities Clear Out
|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
|-
|Enable Admin Utilities Repair and Compact
|SYS, GRP
|Allows the user access to the Compact Database option on the System Tools menu.
|01
|N
|-
|Enable Check Digits
|WHSE, OWNER
|Does the warehouse use check digits, or just location codes?
|11
|Y
|-
|Enable 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
|-
|Enable Encoded Sell By Date
|WHSE, OWNER
|Use encoded sell by dates?
|01
|N
|-
|Enable Full Pick Header Lock
|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
|-
|Enable Mixed Stock
|WHSE, OWNER
|Do you have mixed-stock pallets?
|01
|N
|-
|Enable Multi Pallet Putaway
|WHSE, OWNER
|Allow several pallets to be picked up during putaway
|02
|N
|-
|Enable 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
|-
|Enable Packing
|WHSE, OWNER, GRP
|Allow the RDT user to pack orders
|02
|N
|-
|Enable Pick Dependencies
|WHSE, OWNER
|Ensure part picks are not released for picking until any outstanding replenishment has been completed first
|01
|Y
|-
|Enable Picker Replens
|WHSE, OWNER
|Allow pickers to perform their own replens at the point of picking the part picks.
|02
|N
|-
|Enable RDT Ad Hoc Move
|WHSE, OWNER, GRP
|Allow instigation of a housekeeping Move from the RDT.
|02
|Y
|-
|Enable RDT Ad Hoc Putaway
|WHSE, OWNER, GRP
|Allow Ad Hoc Putaway for shelving locations. Bespoke.
|02
|N
|-
|Enable RDT Bulk PI
|WHSE, OWNER, GRP
|Allow Perpetual Inventory (ad hoc stock check).
|02
|Y
|-
|Enable 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
|-
|Enable RDT Combined Split
|WHSE, OWNER, GRP
|Bespoke: Ad hoc movements of small quantities of stock to other locations
|02
|N
|-
|Enable RDT 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).
|52
|Y
|-
|Enable RDT Daily Cycle Check
|WHSE, OWNER, GRP
|The Daily Cycle Check functionality will be available to the users if this rule is enabled
|02
|N
|-
|Enable RDT Damages
|WHSE, OWNER, GRP
|Allow Damage quantity entry during Goods Receipt
|01
|N
|-
|Enable RDT DC Aisles
|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
|-
|Enable RDT Deconsolidation
|WHSE, OWNER, GRP
|Allow deconsolidation of consolidated orders.
|02
|N
|-
|Enable RDT Despatch
|WHSE, OWNER, GRP
|Allow despatch of deconsolidated orders.
|02
|N
|-
|Enable RDT Despatch Serial No Scanning
|WHSE, OWNER, GRP
|Allow entering serial numbers for picked items. Bespoke.
|02
|N
|-
|Enable RDT Echo Putaway
|WHSE, OWNER
|If enabled, this parameter makes the RDT Receiving process display the suggested putaway location after successfully receiving a pallet.
|19
|0
|-
|Enable RDT Eurodate
|WHSE, OWNER
|Bespoke: Enter Eurodate rather than Manufacture Date
|01
|N
|-
|Enable RDT Layers
|WHSE, OWNER
|Enter Layers and Bits at Goods Receipt
|01
|N
|-
|Enable RDT Loading
|WHSE, OWNER, GRP
|Allow Loading ojnto a vehicle.
|02
|N
|-
|Enable RDT Location Enquiry
|WHSE, OWNER, GRP
|Allow the RDT user to enquire on the contents of a location from the WMS.
|02
|Y
|-
|Enable RDT Mail
|WHSE, OWNER, GRP
|Allow receipt of messages from Maintenance administrators. (Generally, this should always be enabled).
|02
|Y
|-
|Enable RDT Marshall
|WHSE, OWNER, GRP
|Not Yet Implemented.
|02
|N
|-
|Enable RDT Measure Qty
|WHSE, OWNER
|Allow Measure Quantity to be entered on the RDT
|01
|N
|-
|Enable RDT Move Enquiry
|WHSE, OWNER, GRP
|Allow the RDT to see where a pallet is going.
|02
|Y
|-
|Enable RDT Move Select
|WHSE, OWNER, GRP
|Allow cherry-picking of an individual Move task.
|02
|Y
|-
|Enable RDT Pallet Enquiry
|WHSE, OWNER, GRP
|Allow the RDT user to enquire on the contents of a pallet from the WMS.
|02
|Y
|-
|Enable RDT Pallet Move
|WHSE, OWNER, GRP
|Allow the user to complete Full-Pallet Movements generated from the WMS.
|02
|Y
|-
|Enable RDT Part Picking
|WHSE, OWNER, GRP
|Allow the user to complete Case and Unit picks from the RDT.
|02
|Y
|-
|Enable RDT Part Replenishments
|WHSE, OWNER, GRP
|Allow completion of Part Replenishment tasks
|02
|N
|-
|Enable RDT Pick Extra Items
|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
|-
|Enable RDT Pick Location Error
|WHSE, OWNER, GRP
|Allow the RDT picker to cancel a pick at the point of confirming the location code.
|02
|N
|-
|Enable RDT Picking
|WHSE, OWNER, GRP
|Allow the user to complete Full-pallet Picks.
|02
|Y
|-
|Enable RDT Pop Up Description
|WHSE, OWNER
|Pop up description of stock on RDT screen
|38
|N
|-
|Enable RDT Putaway
|WHSE, OWNER, GRP
|Allow Full-Pallet Putaway.
|02
|Y
|-
|Enable RDT Receipt
|WHSE, OWNER, GRP
|Allow Blind (Stock level) and Check (Pallet level) Goods Receipt.
|02
|Y
|-
|Enable RDT Receipt Serial No Scanning
|WHSE, OWNER, GRP
|Allow entering serial numbers for received items. Bespoke.
|02
|N
|-
|Enable RDT Receive Additional Pallets
|WHSE, OWNER, GRP
|Allow additional pallets to be received during the RDT receipt process
|02
|Y
|-
|Enable RDT Reject Spur
|WHSE, OWNER, GRP
|Allow Reject Spur Processing. Bespoke to automated conveyor and P&D systems. Bespoke.
|02
|N
|-
|Enable RDT Replenishment
|WHSE, OWNER, GRP
|Allow completion (and/or generation) of a Replenishment. Bespoke.
|02
|N
|-
|Enable RDT Reposition
|WHSE, OWNER, GRP
|Allow reposition on the RDTs? This option can be over-ridden by the Group setting
|57
|N
|-
|Enable RDT Select Replenishment
|WHSE, OWNER, GRP
|Allow Select Replenishment. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Building
|WHSE, OWNER, GRP
|Allow Shipment Pallet Building. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Despatch
|WHSE, OWNER, GRP
|Allow Shipment Pallet Despatch. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Moves
|WHSE, OWNER, GRP
|Allow Shipment Pallet Moves. Bespoke.
|02
|N
|-
|Enable RDT Stock Adjustment
|WHSE, OWNER, GRP
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|02
|N
|-
|Enable RDT Stock Enquiry
|WHSE, OWNER, GRP
|Bespoke: Enquire on Stock code
|02
|N
|-
|Enable RDT Stock Move
|WHSE, OWNER, GRP
|Allow Stock Moves (request replenishment of pick face). Bespoke.
|02
|N
|-
|Enable RDT Stock Take
|WHSE, OWNER, GRP
|Allow Full (Blind) and Partial (Check) Stock Check.
|02
|Y
|-
|Enable RDT Weighing
|WHSE, OWNER, GRP
|Allow the RDT user to Weight Shipment Packages.
|02
|N
|-
|Enable RDT Weights
|WHSE, OWNER, GRP
|Allow Weight to be entered on the RDT
|58
|N
|-
|Enable Replen Dependencies
|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
|-
|Enable Stock Putaway
|WHSE, OWNER, GRP
|Allow the RDT user to Stock Putaway
|02
|N
|-
|Enable Stock Transfers
|WHSE, OWNER, GRP
|Allow completion of Stock Transfer tasks
|02
|N
|-
|Enable WCS Gen Replen
|WHSE, OWNER
|Let WCS Generate Replenishments
|01
|Y
|-
|Enhanced Pick Exchange
|WHSE, OWNER
|Allow pick exchanges from different locations and for part pallet pick tasks
|01
|Y
|-
|Enter CIM Printer
|WHSE, OWNER
|Controls whether the RDT prompts the user to enter a printer during deconsolidation on which the CIM labels will be printed
|55
|N
|-
|Enter Delivery Reference
|WHSE, OWNER
|Allow the user to enter a delivery reference in RDT Goods Receipt.
|01
|N
|-
|Enter Despatch Pallet Type
|WHSE, OWNER
|Controls whether pickers are prompted to enter the pallet being picked or picked onto
|83
|D
|-
|Enter Despatch Printer
|WHSE, OWNER
|Controls whether the RDT prompts the user to enter a printer during deconsolidation on which the despatch note will be printed
|55
|N
|-
|Enter Media Type
|WHSE, OWNER
|When enabled, the user will be prompted to enter a media type for the final media
|55
|N
|-
|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 Putaway Location
|WHSE, OWNER
|Allow users to receive and putaway items in a single process
|72
|N
|-
|Enter Vintage
|WHSE, OWNER
|Controls whether the Goods Receipt module prompts for a vintage value
|02
|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 Default Manu Date
|WHSE, OWNER
|Bespoke: If this rule is enabled and manufacture dates are required at goods receipt, the RDT will not prompt for this but will instead default the value to the current date.
|01
|N
|-
|Force Sky Picking
|WHSE, OWNER
|Are part pick tasks from bulk treated as sky picks?
|59
|N
|-
|Force Source Confirmation
|WHSE, OWNER
|Force the confirmation of the source picking location for each pick even if it is the same as the previous pick.
|01
|N
|-
|Full Pallet Task Exchange
|WHSE, OWNER
|Controls whether Full Pallet TASK exchange is allowed between orders
|78
|S
|-
|Full Pick Despatch Labels
|WHSE, OWNER
|If disabled, Despatch labels will not be printed for full pallet picks.
|01
|Y
|-
|Generate Customer Pallet Id
|WHSE, OWNER
|If enabled, this rule allows users to determine whether the WMS generates a customer pallet id value.
|01
|N
|-
|Goods Receipt Lookup
|WHSE, OWNER
|Allow Goods Receipt lookup in RDT Goods Receipt
|01
|N
|-
|Goods Receipt Vehicle Checks
|WHSE, OWNER
|Controls whether an enquiry message is sent to the WMS to validate if a GRN has been Vehicle Checked
|01
|N
|-
|GS1-128 Scan Sequence
|WHSE, OWNER
|Bespoke: Determines preferred sequence of fields on GS1-128 Scan
|71
|00
|-
|In Pick Check
|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.
|54
|N
|-
|Largest Task Next Sequence
|WHSE, OWNER
|Set the sequence of picks after selection by Largest Qty
|79
|N
|-
|Latest Sell By Date Check
|WHSE, OWNER
|Controls whether input of SellByDate is checked against latest date
|73
|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 Despatch Note Printer
|WHSE, OWNER
|Controls whether the Loading module prompts for a printer for the despatch note
|01
|N
|-
|Loading Dock Door
|WHSE, OWNER
|Controls whether the Loading user is prompted for Dock Door and how this will be confirmed.
|50
|N
|-
|Loading Exceed Multiple Limit
|WHSE, OWNER
|Controls the action taken by the RDT when the Multiple Limit is exceeded.
|14
|W
|-
|Loading Lift Entry
|WHSE, OWNER
|Controls whether the Loading module prompts for the number of lifts and pallets
|01
|N
|-
|Loading Method
|WHSE, OWNER
|Loading Method in use for the warehouse
|20
|N
|-
|Loading Multiple Limit
|WHSE, OWNER
|This is the limit for how many items can be scanned onto a vehicle before Dock Door must be entered.
|
|0
|-
|Loading Order Enquiry
|WHSE, OWNER
|Controls whether the Loading module allows the user to perform order status enquiry requests
|01
|N
|-
|Loading Scan Multiples
|WHSE, OWNER
|Controls whether the user is allowed to scan multiple loaded items before being prompted to take the items to the Dock Door.
|01
|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
|-
|Loading Sequence
|WHSE, OWNER
|The sequence in which orders will be loaded within the load (affects Loading By Bay Door only)
|36
|N
|-
|Loading Trailer Number
|WHSE, OWNER
|Controls whether the Loading module prompts the user to enter a trailer number value
|01
|N
|-
|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
|25
|
|-
|Log Postponement
|WHSE, OWNER
|Whether pick postponements are recorded in the Exceptions Log
|01
|N
|-
|Loose Item Serial Number
|WHSE, OWNER
|Controls whether serial number entry is required when picking loose cases and units
|9006
|N
|-
|Marshalling Method
|WHSE, OWNER
|Controls whether orders are to be marshalled or not
|9004
|B
|-
|Maximum Putaway Quantity
|WHSE, OWNER
|Maximum quantity allowed to be received and putaway by UPC code (Bespoke)
|04
|0
|-
|Minimum Pallet ID Length
|WHSE, OWNER
|Controls the minimum length of SSCC entered in Receipt
|04
|0
|-
|Move Efficient Flag
|WHSE, OWNER
|Location or priority efficiency
|05
|L
|-
|Multi Stage Confirmation Message
|WHSE, OWNER
|Controls whether confirmation messages are sent to the WMS for multi stage tasks
|02
|N
|-
|Multi-Pallet Picking Sequence
|WHSE, OWNER
|Controls whether the first pallet picked or last pallet picked via WA Dual Cycling is taken to marshalling first
|63
|L
|-
|Multi-Pallet WADC
|WHSE, OWNER
|Determines whether the WADC modules allow multiple pallets to be picked at the same time
|62
|N
|-
|Multiple Putaway Tasks Prompt
|WHSE, OWNER
|Controls whether the RDT prompts the user to complete one or all of the putaway tasks when multiple putaway tasks exist for the customer pallet id
|01
|N
|-
|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
|-
|New Stock Take Message Layout
|WHSE, OWNER
|BESPOKE: Changes the Stock Take message to WMS to a different extended format. USE WITH CAUTION
|01
|N
|-
|Nokia Barcodes
|WHSE, OWNER
|This rule controls whether the RDT will expect to scan Nokia barcode labels
|01
|N
|-
|Num Picks before RSBE
|WHSE, OWNER
|The number of picks to elapse between residual stock balance enquiries
|04
|0
|-
|OBS Menu
|SYS, GRP
|Controls access to the OBS Support Menu
|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
|QMC
|-
|Ora Password
|SYS
|The password of the user for the connection to the Oracle database.
|26
|
|-
|Ora Priority Incoming Queue
|SYS
|The Oracle queue on which high priority messages are stored
|03
|
|-
|Ora User
|SYS
|The username for the connection to the Oracle database
|03
|SCE
|-
|Original Priority Audit
|WHSE, OWNER
|Controls whether an Exceptions record is created to capture the original priority of the pick / movement task
|01
|N
|-
|Pallet Case Label Threshold
|WHSE, OWNER
|Controls whether receipt labels are produced at pallet level or case level based on quantity
|04
|1
|-
|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
|-
|Part Pick Pallet Count
|WHSE, OWNER
|Controls whether Part Picking prompts users to enter a pallet count
|01
|N
|-
|Part Replen Label Format
|WHSE, OWNER
|Format of the Part Replen label
|25
|
|-
|PC Generation Algorithm
|WHSE, OWNER
|Algorithm to generate Picking Containers
|9002
|
|-
|PC Prefix
|WHSE, 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
|-
|Pick By Order
|WHSE, OWNER
|Controls whether a picker is locked to task for a single order
|77
|N
|-
|Pick Catch Weight Per Case
|WHSE, OWNER
|Controls whether Catch Weights are entered at Case instead of Stock/Pick level. Default Disabled.
|01
|N
|-
|Pick Consolidate Group
|WHSE, OWNER
|For Consolidated picking: How to create groups of picks.
|10
|N
|-
|Pick for On-time Delivery
|WHSE, OWNER
|If enabled, this rule will ensure that picks are assigned to pickers in Priority, then OTD Date and Time sequence
|01
|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 Multiple Containers
|WHSE, OWNER
|If enabled, allows creation of several containers in sequence
|01
|N
|-
|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
|-
|Picking Container Adjustment
|WHSE, OWNER, GRP
|Allow the user to adjust Picking Containers. Bespoke
|02
|N
|-
|Picks by Quantity
|WHSE, OWNER
|Allocates pick tasks to the RDT users by quantity, largest first.
|01
|N
|-
|Pre-Receipt Sort (Bespoke)
|WHSE, OWNER, GRP
|Allow Pre-Receipt Sortation (Bespoke)
|01
|N
|-
|Pre-Reposition
|WHSE, OWNER
|Bespoke: Pre-reposition all pending putaways for a stock code when a pallet of the same stock is repositioned
|01
|N
|-
|Print Ad Hoc Putaway Labels
|WHSE, OWNER
|Whether the RDT attempts to print labels for Ad Hoc Putaways
|02
|N
|-
|Print Ad Hoc Stock Move Labels
|WHSE, OWNER
|Controls whether the Ad Hoc Stock Move module prompts the user to print a label
|43
|N
|-
|Print Despatch Labels
|WHSE, OWNER
|Whether the RDT attempts to print despatch labels for picked stock.
|30
|N
|-
|Print Part Replen Labels
|WHSE, OWNER
|Whether the RDT attempts to print labels for Part Replenishments
|43
|N
|-
|Print Stock Despatch Label
|WHSE, OWNER
|Controls whether the Part Picking module allows stock level despatch labels to be produced
|68
|N
|-
|Priority Change Audit
|SYS
|Controls whether an Exceptions record is created to capture when a user changes the priority of a task
|01
|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
|AG_CCWH
|-
|Quick Pack
|WHSE, OWNER
|Allow Home Use orders not assigned to a route/load or assigned to a route/load individually to skip the deconsolidation process
|01
|N
|-
|RDT Box Drawing
|SYS
|What style of box-drawing the RDT's connected to this WCS will use.
|44
|1
|-
|RDT Wait Time
|SYS
|This is the amount of time that the RDT application will wait before re-trying communications to the WCS.
|04
|20
|-
|RDT_WCS LocalPort
|SYS
|This is the port that the WCS listens to for communications from RDTs.
|04
|15002
|-
|Receipt 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 ‘R
|01
|N
|-
|Receipt Enter Type
|WHSE, OWNER
|Allow the user to enter the receipt type in RDT Goods Receipt
|01
|N
|-
|Receipt Expected Quantity Check
|WHSE, OWNER
|If enabled, this parameter makes the RDT compare the received quantity entered with the expected quantity pre-advised
|02
|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
|-
|Receipt Intake Stock Check
|WHSE, OWNER
|Controls Issue Life Check at Receipt
|22
|N
|-
|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
|-
|Receipt Print Labels
|WHSE, OWNER
|Controls where/if pallet labels are printed during the receipt process
|21
|N
|-
|Receipt Selection Type
|WHSE, OWNER
|How to find the receipt on the RDT - via Advice Note or GRN no.
|08
|A
|-
|Receipt Single Barcode
|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
|-
|Redundant Stock Check
|WHSE, OWNER
|If enabled, products marked as redundant are rejected when scanned at receipt
|01
|N
|-
|Regroup Order by Stock
|SYS
|Allow WCS Maintenance users to re-group an order's picks by the number of stock picks on the order, then by location.
|01
|N
|-
|Reprint Despatch Label at Decon
|WHSE, OWNER
|When enabled, the RDT will print despatch labels for orders when deconsolidated
|01
|N
|-
|Request Putaway 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
|-
|RF Use Estimated Pallets
|WHSE, OWNER
|If enabled, then the new estimated pallets message will be sent to the Calidus-3pl Mobile system
|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
|-
|Select Move Allow Held
|WHSE, OWNER
|Allow Select Move Function to include Held Movements
|01
|N
|-
|Select Stock Move by Stock
|WHSE, OWNER
|Allow selection of stock moves by Stock before Pallet
|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
|-
|Serial Maximum Length
|WHSE, OWNER
|Controls the maximum length of a scanned case serial number in Picking. Default 0 (disabled)
|04
|0
|-
|Serial Minimum Length
|WHSE, OWNER
|Controls the minimum length of a scanned case serial number in Picking. Default 0 (disabled)
|04
|0
|-
|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
|-
|Shipment Pallet Build Validation
|WHSE, OWNER
|Controls what validation is followed when assigning shipment packages onto shipment pallets
|60
|P
|-
|Single Picker Per Order
|WHSE, OWNER
|Assign related picks to user on first pick. Default Disabled
|01
|N
|-
|Split Face Sequence
|WHSE, OWNER
|Controls the sort sequence when Split Faces enabled
|75
|1
|-
|Split Pick Quantities
|WHSE, OWNER
|If enabled, allows large picks to be split into more than one pack
|01
|N
|-
|Split Tote
|WHSE, OWNER
|Allow the user to choose to split a picked line over several totes.
|01
|N
|-
|Stock Take Batch Check
|WHSE, OWNER
|When checking pallets during Stock Take, request the user to check the customer batch value
|01
|N
|-
|Stock Take Enter GRN
|WHSE, OWNER
|When adding pallets during Stock Take or Perpetual Inventory, request the user to enter a GRN number
|01
|N
|-
|Stock Take Sell By Date Check
|WHSE, OWNER
|When checking pallets during Stock Take, request the user to check the sell by date value
|01
|N
|-
|Task Identifier
|WHSE, OWNER
|Which field to use to identify pallets
|06
|P
|-
|Temperature Recording
|WHSE, OWNER
|Controls whether Temperature Recording is required at Pre-Advice
|01
|N
|-
|Tote to Carton Standardise
|WHSE, OWNER
|If enabled, the RDT screens will be amended to display Carton in place of Tote
|01
|N
|-
|Track Deconsolidation
|WHSE, OWNER
|When enabled, this rule will inform WMS when orders have been completely deconsolidated
|01
|N
|-
|Trolley IDs
|WHSE, OWNER, GRP
|Allow loading of orders into trolleys
|02
|N
|-
|Update CPID
|WHSE, OWNER, GRP
|Allow the user to update the customer pallet id value. Bespoke
|02
|N
|-
|Update CPID Label Format
|WHSE, OWNER
|Format of Update CPID Label
|25
|
|-
|Update CPID Print Labels
|WHSE, OWNER
|Controls if a pallet label can be printed from the Update CPID module
|01
|N
|-
|Use Dummy Checksum
|SYS
|Used to terminate the interface messages with a dummy checksum value (??)
|01
|N
|-
|Use WMS Pick Sequence
|WHSE, OWNER
|Controls whether pick tasks are assigned to a picker in WMS location pick sequence order
|01
|N
|-
|Use WMS Rotation instead of Cust Batch
|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
|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
|-
|WA DC Exclude S to D moves
|WHSE, OWNER
|Ensures WA DC (interleaving) focuses more on emptying P&D locations rather than completing housekeeping moves.
|01
|Y
|-
|WCS Stock Despatch Label Format
|WHSE, OWNER
|Format of the stock despatch label
|25
|
|-
|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
|
|-
|Weight Volume Check
|WHSE, OWNER
|Check stock dimensions and weight are populated during Goods Receipt.
|01
|N
|-
|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
|*****
|-
|WMS System
|SYS
|Version of WMS that the WCS is connecting to.
|56
|O
|-
|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
|
|-
|Write RPM Logs
|WHSE, OWNER
|Bespoke: Write RPM record to Error Log. Default Disabled
|01
|N
|-
|Zero Negative Quantities
|WHSE, OWNER
|Zero negative values on enquiries. Default Enabled
|01
|Y
|}

Categories:
{| border="1" class="wikitable prettytable apt-searchable"
|- bgcolor="silver"
! <center>Category</center>
! <center>Value</center>

|-
| 01
| N-Disabled

|-
| 01
| Y-Enabled

|-
| 02
| N-Disabled

|-
| 02
| P-Password-Protected

|-
| 02
| Y-Enabled

|-
| 03
| Plain Text

|-
| 04
| Plain Numeric

|-
| 05
| L-By Location

|-
| 05
| P-By Priority

|-
| 06
| C-By Cust Pallet ID

|-
| 06
| P-By Pallet ID

|-
| 06
| S-By Stock

|-
| 07
| B-Blind Receipt

|-
| 07
| C-Check Receipt

|-
| 07
| N-Non Pre-Advised Receipt

|-
| 07
| P-Non Pre-Advised Receipt & Putaway

|-
| 08
| A-By Advice No

|-
| 08
| C-By Cust Pallet Id

|-
| 08
| G-By GRN No

|-
| 09
| L-By Load Number

|-
| 09
| O-By Order Number

|-
| 10
| N-None

|-
| 10
| S-By Stock/Batch

|-
| 11
| C-Combo Check

|-
| 11
| N-Disabled

|-
| 11
| Y-Enabled

|-
| 12
| A-By Aisle

|-
| 12
| C-By Route/Load WMS Consolidation

|-
| 12
| L-By Load/Aisle

|-
| 12
| O-By Order Number

|-
| 12
| P-By Order Page

|-
| 12
| R-By Reference

|-
| 12
| Z-By Area/Zone

|-
| 13
| Date

|-
| 14
| A-Audit

|-
| 14
| E-Error

|-
| 14
| I-Information

|-
| 14
| W-Warning

|-
| 15
| F-Full/Blind

|-
| 15
| P-Preadvised/Partial

|-
| 16
| A-Area (m2)

|-
| 16
| I-Impressions

|-
| 16
| L-Length (m)

|-
| 16
| Q-Quantity

|-
| 16
| V-Volume (m3)

|-
| 16
| W-Weight (kg)

|-
| 17
| Priority Values

|-
| 18
| M-Manual

|-
| 18
| T-Threshold

|-
| 18
| W-Weighting

|-
| 19
| 0-Disabled

|-
| 19
| 1-Fetch Details

|-
| 19
| 2-Display Location

|-
| 20
| B-By Bay Door

|-
| 20
| C-By Carton

|-
| 20
| F-By Final Media Number

|-
| 20
| I-By Picking Container

|-
| 20
| L-By Picking Container and Location

|-
| 20
| N-Disabled

|-
| 20
| P-By Pick

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

|-
| 21
| C-WCS

|-
| 21
| M-WMS

|-
| 21
| N-Neither

|-
| 21
| P-WMS - Prompt For Printer on WCS

|-
| 21
| Q-WCS - Quantity

|-
| 21
| R-WCS - Receipts Only

|-
| 22
| A-Authorisation Required

|-
| 22
| E-Error

|-
| 22
| I-Informational Message

|-
| 22
| N-None

|-
| 23
| B-By Stock and Batch

|-
| 23
| L-By Stock and Batch (Line Type)

|-
| 23
| N-No Id

|-
| 23
| P-By Pallet ID

|-
| 23
| S-By Stock Code

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

|-
| 23
| 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
| D-Printer Dependant

|-
| 29
| M-Marshalling

|-
| 29
| P-Pick

|-
| 29
| S-At Start Only

|-
| 30
| C-Per Case

|-
| 30
| D-Per Despatch Pallet

|-
| 30
| N-Disabled

|-
| 30
| P-Per Pick

|-
| 30
| R-Request Quantity

|-
| 30
| W-WMS

|-
| 31
| D-Deconsolidate Only

|-
| 31
| N-Disabled

|-
| 31
| P-Deconsolidate and Pack

|-
| 32
| A-At Allocation

|-
| 32
| L-At Location

|-
| 33
| Aisle Length

|-
| 34
| Bay Length

|-
| 35
| Level Length

|-
| 36
| A-By Drop Sequence

|-
| 36
| D-By Reverse Drop Sequence

|-
| 36
| N-Disabled

|-
| 37
| C-By Customer Order

|-
| 37
| O-By Order Number

|-
| 37
| P-By Picking Container's Order

|-
| 37
| R-By Route/Load

|-
| 38
| N-Disabled

|-
| 38
| P-Pick Only

|-
| 38
| R-Goods Receipt Only

|-
| 38
| Y-Enabled

|-
| 39
| E-Enter Tray Values

|-
| 39
| G-Generate

|-
| 39
| N-Disabled
|-
|39
|O-Check Order
|-
|39
|P-Password_Protected
|-
|39
|S-Generate SSCC
|-
|39
|T-Pre-Set Tray Values
|-
|39
|Y-Enabled
|-
|40
|Decimal
|-
|41
|M-At Marshalling
|-
|41
|N-Disabled
|-
|41
|S-At Start
|-
|42
|E-At Each Dispatch Pallet
|-
|42
|L-At Location
|-
|42
|N-Disabled
|-
|42
|S-At Start Only
|-
|43
|N-Disabled
|-
|43
|R-Request Quantity
|-
|44
|0-Single Line
|-
|44
|1-Double Line
|-
|44
|1024-Black (Reverse display)
|-
|44
|256-Simple
|-
|44
|512-Block
|-
|45
|C-Stock Code
|-
|45
|O-Stock Description ((Line 1 only)
|-
|45
|T-Stock Description (Line 1 and 2)
|-
|46
|C-Size Pack Text from Stock Code
|-
|46
|I-Impressions Pack Size
|-
|47
|C-WCS
|-
|47
|M-WMS
|-
|48
|D-Detail
|-
|48
|S-Summary
|-
|49
|B-Blind Receipt
|-
|49
|P-Putaway
|-
|50
|E-Enter first and confirm
|-
|50
|N-Disabled
|-
|50
|O-Enter and Validate
|-
|51
|O-By Order Number
|-
|51
|R-By Route/Load
|-
|52
|C-Complete Entire Reference
|-
|52
|N-Disabled
|-
|52
|Y-Enabled
|-
|53
|Plain text (with Reason Code lookup)
|-
|54
|C-Check Order
|-
|54
|L-Check Countback Level
|-
|54
|N-Disabled
|-
|54
|O-Check Order Password Protected
|-
|54
|P-Password Protected
|-
|54
|Y-Enabled
|-
|55
|C-Check Order
|-
|55
|N-Disabled
|-
|55
|Y-Enabled
|-
|56
|414-'414' - Powerhouse WMS
|-
|56
|770-'770' - Oracle WMS
|-
|57
|A-Automatic
|-
|57
|N-Disabled
|-
|57
|P-Password Protected
|-
|57
|Y-Enabled
|-
|58
|G-Goods Receipt Only
|-
|58
|N-Disabled
|-
|58
|P-Pick Only
|-
|58
|Y-Enabled
|-
|59
|N-Disabled
|-
|59
|P-At PND
|-
|59
|Y-Enabled
|-
|60
|P-By Order Priority
|-
|60
|S-By Order Priority/Store Code
|-
|61
|E-Use Estimated Values
|-
|61
|N-Disabled
|-
|61
|Y-Enabled
|-
|62
|I-Picking Only
|-
|62
|N-Disabled
|-
|62
|U-Putaway Only
|-
|62
|Y-Enabled
|-
|63
|F-First Pick First
|-
|63
|L-Last Pick First
|-
|64
|F-Full Before Part
|-
|64
|M-Mixed Sequence
|-
|65
|M-Multi Marshalling Locs
|-
|65
|N-Disabled
|-
|65
|R-Require new Location
|-
|65
|S-Suggest new Location
|-
|65
|Y-Enabled
|-
|66
|M-Minutes
|-
|66
|S-Seconds
|-
|67
|A-Automatic
|-
|67
|N-Disabled
|-
|67
|Y-Enabled
|-
|68
|D-Per Despatch Pallet
|-
|68
|N-Disabled
|-
|69
|I-Task Identifier
|-
|69
|S-Stock/Sell-By-Date
|-
|70
|B-Both
|-
|70
|I-Incoming
|-
|70
|O-Outgoing
|-
|71
|00-Default Identifiers
|-
|71
|01-Stock (240) Then GTIN (01)
|-
|72
|N-Disabled
|-
|72
|R-Returns Only
|-
|72
|Y-Enabled
|-
|73
|A-Authorisation Required
|-
|73
|E-Error
|-
|73
|N-None
|-
|73
|W-Warning
|-
|74
|C-Check Case scans only
|-
|74
|N-Disabled
|-
|74
|U-Check Unit scans only
|-
|74
|Y-Check Case and Unit scans
|-
|75
|1-Up Odd, Up Even
|-
|75
|2-Up Odd, Down Even
|-
|75
|3-Up Even, Up Odd
|-
|75
|4-Up Even, Down Odd
|-
|75
|5-Down Odd, Down Even
|-
|75
|6-Down Odd, Up Even
|-
|75
|7-Down Even, Down Odd
|-
|75
|8-Down Even, Up Odd
|-
|76
|C-Customer Batch
|-
|76
|E-Error
|-
|76
|P-Pallet ID
|-
|76
|S-Sell By Date
|-
|77
|F-Full Pallets
|-
|77
|N-Disabled
|-
|78
|M-Multiple Orders
|-
|78
|S-Single Order
|-
|79
|A-Ascending Aisle
|-
|79
|B-Ascending Aisle/Bay
|-
|79
|N-Default
|-
|80
|D-Default
|-
|80
|R-Reduced
|-
|81
|Plain text (with Reason Code lookup & Blank)
|-
|82
|C-Loc/Case/Unit/Rot
|-
|82
|Q-Loc/Qty/Area
|-
|83
|B-Part Picks and Full Pallet Picks
|-
|83
|D-Disabled
|-
|83
|F-Full Pallet Picks Only
|-
|83
|P-Part Picks Only
|-
|9001
| -Standard site (No bespoke rules)
|-
|9001
|BIBBY-Bibby
|-
|9001
|BRAC-Culina Brackmills (HOD)
|-
|9001
|BRETT-Bretts Transport
|-
|9001
|CENT-Century Logistics
|-
|9001
|CERT-Culina Port Salford (PS)
|-
|9001
|COV-DHL Coventry
|-
|9001
|DHLSKM-DHL Skelmersdale
|-
|9001
|ELLIS-Ellis Hanworth
|-
|9001
|FURRY-DHL EXEL Furry Park
|-
|9001
|FWLMA-XKO Sites
|-
|9001
|HAN-Hanson
|-
|9001
|HODD-Culina Hoddesdon (OCT)
|-
|9001
|MOR-Moran
|-
|9001
|NIJ-DHL EXEL Healthcare
|-
|9001
|POD-Port Of Dover
|-
|9001
|POT-Potter
|-
|9001
|SCH-Schenker
|-
|9001
|TBI-DHL EXEL Dublin RHR
|-
|9001
|TBW-DHL EXEL Whitwood
|-
|9001
|TNT-TNT
|-
|9002
|JJD-JJD
|-
|9003
|B-Blank
|-
|9003
|C-Largest Case Qty First
|-
|9003
|Q-Largest Quantity First
|-
|9003
|S-Sort By Product Strength
|-
|9004
|B-Disabled
|-
|9004
|P-By Picking Container and Location
|-
|9006
|N-Disabled
|-
|9006
|S-Allow Shortages
|-
|9006
|Y-Required
|-
|9007
|Plain text (with Media Type lookup)
|}
==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]]

Set-up Guide

2025-10-30T13:04:23Z

Anw: Mass update of all rules in the system

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = Set-up Guide
| Reference = UG 106181
| Version = 7.03
| Date = 30th October 2025
| Sysver = 3.4
}}


= 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 and whether the truck type is considered intrinsically safe.

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="wikitable 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="wikitable 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.
|-
|Enable RDT Daily Cycle Check
|The Daily Cycle Check functionality will be available to the users if this rule is enabled
|-
|Enable RDT Part Replenishments
|Allow completion of Part Replenishment tasks
|-
|Trolley IDs
|Allow loading of orders into trolleys
|-
|Pre-Receipt Sort (Bespoke)
|Allow Pre-Receipt Sortation (Bespoke)
|-
|Blind Receipt (Bespoke)
|Allow pallets to be received and putaway at the same time (Bespoke)
|-
|Blind Return (Bespoke)
|Allow pallets to be returned and putaway at the same time (Bespoke)
|-
|Enable RDT Stock Adjustment
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|-
|Ad Hoc Stock Move
|Allow Ad Hoc Stock Movements via RF
|-
|Enable Stock Transfers
|Allow completion of Stock Transfer tasks
|-
|Enable Packing
|Allow the RDT user to pack orders
|-
|Enable Stock Putaway
|Allow the RDT user to Stock Putaway
|-
|Ad Hoc Location Move
|Allow Ad Hoc Location Movements via RF
|-
|Update CPID
|Allow the user to update the customer pallet id value. Bespoke
|-
|Picking Container Adjustment
|Allow the user to adjust Picking Containers. Bespoke
|}

The Admin items that can be set up (and their descriptions) are:
{| class="wikitable 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.
|-
|OBS Menu
|Controls access to the OBS Support 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="wikitable 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.
|-
|WMS System
|Version of WMS that the WCS is connecting to.
|}

If the system is connecting using socket connections, the following details can be modified:
{| class="wikitable 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 (??)
|-
|Connection Logging
|Level of logging for System Connections (OBS USE ONLY)
|}

If the system being linked to is using Oracle Advanced Queues, the following options will be available:
{| class="wikitable 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.
|-
|Ora Priority Incoming Queue
|The Oracle queue on which high priority messages are stored.
|}

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="wikitable 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.

|}

There are also settings for the RDT client. These settings are:
{| class="wikitable"
!Name
!Description
|-
|RDT Wait Time
|This is the amount of time that the RDT application will wait before re-trying communications to the WCS.
|-
|RDT Box Drawing
|What style of box-drawing the RDT's connected to this WCS will use.
|-
|RDT Logging
|Whether the RDT's connected to this system log messages sent to and received from the server, for diagnostic purposes.
|-
|RDT Non Fatal Retry Count
|When the RDT application encounters a non-fatal Wavelink error this number specifies how many times it will retry before bombing out. A value set too low could result in application failures where they would normally be recoverable. CHANGE WITH CAUTION.
|}

==== 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="wikitable 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.
|-
|OBS Menu
|Controls access to the OBS Support Menu
|}

=== Bespoke ===
This is bespoke functionality and should only be enabled by your Aptean system implementation team.
{| class="wikitable prettytable"
! <center>Rule</center>
! <center>Description</center>

|-
| Regroup Order by Stock
| Allow WCS Maintenance users to re-group an order's picks by the number of stock picks on the order, then by location.
|-
|Dummy Loc Enq Location
|Controls whether the WCS sends a dummy location enquiry to the WMS
|-
|Dummy Loc Enq Duration
|Sets the duration of time in minutes without a message before a dummy location enquiry is sent to the WMS. Default is 30 min.
|-
|Dummy Loc Timer Duration
|Sets the duration of time for the dummy location check in minutes. Default is every 2 min.
|-
|Dummy Loc Trigger
|Controls the trigger checks of the dummy location enquiry to the WMS. Default is Incoming only.
|-
|Priority Change Audit
|Controls whether an Exceptions record is created to capture when a user changes the priority of a task
|}
=== 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="wikitable 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="wikitable 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="wikitable 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.
|-
|Enable RDT Measure Qty
|Allow Measure Quantity to be entered on the RDT
|-
|Enable RDT Weights
|Allow Weight to be entered on the RDT
|-
|Enable Multi UOM processing
|Whether the WCS deals with multiple UOMs
|-
|Pallet Enquiry Print Labels
|Controls if pallet label can be printed from a pallet enquiry
|-
|Pallet Enquiry Label Format
|Format of pallet enquiry label
|-
|Vendor Managed Inventory
|If this flag is enabled, supplier will be displayed and entered during standard rf modules
|-
|Display UOM
|Display UOM on RDT when user prompted to enter a quantity value.
|-
|Zero Negative Quantities
|Zero negative values on enquiries. Default Enabled
|}
=== 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="wikitable 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.
|-
|Enable RDT Part Replenishments
|Allow completion of Part Replenishment tasks
|-
|Enable RDT Stock Adjustment
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|-
|Trolley IDs
|Allow loading of orders into trolleys
|-
|Pre-Receipt Sort (Bespoke)
|Allow Pre-Receipt Sortation (Bespoke)
|-
|Blind Receipt (Bespoke)
|Allow pallets to be received and putaway at the same time (Bespoke)
|-
|Blind Return (Bespoke)
|Allow pallets to be returned and putaway at the same time (Bespoke)
|-
|Ad Hoc Stock Move
|Allow Ad Hoc Stock Movements via RF
|-
|Enable Stock Transfers
|Allow completion of Stock Transfer tasks
|-
|Enable Packing
|Allow the RDT user to pack orders
|-
|Enable Stock Putaway
|Allow the RDT user to Stock Putaway
|-
|Ad Hoc Location Move
|Allow Ad Hoc Location Movements via RF
|-
|Update CPID
|Allow the user to update the customer pallet id value. Bespoke
|-
|Picking Container Adjustment
|Allow the user to adjust Picking Containers. Bespoke
|}
=== Receipt ===
The parameters on this tab control how receipt works on the RDT.
{| class="wikitable 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.
|-
|Cross Docking
|Is cross-docking enabled for this operation?
|-
|Enter Delivery Reference
|Allow the user to enter a delivery reference in RDT Goods Receipt.
|-
|Change Damage Qty
|If Damaged Pallet Receipt is allowed, is the quantity allowed to be changed from the full pallet quantity? Note: This functionality is supported in the Oracle WMS only.
|-
|Enter Putaway Location
|Allow users to receive and putaway items in a single process
|-
|Receipt Expected Quantity Check
|If enabled, this parameter makes the RDT compare the received quantity entered with the expected quantity pre-advised
|-
|Generate Customer Pallet Id
|If enabled, this rule allows users to determine whether the WMS generates a customer pallet id value.
|-
|Weight Volume Check
|Check stock dimensions and weight are populated during Goods Receipt.
|-
|Enter Vintage
|Controls whether the Goods Receipt module prompts for a vintage value
|-
|Redundant Stock Check
|If enabled, products marked as redundant are rejected when scanned at receipt
|-
|Temperature Recording
|Controls whether Temperature Recording is required at Pre-Advice
|-
|Receipt Intake Stock Check
|Controls Issue Life Check at Receipt
|-
|Allow Receipt Detail Backout
|Controls whether user can back out of Receipt Detail
|-
|Latest Sell By Date Check
|Controls whether input of SellByDate is checked against latest date
|-
|Minimum Pallet ID Length
|Controls the minimum length of SSCC entered in Receipt
|-
|Customer Pallet Validation
|Controls whether an enquiry message is sent to the WMS to validate if a customer pallet value can be received
|-
|Goods Receipt Vehicle Checks
|Controls whether an enquiry message is sent to the WMS to validate if a GRN has been Vehicle Checked
|-
|Capture EAN
|Controls whether users are allowed to enter EAN values for a stock code
|-
|Blind Receipt Data Format
|Controls what the RDT displays in the Blind Receipt/Return modules when displaying the pallet details
|-
|Capture Original SSCC
|Controls whether the Goods Receipt module prompts the user to enter the original SSCC value when generating a new SSCC value.
|}
=== Putaway ===
The parameters on this tab control how putaway works on the RDT.
{| class="wikitable 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
|-
|Print Part Replen Labels
|Whether the RDT attempts to print labels for Part Replenishments
|-
|Part Replen Label Format
|Format of the Part Replen label
|-
|Display Ad Hoc Putaway Locations
|If enabled, this parameter ensures a location enquiry is sent to the WMS from Ad Hoc Putaway to find location assigned to the stock code
|-
|Print Ad Hoc Putaway Labels
|Whether the RDT attempts to print labels for Ad Hoc Putaways
|-
|Ad Hoc Putaway Label Format
|Format of the Ad Hoc Putaway label
|-
|Ad Hoc Putaway Case Scan
|Controls whether the Ad Hoc Putaway module requires case scanning or accepts quantity entry
|-
|Print Ad Hoc Stock Move Labels
|Controls whether the Ad Hoc Stock Move module prompts the user to print a label
|-
|Ad Hoc Stock Move Label Format
|Format of the Ad Hoc Stock Move Label
|-
|Select Stock Move by Stock
|Allow selection of stock moves by Stock before Pallet
|-
|Default Ad Hoc Pallet Move Reason
|Controls the default reason code value for use with the Ad Hoc Pallet Move module
|-
|Multiple Putaway Tasks Prompt
|Controls whether the RDT prompts the user to complete one or all of the putaway tasks when multiple putaway tasks exist for the customer pallet id
|-
|Ad Hoc Pallet Move Reason Prompt
|Controls whether a reason code value is prompted within the Ad Hoc Pallet Move module
|-
|Ad Hoc Pallet Move Change Pallet Type
|Controls whether the user is allowed to change the pallet type within the Ad Hoc Pallet Move module
|-
|Ad Hoc Pallet Move Suggest Location
|Controls whether the WCS request a suggested location from the WMS within the Ad Hoc Pallet Move module
|}
=== 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="wikitable 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
|-
|Log Postponement
|Whether pick postponements are recorded in the Exceptions Log
|-
|Pick for On-time Delivery
|If enabled, this rule will ensure that picks are assigned to pickers in Priority, then OTD Date and Time sequence
|-
|Split Pick Quantities
|If enabled, allows large picks to be split into more than one pack
|-
|Pick Multiple Containers
|If enabled, allows creation of several containers in sequence
|-
|Num Picks before RSBE
|The number of picks to elapse between residual stock balance enquiries
|-
|Choose Marshalling Location
|Allow the pickers to choose a marshalling location when taking a picked pallet to marshalling
|-
|Cherry Picking Selection Type
|Controls how Cherry Picked tasks are assigned to users
|-
|Default Short Pick Reason
|Default reason code for short and zero picks (Bespoke)
|-
|Force Source Confirmation
|Force the confirmation of the source picking location for each pick even if it is the same as the previous pick.
|-
|Full Pick Despatch Labels
|If disabled, Despatch labels will not be printed for full pallet picks.
|-
|Authorise Pick Shortage
|When enabled, this rule will ensure that, when part picks are cancelled or otherwise have their quantity changed, the user will be forced to obtain supervisor authorisation before continuing.
|-
|Calculate Packs
|If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks
|-
|Enhanced Pick Exchange
|Allow pick exchanges from different locations and for part pallet pick tasks
|-
|Add Miscellaneous Charges
|Allow users to add miscellaneous charges to orders
|-
|Shipment Pallet Build Validation
|Controls what validation is followed when assigning shipment packages onto shipment pallets
|-
|Always Display Order
|If enabled, the full pick screen will always display order number rather than route/load
|-
|Combined Part Pick Sequence
|Controls whether full pallet picks are assigned to the RDT before part pallet picks when using the Part Picking module
|-
|Additional Pick Sequence
|Controls whether additional conditions are required for sequencing pick tasks
|-
|Marshalling Method
|Controls whether orders are to be marshalled or not
|-
|Additional Pick Instructions
|Controls whether RDT users can view the additional pick instructions
|-
|Print Stock Despatch Label
|Controls whether the Part Picking module allows stock level despatch labels to be produced
|-
|WCS Stock Despatch Label Format
|Format of the stock despatch label
|-
|Single Picker Per Order
|Assign related picks to user on first pick. Default Disabled
|-
|Pick Catch Weight Per Case
|Controls whether Catch Weights are entered at Case instead of Stock/Pick level. Default Disabled.
|-
|Check Duplicate Serial Numbers
|Controls whether Duplicate serials are checked during Pick. Default Disabled.
|-
|Pick By Order
|Controls whether a picker is locked to task for a single order
|-
|Full Pallet Task Exchange
|Controls whether Full Pallet TASK exchange is allowed between orders
|-
|Use WMS Pick Sequence
|Controls whether pick tasks are assigned to a picker in WMS location pick sequence order
|-
|Display Multi UOM
|Controls the display of Multiple UOM Descriptions when entering Pick Quantity
|-
|Largest Task Next Sequence
|Set the sequence of picks after selection by Largest Qty
|-
|Check EAN on Case Serial
|Controls whether an error is issued if an EAN barcode is scanned as a serial number
|-
|Serial Minimum Length
|Controls the minimum length of a scanned case serial number in Picking. Default 0 (disabled)
|-
|Serial Maximum Length
|Controls the maximum length of a scanned case serial number in Picking. Default 0 (disabled)
|-
|Default Pick Exchange Reason
|Controls the default reason code value for use with pick exchanges
|-
|Enter Despatch Pallet Type
|Controls whether pickers are prompted to enter the pallet being picked or picked onto
|-
|Part Pick Pallet Count
|Controls whether Part Picking prompts users to enter a pallet count
|}
=== Dual Cycling ===
This section controls how the RDT is allocated DC tasks, and how the RDT responds to the user requests.
{| class="wikitable 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.
|-
|Multi-Pallet WADC
|Determines whether the WADC modules allow multiple pallets to be picked at the same time
|-
|Multi-Pallet Picking Sequence
|Controls whether the first pallet picked or last pallet picked via WA Dual Cycling is taken to marshalling first
|}
=== 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.
{| class="wikitable prettytable"
! <center>Name</center>
! <center>Description</center>

|-
| Default Receiving Location
| Default Receiving Location. If entered, the RDT Receipt Module allows the user to choose a receiving location, which defaults to this parameter.
|-
|Default Receiving Location CD
|Default Receiving Location Check Digits
|-
|Default Receiving Location Type
|Default Receiving Location Type
|-
|Conveyor Input Spur
|Bespoke: Conveyor Input Spur Location. Required for RDT Reject Spur Processing
|-
|Conveyor Input Spur CD
|Bespoke: Conveyor Input Spur Check Digits. Required for RDT Reject Spur Processing
|-
|Conveyor Input Spur Type
|Bespoke: Conveyor Input Spur Type. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur
|Bespoke: Conveyor Reject Spur Location. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur CD
|Bespoke: Conveyor Reject Spur Check Digits. Required for RDT Reject Spur Processing
|-
|Conveyor Reject Spur Type
|Bespoke: Conveyor Reject Spur Type. Required for RDT Reject Spur Processing
|-
|Default Putaway Location
|
|-
|Default Putaway Location CD
|
|-
|Default Putaway Location Type
|
|-
|Default Problem Resolution Location
|
|-
|Default Problem Resolution Location CD
|
|-
|Default Problem Resolution Location Type
|
|}

=== 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="wikitable 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
|-
|Force Default Manu Date
|Bespoke: If this rule is enabled and manufacture dates are required at goods receipt, the RDT will not prompt for this but will instead default the value to the current date.
|-
|New Stock Take Message Layout
|BESPOKE: Changes the Stock Take message to WMS to a different extended format. USE WITH CAUTION
|-
|Pre-Reposition
|Bespoke: Pre-reposition all pending putaways for a stock code when a pallet of the same stock is repositioned
|-
|Display PO Number
|Display the PO Number associated with the pick
|-
|Blind Receipt Label (Bespoke)
|RDT label for the Blind Receipt module (Bespoke)
|-
|Blind Return Label (Bespoke)
|RDT label for the Blind Returns module (Bespoke)
|-
|Maximum Putaway Quantity
|Maximum quantity allowed to be received and putaway by UPC code (Bespoke)
|-
|BHS Short Picking
|Bespoke:short picking mechanism that automatically creates a replacement pick
|-
|Goods Receipt Lookup
|Allow Goods Receipt lookup in RDT Goods Receipt
|-
|Split Tote
|Allow the user to choose to split a picked line over several totes.
|-
|Stock Take Batch Check
|When checking pallets during Stock Take, request the user to check the customer batch value
|-
|Stock Take Sell By Date Check
|When checking pallets during Stock Take, request the user to check the sell by date value
|-
|Display Default Receipt Values
|Controls whether the RDT displays the pallet details of the previous pallet as the default values of the pallet being received
|-
|RF Use Estimated Pallets
|If enabled, then the new estimated pallets message will be sent to the Calidus-3pl Mobile system
|-
|Tote to Carton Standardise
|If enabled, the RDT screens will be amended to display Carton in place of Tote
|-
|Duration Measurement
|Controls whether the duration value is sent to the WMS in seconds or minutes
|-
|Multi Stage Confirmation Message
|Controls whether confirmation messages are sent to the WMS for multi stage tasks
|-
|Loose Item Serial Number
|Controls whether serial number entry is required when picking loose cases and units
|-
|Confirm Take To Marshalling
|Bespoke: Require Confirmation before Take To Marshalling
|-
|Buk PI By
|Bespoke: Perform Bulk PI by Task Identifier or Stock/Sell-By-Date. Default is Task Identifier
|-
|Write RPM Logs
|Bespoke: Write RPM record to Error Log. Default Disabled
|-
|GS1-128 Scan Sequence
|Bespoke: Determines preferred sequence of fields on GS1-128 Scan
|-
|Split Face Sequence
|Controls the sort sequence when Split Faces enabled
|-
|Ad Hoc Stock Move Multi Action
|Controls what additional information is required for the Ad Hoc Stock Move functionality to identify individual pallets. Default Error.
|-
|Select Move Allow Held
|Allow Select Move Function to include Held Movements
|-
|Pallet Case Label Threshold
|Controls whether receipt labels are produced at pallet level or case level based on quantity
|-
|Original Priority Audit
|Controls whether an Exceptions record is created to capture the original priority of the pick / movement task
|-
|Update CPID Print Labels
|Controls if a pallet label can be printed from the Update CPID module
|-
|Update CPID Label Format
|Format of Update CPID Label
|}
=== 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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

== 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="wikitable 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
| NOPASSWORD
|-
|Ad Hoc Deconsolidation
|WHSE, OWNER
|Are deconsolidation tasks sequenced manually or by the system?
|01
|N
|-
|Ad Hoc Location Move
|WHSE, OWNER
|Allow Ad Hoc Location Movements via RF
|02
|N
|-
|Ad Hoc Pallet Move Change Pallet Type
|WHSE, OWNER
|Controls whether the user is allowed to change the pallet type within the Ad Hoc Pallet Move module
|01
|N
|-
|Ad Hoc Pallet Move Reason Prompt
|WHSE, OWNER
|Controls whether a reason code value is prompted within the Ad Hoc Pallet Move module
|01
|Y
|-
|Ad Hoc Pallet Move Suggest Location
|WHSE, OWNER
|Controls whether the WCS request a suggested location from the WMS within the Ad Hoc Pallet Move module
|01
|N
|-
|Ad Hoc Putaway Case Scan
|WHSE, OWNER
|Controls whether the Ad Hoc Putaway module requires case scanning or accepts quantity entry
|01
|Y
|-
|Ad Hoc Putaway Label Format
|WHSE, OWNER
|Format of the Ad Hoc Putaway label
|25
|
|-
|Ad Hoc Stock Move
|WHSE, OWNER, GRP
|Allow Ad Hoc Stock Movements via RF
|02
|N
|-
|Ad Hoc Stock Move Label Format
|WHSE, OWNER
|Format of the Ad Hoc Stock Move Label
|25
|
|-
|Ad Hoc Stock Move Multi Action
|WHSE, OWNER
|Controls what additional information is required for the Ad Hoc Stock Move functionality to identify individual pallets. Default Error.
|76
|E
|-
|Add Miscellaneous Charges
|WHSE, OWNER
|Allow users to add miscellaneous charges to orders
|01
|N
|-
|Additional Pick Instructions
|WHSE, OWNER
|Controls whether RDT users can view the additional pick instructions
|67
|N
|-
|Additional Pick Sequence
|WHSE, OWNER
|Controls whether additional conditions are required for sequencing pick tasks
|9003
|B
|-
|Aisle Length
|WHSE, OWNER
|The length of the Aisle portion of the Location code.
|33
|2
|-
|Allow Exchange of Replens
|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 Receipt Detail Backout
|WHSE, OWNER
|Controls whether user can back out of Receipt Detail
|01
|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
|-
|Always Deconsolidate
|WHSE, OWNER
|When enabled, the system will always deconsolidate, even when not strictly necessary (i.e. for single orders)
|55
|N
|-
|Always Display Order
|WHSE, OWNER
|If enabled, the full pick screen will always display order number rather than route/load
|01
|N
|-
|Authorise Pick Shortage
|WHSE, OWNER
|When enabled, this rule will ensure that, when part picks are cancelled or otherwise have their quantity changed, the user will be forced to obtain supervisor authorisation before continuing.
|01
|N
|-
|Automatic Despatch
|WHSE, OWNER
|Automatically despatch confirm an order when it has been deconsolidated
|01
|N
|-
|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
|
|-
|BHS Short Picking
|WHSE, OWNER
|Bespoke:short picking mechanism that automatically creates a replacement pick
|01
|N
|-
|Blind Deconsolidation
|WHSE, OWNER
|When enabled, the user will be prompted to deconsolidate blind
|55
|N
|-
|Blind Receipt (Bespoke)
|WHSE, OWNER, GRP
|Allow pallets to be received and putaway at the same time (Bespoke)
|01
|N
|-
|Blind Receipt Data Format
|WHSE, OWNER
|Controls what the RDT displays in the Blind Receipt/Return modules when displaying the pallet details
|82
|Q
|-
|Blind Receipt Label (Bespoke)
|WHSE, OWNER
|RDT label for the Blind Receipt module (Bespoke)
|49
|B
|-
|Blind Return (Bespoke)
|WHSE, OWNER, GRP
|Allow pallets to be returned and putaway at the same time (Bespoke)
|01
|N
|-
|Blind Return Label (Bespoke)
|WHSE, OWNER
|RDT label for the Blind Returns module (Bespoke)
|49
|B
|-
|Block Stack
|WHSE, OWNER
|Enables some RDT functions to exchange pallets
|01
|N
|-
|Buk PI By
|WHSE, OWNER
|Bespoke: Perform Bulk PI by Task Identifier or Stock/Sell-By-Date. Default is Task Identifier
|69
|I
|-
|Calculate Packs
|WHSE, OWNER
|If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks
|61
|N
|-
|Capture EAN
|WHSE, OWNER
|Controls whether users are allowed to enter EAN values for a stock code
|01
|N
|-
|Capture Original SSCC
|WHSE, OWNER
|Controls whether the Goods Receipt module prompts the user to enter the original SSCC value when generating a new SSCC value.
|01
|N
|-
|Change Damage Qty
|WHSE, OWNER
|If Damaged Pallet Receipt is allowed, is the quantity allowed to be changed from the full pallet quantity? Note: This functionality is supported in the Oracle WMS only.
|01
|Y
|-
|Check Duplicate Serial Numbers
|WHSE, OWNER
|Controls whether Duplicate serials are checked during Pick. Default Disabled.
|74
|N
|-
|Check EAN on Case Serial
|WHSE, OWNER
|Controls whether an error is issued if an EAN barcode is scanned as a serial number
|01
|N
|-
|Cherry Picking Selection Type
|WHSE, OWNER
|Controls how Cherry Picked tasks are assigned to users
|51
|R
|-
|Choose Deconsolidation
|WHSE, OWNER
|Allow the RDT user to choose which Marshalling lane to deconsolidate from
|01
|N
|-
|Choose Marshalling Location
|WHSE, OWNER
|Allow the pickers to choose a marshalling location when taking a picked pallet to marshalling
|65
|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
|-
|Combined Part Pick Sequence
|WHSE, OWNER
|Controls whether full pallet picks are assigned to the RDT before part pallet picks when using the Part Picking module
|64
|M
|-
|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
|-
|Confirm Take To Marshalling
|WHSE, OWNER
|Bespoke: Require Confirmation before Take To Marshalling
|01
|N
|-
|Connection Logging
|SYS
|Level of logging for System Connections (OBS USE ONLY)
|80
|D
|-
|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
|
|-
|Cross Docking
|WHSE, OWNER
|Is cross-docking enabled for this operation?
|01
|N
|-
|Customer Pallet Validation
|WHSE, OWNER
|Controls whether an enquiry message is sent to the WMS to validate if a customer pallet value can be received
|01
|N
|-
|Decon Exceptions
|WHSE, OWNER
|If enabled, this will allow supervisors to immediately resolve discrepancies found at Deconsolidation
|01
|N
|-
|Deconsolidation Logging Level
|WHSE, OWNER
|This rule indicates the detail level of Deconsolidation activity logging
|48
|D
|-
|Deconsolidation Method
|WHSE, OWNER
|Whether Deconsolidation tasks are processed by the WCS
|31
|N
|-
|Deconsolidation Pack ID
|WHSE, OWNER
|This rule indicates which pack size identification field is displayed during deconsolidation
|46
|C
|-
|Deconsolidation Stock ID
|WHSE, OWNER
|This rule indicates which stock identification fields are displayed during deconsolidation
|45
|C
|-
|Default Ad Hoc Pallet Move Reason
|WHSE, OWNER
|Controls the default reason code value for use with the Ad Hoc Pallet Move module
|53
|
|-
|Default Company Code
|SYS
|This is the default company code that the RDT will log on to.
|03
|
|-
|Default Pack Type
|WHSE, OWNER
|Default Pack Type for Pick
|9007
|STD
|-
|Default Pick Exchange Reason
|WHSE, OWNER
|Controls the default reason code value for use with pick exchanges
|53
|
|-
|Default Problem Resolution Location
|WHSE, OWNER
|
|03
|
|-
|Default Problem Resolution Location CD
|WHSE, OWNER
|
|03
|
|-
|Default Problem Resolution Location Type
|WHSE, OWNER
|
|28
|
|-
|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
|
|-
|Default Short Pick Reason
|WHSE, OWNER
|Default reason code for short and zero picks (Bespoke)
|53
|
|-
|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
|-
|Despatch Label Format
|WHSE, OWNER
|Format of the despatch label
|25
|
|-
|Despatch Note Printer
|WHSE, OWNER
|Where the Despatch Note Printer is defined
|47
|M
|-
|Display Ad Hoc Putaway Locations
|WHSE, OWNER
|If enabled, this parameter ensures a location enquiry is sent to the WMS from Ad Hoc Putaway to find locations assigned to the stock code
|02
|N
|-
|Display Decon Summary
|WHSE, OWNER
|This rule controls whether the deconsolidation process displays a summary screen with Order Information at the start of deconsolidating each order
|01
|Y
|-
|Display Default Receipt Values
|WHSE, OWNER
|Controls whether the RDT displays the pallet details of the previous pallet as the default values of the pallet being received
|01
|N
|-
|Display Multi UOM
|WHSE, OWNER
|Controls the display of Multiple UOM Descriptions when entering Pick Quantity
|01
|N
|-
|Display Order Summary
|WHSE, OWNER
|Defines when the order summary screen is displayed on the RDT during part picking.
|42
|S
|-
|Display PO Number
|WHSE, OWNER
|Display the PO Number associated with the pick
|01
|N
|-
|Display UOM
|WHSE
|Display UOM on RDT when user prompted to enter a quantity value.
|01
|N
|-
|Dummy Loc Enq Duration
|SYS
|Sets the duration of time in minutes without a message before a dummy location enquiry is sent to the WMS. Default is 30 min.
|04
|30
|-
|Dummy Loc Timer Duration
|SYS
|Sets the duration of time for the dummy location check in minutes. Default is every 2 min.
|04
|2
|-
|Dummy Loc Trigger
|SYS
|Controls the trigger checks of the dummy location enquiry to the WMS. Default is Incoming only.
|70
|I
|-
|Duration Measurement
|WHSE, OWNER
|Controls whether the duration value is sent to the WMS in seconds or minutes
|66
|M
|-
|Enable Admin Change Warehouse
|SYS, GRP
|Allows the user to change the default warehouse they can see
|01
|N
|-
|Enable Admin 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
|-
|Enable Admin Comms Enquiry
|SYS, GRP
|Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.
|01
|N
|-
|Enable Admin Logs
|SYS, GRP
|Allows the user access to the Logs Enquiry screens in the System Tools menu
|01
|N
|-
|Enable Admin Report
|SYS, GRP
|Allows the user access to the Reports menu
|01
|N
|-
|Enable Admin Settings System
|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
|-
|Enable Admin 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
|-
|Enable Admin Standing Data Enquiry
|SYS, GRP
|Allows the user access to the Enquiry screens only on the Standing Data menu
|01
|N
|-
|Enable Admin 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
|-
|Enable Admin Task Enquiry
|SYS, GRP
|Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.
|01
|N
|-
|Enable Admin Utilities Clear Out
|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
|-
|Enable Admin Utilities Repair and Compact
|SYS, GRP
|Allows the user access to the Compact Database option on the System Tools menu.
|01
|N
|-
|Enable Check Digits
|WHSE, OWNER
|Does the warehouse use check digits, or just location codes?
|11
|Y
|-
|Enable 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
|-
|Enable Encoded Sell By Date
|WHSE, OWNER
|Use encoded sell by dates?
|01
|N
|-
|Enable Full Pick Header Lock
|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
|-
|Enable Mixed Stock
|WHSE, OWNER
|Do you have mixed-stock pallets?
|01
|N
|-
|Enable Multi Pallet Putaway
|WHSE, OWNER
|Allow several pallets to be picked up during putaway
|02
|N
|-
|Enable 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
|-
|Enable Packing
|WHSE, OWNER, GRP
|Allow the RDT user to pack orders
|02
|N
|-
|Enable Pick Dependencies
|WHSE, OWNER
|Ensure part picks are not released for picking until any outstanding replenishment has been completed first
|01
|Y
|-
|Enable Picker Replens
|WHSE, OWNER
|Allow pickers to perform their own replens at the point of picking the part picks.
|02
|N
|-
|Enable RDT Ad Hoc Move
|WHSE, OWNER, GRP
|Allow instigation of a housekeeping Move from the RDT.
|02
|Y
|-
|Enable RDT Ad Hoc Putaway
|WHSE, OWNER, GRP
|Allow Ad Hoc Putaway for shelving locations. Bespoke.
|02
|N
|-
|Enable RDT Bulk PI
|WHSE, OWNER, GRP
|Allow Perpetual Inventory (ad hoc stock check).
|02
|Y
|-
|Enable 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
|-
|Enable RDT Combined Split
|WHSE, OWNER, GRP
|Bespoke: Ad hoc movements of small quantities of stock to other locations
|02
|N
|-
|Enable RDT 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).
|52
|Y
|-
|Enable RDT Daily Cycle Check
|WHSE, OWNER, GRP
|The Daily Cycle Check functionality will be available to the users if this rule is enabled
|02
|N
|-
|Enable RDT Damages
|WHSE, OWNER, GRP
|Allow Damage quantity entry during Goods Receipt
|01
|N
|-
|Enable RDT DC Aisles
|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
|-
|Enable RDT Deconsolidation
|WHSE, OWNER, GRP
|Allow deconsolidation of consolidated orders.
|02
|N
|-
|Enable RDT Despatch
|WHSE, OWNER, GRP
|Allow despatch of deconsolidated orders.
|02
|N
|-
|Enable RDT Despatch Serial No Scanning
|WHSE, OWNER, GRP
|Allow entering serial numbers for picked items. Bespoke.
|02
|N
|-
|Enable RDT Echo Putaway
|WHSE, OWNER
|If enabled, this parameter makes the RDT Receiving process display the suggested putaway location after successfully receiving a pallet.
|19
|0
|-
|Enable RDT Eurodate
|WHSE, OWNER
|Bespoke: Enter Eurodate rather than Manufacture Date
|01
|N
|-
|Enable RDT Layers
|WHSE, OWNER
|Enter Layers and Bits at Goods Receipt
|01
|N
|-
|Enable RDT Loading
|WHSE, OWNER, GRP
|Allow Loading ojnto a vehicle.
|02
|N
|-
|Enable RDT Location Enquiry
|WHSE, OWNER, GRP
|Allow the RDT user to enquire on the contents of a location from the WMS.
|02
|Y
|-
|Enable RDT Mail
|WHSE, OWNER, GRP
|Allow receipt of messages from Maintenance administrators. (Generally, this should always be enabled).
|02
|Y
|-
|Enable RDT Marshall
|WHSE, OWNER, GRP
|Not Yet Implemented.
|02
|N
|-
|Enable RDT Measure Qty
|WHSE, OWNER
|Allow Measure Quantity to be entered on the RDT
|01
|N
|-
|Enable RDT Move Enquiry
|WHSE, OWNER, GRP
|Allow the RDT to see where a pallet is going.
|02
|Y
|-
|Enable RDT Move Select
|WHSE, OWNER, GRP
|Allow cherry-picking of an individual Move task.
|02
|Y
|-
|Enable RDT Pallet Enquiry
|WHSE, OWNER, GRP
|Allow the RDT user to enquire on the contents of a pallet from the WMS.
|02
|Y
|-
|Enable RDT Pallet Move
|WHSE, OWNER, GRP
|Allow the user to complete Full-Pallet Movements generated from the WMS.
|02
|Y
|-
|Enable RDT Part Picking
|WHSE, OWNER, GRP
|Allow the user to complete Case and Unit picks from the RDT.
|02
|Y
|-
|Enable RDT Part Replenishments
|WHSE, OWNER, GRP
|Allow completion of Part Replenishment tasks
|02
|N
|-
|Enable RDT Pick Extra Items
|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
|-
|Enable RDT Pick Location Error
|WHSE, OWNER, GRP
|Allow the RDT picker to cancel a pick at the point of confirming the location code.
|02
|N
|-
|Enable RDT Picking
|WHSE, OWNER, GRP
|Allow the user to complete Full-pallet Picks.
|02
|Y
|-
|Enable RDT Pop Up Description
|WHSE, OWNER
|Pop up description of stock on RDT screen
|38
|N
|-
|Enable RDT Putaway
|WHSE, OWNER, GRP
|Allow Full-Pallet Putaway.
|02
|Y
|-
|Enable RDT Receipt
|WHSE, OWNER, GRP
|Allow Blind (Stock level) and Check (Pallet level) Goods Receipt.
|02
|Y
|-
|Enable RDT Receipt Serial No Scanning
|WHSE, OWNER, GRP
|Allow entering serial numbers for received items. Bespoke.
|02
|N
|-
|Enable RDT Receive Additional Pallets
|WHSE, OWNER, GRP
|Allow additional pallets to be received during the RDT receipt process
|02
|Y
|-
|Enable RDT Reject Spur
|WHSE, OWNER, GRP
|Allow Reject Spur Processing. Bespoke to automated conveyor and P&D systems. Bespoke.
|02
|N
|-
|Enable RDT Replenishment
|WHSE, OWNER, GRP
|Allow completion (and/or generation) of a Replenishment. Bespoke.
|02
|N
|-
|Enable RDT Reposition
|WHSE, OWNER, GRP
|Allow reposition on the RDTs? This option can be over-ridden by the Group setting
|57
|N
|-
|Enable RDT Select Replenishment
|WHSE, OWNER, GRP
|Allow Select Replenishment. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Building
|WHSE, OWNER, GRP
|Allow Shipment Pallet Building. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Despatch
|WHSE, OWNER, GRP
|Allow Shipment Pallet Despatch. Bespoke.
|02
|N
|-
|Enable RDT Shipment Pallet Moves
|WHSE, OWNER, GRP
|Allow Shipment Pallet Moves. Bespoke.
|02
|N
|-
|Enable RDT Stock Adjustment
|WHSE, OWNER, GRP
|Enable RDT users to perform Adhoc adjustments (ORA Only)
|02
|N
|-
|Enable RDT Stock Enquiry
|WHSE, OWNER, GRP
|Bespoke: Enquire on Stock code
|02
|N
|-
|Enable RDT Stock Move
|WHSE, OWNER, GRP
|Allow Stock Moves (request replenishment of pick face). Bespoke.
|02
|N
|-
|Enable RDT Stock Take
|WHSE, OWNER, GRP
|Allow Full (Blind) and Partial (Check) Stock Check.
|02
|Y
|-
|Enable RDT Weighing
|WHSE, OWNER, GRP
|Allow the RDT user to Weight Shipment Packages.
|02
|N
|-
|Enable RDT Weights
|WHSE, OWNER, GRP
|Allow Weight to be entered on the RDT
|58
|N
|-
|Enable Replen Dependencies
|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
|-
|Enable Stock Putaway
|WHSE, OWNER, GRP
|Allow the RDT user to Stock Putaway
|02
|N
|-
|Enable Stock Transfers
|WHSE, OWNER, GRP
|Allow completion of Stock Transfer tasks
|02
|N
|-
|Enable WCS Gen Replen
|WHSE, OWNER
|Let WCS Generate Replenishments
|01
|Y
|-
|Enhanced Pick Exchange
|WHSE, OWNER
|Allow pick exchanges from different locations and for part pallet pick tasks
|01
|Y
|-
|Enter CIM Printer
|WHSE, OWNER
|Controls whether the RDT prompts the user to enter a printer during deconsolidation on which the CIM labels will be printed
|55
|N
|-
|Enter Delivery Reference
|WHSE, OWNER
|Allow the user to enter a delivery reference in RDT Goods Receipt.
|01
|N
|-
|Enter Despatch Pallet Type
|WHSE, OWNER
|Controls whether pickers are prompted to enter the pallet being picked or picked onto
|83
|D
|-
|Enter Despatch Printer
|WHSE, OWNER
|Controls whether the RDT prompts the user to enter a printer during deconsolidation on which the despatch note will be printed
|55
|N
|-
|Enter Media Type
|WHSE, OWNER
|When enabled, the user will be prompted to enter a media type for the final media
|55
|N
|-
|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 Putaway Location
|WHSE, OWNER
|Allow users to receive and putaway items in a single process
|72
|N
|-
|Enter Vintage
|WHSE, OWNER
|Controls whether the Goods Receipt module prompts for a vintage value
|02
|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 Default Manu Date
|WHSE, OWNER
|Bespoke: If this rule is enabled and manufacture dates are required at goods receipt, the RDT will not prompt for this but will instead default the value to the current date.
|01
|N
|-
|Force Sky Picking
|WHSE, OWNER
|Are part pick tasks from bulk treated as sky picks?
|59
|N
|-
|Force Source Confirmation
|WHSE, OWNER
|Force the confirmation of the source picking location for each pick even if it is the same as the previous pick.
|01
|N
|-
|Full Pallet Task Exchange
|WHSE, OWNER
|Controls whether Full Pallet TASK exchange is allowed between orders
|78
|S
|-
|Full Pick Despatch Labels
|WHSE, OWNER
|If disabled, Despatch labels will not be printed for full pallet picks.
|01
|Y
|-
|Generate Customer Pallet Id
|WHSE, OWNER
|If enabled, this rule allows users to determine whether the WMS generates a customer pallet id value.
|01
|N
|-
|Goods Receipt Lookup
|WHSE, OWNER
|Allow Goods Receipt lookup in RDT Goods Receipt
|01
|N
|-
|Goods Receipt Vehicle Checks
|WHSE, OWNER
|Controls whether an enquiry message is sent to the WMS to validate if a GRN has been Vehicle Checked
|01
|N
|-
|GS1-128 Scan Sequence
|WHSE, OWNER
|Bespoke: Determines preferred sequence of fields on GS1-128 Scan
|71
|00
|-
|In Pick Check
|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.
|54
|N
|-
|Largest Task Next Sequence
|WHSE, OWNER
|Set the sequence of picks after selection by Largest Qty
|79
|N
|-
|Latest Sell By Date Check
|WHSE, OWNER
|Controls whether input of SellByDate is checked against latest date
|73
|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 Despatch Note Printer
|WHSE, OWNER
|Controls whether the Loading module prompts for a printer for the despatch note
|01
|N
|-
|Loading Dock Door
|WHSE, OWNER
|Controls whether the Loading user is prompted for Dock Door and how this will be confirmed.
|50
|N
|-
|Loading Exceed Multiple Limit
|WHSE, OWNER
|Controls the action taken by the RDT when the Multiple Limit is exceeded.
|14
|W
|-
|Loading Lift Entry
|WHSE, OWNER
|Controls whether the Loading module prompts for the number of lifts and pallets
|01
|N
|-
|Loading Method
|WHSE, OWNER
|Loading Method in use for the warehouse
|20
|N
|-
|Loading Multiple Limit
|WHSE, OWNER
|This is the limit for how many items can be scanned onto a vehicle before Dock Door must be entered.
|
|0
|-
|Loading Order Enquiry
|WHSE, OWNER
|Controls whether the Loading module allows the user to perform order status enquiry requests
|01
|N
|-
|Loading Scan Multiples
|WHSE, OWNER
|Controls whether the user is allowed to scan multiple loaded items before being prompted to take the items to the Dock Door.
|01
|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
|-
|Loading Sequence
|WHSE, OWNER
|The sequence in which orders will be loaded within the load (affects Loading By Bay Door only)
|36
|N
|-
|Loading Trailer Number
|WHSE, OWNER
|Controls whether the Loading module prompts the user to enter a trailer number value
|01
|N
|-
|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
|25
|
|-
|Log Postponement
|WHSE, OWNER
|Whether pick postponements are recorded in the Exceptions Log
|01
|N
|-
|Loose Item Serial Number
|WHSE, OWNER
|Controls whether serial number entry is required when picking loose cases and units
|9006
|N
|-
|Marshalling Method
|WHSE, OWNER
|Controls whether orders are to be marshalled or not
|9004
|B
|-
|Maximum Putaway Quantity
|WHSE, OWNER
|Maximum quantity allowed to be received and putaway by UPC code (Bespoke)
|04
|0
|-
|Minimum Pallet ID Length
|WHSE, OWNER
|Controls the minimum length of SSCC entered in Receipt
|04
|0
|-
|Move Efficient Flag
|WHSE, OWNER
|Location or priority efficiency
|05
|L
|-
|Multi Stage Confirmation Message
|WHSE, OWNER
|Controls whether confirmation messages are sent to the WMS for multi stage tasks
|02
|N
|-
|Multi-Pallet Picking Sequence
|WHSE, OWNER
|Controls whether the first pallet picked or last pallet picked via WA Dual Cycling is taken to marshalling first
|63
|L
|-
|Multi-Pallet WADC
|WHSE, OWNER
|Determines whether the WADC modules allow multiple pallets to be picked at the same time
|62
|N
|-
|Multiple Putaway Tasks Prompt
|WHSE, OWNER
|Controls whether the RDT prompts the user to complete one or all of the putaway tasks when multiple putaway tasks exist for the customer pallet id
|01
|N
|-
|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
|-
|New Stock Take Message Layout
|WHSE, OWNER
|BESPOKE: Changes the Stock Take message to WMS to a different extended format. USE WITH CAUTION
|01
|N
|-
|Nokia Barcodes
|WHSE, OWNER
|This rule controls whether the RDT will expect to scan Nokia barcode labels
|01
|N
|-
|Num Picks before RSBE
|WHSE, OWNER
|The number of picks to elapse between residual stock balance enquiries
|04
|0
|-
|OBS Menu
|SYS, GRP
|Controls access to the OBS Support Menu
|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
|QMC
|-
|Ora Password
|SYS
|The password of the user for the connection to the Oracle database.
|26
|
|-
|Ora Priority Incoming Queue
|SYS
|The Oracle queue on which high priority messages are stored
|03
|
|-
|Ora User
|SYS
|The username for the connection to the Oracle database
|03
|SCE
|-
|Original Priority Audit
|WHSE, OWNER
|Controls whether an Exceptions record is created to capture the original priority of the pick / movement task
|01
|N
|-
|Pallet Case Label Threshold
|WHSE, OWNER
|Controls whether receipt labels are produced at pallet level or case level based on quantity
|04
|1
|-
|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
|-
|Part Pick Pallet Count
|WHSE, OWNER
|Controls whether Part Picking prompts users to enter a pallet count
|01
|N
|-
|Part Replen Label Format
|WHSE, OWNER
|Format of the Part Replen label
|25
|
|-
|PC Generation Algorithm
|WHSE, OWNER
|Algorithm to generate Picking Containers
|9002
|
|-
|PC Prefix
|WHSE, 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
|-
|Pick By Order
|WHSE, OWNER
|Controls whether a picker is locked to task for a single order
|77
|N
|-
|Pick Catch Weight Per Case
|WHSE, OWNER
|Controls whether Catch Weights are entered at Case instead of Stock/Pick level. Default Disabled.
|01
|N
|-
|Pick Consolidate Group
|WHSE, OWNER
|For Consolidated picking: How to create groups of picks.
|10
|N
|-
|Pick for On-time Delivery
|WHSE, OWNER
|If enabled, this rule will ensure that picks are assigned to pickers in Priority, then OTD Date and Time sequence
|01
|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 Multiple Containers
|WHSE, OWNER
|If enabled, allows creation of several containers in sequence
|01
|N
|-
|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
|-
|Picking Container Adjustment
|WHSE, OWNER, GRP
|Allow the user to adjust Picking Containers. Bespoke
|02
|N
|-
|Picks by Quantity
|WHSE, OWNER
|Allocates pick tasks to the RDT users by quantity, largest first.
|01
|N
|-
|Pre-Receipt Sort (Bespoke)
|WHSE, OWNER, GRP
|Allow Pre-Receipt Sortation (Bespoke)
|01
|N
|-
|Pre-Reposition
|WHSE, OWNER
|Bespoke: Pre-reposition all pending putaways for a stock code when a pallet of the same stock is repositioned
|01
|N
|-
|Print Ad Hoc Putaway Labels
|WHSE, OWNER
|Whether the RDT attempts to print labels for Ad Hoc Putaways
|02
|N
|-
|Print Ad Hoc Stock Move Labels
|WHSE, OWNER
|Controls whether the Ad Hoc Stock Move module prompts the user to print a label
|43
|N
|-
|Print Despatch Labels
|WHSE, OWNER
|Whether the RDT attempts to print despatch labels for picked stock.
|30
|N
|-
|Print Part Replen Labels
|WHSE, OWNER
|Whether the RDT attempts to print labels for Part Replenishments
|43
|N
|-
|Print Stock Despatch Label
|WHSE, OWNER
|Controls whether the Part Picking module allows stock level despatch labels to be produced
|68
|N
|-
|Priority Change Audit
|SYS
|Controls whether an Exceptions record is created to capture when a user changes the priority of a task
|01
|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
|AG_CCWH
|-
|Quick Pack
|WHSE, OWNER
|Allow Home Use orders not assigned to a route/load or assigned to a route/load individually to skip the deconsolidation process
|01
|N
|-
|RDT Box Drawing
|SYS
|What style of box-drawing the RDT's connected to this WCS will use.
|44
|1
|-
|RDT Wait Time
|SYS
|This is the amount of time that the RDT application will wait before re-trying communications to the WCS.
|04
|20
|-
|RDT_WCS LocalPort
|SYS
|This is the port that the WCS listens to for communications from RDTs.
|04
|15002
|-
|Receipt 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 ‘R
|01
|N
|-
|Receipt Enter Type
|WHSE, OWNER
|Allow the user to enter the receipt type in RDT Goods Receipt
|01
|N
|-
|Receipt Expected Quantity Check
|WHSE, OWNER
|If enabled, this parameter makes the RDT compare the received quantity entered with the expected quantity pre-advised
|02
|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
|-
|Receipt Intake Stock Check
|WHSE, OWNER
|Controls Issue Life Check at Receipt
|22
|N
|-
|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
|-
|Receipt Print Labels
|WHSE, OWNER
|Controls where/if pallet labels are printed during the receipt process
|21
|N
|-
|Receipt Selection Type
|WHSE, OWNER
|How to find the receipt on the RDT - via Advice Note or GRN no.
|08
|A
|-
|Receipt Single Barcode
|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
|-
|Redundant Stock Check
|WHSE, OWNER
|If enabled, products marked as redundant are rejected when scanned at receipt
|01
|N
|-
|Regroup Order by Stock
|SYS
|Allow WCS Maintenance users to re-group an order's picks by the number of stock picks on the order, then by location.
|01
|N
|-
|Reprint Despatch Label at Decon
|WHSE, OWNER
|When enabled, the RDT will print despatch labels for orders when deconsolidated
|01
|N
|-
|Request Putaway 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
|-
|RF Use Estimated Pallets
|WHSE, OWNER
|If enabled, then the new estimated pallets message will be sent to the Calidus-3pl Mobile system
|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
|-
|Select Move Allow Held
|WHSE, OWNER
|Allow Select Move Function to include Held Movements
|01
|N
|-
|Select Stock Move by Stock
|WHSE, OWNER
|Allow selection of stock moves by Stock before Pallet
|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
|-
|Serial Maximum Length
|WHSE, OWNER
|Controls the maximum length of a scanned case serial number in Picking. Default 0 (disabled)
|04
|0
|-
|Serial Minimum Length
|WHSE, OWNER
|Controls the minimum length of a scanned case serial number in Picking. Default 0 (disabled)
|04
|0
|-
|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
|-
|Shipment Pallet Build Validation
|WHSE, OWNER
|Controls what validation is followed when assigning shipment packages onto shipment pallets
|60
|P
|-
|Single Picker Per Order
|WHSE, OWNER
|Assign related picks to user on first pick. Default Disabled
|01
|N
|-
|Split Face Sequence
|WHSE, OWNER
|Controls the sort sequence when Split Faces enabled
|75
|1
|-
|Split Pick Quantities
|WHSE, OWNER
|If enabled, allows large picks to be split into more than one pack
|01
|N
|-
|Split Tote
|WHSE, OWNER
|Allow the user to choose to split a picked line over several totes.
|01
|N
|-
|Stock Take Batch Check
|WHSE, OWNER
|When checking pallets during Stock Take, request the user to check the customer batch value
|01
|N
|-
|Stock Take Enter GRN
|WHSE, OWNER
|When adding pallets during Stock Take or Perpetual Inventory, request the user to enter a GRN number
|01
|N
|-
|Stock Take Sell By Date Check
|WHSE, OWNER
|When checking pallets during Stock Take, request the user to check the sell by date value
|01
|N
|-
|Task Identifier
|WHSE, OWNER
|Which field to use to identify pallets
|06
|P
|-
|Temperature Recording
|WHSE, OWNER
|Controls whether Temperature Recording is required at Pre-Advice
|01
|N
|-
|Tote to Carton Standardise
|WHSE, OWNER
|If enabled, the RDT screens will be amended to display Carton in place of Tote
|01
|N
|-
|Track Deconsolidation
|WHSE, OWNER
|When enabled, this rule will inform WMS when orders have been completely deconsolidated
|01
|N
|-
|Trolley IDs
|WHSE, OWNER, GRP
|Allow loading of orders into trolleys
|02
|N
|-
|Update CPID
|WHSE, OWNER, GRP
|Allow the user to update the customer pallet id value. Bespoke
|02
|N
|-
|Update CPID Label Format
|WHSE, OWNER
|Format of Update CPID Label
|25
|
|-
|Update CPID Print Labels
|WHSE, OWNER
|Controls if a pallet label can be printed from the Update CPID module
|01
|N
|-
|Use Dummy Checksum
|SYS
|Used to terminate the interface messages with a dummy checksum value (??)
|01
|N
|-
|Use WMS Pick Sequence
|WHSE, OWNER
|Controls whether pick tasks are assigned to a picker in WMS location pick sequence order
|01
|N
|-
|Use WMS Rotation instead of Cust Batch
|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
|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
|-
|WA DC Exclude S to D moves
|WHSE, OWNER
|Ensures WA DC (interleaving) focuses more on emptying P&D locations rather than completing housekeeping moves.
|01
|Y
|-
|WCS Stock Despatch Label Format
|WHSE, OWNER
|Format of the stock despatch label
|25
|
|-
|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
|
|-
|Weight Volume Check
|WHSE, OWNER
|Check stock dimensions and weight are populated during Goods Receipt.
|01
|N
|-
|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
|*****
|-
|WMS System
|SYS
|Version of WMS that the WCS is connecting to.
|56
|O
|-
|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
|
|-
|Write RPM Logs
|WHSE, OWNER
|Bespoke: Write RPM record to Error Log. Default Disabled
|01
|N
|-
|Zero Negative Quantities
|WHSE, OWNER
|Zero negative values on enquiries. Default Enabled
|01
|Y
|}

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

|-
| 01
| N-Disabled

|-
| 01
| Y-Enabled

|-
| 02
| N-Disabled

|-
| 02
| P-Password-Protected

|-
| 02
| Y-Enabled

|-
| 03
| Plain Text

|-
| 04
| Plain Numeric

|-
| 05
| L-By Location

|-
| 05
| P-By Priority

|-
| 06
| C-By Cust Pallet ID

|-
| 06
| P-By Pallet ID

|-
| 06
| S-By Stock

|-
| 07
| B-Blind Receipt

|-
| 07
| C-Check Receipt

|-
| 07
| N-Non Pre-Advised Receipt

|-
| 07
| P-Non Pre-Advised Receipt & Putaway

|-
| 08
| A-By Advice No

|-
| 08
| C-By Cust Pallet Id

|-
| 08
| G-By GRN No

|-
| 09
| L-By Load Number

|-
| 09
| O-By Order Number

|-
| 10
| N-None

|-
| 10
| S-By Stock/Batch

|-
| 11
| C-Combo Check

|-
| 11
| N-Disabled

|-
| 11
| Y-Enabled

|-
| 12
| A-By Aisle

|-
| 12
| C-By Route/Load WMS Consolidation

|-
| 12
| L-By Load/Aisle

|-
| 12
| O-By Order Number

|-
| 12
| P-By Order Page

|-
| 12
| R-By Reference

|-
| 12
| Z-By Area/Zone

|-
| 13
| Date

|-
| 14
| A-Audit

|-
| 14
| E-Error

|-
| 14
| I-Information

|-
| 14
| W-Warning

|-
| 15
| F-Full/Blind

|-
| 15
| P-Preadvised/Partial

|-
| 16
| A-Area (m2)

|-
| 16
| I-Impressions

|-
| 16
| L-Length (m)

|-
| 16
| Q-Quantity

|-
| 16
| V-Volume (m3)

|-
| 16
| W-Weight (kg)

|-
| 17
| Priority Values

|-
| 18
| M-Manual

|-
| 18
| T-Threshold

|-
| 18
| W-Weighting

|-
| 19
| 0-Disabled

|-
| 19
| 1-Fetch Details

|-
| 19
| 2-Display Location

|-
| 20
| B-By Bay Door

|-
| 20
| C-By Carton

|-
| 20
| F-By Final Media Number

|-
| 20
| I-By Picking Container

|-
| 20
| L-By Picking Container and Location

|-
| 20
| N-Disabled

|-
| 20
| P-By Pick

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

|-
| 21
| C-WCS

|-
| 21
| M-WMS

|-
| 21
| N-Neither

|-
| 21
| P-WMS - Prompt For Printer on WCS

|-
| 21
| Q-WCS - Quantity

|-
| 21
| R-WCS - Receipts Only

|-
| 22
| A-Authorisation Required

|-
| 22
| E-Error

|-
| 22
| I-Informational Message

|-
| 22
| N-None

|-
| 23
| B-By Stock and Batch

|-
| 23
| L-By Stock and Batch (Line Type)

|-
| 23
| N-No Id

|-
| 23
| P-By Pallet ID

|-
| 23
| S-By Stock Code

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

|-
| 23
| 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
| D-Printer Dependant

|-
| 29
| M-Marshalling

|-
| 29
| P-Pick

|-
| 29
| S-At Start Only

|-
| 30
| C-Per Case

|-
| 30
| D-Per Despatch Pallet

|-
| 30
| N-Disabled

|-
| 30
| P-Per Pick

|-
| 30
| R-Request Quantity

|-
| 30
| W-WMS

|-
| 31
| D-Deconsolidate Only

|-
| 31
| N-Disabled

|-
| 31
| P-Deconsolidate and Pack

|-
| 32
| A-At Allocation

|-
| 32
| L-At Location

|-
| 33
| Aisle Length

|-
| 34
| Bay Length

|-
| 35
| Level Length

|-
| 36
| A-By Drop Sequence

|-
| 36
| D-By Reverse Drop Sequence

|-
| 36
| N-Disabled

|-
| 37
| C-By Customer Order

|-
| 37
| O-By Order Number

|-
| 37
| P-By Picking Container's Order

|-
| 37
| R-By Route/Load

|-
| 38
| N-Disabled

|-
| 38
| P-Pick Only

|-
| 38
| R-Goods Receipt Only

|-
| 38
| Y-Enabled

|-
| 39
| E-Enter Tray Values

|-
| 39
| G-Generate

|-
| 39
| N-Disabled
|-
|39
|O-Check Order
|-
|39
|P-Password_Protected
|-
|39
|S-Generate SSCC
|-
|39
|T-Pre-Set Tray Values
|-
|39
|Y-Enabled
|-
|40
|Decimal
|-
|41
|M-At Marshalling
|-
|41
|N-Disabled
|-
|41
|S-At Start
|-
|42
|E-At Each Dispatch Pallet
|-
|42
|L-At Location
|-
|42
|N-Disabled
|-
|42
|S-At Start Only
|-
|43
|N-Disabled
|-
|43
|R-Request Quantity
|-
|44
|0-Single Line
|-
|44
|1-Double Line
|-
|44
|1024-Black (Reverse display)
|-
|44
|256-Simple
|-
|44
|512-Block
|-
|45
|C-Stock Code
|-
|45
|O-Stock Description ((Line 1 only)
|-
|45
|T-Stock Description (Line 1 and 2)
|-
|46
|C-Size Pack Text from Stock Code
|-
|46
|I-Impressions Pack Size
|-
|47
|C-WCS
|-
|47
|M-WMS
|-
|48
|D-Detail
|-
|48
|S-Summary
|-
|49
|B-Blind Receipt
|-
|49
|P-Putaway
|-
|50
|E-Enter first and confirm
|-
|50
|N-Disabled
|-
|50
|O-Enter and Validate
|-
|51
|O-By Order Number
|-
|51
|R-By Route/Load
|-
|52
|C-Complete Entire Reference
|-
|52
|N-Disabled
|-
|52
|Y-Enabled
|-
|53
|Plain text (with Reason Code lookup)
|-
|54
|C-Check Order
|-
|54
|L-Check Countback Level
|-
|54
|N-Disabled
|-
|54
|O-Check Order Password Protected
|-
|54
|P-Password Protected
|-
|54
|Y-Enabled
|-
|55
|C-Check Order
|-
|55
|N-Disabled
|-
|55
|Y-Enabled
|-
|56
|414-'414' - Powerhouse WMS
|-
|56
|770-'770' - Oracle WMS
|-
|57
|A-Automatic
|-
|57
|N-Disabled
|-
|57
|P-Password Protected
|-
|57
|Y-Enabled
|-
|58
|G-Goods Receipt Only
|-
|58
|N-Disabled
|-
|58
|P-Pick Only
|-
|58
|Y-Enabled
|-
|59
|N-Disabled
|-
|59
|P-At PND
|-
|59
|Y-Enabled
|-
|60
|P-By Order Priority
|-
|60
|S-By Order Priority/Store Code
|-
|61
|E-Use Estimated Values
|-
|61
|N-Disabled
|-
|61
|Y-Enabled
|-
|62
|I-Picking Only
|-
|62
|N-Disabled
|-
|62
|U-Putaway Only
|-
|62
|Y-Enabled
|-
|63
|F-First Pick First
|-
|63
|L-Last Pick First
|-
|64
|F-Full Before Part
|-
|64
|M-Mixed Sequence
|-
|65
|M-Multi Marshalling Locs
|-
|65
|N-Disabled
|-
|65
|R-Require new Location
|-
|65
|S-Suggest new Location
|-
|65
|Y-Enabled
|-
|66
|M-Minutes
|-
|66
|S-Seconds
|-
|67
|A-Automatic
|-
|67
|N-Disabled
|-
|67
|Y-Enabled
|-
|68
|D-Per Despatch Pallet
|-
|68
|N-Disabled
|-
|69
|I-Task Identifier
|-
|69
|S-Stock/Sell-By-Date
|-
|70
|B-Both
|-
|70
|I-Incoming
|-
|70
|O-Outgoing
|-
|71
|00-Default Identifiers
|-
|71
|01-Stock (240) Then GTIN (01)
|-
|72
|N-Disabled
|-
|72
|R-Returns Only
|-
|72
|Y-Enabled
|-
|73
|A-Authorisation Required
|-
|73
|E-Error
|-
|73
|N-None
|-
|73
|W-Warning
|-
|74
|C-Check Case scans only
|-
|74
|N-Disabled
|-
|74
|U-Check Unit scans only
|-
|74
|Y-Check Case and Unit scans
|-
|75
|1-Up Odd, Up Even
|-
|75
|2-Up Odd, Down Even
|-
|75
|3-Up Even, Up Odd
|-
|75
|4-Up Even, Down Odd
|-
|75
|5-Down Odd, Down Even
|-
|75
|6-Down Odd, Up Even
|-
|75
|7-Down Even, Down Odd
|-
|75
|8-Down Even, Up Odd
|-
|76
|C-Customer Batch
|-
|76
|E-Error
|-
|76
|P-Pallet ID
|-
|76
|S-Sell By Date
|-
|77
|F-Full Pallets
|-
|77
|N-Disabled
|-
|78
|M-Multiple Orders
|-
|78
|S-Single Order
|-
|79
|A-Ascending Aisle
|-
|79
|B-Ascending Aisle/Bay
|-
|79
|N-Default
|-
|80
|D-Default
|-
|80
|R-Reduced
|-
|81
|Plain text (with Reason Code lookup & Blank)
|-
|82
|C-Loc/Case/Unit/Rot
|-
|82
|Q-Loc/Qty/Area
|-
|83
|B-Part Picks and Full Pallet Picks
|-
|83
|D-Disabled
|-
|83
|F-Full Pallet Picks Only
|-
|83
|P-Part Picks Only
|-
|9001
| -Standard site (No bespoke rules)
|-
|9001
|BIBBY-Bibby
|-
|9001
|BRAC-Culina Brackmills (HOD)
|-
|9001
|BRETT-Bretts Transport
|-
|9001
|CENT-Century Logistics
|-
|9001
|CERT-Culina Port Salford (PS)
|-
|9001
|COV-DHL Coventry
|-
|9001
|DHLSKM-DHL Skelmersdale
|-
|9001
|ELLIS-Ellis Hanworth
|-
|9001
|FURRY-DHL EXEL Furry Park
|-
|9001
|FWLMA-XKO Sites
|-
|9001
|HAN-Hanson
|-
|9001
|HODD-Culina Hoddesdon (OCT)
|-
|9001
|MOR-Moran
|-
|9001
|NIJ-DHL EXEL Healthcare
|-
|9001
|POD-Port Of Dover
|-
|9001
|POT-Potter
|-
|9001
|SCH-Schenker
|-
|9001
|TBI-DHL EXEL Dublin RHR
|-
|9001
|TBW-DHL EXEL Whitwood
|-
|9001
|TNT-TNT
|-
|9002
|JJD-JJD
|-
|9003
|B-Blank
|-
|9003
|C-Largest Case Qty First
|-
|9003
|Q-Largest Quantity First
|-
|9003
|S-Sort By Product Strength
|-
|9004
|B-Disabled
|-
|9004
|P-By Picking Container and Location
|-
|9006
|N-Disabled
|-
|9006
|S-Allow Shortages
|-
|9006
|Y-Required
|-
|9007
|Plain text (with Media Type lookup)
|}
==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]]

Set-up Guide

2025-10-30T11:17:06Z

Anw: New version

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = Set-up Guide
| Reference = UG 106181
| Version = 7.02
| Date = 30th October 2025
| Sysver = 3.4
}}


= 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 and whether the truck type is considered intrinsically safe.

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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

== 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]]

WCS Maintenance

2025-10-30T11:15:55Z

Anw: New version

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = WCS Maintenance Guide
| Reference = UG 106181
| Version = 4.01
| Date = 30th October 2025
| Sysver = 3.4
}}


= WCS Maintenance =
This suite allows administrators to configure the [[WCS]] system, and modify the running of tasks within that system for the RDTs. When you log on, you need to open the WCS database being used by the central WCS. There should only be one. You will not need to open the database if you start the WCS Maintenance program from the WCS Server program. This option is only available if the maintenance program is being run on the WCS Server PC. The Open Database command is on the File Menu.

When you open a database, you will by default be shown a list of recently opened database files.

[[Image:Maint1.png|600px]]

This allows for multiple WCS systems to be in operation for you. If you do not want to use this list, you can disable it by the check box provided. If the database you require is not listed, then you can choose to see more files. This will open a standard windows explorer dialogue. Once you have identified the database, this will be added to the top of your list of recent files. The settings panels allow you to modify the options for this list.

[[Image:Maint2.png|200px]]

You will be asked to enter your company and warehouse codes. This is to identify the data that you will be enquiring on in the RDT database. This can be changed later if required. The codes are the same as in your main warehouse management system.

You are also prompted to enter your username code and password, if required. These are the same as the employee codes in your main warehouse management system.

The options you have available to you within the program depend upon the group your username has been given. The passwords (and other options) for your user, directly relating to this program can be maintained from the main menu from Standing Data Maintenance. If you have unavailable options, these items will be greyed out on the menus, and will not be available from the toolbar. Contact your administrative manager to obtain more options to the system.

There are several menus, which control all the features of the WCS Maintenance suite of windows. They are:

File Menu

Edit Menu

Tasks Menu

RDT Comms

System Tools Menu

Reports Menu

SD Maintenance Menu

Windows Menu

Help

Click on one of the items listed above to find help about the options available on that menu.

Most of the useful items on the menus can be accessed via the toolbar. The toolbar can be maintained to suite your preference. See ToolBars for more information on this.

This help can also be accessed by use of the F1 key, within the windows themselves. This, along with the icon available on most windows, is context-sensitive and will take you straight to a related topic. If no related topic is found, you will be taken to this topic.

== WCS Maintenance Menus ==
Menus:

File Menu

Edit Menu

Tasks Menu

RDT Comms

System Tools Menu

Reports Menu

SD Maintenance Menu

Windows Menu

Help

== File Menu ==
Menu Items:

Open Database

Close Database

Print

Print Selection

Exit

=== Open Database ===
Shortcut: CTRL-O

This command is not necessary if you are running the program from the WCS Server. It can be used to change the database that you are linking to, if multiple RDT systems are in use. Simply follow the prompts until the RDT database is found (it is usually called ‘rdt1.mdb’).

=== Print ===
Shortcut: CTRL-P

This option prints the selected window’s contents. If you have accessed this option from the icon, you will be prompted for confirmation, to prevent printing thousands of pages of data accidentally. If you have selected records from the active window, the button will work as the option Print Selection.

Related Topics:

Print Selection

=== Print Selection ===
This option prints a selection of records from the selected window.

=== Close Database ===
Shortcut: CTRL-W

This option closes down the currently opened database. You will be unable to use most of the functions if you do not open another database. The only options available to you when the database is closed are Repair Database and Compact Database.

Related Topics:

Compact Database

Open Database

=== Exit ===
Shortcut: CTRL-Q

This option exits the WCS Maintenance program.

== Edit Menu ==
Menu Items:

Cut

Copy

Paste

=== Cut ===
Shortcut: CTRL-X

Cuts selected data to the clipboard.

=== Copy ===
Shortcut: CTRL-C

Copies selected data to the clipboard.

=== Paste ===
Shortcut: CTRL-V

This option pastes data from the clipboard to the selected area.

== Tasks Menu ==
Menu Items:

Pallet Movement Maintenance

Pick Maintenance

Picking Container Maintenance

Deconsolidation Maintenance

Goods Receipt Enquiry

Stock Take Enquiry

Shipment Packages Enquiry

Shipment Pallets Enquiry

=== Pallet Movement Maintenance ===
[[Image:Maint3.png|600px]]

On start-up, you are presented with the Select Movements window. When data has been selected, you will be returned to this screen. All data from the movements screen that conforms to your selection criteria will be displayed. The window will display all the data that is required, and in a reasonable order, but this can be modified.

There is an icon bar on this screen, to aid you.

To add new fields to or remove existing fields from the display, right-click on the grid header anywhere and select the option 'Field Chooser', or hit the appropriate icon on the toolbar.

To change the position of the fields in the grid, drag the required field to its new position and then release the mouse button.

You can change the way the data is sorted (the order the rows appears in the grid) in several ways. You can double-click on the column header to sort ascending on that field (low to high). You can then double click again on that field, and it will switch to descending (high to low). Double clicking again will remove the sort.

You could also right-click on the required field header, and choose ascending, descending or none from the pop-up menu.

You can sort on several fields at the same time by using one of the above methods on several of the fields, in the order you require. Each column will be marked to show that data has been sorted within it.

The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

Reprioritisation of movements can be achieved by several methods. You can either reprioritise each line singly by right clicking and choosing re-prioritise line, or you can select several lines. This is done by using shift or control keys with the mouse click, then right-clicking and choosing 'Re-prioritise Selection' from the menu, or the corresponding button. Either way you will be taken to a screen to enter the new priority of the movement(s), then click OK. You will be shown the success or failure of the activity on a progress screen.

When you are finished, the data will be re-displayed with the new elements in place and the WCS database will have been updated.

You can remove a task from the list of available tasks by setting the task to Error status. This is different to holding the task, as held tasks can still block P&D locations - Error tasks won’t. Simply right-click on the task you want setting to error status and choose the Set Error option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been set to error status and will be displayed in red. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

If you wish to print out details of the movements in the list, either those selected or all the records in the list, use the print icon or options from the main WCS maintenance menu.

'''Supervisor options'''

If you are a supervisor user (defined against your user name in the Users Maintenance screen), you also have the option of deleting tasks from the database. Simply right-click on the task you want removing from the database and choose the Delete option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been deleted from the database. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

See also:

Select Data Window

Field Chooser

Miscellaneous

Re-prioritise Entry Window

Help

ToolBars

=== Pick Maintenance ===
[[Image:Maint4.png|600px]]

On start-up, you are presented with the Select data window. When data has been selected, you will be returned to this screen. All data from the screen that conforms to your selection criteria will be displayed. The window will display all the data that is required, and in a reasonable order, but this can be modified.

There is an icon bar on this screen, to aid you.

To add new fields to or remove existing fields from the display, right-click on the grid header anywhere and select the option 'Field Chooser', or hit the appropriate icon on the toolbar.

To change the position of the fields in the grid, drag the required field to its new position and then release the mouse button.

You can change the way the data is sorted (the order the rows appears in the grid) in several ways. You can double-click on the column header to sort ascending on that field (low to high). You can then double click again on that field, and it will switch to descending (high to low). Double clicking again will remove the sort.

You could also right-click on the required field header, and choose ascending, descending or none from the pop-up menu.

You can sort on several fields at the same time by using one of the above methods on several of the fields, in the order you require. Each column will be marked to show that data has been sorted within it.

The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

Reprioritisation of data can be achieved by several methods. You can either reprioritise each line singly by right clicking and choosing re-prioritise line, or you can select several lines. This is done by using shift or control keys with the mouse click, then right-clicking and choosing 'Re-prioritise Selection' from the menu, or the corresponding button. Either way you will be taken to a screen to enter the new priority of the movement(s), then click OK. You will be shown the success or failure of the activity on a progress screen.

When you are finished, the data will be re-displayed with the new elements in place, and the WCS database will have been updated.

You can remove a task from the list of available tasks by setting the task to Error status. This is different to holding the task, as held tasks can still block P&D locations - Error tasks won’t. Simply right-click on the task you want setting to error status and choose the Set Error option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been set to error status and will be displayed in red. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

If you wish to print out details of the data in the list, either those selected or all the items in the list, use the print icon or options from the main WCS maintenance menu.

Picks are allocated to RDT users in groups and these groups are decided when the task is received from the WMS. To split a number of picks out of an existing group into a new group, select a number of picks in one group, then right-click and choose ‘Create Pick Group’. Alternatively, you can click on the icon on the icon bar. The picks will then be split into a new group.

Picks in different groups cannot be put into a new group together. Additionally, pick tasks in progress will not be changed to a new group.

'''Supervisor options'''

If you are a supervisor user (defined against your user name in the Users Maintenance screen), you also have the option of deleting tasks from the database. Simply right-click on the task you want removing from the database and choose the Delete option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been deleted from the database. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

See also:

Select Data Window

Field Chooser

Miscellaneous

Re-prioritise Entry Window

Help

ToolBars

==== Re-prioritise Entry Window ====
When you have chosen lines to re-prioritise, you will be taken to this dialogue window, to enter the new priority of the lines.

[[Image:Maint5.png|200px]]

Once this is done, click OK. You will be shown the success or failure of the activity on a progress screen.

=== Goods Receipt Enquiry ===
This screen allows you to enquire on the Goods Receipt Preadvice file, showing all outstanding receiving tasks for the RDT users.

The form has two views, a detail/select view, and a grid view.

[[Image:Maint6.png|600px]]

[[Image:Maint7.png|600px]]

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Stock Take Enquiry ===
This screen allows you to enquire on the Stock Take file, showing all outstanding stock take tasks available to the RDT users.

The form has two views, a detail/select view, and a grid view.

[[Image:Maint8.png|600px]]

[[Image:Maint9.png|600px]]

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Shipment Packages Enquiry ===
The Shipment Packages Enquiry screen allows the user to see the packages that are available for the RDT Shipment Pallet Building module.

[[Image:Maint10.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint11.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

=== Shipment Pallets Enquiry ===
The Shipment Pallets Enquiry screen allows the user to see the pallets that have been built by the RDT Shipment Pallet Building module. These pallets will be available for Movement or Despatch, depending on the status of the pallet.

[[Image:Maint12.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint13.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

=== Deconsolidation Maintenance ===
The Deconsolidation Maintenance screen allows the user to see the stock that is ready for deconsolidation after picking. The screen also shows orders that are ready for despatch.

The screen allows the status of the tasks to be changed.

[[Image:Maint14.png|200px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint15.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

The screen allows tasks to be held or released. Select one or multiple tasks on the grid, and then press the hold/release button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

The screen allows tasks to have an error status set against them, or cleared. Select one or multiple tasks on the grid, and then press the Set/Clear Error button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

=== Picking Container Maintenance ===
The Picking Container Maintenance screen allows the user to see Picking Containers. The screen also shows orders that are ready for deconsolidation.

The screen allows the status of the containers to be changed.

[[Image:Maint16.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint17.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

The screen allows containers to be held or released. Select one or multiple containers on the grid, and then press the hold/release button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

The screen allows containers to have an error status set against them, or cleared. Select one or multiple containers on the grid, and then press the Set/Clear Error button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

=== Pick Summary Screen ===
The Pick Summary screen allows the user to see a summary of all the picking tasks available in the WCS.

On entry, the screen will be in ‘data select’ mode. Data is selected by entering the owner of the orders and the route. You can select asterisk (*) from the drop-down lists to select all the owners or routes.

Once the criteria have been selected, clicking the refresh button will display the selected data (‘Display’ mode) on a grid.

* Should any of the records on the route/load be in error, the status will be “Error” and the background colour of the whole line will be red. The fore-colour will be in white. The text will be in '''bold.'''
* Should any of the records on the route/load be held, the status will be “Held” and the background colour of the whole line will be red. The fore-colour will be in white. The text will be in '''bold'''.
* Should any of the records on the route/load be in progress, the status will be “In Progress” and the text of the whole line will be displayed in green and '''bold'''.
* Otherwise, the records will be put in default black, with no bold.

The colouring on the line will be decided in the order displayed above. Therefore, if there are tasks held, and there are some in progress, the line will be displayed as if all lines are held.

The grid allows single-line selection and re-sizing of columns and is scrollable.

Where multiple and different customer details are found for a load, ‘*’ (asterisk) is displayed in the Customer column.

The screen displays a status bar, showing the total number of outstanding tasks displayed in the grid. If no records are selected based on the criteria entered, the status bar will display “No records selected”.

Clicking the Refresh button will refresh the record set, based on the selection criteria already entered. The grid will then be re-displayed based on the new data selected.

Clicking the Select button will clear the grid and the screen will re-enter ‘Data Select’ mode and allow you to enter the selection criteria again.

Should you double-click on a line, the pick reprioritisation screen is displayed, showing the orders matching the route and load on the line chosen. This screen will then operate in the same way as the normal pick reprioritisation screen, but without allowing you to re-select data.

=== Field Chooser ===
This screen shows you the all the elements that you can display on the grid.

[[Image:Maint18.png|200px]]

To change the items displayed, check the box next to the fields you want to see, and uncheck those you don’t want to see (by left clicking).

If you are using the field chooser to modify a grid display, the grid display will change as you change the checks. When you have finished, close the window, with either the OK button, or just the ‘X’ in the top-right of the window. The CANCEL button will be greyed out - it is not necessary when the window is used in this way.

If you are using the field chooser to select a layout for a selection template, click the OK button when you are satisfied with the display for the template. If you are not satisfied, click the cancel button, or the ‘X’ in the top-right of the window. The template will revert to the layout it had before you entered.

=== Select Data Window ===
This screen is used to select the data that you require to see on the main window. There are two tabs on this window, a normal tab and an advanced tab.

Topics:

Select Data Window, Normal Tab

Select Data Window, Advanced Tab

==== Select Data Window, Normal Tab ====
This is the area where standard selection criteria can be entered, to retrieve movement information from the database. This is the screen that you will be brought into first.

[[Image:Maint19.png|600px]]

Each of the criteria can be ranged or entered singly, based on the type of data that is held in each field. These can be of several types:

* Character type
* Numeric type
* Selection boxes
* Numeric type (Special)
* Date

Validation exists for each type, so that if entry is incorrect, you will be informed of the correct way.

Standard selection criteria (and their selection types) are:

{| class="prettytable"
| Warehouse
| Selection box, Character type

|-
| Owner
| Character type

|-
| Stock
| Character type

|-
| Pallet
| Numeric type

|-
| Customer Pallet
| Character type

|-
| Priority
| Selection box, Character type

|-
| Source Location
| Character type

|-
| Destination Location
| Character type

|-
| Truck Type
| Selection Box, Character type

|-
| Date From
| Date

|-
| Date To
| Date

|}
For Movements, the following extra criteria are displayed:

{| class="prettytable"
| Audit Number
| Numeric type (Special)

|-
| Line number
| Numeric type (Special)

|-
| Movement Type
| Radio buttons, Character type

|}
For Picks, the following extra criteria are displayed:

{| class="prettytable"
| Route Code
| Character Type

|-
| Load Number
| Numeric Type

|-
| Order Number
| Character Type (Special)

|-
| Page Number
| Numeric Type

|-
| Sequence Number
| Numeric Type

|-
| Pick Type
| Radio Buttons, Character type

|}
When selection criteria are entered, clicking OK will select all information on movements in the database that conform to this.

Further information:

Selection Types

==== Select Data Window, Advanced Tab ====
This is the area where advanced selection criteria can be entered, to retrieve movement information from the database.

Each item on the grid is a line of selection criteria.

When you switch to the advanced tab, any criteria you have entered on the normal tab will be entered automatically on this screen. This is so you can use the previous screen to enter the initial criteria easily, then fine-tune on the more complicated screen.

To enter new lines, you can double click the left mouse button on the indicated line, and you will be taken to a selection box, showing all the elements you can use to select with. You will then be allowed to enter any values with which to select. These values follow the standard selection type rules you would normally use.

You can also right-click on any of the lines. This will allow you to insert a new line in this way. From the menu that pops up here, you can also edit the marked criteria, or delete it.

Rather than entering selection criteria from scratch every time, it is possible to retrieve selection templates previously saved, and use them. To do this, click the ‘Save’ button. These may then be loaded using the ‘Load’ button.

Standard wildcard operation is in effect for the elements whose type permit it (character).

Ranges and lists are also permitted.

When selection criteria are entered, clicking OK will select all information on movements in the database that conform to this.

Further information:

Selection Templates

==== Selection Templates ====
This screen is available from the 'Advanced' tab of the Select Movements window. It allows you to create, retrieve, modify, save or delete templates for movement retrieval.

Selection Templates allow you to save standard retrieval criteria for specific functions for later use, saving re-typing time.

To create a new template, simply add the selection criteria to the grid, in the same way as the advanced tab. When this has been entered, click the 'Save' button. You will then be prompted to save the template.

To retrieve an existing template, click the 'Load' button. You will then be prompted to find your template. When you have selected your template, click 'OK'. The template will then be displayed on the screen, for editing or use.

If a retrieved template has been edited, you should save your template, either back to its original name or as a new template (using the 'Save' button).

To delete a template, use the Load Template window. You will not be asked to confirm your selection.

Fields can be left blank in the advanced criteria, and can be saved as such in the template file. You will not, however be able to use the blank templates until valid data has been entered for them.

==== Selection Types ====
Selection types encompass the entry methods of the different types of fields, and what entries may be allowed in this type.

Further information:

Selection Types, Character Type

Selection Types, Numeric Type

Selection Types, Selection Box/Radio Buttons

Selection Types, Numeric Type (Special)

==== Selection Types, Character Type ====
When entering single selections or ranges, field must be surrounded by '"' (Double Quote).

Characters entered as range delimited by '-' (Hyphen).

Characters entered singly delimited by ',' (Comma).

Wildcards may be used in this type. So, an asterisk (*) may be used to signify many or no characters, and a question mark (?) may be used to signify a single character.

Note: If using wildcards, you may be required to end the string with an asterisk. This is to account for possible trailing spaces. The exception to this is the Special derivative of Character types. In this instance, the asterisk is always assumed.

Examples:

Selecting a single owner ABC:

Enter “ABC” in the field.

Selecting 2 owners, ABC and XYZ:

Enter “ABC”,”XYZ” in the field.

Selecting a range of owners from AAA to CCC:

Enter “AAA”-“CCC” in the field.

Selecting multiples of the above:

Entering

“AAA”-“CCC”,“XYZ”,“YYY”-“ZZZ”

will select any owners in the range AAA to CCC, any between YYY and ZZZ and the owner XYZ.

==== Selection Types, Numeric Type ====
Numbers entered as range delimited by '-' (Hyphen).

Numbers entered singly delimited by ',' (Comma).

Examples:

Selecting a single pallet 00008132

Enter 8132 in the field.

Selecting 2 pallets, 00008132 and 00020001:

Enter 8132,20001 in the field.

Selecting a range of pallets from 00000200 to 00005000:

Enter 200-5000 in the field.

Selecting multiples of the above:

Entering

200-5000,8132,10000-10500

will select any pallets in the range 00000200 to 00005000, any between 00010000 and 00010500 and the pallet 00008132.

==== Selection Types, Numeric Type (Special) ====
In cases like this, special validation may limit entry of ranges.

Audit Number/ Line number.

In this case, a range of audit numbers may be entered, or a range of audit numbers with a single line number, or a single audit number with a range of line numbers.

Examples:

Selecting a single pallet 00008132

Enter 8132 in the field.

Selecting 2 pallets, 00008132 and 00020001:

Enter 8132,20001 in the field.

Selecting a range of pallets from 00000200 to 00005000:

Enter 200-5000 in the field.

Selecting multiples of the above:

Entering

200-5000,8132,10000-10500

will select any pallets in the range 00000200 to 00005000, any between 00010000 and 00010500 and the pallet 00008132.

==== Selection Types, Selection Box/Radio Buttons ====
Data in fields like this will allow standard entry based on the selection types above, but will also allow you to select single values from a pop-up list.

Radio buttons will allow you to select from a fixed list of values. Only one of these may be selected at one time.

For advanced criteria, these items act similarly to character type selection, and will appear as such in the list of criteria.

== RDT Comms ==
Menu Items:

Current Exceptions

Employee Activity

Messages

=== Employee Activity ===
The Employees Analysis window shows a constantly updated list of all the RDTs available on the WCS system, showing their status. The window you are shown initially shows you:

* The RDT ID
* The employee code
* A brief description of their activity.

The screen will display RDT users with activities older than 10 minutes at the top of the list.

The RDT ID is the WCS’s identifier for the RDT. This is included for reporting and system purposes only.

The employee code is from the standing data table on the WCS server. It is updated continually from the WMS table. The RDT user enters this when they log on to their RDT.

The activity description shows the current task in which the RDT is engaged. The description can be:

* Receipt - receiving pallets into the warehouse from a pre-advised Goods Receipt.
* Pick - picking pallets for advised sales orders.
* Replenishment - replenishing pick faces from bulk locations.
* Putaway - Taking pallets from receipt bays to their designated place in the warehouse.
* Movement - Moving a pallet from one area to another.
* Stock Take - involved in an advised stock take cycle count.
* Marshalling - marshalling a sales order load.
* Loading - Loading a sales order.
* Disconnected - the RDT is not connected to the WCS server.
* Idle - not involved in any of the above activities.
* Error - a system error.

The status ‘Idle’ simply shows that the RDT is not linked to an activity that is part of the current functionality. The RDT may well be performing different activities (ad hoc moves, pallet enquiry, etc).

The status ‘Error’ shows that the RDT may not be communicating correctly with the WCS server, but still has a job outstanding against it. The system is designed to self-correct these errors in most instances, but manual intervention may be required. These error lines will be displayed in red, indicating that there may be a problem. To force the system to clear these problem users, right-click on the affected user and choose Clear Locks from the pop-up menu. The system will then clear any tasks the user may have locked, releasing them to the general pool of tasks once more.

To find more information about the current activity of any particular RDT, double-click the left mouse button on the appropriate line. This will take you to the Employee Analysis - Detail window. Alternatively, right-click on the item, and choose Display Details from the pop-up menu.

The screen is kept updated at all times every few seconds. This means that the most up-to-date information about your RDT users is at your fingertips at all times. The window can be re-sized, as can the width of the grid rows, to keep all information on the screen at all times.

Further information:

Detail Window

==== Detail Window ====
This window gives you more detail on the selected line. The window shows you:

* The Employee code and their registered name.
* A short description of the activity.
* A detailed description of the activity.

=== Current Exceptions ===
The Exceptions window shows any tasks completed, but with exceptions. Exceptions include such things as:

* Repositioning a movement or putaway
* Cancelling a movement, replenishment or putaway
* Changing the quantity on a pick
* Cancelling a pick, or picking to zero
* Exchanging pallets on pick, movements or replenishments
* Any Ad-hoc movement
* Setting a task to Error status
* Deleting a task.

If any of these events take place, a message is shown on the exceptions screen immediately, showing the employee, the RDT, a brief description of the error and a date and time. The window shows only exceptions within a specified time period. Double clicking on the line will give you greater detail about the task.

Further information:

Detail Window

=== Messages ===
This screen allows you to send messages to RDT users who are logged on. The list of logged-on RDT users is kept updated at all times, making sure that the users you are sending a message to are always correct. If a user connects or disconnects from the Wireless network, you will be informed on this screen.

Enter your message in the text box provided. You must enter a message.

Pick the users to whom you wish to send a message. The list shows the entire network, including registered companies, warehouses and users. You can pick users individually, or send messages to an entire warehouse, company or the whole network. Either click on your chosen recipient and click the ‘add’ (->) button, or simply drag the intended recipient to the recipients list. Double clicking on a user will give you some information about their current activity.

Once all the intended recipients have been chosen, simply click the ‘send’ button. You will be informed of the progress of the message, and its completion. Messages will appear on RDT terminals when the user next exits a function.

To get a message to a user quicker, set the urgent flag on this screen. The RDT user will then pick up the message the next time they press the ‘Enter’ key.

== System Tools Menu ==
Menu Items:

Re-logon

Change Warehouse

System Settings

Clear out Error log

Clear out Incoming/Outgoing log

Clear out WCS Database

Clear Out Deleted Items

Incoming Log

Outgoing Log

Error Log

Compact Database

Database Utilities

=== Change Warehouse ===
This option allows you to set and change the company code and warehouse id, for the enquiry and movement priority screens.

Note: You can blank the company and warehouse here - this will allow you to view the data for all companies and warehouses on the current database.

=== Clear Out Deleted Items ===
This option will clear out any items in the database marked for deletion, but not yet deleted. Tasks such as these would be created if the database is set not to delete tasks, or if Maintenance users have deleted tasks using the Pallet Movement Maintenance screen.

Related Topics:

WCS Settings

=== Clear out Error log ===
This option will clear down the error log, obeying the user-entered clear-down settings.

=== Clear out Incoming/Outgoing log ===
This option will clear down the incoming and outgoing logs, obeying the user-entered clear-down settings.

=== Clear out WCS Database ===
This option will clear down the entire WCS database, leaving only standing data untouched, obeying the user-entered clear-down settings.

=== Incoming Log ===
This option is used to view the log of all incoming data to the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Outgoing Log ===
This option is used to view the log of all outgoing data from the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Error Log ===
This option is used to view the error log for operations on the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Compact Database ===
This option compresses the WCS database. It is a necessary requirement of SQL databases that this option be present. It can only be run if the database is closed. Close the database using the appropriate button, or choosing ‘Close Database’ from the ‘File’ menu.

=== System Settings ===
This option brings up a multiple panel window for maintaining system options. The tabs available are:

Rules, consisting of:

WCS Settings

Admin Defaults

Clear out Settings

Message Types

Maintenance Settings

See Also:

Rules Maintenance

==== WCS Settings ====
This allows you to modify the communication settings. The content of this form changes, depending on which WMS system you are linking to.

If the system is connecting using socket connections, the following details will be shown:

* WMS IP Address - This is the IP address of the WMS machine. It is in the standard telnet layout (4 numbers, separated by full stops.
* WMS -> WCS Local Port - This is the port that the WCS listens to for communications from the WMS.
* WCS -> WMS Remote Port - This is the port that the WMS listens to for communications from the WCS.

If the system being linked to is using Oracle Advanced Queues, the following options can be changed:

* Oracle Database Name
* User
* Password

Settings common to both connection systems that may be modified are:

* RDT -> WCS Local Port - This is the port that the WCS listens to for communications from RDTs.
* RDT Waiting Time - This is the amount of time that the RDT will wait before re-trying communications.
* WMS -> WCS Re-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.
* Default Company Code - This is the default company code that the RDT will log on to.
* 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.
* 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.
* 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.
* 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
** Exceptions

N.B. 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.

==== Clear out Settings ====
This option is used to enter the settings to control the clear-down options above.

You are prompted to enter the log directory, where details of the clear down’s success will be written.

For each clearable dataset, you can specify whether the clear down program will process this type, and the number of day’s data you wish to keep.

The datasets are:

* Database - Any tasks not actioned within the period specified will be deleted.
* Log Archive - The logs of previous clear down runs.
* Exceptions - Exception events raised from RDT actions.
* Activities - Activity journals of each RDT.
* Deleted Records - Any records marked as deleted (See WCS Settings tab)
* Incoming Log - The next three are cleared for the same period. They are the logs of all transmissions in the WCS.
* Outgoing Log
* Error log

==== Admin Defaults ====
If a user logs on to this program (WCS Maintenance) without having a group set for them, this screen maintains the options available for the user to access.

A list of available modules is shown each with a tick or cross against the module. A tick designates that the module is available, a cross, unavailable. Either double clicking on the item or right clicking, then selecting the appropriate availability can change the options.

Related Topics:

Users Maintenance

Groups Maintenance

Owners Maintenance

Warehouse Maintenance

==== Maintenance Settings ====
This allows you to maintain locations and lists for files used specifically by this program. The options are:

* Default Criteria Templates Folder - Criteria files for use in the Reprioritisation screens.
* Default Report Files Folder - Compiled reports.
* Default Reports Folder - Text files saved from reports will be saved here.

Each of these options includes a browse button, to allow you to pick the area Explorer-style. Each also has a default area.

A recent file list is displayed, showing all the WCS databases accessed by the program. The initial screen uses this when logging on the program. This can be switched off by un-checking the ‘Show File List At Startup’ box. To clear the list, press the ‘Clear List’ button.

Related Topics:

Selection Templates

Run Report

View Report

==== Message Types ====
This tab allows you to maintain the queue settings for Oracle systems.

* Incoming Queue
* Agent

Additionally, the queues available in the WMS should be set here, using the grid provided.

== Reports Menu ==
Menu Items:

Run Report

View Report

=== Run Report ===
This option shows you a screen of all registered reports in the WCS system. Double clicking on a report name will run the selection criteria screen. This allows you to enter the required criteria to select data for the report.

If you have a default company and warehouse, and the report requires these for selection, they will already be set to your defaults, otherwise they will be set to ‘*’ (asterisk), the wildcard character.

If you want to select all the data for that criterion, simply enter the wildcard character at the prompt. All fields can be set to the wildcard character.

Dates can be defaulted using the wildcard character, or set in a different way. If you enter ‘+’ (plus) and then a number, the date entered will be the number of days specified added to today’s date e.g. +15 will ad 15 days to today’s date. You can also enter ‘-‘ (minus) to take days away.

Once all criteria have been entered, the report will be run using the default report destination parameters.

Right clicking on a report will allow you to change the selection criteria and the destination parameters of the report, if the report writing option is available in your version of the WCS. Right clicking on an empty area of the window will allow you to create a new WCS report, if the report writing option is available in your version of the WCS.

=== View Report ===
View report allows you to see any reports saved as files. The WCS will edit the report in the Windows editor associated to the report type.

== SD Maintenance Menu ==
Menu Items:

Users Maintenance

Groups Maintenance

Warehouse Maintenance

Owners Maintenance

Aisles Maintenance

P&D Maintenance

RDT ID Maintenance

Printers Maintenance

Location Truck Checker

Activities Enquiry

Exceptions Enquiry

Truck Enquiry

Reason Code Enquiry

Pallet Type Enquiry

Update Truck Moves Seq

=== Users Maintenance ===
This is the Users Maintenance screen. This allows you to maintain system settings per user.

Users are partially maintained by the WMS, sending data records when an employee is added or deleted. The data sent by the WMS includes the company and warehouse, the employee ID, the description and the shift number. These can all be changed on this screen if desired.

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

This screen allows you to create a password for the user, if required, and create a link to a set of system parameters, via a group ID.

The screen automatically displays all the employees for your default company and warehouse. Changing your company and warehouse will close this screen. When it is next opened, it will display details on your new default company and warehouse. The Refresh button will also check for the new company code and warehouse id.

A lookup is provided for groups, so that you can pick your required group from the list. Once selected, a description is displayed for reference.

If you want to see the set-up of the group you have chosen, press the Edit Group button. You will be taken to the Groups Maintenance screen. You will only be shown the group you have chosen. You can make changes here.

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 user, the data will be displayed.

To navigate to other users 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 user, 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.

‘Works Only in Aisle’: These parameters affect 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.

The Supervisor check box allows the user some additional functionality within the maintenance functions - see Pallet Movement Maintenance for details. It also allows the user to clear locked users in some RDT screens.

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.

Related Topics

Groups Maintenance

Change Warehouse

Lookup Screens

ToolBars

=== Groups Maintenance ===
This is the Groups Maintenance screen. This allows you to maintain system settings for use on the Users Maintenance screen.

Users are partially maintained by the WMS, sending data records when an employee is added or deleted. The data sent by the WMS includes the company and warehouse, the employee ID, the description and the shift number. 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.

The explorer shows all the rules that apply at this level. To change a value, simply find the rule you wish to change and change the value.

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 group, 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 group, the data will be displayed.

To navigate to other groups 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 group, 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. You will only be allowed to delete groups records that are not currently in use.

Related Topics

Lookup Screens

ToolBars

Rules Maintenance

=== Warehouse Maintenance ===
This screen allows you to modify the system and default user settings of the Warehouse.

The screen has several tabs, allowing you to modify settings affecting different broad areas of the system:

The following is a description of the contents of the various settings that can be changed, loosely grouped by area, with some additional elements in greater detail.

'''General'''

Parameters that affect the way the system runs for the warehouse.

The ‘Action Password’ is prompted for whenever any modules are password-protected on the RDT.

The Aisle, Bay and Level lengths are used by the WCS to extract the data correctly from the location codes, so that the system can decide how to prioritise the tasks in the warehouse. These must replicate the values on the WMS, or the system will become unreliable when sending users to the next task.

‘Task Identifier’ controls how the RDT identifies individual pallets in the warehouse. The values are:

By Stock Code - the RDT modules will prompt for Location Code, Owner and Stock code.

By Customer’s Pallet Id - The RDT modules will prompt for Owner and Customer’s Pallet Id.

By System Pallet Id - The RDT modules will prompt for the WMS System Pallet Id.

The ‘Check Digits’ flag controls how the user identified that they are at a particular location. The RDT will either prompt for the user to scan or enter Check Digits for each location (enabled), scan or enter the location code (disabled) or either scan the location code or enter the check digits (Combo Check).

The ‘Move Efficient’ flag controls how tasks are assigned to each user in the warehouse. This is either by Priority/Location sequence, or simple by location sequence.

The ‘Block Stack’ flag controls whether pallets may be exchanged for others in the same location in the warehouse.

The ‘Exchange Replen’ flag controls whether, if the warehouse is set as Block Stack, whether replenishment moves can also be exchanged.

The ‘Allow Task Exchange’ flag controls whether the WCS looks for outstanding tasks in the WCS database before requesting the WMS to exchange a pallet.

The ‘Seamless Exchange’ flag controls whether the user must request to exchange a pallet with the Error key, or whether the exchange occurs seamlessly.

The ‘Mixed Stock’ flag controls whether the WCS allows pallets of mixed stock in the warehouse.

‘Customer Pallet No’ controls whether the RDT system will prompt for Customer Pallet Ids for pallets held in the warehouse.

The ‘WCS Generate Replenishment’ flag controls whether the WCS attempts to generate select replenishments via an Ad Hoc Move, or whether the WMS will reply with a move instead. Note: This should be left as enabled.

The ‘RDT Pop-up description’ flag controls whether the RDT automatically pops up a description of the Stock upon receipt and pick.

‘Measure Quantity’ and ‘Weights’ control whether the system prompts for Measure Quantities or Weights for pallets in the warehouse.

The ‘Multi-UOM processing’ flag control whether the RDT prompts for cases and units.

The flags ‘Pallet Enquiry Print Labels’ and ‘WCS Pallet Enquiry Label Format’ rules control whether the RDT pallet enquiry function is allowed to print labels, and what label format to use.

'''RDT Modules'''

Default modules allowed to RDT users, if the users are not assigned to a group. Please note: Some of these modules are bespoke and require certain WMS system set-up to be enabled. Please check your documentation as to which modules should be enabled.

'''Receipt'''

Parameters that affect the running of a Receipt module in the warehouse.

The ‘Receipt Type’ flag governs how the RDT Receipt module works on the RDT. ‘Check Receipt’ is used when the receipts are advised to a pallet detail level, and ‘Blind Receipt’ is when the receipts are advised to a stock detail level.

The ‘Selection Type’ flag governs how the RDT prompts for the Receipt you are receiving stock against. You can either enter the WMS reference (By GRN number) or the supplier’s reference (By Advice Note).

The ‘RDT Damages’ flag allows RDT Receipt users to specify stock as damaged.

The ‘Enter WMS Rotation’ flag allows the user to enter WMS Rotation during Goods Receipt.

The ‘Default Pallet Type’ flag controls whether the RDT prompts for a default pallet type to assign to all the pallets being received on a GRN in one session.

The ‘Enter Receipt Type’ flag controls whether the RDT user must enter a valid Receipt Type for the GRN.

The ‘Echo Putaway Location’ flag controls whether the RDT receipt process displays the location to which the pallet will be located, after the pallet is received.

The ‘Print Labels’ flag controls where/if pallet labels are printed during the receipt process. If the WCS is printing receipt labels, the flag ‘WCS Receipt Label Format’ defines the format being used.

The ‘Additional Pallets’ flag governs whether the RDT Receipt module allows the user to enter pallets that have not been advised by the WMS. This only affects Receipts that have been advised to a pallet detail level (Check Receipts).

The ‘Single Scan Entry’ flag governs whether the RDT Receipt process prompts for a single barcode scan when adding additional pallets. Please Note: As the single barcode can be in many formats for clients, this feature should only be enabled if the WCS has been modified to work with your Single Barcode format.

Next comes a number of validation checks that can be performed during RDT Goods Receipt. Those flags are:

* Receipt Pallet Count Check - The action the RDT is to take when the number of pallets received for a stock code is exceeded.
* Receipt Total Qty Stock Check - The action the RDT is to take when the total quantity of a stock code received is exceeded.
* Receipt Standard Qty Check (Stock) - The action the RDT is to take when a stock code is received with a non-standard pallet quantity.
* Receipt Pallet Qty Check (Pallet) - The action the RDT is to take when a pallet is received with a quantity that is not that preadvised. This supersedes the previous check.
* Receipt Non-Advised Stock - The action the RDT is to take when the user attempts to receive a stock code that was not preadvised.

The flags can have several values assigned to them, with different effects:

* No Check - No action taken.
* Informational Message - A message is displayed on the RDT, but the user is allowed to continue.
* Error - A message is displayed on the RDT and the user is not allowed to continue.
* Authorisation Required - A message is displayed on the RDT. The user is then required to obtain authorisation from a supervisor user to continue.

The ‘Enter Eurodate’ flag controls whether the user can enter a Eurodate instead of a manufacture date during the Receipt process. The ‘Enter Dates’ flag must also be enabled for this flag to work. Please Note: Only some Eurodate formats are supported. Ensure yours are before enabling this flag.

The ‘Enter Layers’ flag controls whether the RDT Receipt process prompts for the user to enter number of layers and loose cases on a pallet, rather than just the number of cases. Please Note: The WMS must be set up to allow the entry of layers, and to send the data to the WCS when the receipt is preadvised. If not, this flag should be disabled.

'''Putaway/Moves'''

The ‘Multi-pallet Putaway’ flag governs whether the RDT putaway process allows the user to scan more than one pallet to locate at a time.

The ‘Enable Extended Reposition Validation’ is an extended check added to putaways when the pallets are being repositioned.

The ‘Request Putaway Details at Scan’ flag controls whether the RDT putaway process requests a location for the pallet at the time of scanning by the putaway driver, rather than when the pallet is received. Please Note: The WMS’s putaway algorithm must support this type of processing for this flag to be enabled.

The ‘Reposition’ and ‘Cancellation’ flags control whether the RDT is allowed to reposition or cancel Move tasks in the warehouse. These functions can be password-protected.

'''Pick/Post Picking Activities'''

Parameters that affect the running of a Pick module in the warehouse.

The ‘Pick By’ flag controls what the RDT prompts for as confirmation that the correct item has been found for picking.

The ‘Continuous Part Picking’ flag controls whether the user is allowed to continue picking cases of other stock codes on to the same despatch pallet. If enabled, the user is prompted whether the pallet should be taken to the marshalling location, or to continue to the next case pick.

The ‘Pick Into Containers’ flag controls whether RDT Part Picking prompts for Picking Container IDs when part-picking.

The ‘Lost Label’ flag controls whether the user is allowed to confirm a picked pallet by visually checking the details of the pallet (stock code, batch, etc), rather than simply scanning the palled ID or stock code. This is optional.

‘Pick Location Error’ allows the user to cancel a Part Pick when they reach the pick location, before they are told to pick the pallet. This is to allow for damaged pick faces where stock is unavailable. This functionality can be password-protected.

The ‘Residual Stock Balance Enquiry’ flag controls whether the WCS checks the available quantity on the WMS pallet record at the time of picking, to ensure that the most up-to-date information is available to the picker at all times. This option can be password-protected.

If the ‘Use WMS Rotation’ 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.

The ‘Picker Replens’ flag controls whether the RDT user is allowed to pick up the replenishment move to the pick face for the pick they are currently completing. This functionality is not compatible with Pick Dependencies.

The ‘Pick Dependencies’ flag controls whether Part Picks are available to the pickers if a corresponding replenishment move is on the WCS. If enabled, the pick is not available.

The ‘Replen Dependency’ flag controls whether the WCS allows only one move into a specific location to be available to RDT users at a time.

The ‘Pick In Sequence’ rule controls the sequence orders are released for picking. This is based on the Drop sequence, interfaced from the WMS.

The ‘Pick Page Allocation’ flag controls how the WCS allocates Part Pick tasks to the users. ‘By Aisle’ means that the users are given tasks for an aisle for the current order or load.

‘Concurrent Picks’ controls whether the RDT Part Picking module allows the users to pick several orders or loads at the same time. This functionality has been enabled for use when Loads are being picked rather than Orders.

The ‘Lock Pick Header’ flag controls whether the RDT Full pallet picking option locks all picks for his area to him, or whether it would allow many users to access these picks.

The ‘Consolidation Group’ flag controls how the stock is consolidated during part picking.

The ‘Force Sky Picking’ rule controls whether part pick tasks from bulk area treated as sky picks.

The ‘Print Despatch Labels’ flag controls whether the WCS prints labels for the stock picked in the Part Picking module. The format used for the labels is defined in the ‘WCS Despatch Label Format’ field following. Clicking on the button shows an ‘Open File’ dialogue, allowing you to pick the format required. The format will have been created by OBS specifically for your use. The time when these labels are printed is controlled by the ‘Pick Label Prompt’ rule.

The ‘User Select Pick Location’ rule controls whether the user is allowed to specify the location from which to start picking.

The ‘Deconsolidation Method’ flag controls whether Deconsolidation tasks are processed by the WCS. The rule ‘Ad Hoc Deconsolidation’ controls whether deconsolidation tasks are sequenced manually or automatically by the system.

The ‘Loading Method’ flag controls whether the warehouse is loading pallets after picking, and the method by which loading is done.

'''Dual Cycling'''

Parameters that affect the running of Dual Cycling in the warehouse, and whether it is allowed.

‘Enable Dual Cycling’ enables the use of Dual Cycling in the warehouse. If the flag is enabled, other modules are made available to RDT users that interleave tasks in the most efficient way.

The ‘NADC Crossover Method’ flag controls how the RDT crosses over to another narrow aisle when in Narrow Aisle Dual Cycling (NADC). The values are:

* Manual - The RDT user chooses when to change aisle.
* Threshold - the RDT crosses over to complete moves higher than the threshold priority (‘NADC Threshold Priority’)
* Weighting - Future development - should not be enabled.

The ‘Send Aisle Status’ flag governs whether the WCS informs the WMS when Aisles are currently occupied with Trucks. For some systems, this can affect which locations are suggested for putaway. This message is only sent if the aisles are designated as Narrow Aisles, a parameter entered on Aisles Maintenance.

The ‘NADC Aisle Lock’ rule controls the point at which an aisle is locked to prevent other RDTs using the aisle

The ‘RDT DC Aisle Selection’ flag controls whether an RDT user is allowed to select the aisle range in which to work when using Narrow Aisle Dual Cycling. If the flag is enabled, the user is prompted for an aisle range in which to work. This range will default to the values entered against the user’s Employee Id on the Users Maintenance screen. If the flag is disabled, the user will not be given the opportunity to change their allocated range. In this instance, a range must be entered for the user.

The ‘NADC Skip Putaway’ flag controls whether an RDT NADC user is allowed to skip a putaway move and go straight back to picking from the aisle again.

Other flags on this screen are either for system use only, or are for future development. These should not be changed unless specifically instructed to do so by the OBS team.

'''Default Locations'''

Some default locations used by the system in some modules.

You can modify values on each tab by clicking on the relevant tab and changing the values in the required fields.

To choose the warehouse you want to look at or change, use the scrollbar on the bottom of the form to navigate to the record you want, or click on the lookup icon on the toolbar. This will display a screen of all the warehouses set up in the system.

You can get the data from the database again by clicking on the refresh button on the toolbar.

When you have completed changing the values, save the data by clicking on the Save button on the toolbar. It is not necessary to save changes in between moving from tab to tab.

'''Bespoke'''

Bespoke rules have been created for sites to control specific functionality for those sites only and are unlikely to be used anywhere else.

‘Bespoke Site Rule’ is a broad rule used to control the various site-specific rules created in the past under one value. The value of this rule is normally the company or site running the system.

The ‘Bespoke Kraft Batch’ rule controls extraction of batch data for Kraft.

The ‘Pick by Carton’ functionality replaces certain parts of the normal part picking functionality, by requiring the user to scan a stock code on each individual carton, as they are placed on the despatch pallet. This functionality requires many parameters to be set up for the warehouse, and must be enabled only by the WCS support team.

The ‘Encoded Sell-by dates’ flag controls whether sell-by dates are entered encoded into the system.

The ‘Allow Overpicking’ rule allows RF users to pick more than the requested amount.

The ‘Batch Delivery’ flag enables some processing to link to a bespoke delivery system.

See also:

Lookup Screens

ToolBars

Aisles Maintenance

Users Maintenance

Rules Maintenance

Barcode Maintenance

=== Owners Maintenance ===
This screen allows you to see the owners set up on the system, flags specific to the Owner, plus any rules set up for the Owner.

This maintenance form works very similarly to the Warehouses maintenance. All warehouse rules are replicated at an Owner level. Therefore, please see the warehouses maintenance section to see a description of the rules maintained. Any specific Owner rules and screen-specific functionality is listed in this section.

To set up rules for an Owner, the Owner must be set to Restrictive. This means that only certain members of the workforce can work for this Owner, as they will be allowed to operate in a different way to the rest of the warehouse.

Once the Owner is set to Restrictive, rules will be generated and you will be allowed to modify them.

An owner that is not restrictive inherits the rules of the warehouse. Therefore, any RDT users working for owners that are non-restrictive will get their settings from the Warehouse they logged in as, not the Owner. Additionally, they will also be given work to complete for other non-restrictive Owners.

See also:

Warehouse Maintenance

Lookup Screens

ToolBars

Rules Maintenance

Barcode Maintenance

=== Barcode Maintenance ===
This screen allows the users to define what barcodes will be extracted from UCC/EAN-128 barcodes at receipt of pallets into the system.

Click on the items required and save using the button provided.

See also:

Warehouse Maintenance

Owners Maintenance

=== Aisles Maintenance ===
This screen allows you to modify or add aisles for the warehouse.

To add new records, press the new button on the toolbar. Once you have entered your new aisle, 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 aisle, the data will be displayed.

To navigate to other aisles 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 an aisle, you may wish to change some parts of it. Simply click on your chosen field and edit it. Some fields have lookups enabled on them, denoted by the ‘!’ button to the right. Just click on this item to see a list of compatible data to enter here.

If aisle sequences or certain parameters are changed, the program will re-calculate the order of tasks in the warehouse for you.

Once you have made all your changes, press the save or OK button to save your data.

Related Topics:

Update Truck Moves Seq

=== P&D Maintenance ===
This screen allows you to modify or add P&Ds for the warehouse.

To add new records, press the new button on the toolbar. Once you have entered your new P&D 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 P&D, the data will be displayed.

To navigate to other P&D’s 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 P&D, 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 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.

=== RDT ID Maintenance ===
This screen allows you to modify RDT Ids in the system.

This is an optional setup 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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

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 aisle, the data will be displayed.

To navigate to other records 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 record, 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 button or OK button to save your data.

To delete a record, press the delete button on the toolbar, then confirm through the popup dialogue. You will only be allowed to delete RDT records that are not currently in use.

=== Printers Maintenance ===
This is the Printers maintenance screen. This allows you to change the name associated to a network printer.

Printers can be either networked windows printers, or direct TVP/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.

You can test a connection to a TCP/IP printer using the test connections and test file buttons. You may also identify block markers and characters for the file.

Related Topics

Lookup Screens

ToolBars

=== Location Truck Checker ===
This screen allows you to check which trucks are available to move between specified location types.

Click on a location type on the two boxes. Once you have chosen your location types to check, click the Check button. This will show you the compatible trucks between the two location types.

=== Activities Enquiry ===
This screen allows you to enquire on the RDT Activities file, showing all tasks completed by RDT users.

The form has two views, a detail/select view, and a grid view.

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Exceptions Enquiry ===
This screen allows you to enquire on the Exceptions file, showing all tasks completed with exceptions by RDT users.

The form has two views, a detail/select view, and a grid view.

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Truck Enquiry ===
This option is used to view the Truck Types standing data, sent from the WMS.

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 and whether the truck type is considered intrinsically safe.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Reason Code Enquiry ===
This option is used to view the Reason Codes standing data, sent from the WMS.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Pallet Type Enquiry ===
This option is used to view the Pallet Types standing data, sent from the WMS.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Update Truck Moves Seq ===
This option is used to recalculate the sequences of the truck move tasks in the WCS, with relation to certain flags against the aisle being changed.

Related Topics:

Aisles Maintenance

=== Lookup Screens ===
All the lookup screens in the WCS have the same functionality. Generally, lookup screens are used to display quantities of data where a combo box may not show all the support data that is required. A lookup will provide this extra information.

When you enter the lookup screen, the data is displayed from top to bottom, alphabetically. If required, you can scroll the data using the scrollbar on the side. When you have chosen your line, you can return to the calling screen by:

Double clicking on the line

Pressing Return on the line

Selecting the line and pressing OK

To return to the calling screen without choosing data, simply press the cancel button.

To find specific data, you can press the first letter of the data you want. This will take you to the first occurrence of the data starting with that letter. Subsequent presses of the same key will move you on to the next occurrence.

Quickly typing the first few letters of the data you are looking for will refine the search, until you have found your data.

== Windows Menu ==
This menu is a standard windows menu. It includes the options:

* Cascade
* Tile Horizontal
* Tile Vertical
* Arrange Icons

The menu also includes a list of all opened windows, so the user can switch between them easily when necessary.

== Help ==
Shortcut: F1

This menu allows you to access the help files associated with the WCS Maintenance program and windows. It can also be accessed from the toolbar using the appropriate button. The help given is context-sensitive, so you should be directed straight to help about your current screen. If direct help is not available from this screen, you will be taken to a topic list, where you can choose from all the help available.

You can also see the version of the software you are running by clicking the About menu item.

== Miscellaneous ==
=== Refresh Screen ===
The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

=== ToolBars ===
Toolbars can be modified using the standard Windows method of double clicking on a blank portion of the toolbar. This will bring up the toolbar modification window

Modifications can be made to several areas by adding from the left-hand window to the right-hand window.

You can change the position of the items in the toolbar.

You can add as many of the separator items as you like - there will always be more of them in the left-hand window!

=== Database Utilities ===
This program allows you to enquire and change any data on the system database. THIS OPTION IS ENABLE FOR SYSTEM MAINTENANCE ONLY, AND SHOULD NOT BE USED FOR ANY OTHER REASON. The DBUTILS program is separate and as such can be removed from the local functionality.

Usage of the program: Trained users only.

=== Rules Maintenance ===
This program uses a standard mechanism for maintaining rules in the system. This mechanism is described here.

The rules required are displayed in an explorer window, showing the rule groups on the left-hand pane, and the rules belonging to that group in the right-hand pane.

To find rules, click on the appropriate section in the left-hand pane. The rules will display on the right-hand pane. Should there be too many rules to display on one screen, the screen will provide a scroll-bar.

Rules can be broken down into several types:

Fixed Values - these will be displayed in a drop-down list, for you to select.

Text values - plain text for you to type the value in.

Numeric values - plain numeric values for you to type in.

Browse buttons - where the WCS requires a directory listing or file selection, a browse button is provided.

Database lookups - there the WCS requires a data value, a drop-down list is provided with the values allowed. There will also be a blank value on the list for you to select.

As each value is modified and you move to the next, the data will be saved.

Screen which contain Rules explorers:

Warehouse Maintenance

Groups Maintenance

Owners Maintenance

System Settings

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

RDT Functionality

2025-10-30T11:14:33Z

Anw: New version. Added 291596 Narrow Aisle Putaway Algorithm; 291594 Truck Type Logon Validation; 291597 Extended Putaway Reposition Validation; 292218 - Narrow Aisle Part Pick Confirmation; 292219 - Pick Exchange Amendment

{{Doc_Title
| Client = Aptean
| System = WCS
| Title = RDT Functionality Guide
| Reference = UG 106181
| Version = 11.02
| Date = 30th October 2025
| Sysver = 3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client. Function keys are standardised throughout the RDT system, consisting of:

* F1- Confirm Key
* F2- Amend Key
* F3- Add Key
* F4- Error Key
* F5- Special/Zero Key
* F7- Enquiries menu
* F8- Additional Information Key
* F9- Help Key
* F10- Return to Main Menu Key
* CLEAR- Backup key
* CRSRUP- Previous Key
* CRSRDN- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

=='''Multi-part movements'''==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="prettytable"
| #

| Source
|
|
| Destination

|-
| #

| Source
| Interim1
|
|

|-
| #

| Source
|
| Interim2
|

|-
| #

|
| Interim1
| Interim2
|

|-
| #

|
| Interim1
|
| Destination

|-
| #

|
|
| Interim2
| Destination

|}
== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="prettytable"
| '''Truck Type (Code)'''
| '''Tasks to be done'''

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="prettytable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

Wide Area Dual Cycling

Narrow Aisle Dual Cycling

Pallet Moves

Pallet Replens

Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':

Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="prettytable"
| '''Aisle'''
| '''Sequence'''

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="prettytable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="prettytable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="prettytable"
! Task
! From
! To
! Aisle

Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:

OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.

SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

=='''Owner Restrictions'''==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="prettytable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

=='''Movement Exceptions'''==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

If the 'Extended Reposition Validation' rule is set to enabled on the WCS then when a user tries to reposition a pallet, the system will perform extra validation with the WMS.

The following checks are made:
* Check that the pallet exists.
* Check that the location exists.
* Check that the pallet type of the pallet being repositioned is allowed in the location.
* Check the bonded flags of the pallet and location.
** If the pallet is bonded, check that the location is also bonded.
** If stock already exists in the location, check that the bonded flags match the bonded flag of the pallet being repositioned.
* Check that the location is available for the pallet type.
* If the location is a multi-deep location then check whether there are other pallets in the location and that they match the location validation flag setting.
* Check that the location is either a bulk location (Loc Use Type '1'), receipt location ('3'), returns location ('4'), damaged stock location ('5') or a multi-pallet location ('M') and there are no pallets which do not satisfy the location validation (Use) flag setting.
** 4 - Valid pallets contain the same stock, batch number and owner batch
** 5 - Valid pallets contain the same stock.
** 6 - Valid pallets contain the same stock and sell-by date.
** 7 - Check the last receipt location for pallets containing the same GRN and stock.
** 8 - Valid pallets contain the same stock and manufacturing date

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

=='''Multi-Pallet Locations'''==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:

Product Code

Batch

Manufacture Date

Sell-by date

GRN number

Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:

Task Exchange

Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Enhanced Pick Exchange ===
The rule 'Enhanced Pick Exchange' controls whether part pick tasks can be exchanged and also whether pick tasks can be exchanged for pallets from different locations. This also affects full-pallet picking pallet exchange.

If the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. If the ‘Enhanced Pick Exchange’ rule is set to ‘Disabled’ then the RDT will not prompt the user to enter the location of the new pallet and a ‘651’ pallet exchange enquiry message will be sent to the Calidus ''3pl'' system in the present format after the new pallet has been entered.

During full-pallet picking, if the ‘Enhanced Pick Exchange’ rule is set to ‘Enabled’, then the RDT will prompt the user to enter the location of the new pallet after entering a pallet value. This will validate the exchanged pallet with the existing one and may display errors depending on WMS validation configuration.

During part-pallet picking, if the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. After identifying the new pallet, the RDT will prompt the user to enter the location of the new pallet as the 'Enhanced Pick Exchange' rule must be set to 'Enabled' for part pallet pick tasks to be exchanged. This will validate the exchanged pallet in the same way.

The validation errors that may be displayed are:

* unknown pallet.
* pallet under stock take.
* unable to exchange replen.
* location is not a multi pallet location.
* exchanged pallet unknown.
* pallet is unavailable.
* bonded flags do not match.
* stock codes do not match.
* customer batch values do not match.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<nowiki><TEMPLATE></nowiki>

ABC Pick Label

Marshalling Location:

{MarshLoc}

<nowiki></TEMPLATE></nowiki>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:

ABC Pick Label

Marshalling Location:

MAR01A

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="prettytable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet. Enhanced pick exchange may also be enabled - see the section above for details.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

Note that, if Sky Pick is enabled, sky picks at P&D locations can be picked up, moved and completed using this module in the wide areas.

When this module is used in the Narrow Aisle areas when Sky Picking is enabled "At PND", then these sky picks will also be completed here. the process is:

* Narrow aisle truck driver retrieves the pallet from the narrow aisle bulk location and takes the pallet to the PND out location.
* Narrow aisle truck driver removed the required amount of stock from the pallet onto another pallet, entering a unique id for the new pallet so that it can be identified, and leaves this new pallet at the PND out location.
* Narrow aisle truck driver returns the remaining original pallet back to the narrow aisle source location.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:
* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

Note that, if Sky Pick is enabled "At PND", sky picks at P&D locations can be picked up, moved and completed using this module.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:

FPP- P&D to MARSH

Replen- P&D to PICK

Sky Pick- P&D to SPLIT

- SPLIT to P&D

Move - P&D to P&D

Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:

FPP- BULK to MARSH

Replen- BULK to PICK

Sky Pick- none required - only in NA

Move - BULK to BULK

Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

=='''Logging'''==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

=='''Parameter-controlled Functions'''==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

=='''RDT Messages'''==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
==='''RDT Log-on Procedure.'''===

[[Image:FunctionalityFlowChart1.png]]

#
==='''Receipts.'''===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

#
==='''Putaways.'''===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

#
==='''Full Pallet Picking.'''===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

#
==='''Part-pallet Picking.'''===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

#
==='''Pallet Moves.'''===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

#
==='''Stock Take.'''===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

#
==='''Pallet Enquiry.'''===

[[Image:FC26.PNG]]

#
==='''Location Enquiry.'''===

[[Image:FC27.PNG]]

#
==='''Movement Enquiry.'''===

[[Image:FC28.PNG]]

#
==='''Ad Hoc Movements.'''===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

#
==='''Bulk PI.'''===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

#
==='''Select Moves.'''===

[[Image:FC33.PNG]]

#
==='''Loading by Carton.'''===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

#
==='''Shipment Pallet processes.'''===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

#
==='''Select Replenishment.'''===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

#
==='''Serial Number Capture at Goods Receipt.'''===

[[Image:FC40.PNG]]

#
==='''Serial Number Capture at Despatch.'''===

[[Image:FC41.PNG]]

#
==='''Combined Split.'''===

[[Image:FC42.PNG]]

#
==='''Ad Hoc Putaway.'''===

[[Image:FC43.PNG]]

#
==='''Cherry Picking.'''===

[[Image:FC44.PNG]]

#
==='''Deconsolidation.'''===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

#
==='''Despatch by Order.'''===

[[Image:FC49.PNG]]

#
==='''Loading (by Picking Container).'''===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

RDT Functionality

2025-10-30T11:05:50Z

Anw: 292219 - Pick Exchange Amendment

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=RDT Functionality Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client. Function keys are standardised throughout the RDT system, consisting of:

* F1- Confirm Key
* F2- Amend Key
* F3- Add Key
* F4- Error Key
* F5- Special/Zero Key
* F7- Enquiries menu
* F8- Additional Information Key
* F9- Help Key
* F10- Return to Main Menu Key
* CLEAR- Backup key
* CRSRUP- Previous Key
* CRSRDN- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

=='''Multi-part movements'''==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="prettytable"
| #

| Source
|
|
| Destination

|-
| #

| Source
| Interim1
|
|

|-
| #

| Source
|
| Interim2
|

|-
| #

|
| Interim1
| Interim2
|

|-
| #

|
| Interim1
|
| Destination

|-
| #

|
|
| Interim2
| Destination

|}
== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="prettytable"
| '''Truck Type (Code)'''
| '''Tasks to be done'''

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="prettytable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

Wide Area Dual Cycling

Narrow Aisle Dual Cycling

Pallet Moves

Pallet Replens

Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':

Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="prettytable"
| '''Aisle'''
| '''Sequence'''

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="prettytable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="prettytable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="prettytable"
! Task
! From
! To
! Aisle

Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:

OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.

SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

=='''Owner Restrictions'''==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="prettytable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

=='''Movement Exceptions'''==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

If the 'Extended Reposition Validation' rule is set to enabled on the WCS then when a user tries to reposition a pallet, the system will perform extra validation with the WMS.

The following checks are made:
* Check that the pallet exists.
* Check that the location exists.
* Check that the pallet type of the pallet being repositioned is allowed in the location.
* Check the bonded flags of the pallet and location.
** If the pallet is bonded, check that the location is also bonded.
** If stock already exists in the location, check that the bonded flags match the bonded flag of the pallet being repositioned.
* Check that the location is available for the pallet type.
* If the location is a multi-deep location then check whether there are other pallets in the location and that they match the location validation flag setting.
* Check that the location is either a bulk location (Loc Use Type '1'), receipt location ('3'), returns location ('4'), damaged stock location ('5') or a multi-pallet location ('M') and there are no pallets which do not satisfy the location validation (Use) flag setting.
** 4 - Valid pallets contain the same stock, batch number and owner batch
** 5 - Valid pallets contain the same stock.
** 6 - Valid pallets contain the same stock and sell-by date.
** 7 - Check the last receipt location for pallets containing the same GRN and stock.
** 8 - Valid pallets contain the same stock and manufacturing date

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

=='''Multi-Pallet Locations'''==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:

Product Code

Batch

Manufacture Date

Sell-by date

GRN number

Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:

Task Exchange

Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Enhanced Pick Exchange ===
The rule 'Enhanced Pick Exchange' controls whether part pick tasks can be exchanged and also whether pick tasks can be exchanged for pallets from different locations. This also affects full-pallet picking pallet exchange.

If the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. If the ‘Enhanced Pick Exchange’ rule is set to ‘Disabled’ then the RDT will not prompt the user to enter the location of the new pallet and a ‘651’ pallet exchange enquiry message will be sent to the Calidus ''3pl'' system in the present format after the new pallet has been entered.

During full-pallet picking, if the ‘Enhanced Pick Exchange’ rule is set to ‘Enabled’, then the RDT will prompt the user to enter the location of the new pallet after entering a pallet value. This will validate the exchanged pallet with the existing one and may display errors depending on WMS validation configuration.

During part-pallet picking, if the user selects the option to exchange the pallet then the RDT will prompt the user to identify the new pallet. After identifying the new pallet, the RDT will prompt the user to enter the location of the new pallet as the 'Enhanced Pick Exchange' rule must be set to 'Enabled' for part pallet pick tasks to be exchanged. This will validate the exchanged pallet in the same way.

The validation errors that may be displayed are:

* unknown pallet.
* pallet under stock take.
* unable to exchange replen.
* location is not a multi pallet location.
* exchanged pallet unknown.
* pallet is unavailable.
* bonded flags do not match.
* stock codes do not match.
* customer batch values do not match.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<nowiki><TEMPLATE></nowiki>

ABC Pick Label

Marshalling Location:

{MarshLoc}

<nowiki></TEMPLATE></nowiki>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:

ABC Pick Label

Marshalling Location:

MAR01A

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="prettytable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet. Enhanced pick exchange may also be enabled - see the section above for details.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

Note that, if Sky Pick is enabled, sky picks at P&D locations can be picked up, moved and completed using this module in the wide areas.

When this module is used in the Narrow Aisle areas when Sky Picking is enabled "At PND", then these sky picks will also be completed here. the process is:

* Narrow aisle truck driver retrieves the pallet from the narrow aisle bulk location and takes the pallet to the PND out location.
* Narrow aisle truck driver removed the required amount of stock from the pallet onto another pallet, entering a unique id for the new pallet so that it can be identified, and leaves this new pallet at the PND out location.
* Narrow aisle truck driver returns the remaining original pallet back to the narrow aisle source location.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:
* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

Note that, if Sky Pick is enabled "At PND", sky picks at P&D locations can be picked up, moved and completed using this module.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:

FPP- P&D to MARSH

Replen- P&D to PICK

Sky Pick- P&D to SPLIT

- SPLIT to P&D

Move - P&D to P&D

Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:

FPP- BULK to MARSH

Replen- BULK to PICK

Sky Pick- none required - only in NA

Move - BULK to BULK

Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

=='''Logging'''==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

=='''Parameter-controlled Functions'''==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

=='''RDT Messages'''==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
==='''RDT Log-on Procedure.'''===

[[Image:FunctionalityFlowChart1.png]]

#
==='''Receipts.'''===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

#
==='''Putaways.'''===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

#
==='''Full Pallet Picking.'''===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

#
==='''Part-pallet Picking.'''===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

#
==='''Pallet Moves.'''===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

#
==='''Stock Take.'''===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

#
==='''Pallet Enquiry.'''===

[[Image:FC26.PNG]]

#
==='''Location Enquiry.'''===

[[Image:FC27.PNG]]

#
==='''Movement Enquiry.'''===

[[Image:FC28.PNG]]

#
==='''Ad Hoc Movements.'''===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

#
==='''Bulk PI.'''===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

#
==='''Select Moves.'''===

[[Image:FC33.PNG]]

#
==='''Loading by Carton.'''===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

#
==='''Shipment Pallet processes.'''===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

#
==='''Select Replenishment.'''===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

#
==='''Serial Number Capture at Goods Receipt.'''===

[[Image:FC40.PNG]]

#
==='''Serial Number Capture at Despatch.'''===

[[Image:FC41.PNG]]

#
==='''Combined Split.'''===

[[Image:FC42.PNG]]

#
==='''Ad Hoc Putaway.'''===

[[Image:FC43.PNG]]

#
==='''Cherry Picking.'''===

[[Image:FC44.PNG]]

#
==='''Deconsolidation.'''===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

#
==='''Despatch by Order.'''===

[[Image:FC49.PNG]]

#
==='''Loading (by Picking Container).'''===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

RDT Functionality

2025-10-30T10:54:23Z

Anw: 292218 - Narrow Aisle Part Pick Confirmation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=RDT Functionality Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client. Function keys are standardised throughout the RDT system, consisting of:

* F1- Confirm Key
* F2- Amend Key
* F3- Add Key
* F4- Error Key
* F5- Special/Zero Key
* F7- Enquiries menu
* F8- Additional Information Key
* F9- Help Key
* F10- Return to Main Menu Key
* CLEAR- Backup key
* CRSRUP- Previous Key
* CRSRDN- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

=='''Multi-part movements'''==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="prettytable"
| #

| Source
|
|
| Destination

|-
| #

| Source
| Interim1
|
|

|-
| #

| Source
|
| Interim2
|

|-
| #

|
| Interim1
| Interim2
|

|-
| #

|
| Interim1
|
| Destination

|-
| #

|
|
| Interim2
| Destination

|}
== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="prettytable"
| '''Truck Type (Code)'''
| '''Tasks to be done'''

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="prettytable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

Wide Area Dual Cycling

Narrow Aisle Dual Cycling

Pallet Moves

Pallet Replens

Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':

Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="prettytable"
| '''Aisle'''
| '''Sequence'''

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="prettytable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="prettytable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="prettytable"
! Task
! From
! To
! Aisle

Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:

OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.

SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

=='''Owner Restrictions'''==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="prettytable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

=='''Movement Exceptions'''==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

If the 'Extended Reposition Validation' rule is set to enabled on the WCS then when a user tries to reposition a pallet, the system will perform extra validation with the WMS.

The following checks are made:
* Check that the pallet exists.
* Check that the location exists.
* Check that the pallet type of the pallet being repositioned is allowed in the location.
* Check the bonded flags of the pallet and location.
** If the pallet is bonded, check that the location is also bonded.
** If stock already exists in the location, check that the bonded flags match the bonded flag of the pallet being repositioned.
* Check that the location is available for the pallet type.
* If the location is a multi-deep location then check whether there are other pallets in the location and that they match the location validation flag setting.
* Check that the location is either a bulk location (Loc Use Type '1'), receipt location ('3'), returns location ('4'), damaged stock location ('5') or a multi-pallet location ('M') and there are no pallets which do not satisfy the location validation (Use) flag setting.
** 4 - Valid pallets contain the same stock, batch number and owner batch
** 5 - Valid pallets contain the same stock.
** 6 - Valid pallets contain the same stock and sell-by date.
** 7 - Check the last receipt location for pallets containing the same GRN and stock.
** 8 - Valid pallets contain the same stock and manufacturing date

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

=='''Multi-Pallet Locations'''==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:

Product Code

Batch

Manufacture Date

Sell-by date

GRN number

Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:

Task Exchange

Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<nowiki><TEMPLATE></nowiki>

ABC Pick Label

Marshalling Location:

{MarshLoc}

<nowiki></TEMPLATE></nowiki>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:

ABC Pick Label

Marshalling Location:

MAR01A

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="prettytable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

Note that, if Sky Pick is enabled, sky picks at P&D locations can be picked up, moved and completed using this module in the wide areas.

When this module is used in the Narrow Aisle areas when Sky Picking is enabled "At PND", then these sky picks will also be completed here. the process is:

* Narrow aisle truck driver retrieves the pallet from the narrow aisle bulk location and takes the pallet to the PND out location.
* Narrow aisle truck driver removed the required amount of stock from the pallet onto another pallet, entering a unique id for the new pallet so that it can be identified, and leaves this new pallet at the PND out location.
* Narrow aisle truck driver returns the remaining original pallet back to the narrow aisle source location.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:
* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

Note that, if Sky Pick is enabled "At PND", sky picks at P&D locations can be picked up, moved and completed using this module.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

Sky Picking is supported in this module, when Sky Picking is configured to be 'At PND'. In this case, the RDT user will then complete the part pick task using the DC Out module in the same manner as using the Picking module, i.e. scan source location, scan pallet id, scan PND location, enter picking container id, enter quantity, return pallet to the original location and scan source location again.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:

FPP- P&D to MARSH

Replen- P&D to PICK

Sky Pick- P&D to SPLIT

- SPLIT to P&D

Move - P&D to P&D

Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:

FPP- BULK to MARSH

Replen- BULK to PICK

Sky Pick- none required - only in NA

Move - BULK to BULK

Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

=='''Logging'''==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

=='''Parameter-controlled Functions'''==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

=='''RDT Messages'''==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
==='''RDT Log-on Procedure.'''===

[[Image:FunctionalityFlowChart1.png]]

#
==='''Receipts.'''===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

#
==='''Putaways.'''===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

#
==='''Full Pallet Picking.'''===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

#
==='''Part-pallet Picking.'''===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

#
==='''Pallet Moves.'''===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

#
==='''Stock Take.'''===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

#
==='''Pallet Enquiry.'''===

[[Image:FC26.PNG]]

#
==='''Location Enquiry.'''===

[[Image:FC27.PNG]]

#
==='''Movement Enquiry.'''===

[[Image:FC28.PNG]]

#
==='''Ad Hoc Movements.'''===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

#
==='''Bulk PI.'''===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

#
==='''Select Moves.'''===

[[Image:FC33.PNG]]

#
==='''Loading by Carton.'''===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

#
==='''Shipment Pallet processes.'''===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

#
==='''Select Replenishment.'''===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

#
==='''Serial Number Capture at Goods Receipt.'''===

[[Image:FC40.PNG]]

#
==='''Serial Number Capture at Despatch.'''===

[[Image:FC41.PNG]]

#
==='''Combined Split.'''===

[[Image:FC42.PNG]]

#
==='''Ad Hoc Putaway.'''===

[[Image:FC43.PNG]]

#
==='''Cherry Picking.'''===

[[Image:FC44.PNG]]

#
==='''Deconsolidation.'''===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

#
==='''Despatch by Order.'''===

[[Image:FC49.PNG]]

#
==='''Loading (by Picking Container).'''===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

RDT Functionality

2025-10-30T10:41:43Z

Anw: 291597 Extended Putaway Reposition Validation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=RDT Functionality Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client. Function keys are standardised throughout the RDT system, consisting of:

* F1- Confirm Key
* F2- Amend Key
* F3- Add Key
* F4- Error Key
* F5- Special/Zero Key
* F7- Enquiries menu
* F8- Additional Information Key
* F9- Help Key
* F10- Return to Main Menu Key
* CLEAR- Backup key
* CRSRUP- Previous Key
* CRSRDN- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

=='''Multi-part movements'''==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="prettytable"
| #

| Source
|
|
| Destination

|-
| #

| Source
| Interim1
|
|

|-
| #

| Source
|
| Interim2
|

|-
| #

|
| Interim1
| Interim2
|

|-
| #

|
| Interim1
|
| Destination

|-
| #

|
|
| Interim2
| Destination

|}
== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="prettytable"
| '''Truck Type (Code)'''
| '''Tasks to be done'''

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="prettytable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

Wide Area Dual Cycling

Narrow Aisle Dual Cycling

Pallet Moves

Pallet Replens

Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':

Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="prettytable"
| '''Aisle'''
| '''Sequence'''

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="prettytable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="prettytable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="prettytable"
! Task
! From
! To
! Aisle

Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:

OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.

SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

=='''Owner Restrictions'''==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="prettytable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

=='''Movement Exceptions'''==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

If the 'Extended Reposition Validation' rule is set to enabled on the WCS then when a user tries to reposition a pallet, the system will perform extra validation with the WMS.

The following checks are made:
* Check that the pallet exists.
* Check that the location exists.
* Check that the pallet type of the pallet being repositioned is allowed in the location.
* Check the bonded flags of the pallet and location.
** If the pallet is bonded, check that the location is also bonded.
** If stock already exists in the location, check that the bonded flags match the bonded flag of the pallet being repositioned.
* Check that the location is available for the pallet type.
* If the location is a multi-deep location then check whether there are other pallets in the location and that they match the location validation flag setting.
* Check that the location is either a bulk location (Loc Use Type '1'), receipt location ('3'), returns location ('4'), damaged stock location ('5') or a multi-pallet location ('M') and there are no pallets which do not satisfy the location validation (Use) flag setting.
** 4 - Valid pallets contain the same stock, batch number and owner batch
** 5 - Valid pallets contain the same stock.
** 6 - Valid pallets contain the same stock and sell-by date.
** 7 - Check the last receipt location for pallets containing the same GRN and stock.
** 8 - Valid pallets contain the same stock and manufacturing date

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

=='''Multi-Pallet Locations'''==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:

Product Code

Batch

Manufacture Date

Sell-by date

GRN number

Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:

Task Exchange

Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<nowiki><TEMPLATE></nowiki>

ABC Pick Label

Marshalling Location:

{MarshLoc}

<nowiki></TEMPLATE></nowiki>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:

ABC Pick Label

Marshalling Location:

MAR01A

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="prettytable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:

* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:

FPP- P&D to MARSH

Replen- P&D to PICK

Sky Pick- P&D to SPLIT

- SPLIT to P&D

Move - P&D to P&D

Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:

FPP- BULK to MARSH

Replen- BULK to PICK

Sky Pick- none required - only in NA

Move - BULK to BULK

Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

=='''Logging'''==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

=='''Parameter-controlled Functions'''==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

=='''RDT Messages'''==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
==='''RDT Log-on Procedure.'''===

[[Image:FunctionalityFlowChart1.png]]

#
==='''Receipts.'''===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

#
==='''Putaways.'''===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

#
==='''Full Pallet Picking.'''===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

#
==='''Part-pallet Picking.'''===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

#
==='''Pallet Moves.'''===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

#
==='''Stock Take.'''===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

#
==='''Pallet Enquiry.'''===

[[Image:FC26.PNG]]

#
==='''Location Enquiry.'''===

[[Image:FC27.PNG]]

#
==='''Movement Enquiry.'''===

[[Image:FC28.PNG]]

#
==='''Ad Hoc Movements.'''===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

#
==='''Bulk PI.'''===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

#
==='''Select Moves.'''===

[[Image:FC33.PNG]]

#
==='''Loading by Carton.'''===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

#
==='''Shipment Pallet processes.'''===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

#
==='''Select Replenishment.'''===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

#
==='''Serial Number Capture at Goods Receipt.'''===

[[Image:FC40.PNG]]

#
==='''Serial Number Capture at Despatch.'''===

[[Image:FC41.PNG]]

#
==='''Combined Split.'''===

[[Image:FC42.PNG]]

#
==='''Ad Hoc Putaway.'''===

[[Image:FC43.PNG]]

#
==='''Cherry Picking.'''===

[[Image:FC44.PNG]]

#
==='''Deconsolidation.'''===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

#
==='''Despatch by Order.'''===

[[Image:FC49.PNG]]

#
==='''Loading (by Picking Container).'''===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

RDT Functionality

2025-10-30T10:31:19Z

Anw: 291594 Truck Type Logon Validation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=RDT Functionality Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= INTRODUCTION =
The purpose of this document is to introduce the clients to functionality available in the RDT system. An overview is included of the functionality required and flows are included to show how these processes work.

'''Note:''' Any flowcharts shown or referenced in this document are intended only as a guide to the functionality available in the WCS. The exact functionality is largely configurable and can differ substantially from that shown. However, an effort is made to ensure that the flow charts are updated after major developments.

== Notes ==
If this document is being viewed electronically, all cross-references are in shaded blue and will take you to the reference by clicking on the item. If this document is printed in colour, the cross-references are in blue.

= RDT Concept =
The main Calidus 3PL system controls the overall data for the system.

Where warehouse movements and other truck-based tasks must be controlled, the manual system usually produces a paper-based instruction or set of instructions for the fork-list truck drivers to complete. When work is completed, the system has the data from the sheets entered in to it and the work is confirmed.

The RDT system replaces the paper-based system, by sending tasks to the RDT system, then allocating the tasks to trucks as and when they require them.

Where paper is used to issue instructions, the RDT will have instructions sent from WMS.

The system created for Calidus 3PL integrates to the main system seamlessly. The current Calidus 3PL update screens (that the RDT system replaces) can be used as backup processes, in the event of system failure. The paper-based system can also be run in parallel with the RDT system for further security. Messages can be resent both from Calidus 3PL and from the RDT system, allowing for recovery.

= WCS Structure =
The OBS RDT system has been created using relatively simple programming methods. Where code is required, this is written in Visual Basic. Where connectivity is required (both wireless and wired), third party software has been bought as programming libraries for VB, for example Wavelink for the wireless LAN. These programming modules have allowed us to put together a relatively simple solution to the communications issues ([[#RDT Messages]])
As can be seen, Wavelink controls all the communication to the RDTs and each RDT has its own control program, which Wavelink starts, whenever an RDT attempts to communicate with it. This application is written by OBS and provides the screen layouts and validation that the RDT users meet during a session.

The WCS Server controls all communications to and from the WMS, receiving outstanding tasks and sending back completed ones. It also accesses its storage database on request from the RDT control applications, which request work. All messages pass through the server at some point.

From the WMS, the interface also has a generic sender and a receiver, which must be running. They and the WCS interface communicate via socket communication using TCP/IP or via Oracle Advanced Queues.

The transmitter picks up messages from the portion of the Calidus 3PL system that has been written to send messages. These messages are packaged and sent to the socket or queue. The WCS interface picks these messages up and stores them on its task database.

The receiver picks messages up from the socket, validates them to some degree and then passes the messages to a third program, the RMP, or Route Message Processor (In the Oracle system, this is handled by the queues). This is specific to our Calidus 3PL system (as opposed to the other two that can be used generically), as the messages are interrogated to find what type of message they are, then routed to the correct processing program. These processing programs then transfer the data to the main Calidus 3PL database, in the same way that the manual screens do.

== PC Requirements ==
The WCS has been written to make the most of the available memory and processing power of the PC.

=== Hardware Requirements ===
* Best processor (normally single processor only)
* 256 Mb RAM min (512 Mb plus recommended)
* 6 Gb disk space min (20Gb over multiple disks recommended)
* Windows 2003/2000/XP/NT4 (Server preferred)
* CD-ROM
* 56K Modem and direct telephone line, or access to PC WAN via dial-up

=== Software Requirements ===
* PC Anywhere (latest version) or other Remote control software plus file transfer capabilities. OBS recommend Remote Desktop Connection with FTP Server capability.
* Wavelink StudioCOM (latest version 3.7) by Wavelink - plus licenses.
* Wavelink SNC24 (latest version 4) by Wavelink. (Only required if monitoring/administration of the wireless LAN is required).
* Wavelink Avalanche by Wavelink (Only required if the Wavelink client is to not already installed on the RDTs.

= RDT Functionality =
== RDT Logon ==
When users connect to the RDT system through their RDTs, they will be required to log in (see flow chart [[#RDT Log-on Procedure.]]). This login structure requires them to specify a Warehouse (a default company is assigned to them), a user ID, and a truck type. This information allows the WCS to decide on the information the RDT user is assigned during his working shift. The Employee code entered at log-on can only be used one at a time.

The RDT logon process may also check whether the truck type in intrinsically safe to use for that RDT.

Once the user has entered a truck type value, the logon process will retrieve the intrinsically safe values for the RDT being logged onto and the truck type entered by the user.

If the RDT is marked as intrinsically safe then the user will be able to log on as any truck type, i.e. both intrinsically safe and non-intrinsically safe truck types.

If the RDT is '''not''' marked as intrinsically safe, i.e. a standard RDT, then the user will not be able to log on as an intrinsically safe truck type and the RDT will display the error message “Logon as truck type ''X'' is not allowed on this device” where ''X'' is the truck type value entered.

The user may also choose to enter a default owner. This is used whenever the system prompts the user to enter an owner code. A description of what the owner is used for is provided in [[#Owner Restrictions]].

Depending on the warehouse chosen, the user may be prompted to enter two flags; bulk and system-directed. The first relates to whether the user is working in a narrow aisle environment (Y), or wide area (N). The second flag, system-directed, controls whether the dual cycling menu options appear for a user (Y).

Once logged in to the system, the user will be shown a main menu of available functions. The available functions can be set up against each individual user in the WCS, as can be seen in [[#Parameter-controlled Functions]].

== Function keys ==
The user is provided with help, showing them any special key presses that have an effect in the current module. A key can be pressed in some modules to display additional information requires by the user. The information displayed is bespoke to the client. Function keys are standardised throughout the RDT system, consisting of:

* F1- Confirm Key
* F2- Amend Key
* F3- Add Key
* F4- Error Key
* F5- Special/Zero Key
* F7- Enquiries menu
* F8- Additional Information Key
* F9- Help Key
* F10- Return to Main Menu Key
* CLEAR- Backup key
* CRSRUP- Previous Key
* CRSRDN- Next Key

This approach of standardised function keys gives the users familiarity with the operation of each module.

=='''Multi-part movements'''==
Whenever a movement task is raised in the system, if only certain truck types can access certain locations, the system must utilise P&D location. This type of operation leads to multi-part movements, consisting of several stages, numbered by the WCS for simplicity:

{| class="prettytable"
| #

| Source
|
|
| Destination

|-
| #

| Source
| Interim1
|
|

|-
| #

| Source
|
| Interim2
|

|-
| #

|
| Interim1
| Interim2
|

|-
| #

|
| Interim1
|
| Destination

|-
| #

|
|
| Interim2
| Destination

|}
== Movements by Truck Type ==
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.

For example, our warehouse contains five areas:

* Receipt Bays (REC)
* Marshalling/Despatch Bays (MAR)
* High Bay Narrow Aisle (NA)
* Low Bay bulk storage (BLK)
* Pick Faces (PIC)
* P&D locations (PND)

We have four truck types:

{| class="prettytable"
| '''Truck Type (Code)'''
| '''Tasks to be done'''

|-
| Reach Truck (RT)
| Moving pallets around in Low Bay; Replenishing pick faces; picking full pallets from low bay; put away pallets to Low Bay

|-
| Counter-balance (CB)
| Taking pallets from P&D locations to Marshalling; put pallets on to P&D for High Bay putaway

|-
| Picker hand cart (PK)
| Picking from pick faces and taking to marshalling

|-
| Narrow Aisle truck (NA)
| Moving full pallets around in High Bay

|}
Therefore, we set up location types as follows:

{| class="prettytable"
! Loc Type
! Trucks Allowed

|-
| REC
| RT, CB

|-
| MAR
| RT, CB, PK

|-
| NA
| NA

|-
| BLK
| RT

|-
| PIC
| RT, PK

|-
| PND
| CB, NA

|}
This set-up allows all trucks access to the location types required to do their jobs.

The set-up can be modified to allow for drivers who only have to do one job (e.g. a variant of RT that can only pick pallets to marshalling - it can't put them away, or a truck that can only do replenishments). It can also be modified to take into account certain restrictions on truck height (for example, reach trucks that can only reach 5, 6 or 7 levels high).

== Location Efficiency ==
Location efficiency in the RF system applies in many modules (listed below) when the Move Efficient rule is set to 'By Location'. Some other flags also determine whether this functionality is enabled.

When Move Efficient rule is set to 'By Location'

Wide Area Dual Cycling

Narrow Aisle Dual Cycling

Pallet Moves

Pallet Replens

Stock Replens (both when collecting items from bulk then delivering items to the pick faces)

When Pick Allocation is not set to 'By Order Page':

Part Picking

When the Move Efficient rule is set to 'By Priority', the tasks are provided to the user in priority and time sequence.

=== Set-up ===
In order for RF Location Efficiency to operate, several setup items must be completed first.

The warehouse parameters for Aisle, Bay and Level length must be set up for the WCS to know how to extract and examine the different portions of the tasks' location code.

The Aisles must be set up in Calidus 3PL-Mobile.

The aisles must be configured with the following information:

* Aisle Sequence - this must be set to indicate how close one aisle is to another. If the aisle sequences of two aisles are the same, the tasks will be mixed in together.
* Linked Aisle - in addition to aisles having the same sequence, marking the aisles as linked to another aisle ensures that the tasks are mixed together. Additionally, for Narrow Aisle Dual Cycling, both of the aisles will be marked as occupied by the RDT, if the aisles are configured as Narrow Aisles here.
* Split Faces - if this flag is set, the odd and even bays are sorted separately, ensuring that tasks on the same face are seen as closer than tasks on the opposite face.
* High End Access - if the this flag is enabled, the bay sequence within the aisle will be reversed, in that the tasks will be delivered to RDT users from high bay sequences to low bay sequences, rather than the normal default, which is low to high.

=== Process ===
Location efficiency is always subservient to Priority. If all tasks are at the same priority, the tasks will be completed in location efficient manner.

The last location the RDT user moved to is used to define where the user is for the next selection.

Aisle Sequences are chosen based on the last aisle the user was at. The aisle is chosen by calculating how close the aisle is to the current aisle. This is achieved by taking the absolute result of sequence of the current aisle from the sequence of the tasks' aisle.

So:

{| class="prettytable"
| '''Aisle'''
| '''Sequence'''

|-
| A
| 10

|-
| B
| 20

|-
| C
| 45

|-
| D
| 40

|-
| E
| 50

|}
If we have the following tasks available:

{| class="prettytable"
! Task
! From
! To

|-
| 1
| A/01/01
| C/01/01

|-
| 2
| B/01/01
| E/01/01

|-
| 3
| D/01/01
| D/99/01

|-
| 4
| C/01/01
| D/01/01

|-
| 5
| E/01/01
| A/01/01

|-
| 6
| C/02/01
| C/99/01

|}
If the user's current location is C/01/01, the relative nearness of each task (by aisle) is:

{| class="prettytable"
! Task
! From
! To
! Nearness

|-
| 1
| A/01/01
| C/01/01
| 35

|-
| 2
| B/01/01
| E/01/01
| 25

|-
| 3
| D/01/01
| D/99/01
| 5

|-
| 4
| C/01/01
| D/01/01
| 0

|-
| 5
| E/01/01
| A/01/01
| 5

|-
| 6
| C/02/01
| C/99/01
| 0

|}
Therefore, the closest task is either 4 or 6.

The algorithm then checks how close the bay is to the current location, if the task is in the same aisle, by converting the bay into base 36, then taking this bay sequence away from the current location bay sequence.

If the tasks are not in the same aisle, the tasks are simply sorted on bay sequence ascending.

So, in our example above:

{| class="prettytable"
! Task
! From
! To
! Aisle

Nearness
! Bay Nearness

|-
| 4
| C/01/01
| D/01/01
| 0
| 0

|-
| 6
| C/02/01
| C/99/01
| 0
| 1

|-
| 3
| D/01/01
| D/99/01
| 5
| -

|-
| 5
| E/01/01
| A/01/01
| 5
| -

|-
| 2
| B/01/01
| E/01/01
| 25
| -

|-
| 1
| A/01/01
| C/01/01
| 35
| -

|}
So task 4 is closest.

The level nearness is decided in the same way.

== Locations and Check Digits Options ==
Check digits can be enabled or disabled from the WCS Maintenance program. This gives the functionality that the WCS can be used in warehouses without the expenditure of new location labels, but with a slight loss of accuracy.

The options available are:

* Location - the user is prompted to scan or enter the location again.
* Check Digit - the user is prompted to scan or enter the check digits associated with the location.
* Combo - the user is prompted to scan a barcode at confirmation. If the barcode is scanned, the program expects the barcode to contain the location code. If data is keyed in, the program expects that the data keyed will be the check digits of the location.

Combo check gives the most functionality, as the barcodes can be used to scan locations for when location entry is required (for example, in Ad Hoc Pallet Moves, and repositioning pallet moves).

All validation types described above depend on the location labels the warehouse has - if no barcodes are available to be scanned, then the program will still prompt, but manual entry of the check digits is accepted instead.

The check digits prompted for depend on the data set up in the WMS - if check digits are enabled on some locations but not others, locations without check digits are still prompted, but the program will accept a blank entry (keying RETURN over the field). Additionally, if check digits are entered for locations in the WMS, but Check Digit validation is not enabled in the WMS, the WCS can still check entry of check digits, but the WMS will not require the users to enter them at manual confirmation.

== Pallet Identification ==
In order to identify that the user has found the correct pallet, most of the RDT modules will prompt for a pallet ID. This is normally a unique identifier for the pallet within the warehouse. The WMS can support two types of pallet identifier, the system pallet ID and a customer's pallet ID (the pallet ID of the pallet in any previous computer systems).

The WCS supports the use of either of these pallet Ids to identify a pallet. The WCS can also support identifying pallets by neither of these, but simply by location and stock code.

== P&D processing ==
The WCS controls P&D locations for multi-part moves ([[#Multi-part movements]]) in several ways.

P&D locations can be assigned to inbound and outbound movements within an aisle in the WMS and the WCS.

There are several different types of P&D location used by the WCS:

* Sequential - FIFO and LIFO P&Ds
* Random - where each pallet is accessible at any time

The P&D locations can also be listed as having limited or unlimited storage space for pallets.

The system can cope with the same P&D location used for both in and out, for any of the above types.

In order to cope with multiple face opportunities, there are two further parameters on the aisle:

OPP AISLE - if this is populated, the aisle (and the opposite aisle) are treated as faces of the same aisle. When location efficiency is being used, all moves for this aisle and the opposite aisle are treated as from the same aisle.

SPLIT FACES? - If this flag is set, and there is no OPP AISLE, the faces are split ODD and EVEN. If the OPP AISLE flag is set, it should be split AISLE and OPP AISLE.

Moves on P&Ds acquire the priority of any tasks behind them. This means that any high-priority pallet arriving on a P&D will bump the priority of any pallets before it, allowing the high priority move to get out of the racking quicker.

When moving pallets out of NA areas, the system allows for limited P&D space. E.g. when there are 7 high priority outbound moves from an aisle, and only room for 3 pallets at P&D out, only 3 can be done before the P&D must be cleared.

If, during Narrow Aisle Dual Cycling, a pallet is found on an inbound P&D for which there are no movements to the P&D's aisle, the system will ask the operator to confirm the pallet number by re-scanning it.

If the pallet is number is confirmed, the system will check to see if there are any other tasks for that pallet from any other locations in the warehouse that aren't currently being performed by another user. If there are, the system will generate a task to move the pallet from the current location to the location from which the existing task will take the pallet from. If the move generated is to a P&D that is not blocked and the operator's truck is allowed access to, the movement is shown on the RDT. If not, an error message is shown on the RDT.

An exception will be logged with the comment 'Pallet P&D Error' when this occurs.

== Barcode support ==
The WCS supports as standard the following barcode types to be scanned for fields:

* EAN-13
* EAN-8
* CODE-128
* CODE-39
* CODE I25
* UCC/EAN-128

Further barcode types can be supported, but are sometimes limited by the barcode scanner and software.

The UCC/EAN-128 standard is applied in a generic fashion for the most common data items.

Additionally, the RDT Receipt module allows the user to scan UCC/EAN-128 barcodes with multiple data items in a single scan.

The WCS holds an optional table of stock codes, against which it can hold alternative barcodes for the stock. If this table is populated, the WCS will recognise all barcodes associated to the stock code, whenever a stock code entry is required. An example of this means that EAN barcodes for sales, distribution or consumer units may be scanned for each stock code in place of entering the system stock code.

The WCS Stock Barcodes table is maintained from the WMS.

== Multiple UOM Processing ==
If enabled (in the WMS and WCS), the WCS is capable of entering either a simple Cases value, or Cases and Units. In this document, the entry of either of these values is referenced as Quantity entry.

If enabled and the UOM factor between cases and units is greater than 1, the WCS will prompt the user to enter both a cases and units value. These two values are delimited by a forward slash ("/"), for ease of recognition. The user will be prompted first for the case count, then the unit count. The only exception here is when the user is picking units only from a unit pick face. The user will then only be prompted for a unit value, the case value defaulting to zero.

If the systems are not enabled for multiple UOM entry, or the stock being actioned has a UOM factor of 1 (i.e. 1 case = 1 unit), the WCS will only prompt for a case count.

Whatever the values entered on the RDT, the quantities sent back to the WMS will be the conglomerated values (cases, multiplied by the UOM factor, plus the number of units).

=='''Owner Restrictions'''==
When logging on to the RDT, the user is prompted to enter an Owner Code. This owner can control the work that a user is allowed to perform in the warehouse. If a user is set that way, they are known as a restrictive owner.

The owner entered at log-on is part of the selection criteria for the WCS task retrieval. (E.g. if the user logs on as 174, they can only do tasks for owner 174).

If the owner selected has no restrictions, the user entering the owner will only be restricted to those owners without the flag.

For example:

{| class="prettytable"
! Owner
! Restricted Flag

|-
| AAA
| N

|-
| BBB
| Y

|-
| CCC
| Y

|-
| DDD
| N

|-
| EEE
| N

|}
If the user logs in as BBB, they will only get tasks for BBB

If the user logs in as CCC, they will only get tasks for CCC.

If the user logs in as AAA, they can get tasks for AAA, DDD or EEE

The tasks restricted in this way will be:

* Goods Receipt
* Putaway
* Pallet Movements/Replenishments
* Picks (Full- and Part pallet)
* Truck Moves/Dual cycling (a combination of all full-pallet movements in the WCS)

If the user is restrictive, it can have settings against it in the WCS. This means that restrictive owners (i.e. owners with their own workforce) can operate in a different way to those that are not restrictive. These owners use the warehouse defaults.

=='''Movement Exceptions'''==
During the processing of some tasks - Putaway, Pallet Moves and Ad Hoc Pallet Moves - the RDT may give some options to the user, to allow them to reflect actions that they took, if they were not what the WCS expected them to do. These are called Movement Exceptions.

Note: If the warehouse is marked as a Block Stack warehouse within WCS, there is another exception called Exchange Pallet. This is covered in great detail in [[#Multi-Pallet Locations]].

=== Reposition ===
In standard pallet movements and putaways, the user can be optionally offered the ability to reposition the pallet to a new destination. This will reflect the new destination in the WMS when completed.

If the user is unable to position the pallet in the suggested location because the aisle is blocked or the location is otherwise inaccessible, the user will have the ability to choose a new location for the pallet, by pressing F4 to reposition the pallet. This option can be password-protected for those users who are given the option. It is intended that this password would be known only to the shift supervisors and as such the user will have to ask the supervisors to authorise the reposition. The RDT will request the user to find a new empty location for the pallet. They will also be asked to confirm the check-digits of the location, if required. Should the location be available, the user will be allowed to use this location. When the task is completed, this information is sent back to the WMS, where the putaway will be confirmed into the new location. The WCS will also create an exception (visible in WCS Maintenance) showing the location the pallet was originally intended for, for information purposes.

=== Extended Reposition Validation ===
When repositioning pallets, the WCS can check that the locations are valid in two ways.

The standard way is for the WCS to check only that the location exists and validate the check digits entered by the user.

This can be modified so that the WCS validates in exactly the same way as the WMS, in that it checks that the location availability, the pallet type, number of pallets, bonded status, multi-pallet validation, etc.

=== Cancellation ===
For some types of pallet movements, the user can be optionally offered the ability to cancel the movement. This returns the pallet to the original source location on the WMS. This is only offered at the source location.

=='''Multi-Pallet Locations'''==
The WMS contains functionality relating to multi-deep locations, which can be used to handle normal multi-deep locations, block stack locations, drive-in locations, etc - any location where pallets are stored where it is sometimes difficult to locate the exact pallet you want.

The WMS controls pallets moving in these locations during putaway, and can ensure than only pallets of similar properties are held in each location, by a combination of some or all of the following criteria:

Product Code

Batch

Manufacture Date

Sell-by date

GRN number

Quantity

Should pallets be received with different criteria than those marked for validation against the multi-deep location, they will not be located within that location.

The WMS can also manage that the locations be left marked as full, until all of the pallets within a particular location have been moved out, ensuring that newer stock is not positioned in the location before the old stock.

Moving pallets into the multi-deep locations pose no problems for the WCS, as the movements are identical to moves into other, fully-accessible locations. The problems occur whenever pallets are removed from the location.

Whenever the WMS says that something should be done (for example, picking), the pallets being moved are 'hard allocated' to the task. This doesn't change. What does happen is that the user is given the opportunity to exchange the pallet for another one, as long as it matches some criteria.

When a user is given a task to complete from a multi-pallet location, they are sent to the location by the normal manner and asked to confirm the location. Once confirmed, the RDT will ask them to confirm the pallet being picked. At this point, the user is able to press a function key to exchange the pallet for another in that location.

This exchange is done by two methods:

Task Exchange

Pallet Exchange

=== Task Exchange ===
The first thing that the WCS does is check to see if there is an outstanding task available within the WCS for the pallet that you have scanned. If there is, the WCS seamlessly instructs the user to complete this task first. So, if this was for another order, the RDT would instruct the user to pick this pallet for the other order first, and then send them back to the same location to try to pick their pallet again. The option for exchange pallet is available again at this point.

=== Pallet Exchange ===
Should there be no task available for the user to exchange to, the WCS will ask the WMS to validate the pallet scanned as the replacement pallet, to ensure that the pallet can be exchanged. This checks various details such as whether the pallet is:

Allocated to another order

Already moving to another location

Under stock take.

If this is the case, the pallet is not exchanged.

The location must be marked as a multi-deep location. If not, no exchange is allowed.

The process also validates the sell-by date and manufacture date, depending on the set-up of the stock within the WMS. However, it is assumed that the validation against the location has ensured that the pallets within the location are already compatible for exchange, as the location will have validated this when the pallets were put in the location.

If the pallet passes the validation, the RDT user is allowed to continue the task, taking the pallet requested instead. The WMS will hold the new pallet during this exchange manoeuvre. When the task is completed, the WMS will complete the task and formalise the exchange:

The original pallet will be released for further allocation to tasks

The new pallet will have been actioned as if it was the original pallet

The audit trail (and all supporting files) will be maintained.

=== Options Available ===
It is also possible to allow replenishment movements of Pick Faces to be exchanged for another pallet. The checking on the pallet is more stringent than before, checking such things as total available quantity as well as others. In this instance, the exchange is reflected not only on the replenishment movement itself, but on all the orders picking from that pallet. So, the WMS changes the pallet, and re-sends all the pick tasks associated to that pallet at the point of exchange - all the old picks are cancelled.

== Labelling ==
In certain modules (e.g. Goods Receipt, Picking), the WCS can be set up to print labels. This is done by merging the information of the task being processed (e.g. the current pick task) with a defined format. The items that can be merged are being expanded all the time and are referenced by defined field names in the modules.

For example, in picking, there is a defined field called 'MarshLoc'. This is the defined marshalling location for the current pick task. A plain text label template for the despatch label may look like the following:

<nowiki><TEMPLATE></nowiki>

ABC Pick Label

Marshalling Location:

{MarshLoc}

<nowiki></TEMPLATE></nowiki>

If the task in question has a marshalling location of 'MAR01A', the WCS would merge the template and the data to produce a single label similar to the following:

ABC Pick Label

Marshalling Location:

MAR01A

The templates can be as complex or simple as required. So, if templates are created in ZPL2 label printer formatting, the WCS will still merge the data at the point requested i.e. the field name in curly brackets.

Each RDT modules allowing label printing have a section showing the fields currently allowable on labels printed.

A full discussion around the setting up of printers for use with the WCS can be found in the WCS Setup Guide
= GENERIC RDT Modules =
== Goods Receipt ==
This module replaces the Goods Receipt Confirmation screen on the manual system, or can be used to complement manual (paper-based) receiving.

Preadvices are entered manually in the WMS Goods Receipt Preadvice screen or received through EDI.

Messages are sent to WCS either from the GR Preadvice screen at the request of a user or automatically from the incoming EDI.

The preadvice to RDTs can be to a stock level, or to a pallet level, depending on how much detail was entered on the WMS.

See flow-charts [[#Receipts.]]

The user is prompted to enter the GRN number from the manual system. This matches to a Preadvice on the WCS. A flag controls whether the user can identify receipts from the Advice Note number.

The user can then conditionally be prompted for:

* A default pallet type used for all pallets during that receipt session
* A receiving location
* A receipt type (reflected on the WMS)
* Whether the user wishes to see the ultimate destination location when each pallet is received
* Printer information, if the WCS is printing labels to wireless printers.

The user then enters all the required information per pallet received. This information varies on the set-up of the WCS, but can include:

* Pallet ID (can by system-generated)
* Customer's pallet ID
* Stockist code
* Stock code
* Batch
* Manufacture and sell-by dates
* Quantities (Including Measure Quantity functionality)
* Weights

The majority of this information could be barcoded on the label, and therefore the WCS allows the user to scan barcodes for each item.

Additionally, if the label contains a barcode with multiple items of information in it (in this case, UCC/EAN-128 barcodes), the WCS can optionally prompt the user to scan these barcodes first.

The items extracted from the barcode can be set up against the warehouse or owner. Only those items actually required by the stock code will be extracted.

Pallets being received can be identified via system pallet ID, customer pallet ID or stock code. For the Blind goods receipt module, Stock code is the identifying key and will be scanned first. For Check goods receipts, the Customer Pallet ID is the identifying key. If the data is preadvised to a pallet level, all of the items above can be defaulted from the preadvice.

The level of validation performed by the WCS on the received stock can be modified extensively, and can include checks on additional stock items, total stock quantity and standard pallet quantities, with four levels of validation (Ignore, Informational message, Supervisor Override, Error).

* Ignore - No check is made.
* Informational message - a check is made and a warning is issued. The user is allowed to continue receiving the pallet.
* Error - a check is made and a warning is issued. The user is not allowed to continue receiving the pallet.
* Supervisor Override - a check is made and a warning is issued. The user must obtain authorisation from a supervisor before they are allowed to continue. The supervisor must enter their employee code and password on the terminal as this authorisation. This authorisation is logged on WCS's Exception table, for auditing purposes.

Each pallet entered generates a putaway message to the RDT and updates the system with the required information, in the form required by the WMS.

A damaged quantity and reason can also be entered against a pallet. This will create a separate pallet for the damaged stock, and can optionally suggest a damages location for the stock.

It should be noted that RDT Goods Receipt might be slower than manual entry. This is because of the keying of data required on the RDT. If the pallets are labelled with barcodes before receipt and preadvised data is correct, this can speed up. The WCS can be set up in such a way that goods receipts are controlled via the normal WMS screens, with putaways controlled via the WCS.

== Pallet Identification and Labelling ==
A problem within most warehouses is the ability to label pallets effectively -
if the receipt process is perfect, but the labelling process is manual, errors will occur.

Standard WMS processing requires the user to print out the pallet labels after the pallets have been entered into the system, then requiring the user to match the label to the pallet received.

Below are some processes which can be used to help the issue.

=== Use Customer's Pallet Labels ===
Sometimes the pallets received by the warehouse do not require re-configuration and are already labelled from the customer's systems. The WCS can be configured to capture this Customer's Pallet ID at receipt stage. This can then be used as the WCS task identifier when moving pallets around the warehouse or picking them.

=== WCS Receipt Label ===
The WCS can print pallet labels to a wireless printer. The label is printed directly as the pallet is received and the label placed onto the pallet before the user moves on to receiving the next pallet. This reduces the danger of pallets being incorrectly labelled. Standard formats exist for receipt labelling.

'''Note: '''Wireless label printers may require a different pallet label to be programmed, as the programming languages of the different types of label printer vary.

'''Note: '''Wireless label printers are expensive and may constitute a reason for not printing from the WCS. However, this process could be used in conjunction with fixed printers in the receiving area, although the benefit of staying with the pallet whilst labelling is lost.

If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
| '''Field'''
| '''Description'''

|-
| StockCode
| Received stock on pallet

|-
| CustBatch
| Received Batch

|-
| SysDate
| Date Received

|-
| Qty
| Received quantity of stock on pallet

|-
| SPID
| System Pallet ID

|-
| SellByDate
| Received Sell-by Date

|-
| ManuDate
| Received Manufacture Date

|-
| WMSRot
| WMS Rotation

|}
=== WMS Receipt Label ===
Automatically produce label to defined printer, using a version of the format that already exists within WMS. The user would then immediately go to the printer upon receiving the pallet, and pick up their label. They would then take it back to the pallet they had just received, and label it. '''Note: '''A version of the WMS label print may need to be created, to be run automatically from the WMS RF update program.

'''Note:''' There is some room for error in this process, as the user must get the label from a common printer and leave the pallet behind. The defined printer would be made common for the owner, meaning that several people could be printing to the same printer at the same time.

=== Pre-label ===
A pre-printed roll of labels could be used, showing a unique identifier on each small label. Whenever a user receives a pallet, the first actions they take are to place one of these small unique labels on the pallet and scan that into the RDT during receipt. This will be held as the Customer's Pallet ID.

If the ID is being used solely for the WCS identifier, and no further pallet label is required, the process can stop here. Should a more detailed label be required, labels can then be produced either automatically from WCS or produced at the end of receiving for all the pallets, directly from the normal WMS goods receipt screens.

It may then be necessary to have WMS label prints that show the Customer's pallet ID (the place the WMS stores the data) as a barcode.

The user would then use the Customer's pallet ID on the labels retrieved to match against the pre-labelled pallets. This would reduce the checking required in labelling pallets.

'''Note:''' The normal system pallet ID or the customer's pallet ID could be used to identify the stock in the warehouse in the WCS.

'''Note:''' There would be a cost overhead in using the pre-printed roll of unique labels, plus the risk of using an identifier that has been used before - the system would not then allow receipt of the pallet.

'''Note:''' The benefit of a pallet being immediately available for putaway may be compromised using this method, depending on how it is implemented.

== Putaway ==
If the system uses RDT Goods Receipt, the putaway messages are sent automatically to the WCS as each pallet is updated.

If RDT Goods Receipt is not in use (or the receipt has not been completed via the WCS at all), the system will send putaway messages to the WCS when CONF is entered in the Goods Receipt Confirmation screen.

See flow chart [[#Putaways.]]

The RDT user scans the pallet to be put away. This can be via system pallet ID, customer pallet ID or stock code and quantity. The WCS checks that there is a putaway for this pallet. If there is, the user is prompted to take the pallet to the assigned destination location. When at the destination, the user is asked to confirm their location in the standard fashion. Once the location is confirmed, the pallet is confirmed put away by the system.

If user is unable to position the pallet in the suggested location, they can be optionally given the option to reposition the pallet to a new location. See section [[#Movement Exceptions]] for details.

The user can display further information about the pallet by pressing the additional information key. This will currently display the Owner and Stock codes on the pallet.

If the pallet being put away has several stock codes on it, the RDT user will be prompted to confirm the stock and quantity for each item, as a check when the pallet is being positioned.

If the stock on the pallet is being positioned to several locations (i.e. multiple stock codes being put in their respective pick faces), the RDT will direct the users to each required location in order, confirming the stock and quantity when there for each item.

If required (and enabled) the RDT user can pick up several pallets on the truck at once and the user will be taken to each pallet's destination in order.

== Pallet Enquiry ==
See flow chart [[#Pallet Enquiry.]]

By entering this module and scanning the pallet ID, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Rotation
* Customer's Batch
* Owner code
* Stock code
* Description of the stock
* Pallet quantity in location
* Manufacture and sell-by dates

If there are multiple pallets in the warehouse with this identifier, or the pallet is of mixed stock, all the information is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the records to be displayed are decided upon by the use of the following table:

{| class="prettytable"
! <center>Moving Out</center>
! <center>Moving In</center>
! <center>On Hand</center>
! Reason
! <center>Show?</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>Y</center>
| Stock move in and out
| <center>Y</center>

|-
| <center>Y</center>
| <center>Y</center>
| <center>N</center>
| P&D pallet
| <center>N</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>Y</center>
| Pallet moving out
| <center>Y</center>

|-
| <center>Y</center>
| <center>N</center>
| <center>N</center>
| NOT POSSIBLE IN SYSTEM
| <center>N</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>Y</center>
| Stock Replenishment
| <center>Y</center>

|-
| <center>N</center>
| <center>Y</center>
| <center>N</center>
| Record to - shown above
| <center>N</center>

|-
| <center>N</center>
| <center>N</center>
| <center>Y</center>
| Normal Pallet
| <center>Y</center>

|-
| <center>N</center>
| <center>N</center>
| <center>N</center>
| Error situation which users may want to see
| <center>Y</center>

|}
This enquiry is also available from the Enquiries sub-menu from any other task.

Pallet labels can be printed from this module. This is configurable and uses a label format defined on WCS. Standard formats are available.

== Location Enquiry ==
See flow chart [[#Location Enquiry.]]

By entering this module and scanning the location code, the user is provided information about the pallet, consisting of the main elements from the WMS:

* Pallet ID
* Customer pallet ID
* Owner code
* Stock code
* Description of the stock
* Location quantity

If there are multiple pallets in the location, or the pallets are of mixed stock, all the information for these pallets is displayed, allowing the user to page through the available information in any order they choose.

In the event of a movement on the pallet, the pallets will be displayed showing the on-hand quantity. This means that if a pallet is moving out of the location, it will be shown with the full quantity. If the pallet is moving into the location, it will be shown with zero quantity.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Movement Enquiry ==
See flow chart [[#Movement Enquiry.]]

The two previous sections contain references to pallets mid-movement. The enquiries show the data to the best of the WMS's ability. This enquiry shows any outstanding tasks on the WCS's database, showing the source and destination of the pallet. This allows users to decide what must be done when a rogue pallet is found.

This enquiry is also available from the Enquiries sub-menu from any other task.

== Stock Enquiry ==

The module requests the user to enter an Owner (defaulted from the logon) and a stock code.
For the stock code, the user can scan any barcode that has been set up for the stock code in ''CALIDUS'' WMS (for example, an EAN Code).
''CALIDUS'' Mobile will retrieve the details of the stock code and display them. The details are:
*Owner Code
*Stock Code
*Description
*Standard Pallet Quantity
*Case Quantity
*Defined Pick Face
*Measure Quantity details, if present.

== Picking ==
=== Full Pallet Picking ===
See flow chart [[#Full Pallet Picking.]]

On entry to the picking module, the WCS will provide the user with a pick request to fulfil. If this is a full pallet bulk pick, the user will be prompted to go to the location of the pallet, and pick it. If the location is unavailable, the user can change the pallet to be picked.

If the user wishes to change the pallet to pick, they can press the error key and choose 'Pallet change'. If the pallet is changed in this way, the user will be forced to enter the quantity picked and the quantity remaining, in case the new pallet has a different quantity available on it than the first pallet.

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key.

=== Part-pallet Picking ===
Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section [[#Multiple UOM Processing]] for details of multiple UOM processing.

See flow chart [[#Part-pallet Picking.]]

On entry to the part-picking module, the WCS will provide the user with a pick request to fulfil. The user will first have a summary screen displayed, showing the order or route/load given to the user and the number of tasks for the user to complete. The customer name is also included, from the first pick task.

The user will be prompted to go to the location of the pallet, and pick it. (The user has the option of choosing where to start picking, i.e. they can choose a start location at this point.)

Checks can be made on the pick pallet to ensure that the required replenishment has been completed to the pick location before the pick is released to the pickers.

If the location is unavailable, the user can cancel the pick.

The user will be prompted to confirm either the stock code or the pallet, depending on whether the stock is palletised. There is also the option to identify the pallet by the stock code only, by stock and batch or by pallet and stock, with a visual confirmation of batch.

The user also optionally has the ability to show the exact details of the pallet, to identify the pallet if the pallet label is missing.

The user will then be prompted to enter the picked quantity.

The pick quantity can be entered as a quantity (or cases/units), or the RDT can prompt the user to scan the stock code of the case being picked once for each carton removed from the location (carton picking). At this point, the RDT can print a carton label for each carton removed. If entered as a quantity, the RDT can optionally allow over-picking (for variable carton quantities).

The WCS can also be set up to consolidate quantities on orders allocate to route/loads, so that only one pick per pallet in a location need be completed in order to fulfil all the stock required by all the orders.

After entering the picked quantity, the user can be optionally prompted to enter the remaining quantity. This is to ensure that the pick faces have an accurate amount on the pallet.

The WCS can also be set up so that the module will require the supervisor to enter a system password to allow the user to continue with their task, should they change any quantity. This validation is performed on-line, from the data held on the WMS at the point of picking. If the quantities are different to the values sent, the user will be prompted to enter a reason code, which will be passed on to the WMS.

The process also includes Despatch Pallet building, when part picks are consolidated on to one pallet. This functionality is flagged in the WCS.

In this case the RDT will, at the point of completing a single case pick, ask the user if they want to continue picking, or take the pallet to the marshalling location. If the user chooses to continue picking, the RDT will prompt the user for the next pick in the list. If the user chooses that they have finished picking on to their pallet, they will be told to take the pallet to the marshalling location.

The user can, when building despatch pallets, give them a unique identifier called a picking container. This is prompted for when picking starts, and after each trip to marshalling. This identifier is held on the WMS and is used in the deconsolidation process

When taking the pallet to marshalling, the RDT displays either the order or the route/load of which the stock is part. If the order is on a load, the order reference can be found by using the Information function key. This pop-up will also display the customer name and address.

When the pallet has been confirmed picked, a message is sent to the WMS.

If the quantities involved are valid (i.e. they add up the quantity available on the pallet), the line will be confirmed. If not, the line will not be confirmed, and the WMS will request that a user confirm the line manually, and make any necessary changes to the data on the WMS.

Should all lines be automatically confirmed on an order or route/load, the WMS can automatically print a despatch note in the required format to a defined printer. This is configurable and, if printed, will print in the format defined for the owner.

During picking, it may be that a pallet to pick has problems, or may not yet be available for picking. In this instance, the client wishes to put this pick to the back of their 'queue', and process any other picks for the order. The module provides a function key press to accommodate this.

Despatch or Pick label printing is supported in the WCS. The printing can take place either at the point of picking or taking to marshalling, to deal with several types of printer. Any wireless or networked printer may be supported.

Sky-picking and split-down picks are also accommodated in the WCS.

When the quantities and the pallet have been confirmed, the user will be prompted to go to the destination location, which will be a marshalling location. When confirmed, the data is updated on the WMS.

=== Pick Locking ===
The normal processing of picks in the WCS includes the ability to lock several picks together, to ensure that the user completes all tasks together.

This functionality is standard, as the locking record is based around the 'pages' functionality in the WMS. This is where sort sequences, pick sequences and page totals define a Page Number for a number of picks records (WARE_DESPATCH_DETAILS). An order would most commonly be broken down into pages as follows:

* Type (Pick, Bulk, etc)
* Area
* Aisle

Each time these items change, another page would be produced.

In standard, when the WCS receives these picks from the WMS, it creates the pick details record (Picking) and the task to control the pick (the Truck Move and Pending Truck Moves records). It also creates locking record (Picking Header) for each Order Number/Page combination. If picks for that page already exist, it associates the picking record arriving with the already existing Picking Header record.

When a user enters the Picking or Part Picking modules on the RDT, they are assigned the first pick that they are capable of doing (following the rules about location efficiency and priority). The WCS locks this picking task to the user, and also locks the appropriate header record as well, thereby preventing any other user accessing picks on that order/page.

When the user completes a pick, the task is deleted, and the picking record deleted if appropriate (there could be further stages to the move - from P&D to marshalling, for example)

When the user completes all the picks for the page, the picking header is also deleted.

If the user does not complete all picking tasks on the page, but backs out of the tasks, the current pick is released, and the Picking Header is also released, to allow someone else to continue with the picks.

It is also possible to create locking headers in different ways, depending on the set-up of the WCS and the data received from the WMS. In all cases, however, there must be a Picking Header record created, and the Picking and Part Picking options on the RDT will always lock this record.

Aisle locking can be enabled on the WCS, for Order or Route/Load combinations. The result is that, when the WCS receives the picks, it ignores the Page Number against the Order, and creates Picking Header records solely against the Order/aisle. If the Load Number is populated on the inbound pick, the Picking Header is created against the Route/Load/Aisle.

The WCS can also force an Order or Route/Load to be completely assigned to pickers before allowing any other pick to be completed. This forces all picks to be sent to the marshalling lane for one Order or Route/Load before any other is begun, and can aid in Marshalling.

The WCS can force the entire order or route/load to be assigned to one user, depending on type (e.g. full pallet picks will be given to one user, part-pallet picks will be given to another, different product types will be given to yet another, etc).

It should be noted that this type of locking is ignored in certain modules on the WCS, resulting in the ability to complete picks without locking out any other users. Examples of such modules are:

* Dual Cycling (NADC, WADC)
* Truck Moves
* Select Move

=== Allocating Picking Tasks to Users ===
Pick moves on the WCS are created on receipt of messages sent from the WMS. The move details are set up in the light of the group/owner/warehouse/system flag settings current at that time. The picks are allocated to pick groups (Picking Headers) so that allocation of picks to RDTs can be controlled. Any combining of picks together, if not been done by WMS, (consolidated picks) is also done at this time.

When an RDT requests pick tasks, the request is actioned in two phases:

# All suitable picks are selected from the available moves. The significant flags referred to are "Enable Pick Dependencies", "Concurrent Picking", "Pick Page Allocation", "Enable Hold Priority", "Pick In Sequence", "Pick Consolidate Group", "Pick By Carton". The selection is made on the basis of:

#
#* Move is associated with a Picking Header (i.e. is a pick),
#* Company of move matches Logon Company,
#* Warehouse of move matches Logon Warehouse,
#* Owner of move matches Logon Owner is this is restricted; otherwise Owner of move is a non-restricted Owner,
#* The From-Location-Type of move permits the Logon Truck Type,
#* The To-Location-Type of move permits the Logon Truck Type,
#* Move has not already reached Destination Location, i.e. is not returning the pallet to Source Location after picking from it,
#* Status Flag of move is PENDING,
#* Priority of move is not HELD,
#* Type of move is not a Stock Move,
#* When requesting Part Picks, Type of move is a PART PICK; When requesting Full Pallet Picks, Type of move is not a PART PICK,
#* Picking Header associated with the move is already assigned to the RDT or is not assigned to any RDT,
#* Picking Header associated with the move is already assigned to the Employee or is not assigned to any Employee,
#* Either- Stage of move is beyond first, i.e. moved out of Source Location, Or- No replenishment move on the same pallet is yet to deliver to the Source Location,
#* If next stage of move is to a PND, that there is room for another pallet (i.e. max number of pallets in the PND will not be exceeded),
#* If Full Pick and next stage of move is from a PND- if Type of PND is FIFO that there is not another pallet at the PND which had been moved there earlier; If LIFO that there is not another pallet at the PND which had been moved there later,
#* If move is for a Route/Load, that the move is on the order which has highest Drop No in that Route/Load (new development)

# The list of suitable picks is ordered on the criteria (highest priority first):

#
#* Pick Header of move already has moves assigned to an RDT,
#* Pick Header already assigned to Employee,
#* Priority of move,
#* If Employee specified Start Location, sequence number of move (which designates sequence of locations from Start Location),
#* Order Number,
#* Page Number,
#* Sequence Number (on page).

'''Note:''' As described above, the allocation of picks is dependent on decisions made not only at picking time but also when the pick details first sent to WCS from WMS. If changes are made on the WMS to location definitions or on the WCS to certain flag settings, any pending picks which are dependent on these definitions/settings should be removed and re-sent.

=== Labelling ===
If labelling pallets through the WCS, the following items can currently be used on the produced pallet label:

{| class="prettytable"
! Field
! Description

|-
| RouteCode
| Route/Load to which the order is assigned

|-
| LoadNo
| "

|-
| EXELOrdNo
| Order Reference (first 15 characters)

|-
| OrderRef1
| Alternative Order References

|-
| OrderRef2
| "

|-
| OrderDescription
| "

|-
| DateTime
| Dates and Times

|-
| SysDate
| "

|-
| SysTime
| "

|-
| OwnerCode
| Owner of the stock picked

|-
| Picker/Picker ID
| The ID of the picker

|-
| MarshLoc
| The Marshalling location of the order

|-
| PickText
| The instructions sent out on the last pick task completed.

|-
| StockCode
| Received stock on pallet

|-
| PalletID
| System Pallet ID of the stock last picked.

|-
| TotalQtyPicked
| Qty Picked of the last stock Picked

|-
| TotalQtyAlloc
| Qty originally allocated of the last stock picked

|-
| Prio
| Priority of the last task completed in WCS

|-
| Name
| Customer's name and address

|-
| AddrLine1
| "

|-
| AddrLine2
| "

|-
| Town
| "

|-
| County
| "

|-
| Country
| "

|-
| PostCode
| "

|}
== Pallet Moves/Replenishment ==
See flow chart [[#Pallet Moves.]]

The user is prompted to go to a location. Once they have confirmed their position, they are told to scan the correct pallet. Once this is confirmed, they are required to move the pallet to the correct destination location.

This process is the basis for any RDT system. As such, it requires the ability to correct any inconsistencies between the main database and the physical stock. The user is given several processes to accomplish this, most of which can be enabled or disabled:

* Reposition pallet at destination
* Cancel movement at source
* Change pallet (in block stack or multi-deep warehouses)
* Display further information about the pallet

See section [[#Movement Exceptions]] for details of Movement Exceptions.

=== Mixed Stock moves ===
The system allows for pallets of several stock codes to be moved.

=== Replenishments ===
Replenishments are dealt with in the same way as pallet moves, but obviously have a greater effect if exceptional events occur. Therefore, a replenishment move may not be repositioned, although it may be cancelled. See section [[#Movement Exceptions]] for details. Replenishments can be those generated from the WMS from Allocation (Dynamic replenishments) or requested Bulk-to-Pick replenishments. The system also supports the user of Replenishment locations above the pick face.

The WCS can reduce the number of replenishments available to a pick face to one, by the use of a flag, to avoid overloading a pick face.

=== Replenishment Strategy ===
The WCS contains several mechanisms of controlling replenishment moves to a pick face:

# Picker Replens, which allow the picker the ability to reprioritise the required replenishment to the pick face, or even do it themselves;
# Pick Dependencies, which stop the user being sent for a specific pick if the replenishment associated to that pick has not been completed;
# Replenishment Dependencies, which prevent the moving of more than one replenishment move to a pick face at a time.

Another area that can be seen as 'replenishment' is the split-down functionality.

=== Split-down Functionality ===
When picking from high-bay, defined as racking (non-pick) areas with P&D locations defined against the aisles, the WCS will plan those moves out to a defined Split-down area. They become 3-stage moves:

# Move from bulk location to P&D location
# Move from P&D location to defined split-down area
# Pick from pallet in split-down area to defined marshalling location for the order or route/load.

The WCS will not allow the user to be sent for the pick before the split-down move has been completed.

The pallet will stay in the defined split-down area until all picks designed to take stock from the pallet have been completed.

When all have been completed, the pallet will then be planned back into the racking, back to its original bulk location, through a 2-stage move:

# Move from defined split-down location to P&D location
# Move from P&D location back to racking.

== Cherry Picking ==
See flow chart [[#Cherry Picking.]]

The Cherry Picking module allows a user to pick the first available pick task for an entered order. The users do not lock tasks - other users are allowed to pick on the same order. Users are allowed to complete as many tasks as are available and valid for them on the order, if continuous part picking is allowed.

If there are no more picks available on the selected order, the user is returned to the prompt for Order number.

In all other ways, the pick acts exactly as the part picking module.

== Deconsolidation ==
In order for this module to be used, the system must have enabled Picking Containers for the picking function.

See flowchart [[#Deconsolidation.]]

When orders are pick confirmed, either automatically through the RDT confirmation of picks, or manually, if required, a message will be sent to the WCS to allow the orders to be deconsolidated. Note: Route/loads can't be deconsolidated until all orders on the route/load have been confirmed as picked by the WMS.

The RDT user will enter the new deconsolidation module and will be prompted to scan a container number in any marshalling location.

The WCS will first confirm that this route/load is available for deconsolidation and packing (i.e. the route/load has been pick confirmed in the WMS). If this is not the case, an error will be displayed.

If available, the WCS will then check that the picks require deconsolidation. The rules for this are:

The order must have been allocated to a route/load within the WMS.

If on a route/load, there must be multiple customers for the orders on the route/load.

If the picking container scanned does not conform to these rules, the user will simply be prompted to confirm that the stock is ready to be despatch confirmed. If the user responds that this is the case, a message will be sent to the WMS to confirm the order(s) as despatch confirmed.

If the stock is available for deconsolidation, the RDT will prompt the user to collect all the other containers for the route/load, displaying them as a list, with the user scanning each container number required.

Should a container not be found, the user will have an error function at this point, which should be supervisor controlled. If they press the error key, the unit will prompt them to get authorisation from a supervisor. Once authorised, the packing tasks will be set to an error status, awaiting manual confirmation within the WMS.

When all picking containers have been confirmed as found, the RDT will display a summary screen, showing the first order to be packed, displaying the customer on the order, the order number and the total number of cases to be packed.

The user can optionally enter a final media container number at this point. This will not be validated in the WCS as the maintenance of these final media container numbers is expected to be controlled by external systems.

This final media number will be sent back and stored on the WMS.

There will be an option on the RDT screen (via a function key press) to change the final media being packed into. This is so that orders which spread over multiple packs can be accommodated.

The RDT will then prompt for the first stock code to be packed on the order and the picking container in which this stock can be found and require the user to confirm the stock by scanning the barcode on the stock code.

When the barcode is scanned, the RDT checks that the EAN barcode scanned is not duplicated on another stock code. If it is, the RDT displays a warning for the user that this is the case.

The RDT will then display the first batch for that stock code on that order and the total quantity to be found in the picking container for that stock, batch and order. The user will be asked to confirm the amount found in the container for that stock, batch and order.

If the amount entered by the user does not match the amount expected in the container, the user will be asked to confirm the amount found again. The RDT will continue to prompt for the quantity found until the user enters the same quantity twice in a row. Once the quantities entered match, the RDT will request a supervisor's username and password to unlock the terminal.

The supervisor should confirm the problem that the user is having and, should a shortage still be found, they will be asked to confirm the actual quantity found.

The user should remove the stock from the picking container and pack the stock in the final media at this point.

Once the quantity is confirmed, either by correctly entering it on the first attempt or by supervisor override, and the final picking container is identified, the figure will be reflected back on to the WMS immediately.

The user will then be asked to confirm the quantity of all other batches for that stock and all other stock items for that order, until all lines are packed.

The user will be prompted to pack all items for all orders on the route/load, until all orders are confirmed packed.

Once all orders have been deconsolidated, the RDT will display that all tasks are deconsolidated, and the orders will be made ready to despatch on the WCS.

There is a rule-controlled variant of Deconsolidation called Ad Hoc Deconsolidation.

If this rule is set, the user has the ability to choose the sequence of the orders deconsolidated, rather than being told which orders to deconsolidate.

Additionally, if this rule is set, the user has the ability to choose which stock on the order is to be deconsolidated first.

== Despatch by Order ==
In order to use this module, the system must have Picking Containers and Deconsolidation enabled.

See flowchart [[#Despatch by Order.]]

When entered, the RDT module will prompt for an order to be despatched. The user will scan the order number from the despatch note, or will key in the order number. The order number scanned will be displayed on the screen. Any number of orders can be scanned at this point, the list below the scanned item showing all orders scanned, latest at the top.

Once the user has scanned all the orders required, they can confirm that the orders are to be despatched by pressing F1. The RDT will display a confirmation box. Should the user cancel, they will be returned to the order prompt. Should they confirm that the orders are to be despatched, the WCS will send a message to the WMS for each order entered, confirming that the orders are to be despatch confirmed.

== Stock Check ==
There are two types of stock taking procedure:

* Full Stock Check - This is where the user enters what is counted without recourse to the current stock levels (blind stock check).
* Partial Stock Check - This is where the user checks stock against the current stock levels.

On the WMS, a range of locations, stock codes etc. to stock check should be chosen, described more fully in the client-generated operations document. The user will be prompted to confirm his selections, and this will submit the stock take cycle to be processed. It is at this point that the messages will be sent to the WCS, if the interface is turned on.

Enter the Stock take module, and the RDT will display a cycle to be processed. The cycle is chosen based on its priority and age. If the user does not wish to process this cycle, he can enter another, valid cycle here.

Once the required cycle is chosen, the user confirms their selection. The user will now be taken into the stock take module proper.

If the user has selected a 'partial' stock take, they will be taken into the partial-processing module. If they have chosen a 'full' (blind) stock take, they will be taken into the full processing module.

See flow chart 7.16.

=== 'Full' Stock Check ===
The RDT will prompt the user to go to a location and confirm that they are there. The user should then enter the pallet ID. If there are no pallets in the location, the user should press confirm and move on.

If the pallet ID is entered, the user should then enter the stock code.

The user should then enter the quantity. Once this has been entered, the user will be prompted to confirm the quantity entered.

Once the data is entered and confirmed, the WCS compare the data against the pre-advised levels. If the pallet ID and stock code entered were part of the cycle, the quantities are checked. If the quantities are the same, a message is sent that the pallet was found successfully. If the quantities are different, the WMS will be informed that the pallet was there, but modified. If the pallet was not advised, the user will be taken into the add sub-process, to enter the rest of the pallet details (such as the manufactured date etc.)

At this point, the WCS will decide if this was a mixed pallet, by trying to find any other advised pallets in that location of the same pallet ID. If any are found, the user will be taken to the product prompt again. The user should confirm whether the remaining stock on the pallet is present in the same way as above.

Once all pallets in the location have been counted, the user confirms this and they will be taken to a new location to count.

=== 'Partial' Stock Take ===
The RDT will process the first record in the stock check. This will be ordered by the method chosen in the cycle generation screen, either location within product, or product within location, the latter being the more common choice for RDTs.

The user will be prompted to go to a location and confirm that they are there. If these are valid, then the user will be shown the first pallet for this location, and the quantity details for this pallet. At this point, there are several actions available to the user:

* If the quantities are correct, the user can confirm.
* If the quantities are incorrect, the user can amend the quantities. The RDT will then display the correct quantities, and the user will then confirm this amendment.
* If the Pallet does not exist on the location, the user should zero the quantities. The RDT will then display the pallet, with zero quantities, and the user will confirm this.

If there are no more pallets to display in this location, the RDT will display a message as such, and allow the user to confirm this. If there is another pallet in this location, the user can add one by pressing the add key. The user will be taken into the add sub-process.

=== Add sub-process ===
The 'add' sub-process will prompt the user for all essential information about the pallet, such as the location, pallet ID, stock code, manufactured date etc. When the user has finished input of the pallet's details, they will be taken through the cycle again to check the details entered. When the user is happy with the entered details, they will confirm it.

== Bulk PI ==
See flowchart [[#Bulk PI.]]

This function allows the user to check the contents of any location in the warehouse at any time. The function is only available when an on-line link to the WMS is available.

The user is prompted to go to a location. The user will scan the location to be checked. The WCS will then check what is in that location with the WMS.

The user will then be prompted to enter the pallet(s) found in the location. Once the pallet has been identified, the user will be prompted to blind enter the quantity on the pallet. Should the user enter the quantity as expected, the check will be confirmed and the RDT will request if there are any more pallets in the location. The checks continue in similar fashion until all pallets are checked.

Should the quantity entered not be the same as on the WMS, the user will be required to re-confirm the amount counted. Only when the user has confirmed two identical counts in a row will the value be accepted.

On confirming a pallet, a message will be sent to the WMS with the count details. The WMS will not perform any required adjustments, although this is configurable.

Any discrepancies discovered by the process are fully documented on the WMS, accessible through an Ad Hoc Stock Take report. This report can show, by date, owner and /or stock, the pallets checked and discrepancies discovered.

== Daily Cycle Checking ==
High-value stock codes are defined as those stock codes which belong to the defined high-value Product Range/Class/Category/Group combination.

High-value locations are defined as locations which are present on the Location Class information for the defined high-value Product Range/Class/Category/Group combination or locations with high-value stock in them.

Normal locations are defined as any locations that are not high-value locations, or locations without high-value stock in them.

The high-value locations are maintained on the existing Location Class maintenance screen, for the defined high-value Product Range/Class/Category/Group combination. This combination is defined on the Daily Cycle Check parameters screen, following.

The Daily Cycle Check Parameters allows the users to enter the period over which the stock will be checked. So, the user will be able to enter:

* A number of days over which the standard stock in the warehouse must be checked, and;
* A number of days over which the high-value stock must be checked.

Additionally, this screen allows the users to define:

* The maximum number of tasks which can be allocated to a single user to check in one 'batch'.
* The combination of Product Range/Class/Category/Group that defines high-value stock.

The Daily Cycle Check screen allows the users to generate location checks for the WCS, by letting the user select whether to run the generation for a normal daily location check and/or a high-value location check (by entering 'Y' at the requested prompts).

The screen generates the tasks for the stock to be checked by first building a list of all the stock that has been checked over the preceding period (from the parameters) for the requested stock type. All of the locations checked over this period will then be excluded from a list of all locations of the selected type in the warehouse. Only Pick and Bulk locations will be included in this task list, as any other location types are either transient locations (for example Marshalling or Receipt) or due to be checked by other processes (for example Damages or Returns).

The number of tasks to be generated will be the total number of records on this location list, divided by the number of days in the period requested, rounded up.

For example:

In a warehouse where there are 20,000 locations, 15,000 for normal stock and 5,000 for high-value stock.

The users have checked 3,000 normal locations and 1,000 high-value locations in the previous periods.

When checking normal locations over a period of 90 days:

The number of normal location check tasks generated will be 12,000/90 = 134.

When checking high-value locations over a period of 60 days:

The number of high-value location check tasks generated will be 4,000/60 = 67

The process produces tasks for these checks and sends them to WCS. The tasks are split into groups, the number of tasks in each group not to exceed the parameter of the maximum number of checking tasks per group. These tasks are sorted by the WMS into a location-efficient sequence (using the putaway sequence of the location).

WCS will receive these tasks and save them to the database. These tasks will be organised in the groups specified by the WMS for ease of checking.

WCS will delete any outstanding checks on the system which have not yet been completed by the users, before adding the new checking tasks. If any individual tasks are in progress by users, these will not be deleted by this process, although tasks in the same group which have not yet been completed will be removed. This is because the WMS will send through new checking tasks for those locations where a check has not yet been completed.

The Daily Cycle Check module on the RDT will check for outstanding available checking tasks in the system. If no check tasks are found, the user will be informed and the module will exit.

When check tasks are found, the system allocates all the tasks in this group to this user, so that only one checker is allocated to each group of tasks being checked. The user is directed to the location first in the list (as ordered by the sequence of the task set by WMS when generating the tasks).

Once the user has confirmed the location in the normal way (by scanning or keyboard entry of check digits or the location code, as configured in the WCS), the RDT will direct the user to check the location in exactly the same way as the current RDT Module Bulk PI.

As each location is checked, WCS sends back check confirmation messages to the WMS, which will keep an audit of all locations checked, along with any discrepancies noted by the users. No automatic adjustments or holds of the discrepancies are made in the WMS. The task to check this location is also removed from the WCS.

To see locations which have been checked, the user can run the Ad Hoc Stock Take report, specifying a period to produce

Once a location has been checked, the RDT user will be directed to check the next location in sequence on the group of tasks being checked.

Should the user back out of these checking tasks, any tasks remaining to be checked on this group of tasks will be de-allocated from that user, so that the next checker asking for tasks can be allocated the checks.

== Select Replenishment ==
See flow chart [[#Select Replenishment.]]

This function allows an RDT user to scan a pick face, check whether there are any outstanding replenishment moves for the pick face, and complete the moves if required. The process will also generate replenishments if none are available on the WMS.

The process prompts the user to enter and confirm a location. The location is validated for several criteria:

* Pick Face
* Unknown location
* Multiple Stock codes assigned to pick face.

If multiple stock codes are assigned to the pick face, the RDT prompts the user to enter/select their owner and stock code.

Once the stock and location are confirmed, the WCS searches for any move available to replenish the pick face.

If a move is found, the user is offered the choice of completing the move as per normal pallet moves (if they are able to complete the move), or to reprioritise the move to the highest priority, ensuring it is delivered to the pick face as quickly as possible.

If no moves are available on the WCS, it checks with the WMS to see if any are available. At this point, further checks are made:

* Move exists on WMS not WCS
* Problem generating move
* No pallet of required type available

Should a pallet be found, the user is asked to complete the move in the same way as before

== Select Moves ==
See flow chart [[#Select Moves.]]

A function exists to select an individual movement task by a range of criteria. The criteria are:

* By location (Current location, source location, destination location)
* By Pallet ID (System or Customer)
* By WMS Movement reference (Movement Audit number and Line number)

Once the task is identified, the user is allowed to complete the movement task in the same way as in the normal modules.

== Ad Hoc Pallet Moves ==
See flow chart [[#Ad Hoc Movements.]]

Ad Hoc Pallet Moves in WCS are used to process movements that originate with the RDT users, rather than originating with WMS. This is to allow users to resolve problems quickly, without having to key tasks into WMS first.

Like all WCS modules, this can be disabled or password protected on users' menus.

These moves will be validated by the WCS and the WMS in combination. The user will be prompted to enter a reason code, which must be valid. They will then be prompted to enter the location from which to move a pallet. This will be validated on the WMS and the user will be required to confirm the location in the standard fashion. The user will then be prompted to enter the pallet to move, which must be present in the WMS. If this is valid, the user will be prompted for the destination location and confirmation.

When all these steps are complete, the user will be returned to the main menu, the pallet will have been moved and an audit trail maintained in WMS and WCS.

== Dual Cycling ==
The WCS also allows dual cycling in several forms: Narrow Aisle dual cycling (and the subsets allowing only moves in or out), and Wide Area dual cycling. The menu options are controlled by the log-on process, as described earlier.

Each dual cycling process supports the same functionality as any of the tasks it is performing, obeying all the same rules.

All full-pallet tasks in the WCS are available for RDT users utilising Dual Cycling.

Several parameters in the WCS control the exact performance of the Dual Cycling algorithm, including:

* Nearest Location
* Aisle Locking
* Priority thresholds
* User Aisle access, limiting individual users to certain aisles
* User's Truck Type

=== Narrow Aisle Dual Cycling ===
The WCS allows the user to select an aisle range in which they work. This range of aisles can be preset against the use using the WCS Maintenance utility. The range controls the aisles the user can work in.

There are several types of dual cycling options. All of these options can be used in conjunction with each other. So, if there is a requirement to have one truck in bulk doing all putaways and one truck in bulk doing all outbound moves, this is allowed by the WCS.

==== NADC IN ====
This option allows the users to perform the tasks which are going into the aisles. For this operation, that will be putaways. There is a possibility that this will also be housekeeping moves into the narrow aisle locations, but these are minimal.

==== NADC OUT ====
This option allows the users to perform the tasks which are going out of the aisles. For this operation, that will be full-pallet picks and replenishment moves. There is a possibility that this will also be housekeeping moves out the narrow aisle locations, but these are minimal.

==== NADC ====
Full dual cycling, mixing full pallet tasks both in and out of the warehouse. This does all of the tasks specified in the above two configurations. The tasks and the order in which they are completed depend on the configuration below.

==== NADC Configuration ====
The NADC options can be configured in several ways:

'''Manual:'''

The WCS shows a list of aisles that the user is working in (chosen at log on). This also shows the number of pallets planned to come out of the aisles, the number planned in, and whether the P&D locations are full. For this configuration, this will not cause an issue, as the P&D locations are effectively unlimited.

The user chooses an aisle from the list. They are then assigned a task from that aisle. The aisle is locked to that user and no other NADC user can access (or indeed) that aisle.

The user completed tasks in that aisle until there are no more tasks in the aisle, or they choose to move to a different aisle. When this happens, the aisle list is shown again.

The tasks completed depend on the type chosen (NADC IN, NADC OUT or NADC). The user completed as many of the tasks in the aisle as they can until there are no more tasks or they leave the aisle to go to another.

'''Threshold''':

A parameter is set in WCS, showing a threshold priority. This priority controls what the NADC process sees as high priority tasks, or just tasks that can be mixed together.

Any tasks which are below the threshold priority are grouped together and dealt with in strict location efficient order. The user will work in the aisle they are in, until no more tasks are available. The user will then be prompted to move to a nearby aisle with tasks in to complete until all outstanding tasks are completed in that aisle. The truck will move between aisles until all tasks are completed.

When tasks are received which are above the threshold priority, the tasks are allocated immediately to the next available truck that has access to those aisles.

All the high priority tasks must be completed first before any of the tasks below the threshold are completed.

When all the high priority tasks are completed, the user carries on completing the lower priority tasks until all are completed.

In Threshold setup, the priorities of the outbound tasks are the driving force, not the inbound tasks. In NADC IN, all the inbound tasks are completed in location efficient manner. In NADC OUT the high priority outbound tasks are completed first in a location efficient manner, and then the low priority tasks are completed, also in a location efficient manner.

In NADC, the high priority outbound tasks are completed first in a location efficient manner. After each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more high priority picking tasks available, the low priority tasks are completed, also in a location efficient manner. As above, after each outbound task is completed, the WCS will ask the user to complete a putaway in that aisle, if one is available. When all outbound tasks are completed within an aisle, the user will move to another aisle with outbound tasks, regardless of the number of inbound tasks remaining in the aisle.

When there are no more outbound tasks available to be completed within the aisles, the user will be prompted to complete the putaways in the aisles, in a location efficient manner.

=== Wide Area Dual Cycling (WADC) ===
Wide Area dual cycling will interleave any tasks in the wide area in the most efficient manner, attempting to ensure that the trucks operating in this area have pallets on the tines for as long as possible.

WA dual cycling needs to account for movements of the following types:

FPP- P&D to MARSH

Replen- P&D to PICK

Sky Pick- P&D to SPLIT

- SPLIT to P&D

Move - P&D to P&D

Putaway- REC to P&D

WA racking areas would be controlled via a different truck type. (Truck types limit the moves a user is able to do by the standard location type functionality in WMS). In WA racking, the tasks would be:

FPP- BULK to MARSH

Replen- BULK to PICK

Sky Pick- none required - only in NA

Move - BULK to BULK

Putaway- REC to BULK

Putaways should not be allowed to be picked up from receiving location if the P&D it is to be placed to is currently full (in a limited P&D environment). This should only occur if the number of pallets allowed at the P&D is set higher in WMS than WCS. This is a reasonably valid set-up, to allow for the time taken to take a pallet from receiving to P&D, and then to be put away by a NA truck.

The sequence of actions would be:

# Start WA DC
# Check for putaways or cross-docks available.
# If none, display message, go to 5.18.2below.
# If some, get task (user scans PID)
# If cross-dock, take to marshalling, go to 5.18.2below
# If putaway, take to P&D or BULK
# Get next task (if location efficient, nearest; if priority efficient, next in sequence)
# If none, display message, go to 5.18.2below.
# If task is move (P&D to P&D, P&D to BULK, BULK to P&D or BULK to BULK), complete task, go to 5.18.2above.
# If task is sky pick (P&D to SPLIT)
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If task is FPP (P&D to MARSH or BULK to MARSH) or Replen (P&D to PICK or BULK to PICK),
## Complete task
## Look for sky pick (SPLIT to P&D). If found, complete task, go to 5.18.2above.
# If no tasks found at all in loop, display message and exit else go to 5.18.2above.

=== DC Examples ===

[[Image:Diag1.PNG]]

In this example, we have 5 physical aisles (denoted by an 'A' before the number), made up of 10 aisles in the system. The threshold priority for this example is 4. Each aisle has its input P&D shown, and it is assumed that these P&Ds will have 'abundant' moves on them. The numbered boxes in the aisles (e.g. 4) are the tasks to be moved to the output P&Ds. For the purposes of this example, it is assumed that the P&Ds will be emptied immediately. Tasks will be identified in this example by the aisle and priority e.g. 5-7 denotes the priority 7 move in aisle 5 (physical aisle A3).

So, a driver logs on to an RDT, operating NA DC in the aisle range 1 to 10.

The WCS will direct them to the highest priority task in the range. In this case, this is either 1-2 or 6-2. It is assumed for this example that the driver will be sent to 1-2.

All tasks in the physical aisle A1 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 1-2, then 1-3, then 2-3. In between each of these tasks a putaway will be interleaved, if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 6-2 in A3.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is 6-2, then 5-3. Again, each task will be interleaved with a putaway if possible.

When all of the outbound tasks above the threshold priority have been completed in the physical aisle, the WCS will direct the driver to the nearest, highest-priority task (above the threshold value) to their current location, within the aisle range. This is task 3-3, rather than 9-3, as it is closer.

All tasks in the physical aisle A3 above the threshold priority will then be completed, in priority/location sequence. In our example, this is only the task 3-3, then a putaway.

The next task is 9-3, as this is the closest task above the threshold value. The user will then complete tasks 9-3, followed by 10-3.

At this point, all tasks with priorities above the threshold, within the user's aisle range have been completed. The WCS will now direct the user to the closest task within the range, regardless of priority. (Note: If a higher-priority task becomes available during this next stage, the user will be directed to it).

The next closest task is 10-4, then 9-4, both being in the same physical aisle in which the user is currently. Next, the user would be directed to physical aisle A4, to complete the tasks there, i.e. 7-5, 8-4, 8-6 then 7-8.

The remaining tasks would be processed in the following order:

Move to A3. Do tasks 5-8, 6-8, 5-7.

Move to A2. Do task 4-8.

Move to A1. Do tasks 1-8, 2-8.

As has already been noted, all tasks will be interleaved with putaways if they are available.

In our example, we have now completed all tasks out of all aisles in the range. We still have 5 input P&D locations, with 3 pallets on each, to be placed into the racking. These will then be completed by the WCS. Note: If more pulling tasks of whatever priority become available during this phase, the user will be directed to it.

The inbound tasks will be allocated to the driver in much the same way as the outbound (pulling) tasks were allocated to him, as can be seen in the following example.

[[Image:Diag2.PNG]]
In this example, we are concerned only with the inbound tasks on the input P&D locations. We assume for the purposes of this example that no pulling tasks are available in the aisle range, nor that any will arrive during the example. We also assume that the pallets are there on the P&D, in the order suggested by the WCS.

At the end of our last example, the driver was in physical aisle A1. We will begin again at this point.

The WCS would suggest the user to go to PD1, as there is a task above the threshold priority waiting to be put away. The RDT would request the driver to scan the pallet being put into the racking. The tasks would be completed in the order in which they are on the P&D, regardless of the order of the tasks. In our example, they are in the correct order.

Once all tasks on this P&D are completed, the WCS directs the user to the next P&D, within their aisle range, with the highest-priority task on it. In this case, that is PD2, for aisle A2. The P&D does have a task on it at priority 2, even though it is second on the P&D.

The driver would then complete the first task, at priority 3, before completing the second task at priority 2. Once this second task is completed, however, the WCS will direct the driver to the next aisle with a high-priority task on it, as there are no more tasks on PD2 to be completed.

The aisle the driver would be directed to in our example would be A3, and PD3 has a priority 2 task on it. The driver would then put all three pallets away, in order to clear the priority 2 task on the P&D.

Once completed, the WCS would then direct the driver to PD5, to complete the high priority tasks on the P&D.

The user would then be directed to complete the tasks remaining on the P&Ds in the following order: The three tasks on PD4 would be next, as they are closest the driver's previous location (PD5), then the remaining task on PD2.

==Stock Replenishments==

At the point of part replenishments being generated by ''CALIDUS'' WMS, tasks will be sent to ''CALIDUS'' Mobile to complete them via the RF units.

To control whether these tasks are sent from this process, a new Owner rule must be set up. This allows the users to specify, per owner, whether part replenishment tasks are being sent to ''CALIDUS'' Mobile to be completed.

These tasks show the source (bulk), destination (pick face), pallet ID from, pallet ID to (the newly-created pallet ID in the pick face) and various other details of the stock, to aid in printing labels for the stock items.

These stock replenishment tasks are generated from the standard ''CALIDUS'' WMS screens (Bulk to Pick Replenishment, and dynamically from the Allocation process). The rules defining whether full pallets or part pallet replenishments are generated are standard.

The RF application has a Part Replenishment module and follows the flow below:

*The RDT user enters the Part Replenishment module.
*The user will be prompted to enter a Printer at this point.
*(1) The user will be directed to the first available high-priority part-pallet replen, in a location-efficient manner.
*(2) The RDT will prompt the user to go to the source location (i.e. the bulk location of the replenishment). They will confirm the location by scanning the barcode or entering the check digits.
*The RDT will tell the user which pallet to get and the user will confirm by scanning or keying the pallet id.
*The RDT will inform the user of the number of boxes required to be collected for the replenishment. The RDT will also display the pack size and total impressions quantity being collected (if the stock is impressions-controlled). The user will confirm by entering the quantity taken from the pallet. The user will have the ability to change the quantity being replenished (by entering a different value or entering 0 if no stock can be picked. In this case, the user will be prompted to enter a reason code.
*Once the user has confirmed the quantity of stock being picked, the RDT will request the user how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box. The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once this is completed, the RDT will display a dialogue confirming that this stock has been collected. The user will be asked if they want to continue collecting stock or take what has been collected so far to the respective pick faces. If the user chooses to continue picking, the RDT will request the next available high-priority part-pallet replen, in a location-efficient manner and then return the user to (2) above.
*Should the user choose to take the stock to the pick faces (or there are no more replenishments available at this time), (3) the user will be prompted which ‘pallet’ of stock to deliver first. The user will scan the pallet id on one of the cartons collected.
*The RDT will direct the user to the pick face being replenished with this pallet. It will display the total qty, impressions and pack size (as relevant). It will request the user to confirm the pick face by scanning the barcode or keying the check digits. At this point the user will take all the stock off the pallet for that pallet and replenish the pick face. The labels on the boxes (printed at pick) will be used to identify the pallets in the pick face. The user will have the option of re-printing the pallet labels at this point (via a function key press) in case the labels on the boxes are unusable or discarded. If the user choose this option, they will be asked how many pallet labels are required for this replenishment. The user should enter the number of labels required to label each box in the pick face (i.e. the tote). The RDT will print that number of labels in the required format. If there is an issue with the printer or the labels do not appear, the user will have the option of reprinting the labels or changing the printer at this point, before confirming that the labels are printed OK.
*Once all the stock is in the location and labelled, the user will confirm the replen completed by scanning the barcode or keying the check digits. If there are more pick faces to replenish from the stock collected, the RDT will then direct the user to scan the next pallet and continue from (3) above. If there are no more pick faces to replenish in this run (i.e. all the stock has been replenished), the RDT will display a completion dialogue and ask the user if they want to continue replenishing stock. If the user chooses to continue replenishing, the user will be returned to (1) above. If not, the RDT will exit to the main menu.

''CALIDUS'' Mobile sends a completion message back to ''CALIDUS'' WMS for each replenishment move completed in this manner.

= Bespoke RDT Modules =
Other modules developed in the past, but not part of the standard product, are:

* Serial number Capture at Receipt and Despatch
* Loading and despatch confirmation by carton
* Shipment Pallet building (from Packing)
* Housekeeping moves of Shipment Pallets
* Despatch by Shipment Pallet ID
* Links to automated systems (MHE, camera scanners, conveyors, P&D systems, etc)
* Uploading of batch files to WMS
* Stock Moves (Combined Split)
* Ad Hoc Putaway

Some these modules are covered in more detail in the following sections.

== Serial Number Capture at Receipt and Despatch ==
This functionality does not link into the generic receipt module, or into any despatch modules.

The nature of serial number scanning is such that the Serial Number processing and validation is dependent entirely upon the barcodes received and the format of the information contained therein.

Flowcharts for these processes can be found in appendices.

=== Serial Number Capture at Receipt ===
The RDT will prompt the user for the GRN being received against, which is validated.

The user then enters the pallet the serial numbers are being received against, which is also validated against the preadvice sent from the WMS.

The preadvice contains details of how serial numbers are to be entered for each stock code. These types are Range or Random.

If the type is Range, the user is prompted to enter a first and last serial number for the range. The RDT examines this to ensure it fulfils the quantity required for the receipt line, by extracting the data from the serial numbers.

If the type is Random, the user is prompted to enter a Lot number for the subsequent serial numbers. The RDT will then prompt for a batch of serial numbers, up to the amount required in one lot. The RDT will then continue to prompt for the required number of Lots until the pallet is completed.

The user can then continue entering serial numbers for all other pallets on the receipt, until all are completed.

=== Serial Number Capture at Despatch ===
The RDT prompts the user for the Order Number being despatched, which is validated.

The RDT then retrieves the details of the first stock to be despatched, and displays the details of the line, plus the details of the pallet to be found in the despatch bay.

The user can then choose a scanning method:

By Batch - The user confirms that all serial numbers for a specific customer's batch have been despatched.

By Lot - The user confirms that entire Lots of serial numbers have been despatched.

By Serial - The user confirms each serial number despatched individually.

When the order line has been completely fulfilled, the user is prompted to move on to the next order line, until all required serials for all lines have been scanned.

== Loading by Carton ==
In order to use this process, carton picking must be used (a variant of Part Picking, where all cartons are labelled with unique carton references as they are picked).

When WCS sends message to WMS regarding completion of the picking task, the system should create carton records for each carton picked.

See flow chart [[#Loading by Carton.]]

RDT logs in to Loading process.

Scan / Enter Store number(s) or Route/Load.

Scan / Enter Vehicle number

Then scan Carton barcode for the items to put them on the truck.

If an item is found where the barcode is unreadable or the barcode is missing, there is a function key - No ID. When pressed, the user should be prompted to enter the order number and the item number. This should be enough to identify the item.

Function keys available:

F1 - Truck Full - Show user summary screen of what is on that truck. User confirms.

F4 - Finished (no more stock for order/route/load) - Show user screen of what is missing for the route/load. User told to find shortages. If the user confirms that they are finished again (by pressing the same function key), the unit should prompt for a supervisor username and password.

When completed, the WCS marks all cartons scanned as loaded and then creates a flat-file EDI message for sending back to the WMS.

When the EDI message is received, the WMS updates its carton records with the cartons loaded, the prints a despatch note for the stock.

== Loading (by Picking Container) ==
This process can be used in place of the Despatch process above. It can be used either directly from Pick Confirmation, or from Deconsolidation and Pack (using the final media number).

See flowchart [[#Loading (by Picking Container).]]

In order to use this module, the system must have Picking Containers enabled.

The user is prompted to enter a route/load or order to be loaded. Once confirmed, the RDT displays a list of all the containers that must be found for the stock to be considered loaded. The user must scan the picking container of the pallets loaded.

If containers are lost, the user is given the ability to reflect this through an error function key.

As each container is entered, they are removed from the RDT screen.

Once all containers are loaded, the WMS is updated showing that the order or load is despatched.

== Shipment Pallet Processes ==
These functions should only be used if Packaging functions are in use and are RF enabled (currently only in Oracle FSCE).

All shipment pallet and location information is held against the order and pack list, and is not replicated in the normal WMS pallet tables.

Flowcharts for these processes can be found in appendix [[#Shipment Pallet processes]].

=== Shipment Pallet Building ===
This module is used to take completed packages and place them on a shipment pallet, ready for loading and despatch.

The user is prompted to enter a valid package, which is then validated.

The user then scans a shipment pallet ID, usually from a list of pre-printed unique barcode labels.

If the pallet already exists, the RDT checks the validity of placing the package on the shipment pallet. The criteria used to check this varies based on the data that is sent through to the WCS for this purpose, but commonly consists of carrier, priority and a 'Share Pallet' flag, which controls whether packages of different priorities can be shipped together.

If the pallet does not exist, one is created, with the criteria of the package being placed on it.

When placed on a pallet, the package is updated on WMS to show the pallet on which it is to be despatched.

=== Shipment Pallet Move ===
This module is used to move completed shipment pallets to storage locations, prior to them being loaded and despatched.

The user is prompted to enter a valid shipment pallet. This pallet must be fully built and closed. Closing of shipment pallets is achieved on the WMS, which then updates the WCS.

The RDT then prompts for the storage location of the shipment pallet, which is validated.

The WMS is updated with the new storage location of the pallet.

A pallet may be moved several times before it is loaded.

=== Shipment Pallet Despatch ===
This module is used to confirm that a shipment pallet has been loaded and despatched.

The user is prompted to enter a shipment pallet, which is validated as ready for despatch.

The user is then asked to confirm that this pallet is loaded.

When confirmed, the WMS is informed that the pallet is despatched.

== Combined Split ==
This is a module written for another WMS and is currently unavailable in the normal WCS/WMS combination, either Oracle or C-ISAM.

The combined split module allows stock to be moved from one pallet to another on an ad-hoc basis.

See flowchart [[#Combined Split.]]

The user scans or enters the pallet of the stock to be moved.

The Owner of the stock is prompted for. A default value will be displayed if one was entered when the user logged on.

The stock to be moved is then prompted for. Once the code has been scanned or entered, it is checked against the WMS to validate it. If details of the stock for the source pallet cannot be found, an error is displayed - 'Stock xxx not found on Pallet yyy'

The quantity to be moved is prompted for. If the user has entered more than there is expected to be on the pallet, an error is displayed showing the amount entered and the amount the system expects to be present on the pallet.

At the next prompt, the ID of the destination pallet is scanned or entered. If the user enters '0', they are given the opportunity to enter a destination location instead. This location is validated as normal

When all details have been entered, stock update messages are sent to WMS.

== Ad Hoc Putaway ==
This module is for use in a shelving environment, where stock on a pallet is taken to individual shelves, and as much of it is located in that location as possible.

See flowchart [[#Ad Hoc Putaway]].

The user is prompted to fetch a pallet and find a location in which some of the stock can be located. Once confirmed at this location, the user is prompted to enter the amount of the stock they intend to put away in that location, and then scan the stock code on each carton once for each carton put away.

Once all the stock has been put away, the user can then move onto other locations, until the pallet is empty.

If they reach the end of the aisle with stock left on the pallet, the user can press F1 to indicate that the pallet still has stock on it. They are then prompted to return the half-full pallet to the receiving location.

If all the stock on the pallet can fit in one location, the user can press the F5 key when prompted for the putaway quantity, to indicate that all remaining stock is to be placed in the location.

If the pallet has less stock on it than the user was informed of, the user can indicate that the pallet is empty by pressing the F4 key. They must obtain authorisation from a supervisor to continue.

= WCS Functionality =
A priority of the development team has been to make the WCS system front-end as user-definable and friendly as possible. This means that most of the screens described below have customisable toolbars, customisable table structures, and hot-menus. Help is also provided. The menu system has been tailored to place most frequently used functions in reasonable order for speed. Hot key combinations have also been used, staying as close to Microsoft â„¢ standards as possible for familiarity.

A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.

== User Logon ==
Employee codes are used to log on to the WCS Maintenance system, in the same way that the RDT users are required to log in. This allows for the logging of actions taken by administrative users. The system will not allow the user to log on to the system if they are logged on somewhere else, depending on the way the user has been set up in the WCS.

== Reprioritisation of Pallet Moves and Picks ==
These screens allow the users to manually modify the priority of existing movements and picks (full pallet and case picks) within the system. Standard and advanced selection criteria are provided and these selection values can be saved as templates for quick recall.

Tasks can be set to error status, held, recalled to available tasks and even deleted from the WCS (with logging), if the user has sufficient privilege.

== Pick Summary ==
To aid in identifying the current picking work-load, this screen displays the tasks grouped by route and load, showing the total number of tasks per load and a general status of the load (error, in progress, pending, held). Double-clicking on a line displays all the picking tasks in the screen shown above.

=='''Logging'''==
All incoming messages, outgoing messages, completed tasks and exceptions are logged to the database, so that they can be reported on. It is also possible to have all of these logging messages sent to a separate database, for easier archiving later.

== Employee Activity ==
This screen displays all employees logged on to RDTs in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an employee is engaged in RDT activity, details of this activity can be seen by double clicking on the relevant employee - a pop-up screen will display the details of the job.

Any user that has had communication problems with the WCS (an unlikely occurrence, normally due to RDT hardware damage) can be freed from the WCS, allowing any tasks they were involved in to be completed by other available RDT users.

Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Exceptions ==
Exceptions are pre-defined events that occur in RDT processing of tasks. Examples of exceptions are: changing the quantity of a pick; cancelling a pick; cancelling a move; repositioning a move; changing a pallet on a move; changing a pallet on a pick or; adding a pallet at stock take. These may need to be observed and acted on by administrative staff and need to be viewable. This screen displays all exceptions that occur in the specified company and warehouse. The screen is automatically refreshed every few seconds to keep the screen as current as possible. When an exception has been logged, details of this activity can be seen by double clicking on the relevant line - a screen will display the details of the job.

Any Exception activity (e.g. modifying pick quantities, supervisor overrides, administration functions, repositioning and cancellation of movements, etc) by a WCS user is logged (see [[#Logging]] above) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.

== Enquiries ==
Enquiries are provided for:

* Goods Receipts
* Stock Takes
* Shipment Pallets and Packages
* Pick Containers
* Deconsolidation and Despatches
* Movements
* Picks
* Historical Activities
* Historical Exceptions
* Location Types
* Trucks
* Pallet Types
* Reason Codes
* Receipt Types

== Standing Data Maintenance ==
The WCS provides the ability to maintain the standing data required by the system, including:

* System Parameters
* Warehouses
* Users (employees)
* Owners
* Groups
* Aisles
* RDTs

== Held Priority ==
This allows the lowest level of priority (9) to be processed as a held task. The task will then not be actionable by RDT users until the task is released. This feature can be turned off.

== Deleted records ==
It is possible to change the WCS system to not delete completed tasks from the database when they have been completed. They are instead marked for deletion. These are then cleared out by a scheduled event (see later). This method has the advantage that logging of events has greater detail, but has the disadvantage of taking more space in the database. This system of not deleting records also allows re-submissions and reprocessing of tasks on the RDT.

== Parameter-controlled communication ==
System administrators have the ability to access additional set-up screens. These screens allow the WCS to be customised to communicate with any networked machine, via TCP/IP.

=='''Parameter-controlled Functions'''==
Each RDT module can be enabled, disabled or password protected by system administrators. This can be done for an individual user, or for a warehouse as a default. This means that the system can be tailored for specific use for a warehouse, or even a specific user in a warehouse.

WCS Administration functions can also be tailored for each user in the WCS, so that certain functions can be limited to certain users.

== Total database control ==
System administrators have access to generic database maintenance functions. These include:

* Repairing and compacting the RDB
* Clearing log files
* Complete file maintenance, via a separate utility
* Clear-down parameters

== Reports (user-definable) ==
Generic reports are available to the user, showing statistical analysis of employee activity, problems encountered, etc. Some data list reports are included for auditing.

Reports are viewed through the standard Windows functions i.e. notepad or Word, and can be exported for external printing or directly for emailing.

Reports are available as standard using the MS report designer component. Users can write their own reports utilising any ODBC-compliant report-writing tool at their disposal.

== Scheduler ==
A scheduler is included as part of the package to allow the user to place some small system maintenance programs onto the PC to run at regular intervals. These automatic maintenance programs are listed below.

=== Clear-down ===
This program clears out old data and log files and tidies them up in a folder, specified by a system administrator. The number of days that the data stays on the system is user-definable, as is which data is cleared out.

=== Compactor ===
The compactor repairs and compacts the RDB on a regular basis. This is not strictly necessary on well-managed systems, but will aid those users who wish the run the WCS in a very automated way.

=='''RDT Messages'''==
The WCS has a facility to send messages to RDT users who are on the Wireless LAN. These messages can be controlled in this way by logging the administrative user on to the Wireless LAN through the WCS Server. Messages are typed in, a user or user is chosen and the message is delivered to the RDT user the next time they request work. Warehouses that require communications to remote RDT users can now do so without further expense.

=Appendices=

==WCS-WMS Communication==

[[Image:Diag3.PNG]]

==Flowcharts==
==='''RDT Log-on Procedure.'''===

[[Image:FunctionalityFlowChart1.png]]

#
==='''Receipts.'''===

[[Image:FunctionalityFlowChart2.PNG]]

[[Image:FunctionalityFlowChart3.PNG]]

[[Image:FunctionalityFlowChart4.png]]

[[Image:FunctionalityFlowChart5.png]]

[[Image:FunctionalityFlowChart6.PNG]]

[[Image:FunctionalityFlowChart7.PNG]]

#
==='''Putaways.'''===

[[Image:FC8.PNG]]

[[Image:FC9.PNG]]

[[Image:FC10.PNG]]

#
==='''Full Pallet Picking.'''===

[[Image:FC11.PNG]]

[[Image:FC12.PNG]]

[[Image:FC13.PNG]]

#
==='''Part-pallet Picking.'''===

[[Image:FC14.PNG]]

[[Image:FC15.PNG]]

[[Image:FC16.PNG]]

[[Image:FC17.PNG]]

[[Image:FC18.PNG]]

#
==='''Pallet Moves.'''===

[[Image:FC19.PNG]]

[[Image:FC20.PNG]]

[[Image:FC21.PNG]]

#
==='''Stock Take.'''===

[[Image:FC22.PNG]]

[[Image:FC23.PNG]]

[[Image:FC24.PNG]]

[[Image:FC25.PNG]]

#
==='''Pallet Enquiry.'''===

[[Image:FC26.PNG]]

#
==='''Location Enquiry.'''===

[[Image:FC27.PNG]]

#
==='''Movement Enquiry.'''===

[[Image:FC28.PNG]]

#
==='''Ad Hoc Movements.'''===

[[Image:FC29.PNG]]

[[Image:FC30.PNG]]

#
==='''Bulk PI.'''===

[[Image:FC31.PNG]]

[[Image:FC32.PNG]]

#
==='''Select Moves.'''===

[[Image:FC33.PNG]]

#
==='''Loading by Carton.'''===

[[Image:FC34.PNG]]

[[Image:FC35.PNG]]

#
==='''Shipment Pallet processes.'''===

[[Image:FC36.PNG]]

[[Image:FC37.PNG]]

#
==='''Select Replenishment.'''===

[[Image:FC38.PNG]]

[[Image:FC39.PNG]]

#
==='''Serial Number Capture at Goods Receipt.'''===

[[Image:FC40.PNG]]

#
==='''Serial Number Capture at Despatch.'''===

[[Image:FC41.PNG]]

#
==='''Combined Split.'''===

[[Image:FC42.PNG]]

#
==='''Ad Hoc Putaway.'''===

[[Image:FC43.PNG]]

#
==='''Cherry Picking.'''===

[[Image:FC44.PNG]]

#
==='''Deconsolidation.'''===

[[Image:FC45.PNG]]

[[Image:FC46.PNG]]

[[Image:FC47.PNG]]

[[Image:FC48.PNG]]

#
==='''Despatch by Order.'''===

[[Image:FC49.PNG]]

#
==='''Loading (by Picking Container).'''===

[[Image:FC50.PNG]]

[[Image:FC51.PNG]]

WCS Maintenance

2025-10-30T10:28:37Z

Anw: 291594 Truck Type Logon Validation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=WCS Maintenance Guide
|Reference=UG 106181
|Version=4
|Date=14th November 2007
|Sysver=3.4
}}


= WCS Maintenance =
This suite allows administrators to configure the [[WCS]] system, and modify the running of tasks within that system for the RDTs. When you log on, you need to open the WCS database being used by the central WCS. There should only be one. You will not need to open the database if you start the WCS Maintenance program from the WCS Server program. This option is only available if the maintenance program is being run on the WCS Server PC. The Open Database command is on the File Menu.

When you open a database, you will by default be shown a list of recently opened database files.

[[Image:Maint1.png|600px]]

This allows for multiple WCS systems to be in operation for you. If you do not want to use this list, you can disable it by the check box provided. If the database you require is not listed, then you can choose to see more files. This will open a standard windows explorer dialogue. Once you have identified the database, this will be added to the top of your list of recent files. The settings panels allow you to modify the options for this list.

[[Image:Maint2.png|200px]]

You will be asked to enter your company and warehouse codes. This is to identify the data that you will be enquiring on in the RDT database. This can be changed later if required. The codes are the same as in your main warehouse management system.

You are also prompted to enter your username code and password, if required. These are the same as the employee codes in your main warehouse management system.

The options you have available to you within the program depend upon the group your username has been given. The passwords (and other options) for your user, directly relating to this program can be maintained from the main menu from Standing Data Maintenance. If you have unavailable options, these items will be greyed out on the menus, and will not be available from the toolbar. Contact your administrative manager to obtain more options to the system.

There are several menus, which control all the features of the WCS Maintenance suite of windows. They are:

File Menu

Edit Menu

Tasks Menu

RDT Comms

System Tools Menu

Reports Menu

SD Maintenance Menu

Windows Menu

Help

Click on one of the items listed above to find help about the options available on that menu.

Most of the useful items on the menus can be accessed via the toolbar. The toolbar can be maintained to suite your preference. See ToolBars for more information on this.

This help can also be accessed by use of the F1 key, within the windows themselves. This, along with the icon available on most windows, is context-sensitive and will take you straight to a related topic. If no related topic is found, you will be taken to this topic.

== WCS Maintenance Menus ==
Menus:

File Menu

Edit Menu

Tasks Menu

RDT Comms

System Tools Menu

Reports Menu

SD Maintenance Menu

Windows Menu

Help

== File Menu ==
Menu Items:

Open Database

Close Database

Print

Print Selection

Exit

=== Open Database ===
Shortcut: CTRL-O

This command is not necessary if you are running the program from the WCS Server. It can be used to change the database that you are linking to, if multiple RDT systems are in use. Simply follow the prompts until the RDT database is found (it is usually called ‘rdt1.mdb’).

=== Print ===
Shortcut: CTRL-P

This option prints the selected window’s contents. If you have accessed this option from the icon, you will be prompted for confirmation, to prevent printing thousands of pages of data accidentally. If you have selected records from the active window, the button will work as the option Print Selection.

Related Topics:

Print Selection

=== Print Selection ===
This option prints a selection of records from the selected window.

=== Close Database ===
Shortcut: CTRL-W

This option closes down the currently opened database. You will be unable to use most of the functions if you do not open another database. The only options available to you when the database is closed are Repair Database and Compact Database.

Related Topics:

Compact Database

Open Database

=== Exit ===
Shortcut: CTRL-Q

This option exits the WCS Maintenance program.

== Edit Menu ==
Menu Items:

Cut

Copy

Paste

=== Cut ===
Shortcut: CTRL-X

Cuts selected data to the clipboard.

=== Copy ===
Shortcut: CTRL-C

Copies selected data to the clipboard.

=== Paste ===
Shortcut: CTRL-V

This option pastes data from the clipboard to the selected area.

== Tasks Menu ==
Menu Items:

Pallet Movement Maintenance

Pick Maintenance

Picking Container Maintenance

Deconsolidation Maintenance

Goods Receipt Enquiry

Stock Take Enquiry

Shipment Packages Enquiry

Shipment Pallets Enquiry

=== Pallet Movement Maintenance ===
[[Image:Maint3.png|600px]]

On start-up, you are presented with the Select Movements window. When data has been selected, you will be returned to this screen. All data from the movements screen that conforms to your selection criteria will be displayed. The window will display all the data that is required, and in a reasonable order, but this can be modified.

There is an icon bar on this screen, to aid you.

To add new fields to or remove existing fields from the display, right-click on the grid header anywhere and select the option 'Field Chooser', or hit the appropriate icon on the toolbar.

To change the position of the fields in the grid, drag the required field to its new position and then release the mouse button.

You can change the way the data is sorted (the order the rows appears in the grid) in several ways. You can double-click on the column header to sort ascending on that field (low to high). You can then double click again on that field, and it will switch to descending (high to low). Double clicking again will remove the sort.

You could also right-click on the required field header, and choose ascending, descending or none from the pop-up menu.

You can sort on several fields at the same time by using one of the above methods on several of the fields, in the order you require. Each column will be marked to show that data has been sorted within it.

The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

Reprioritisation of movements can be achieved by several methods. You can either reprioritise each line singly by right clicking and choosing re-prioritise line, or you can select several lines. This is done by using shift or control keys with the mouse click, then right-clicking and choosing 'Re-prioritise Selection' from the menu, or the corresponding button. Either way you will be taken to a screen to enter the new priority of the movement(s), then click OK. You will be shown the success or failure of the activity on a progress screen.

When you are finished, the data will be re-displayed with the new elements in place and the WCS database will have been updated.

You can remove a task from the list of available tasks by setting the task to Error status. This is different to holding the task, as held tasks can still block P&D locations - Error tasks won’t. Simply right-click on the task you want setting to error status and choose the Set Error option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been set to error status and will be displayed in red. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

If you wish to print out details of the movements in the list, either those selected or all the records in the list, use the print icon or options from the main WCS maintenance menu.

'''Supervisor options'''

If you are a supervisor user (defined against your user name in the Users Maintenance screen), you also have the option of deleting tasks from the database. Simply right-click on the task you want removing from the database and choose the Delete option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been deleted from the database. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

See also:

Select Data Window

Field Chooser

Miscellaneous

Re-prioritise Entry Window

Help

ToolBars

=== Pick Maintenance ===
[[Image:Maint4.png|600px]]

On start-up, you are presented with the Select data window. When data has been selected, you will be returned to this screen. All data from the screen that conforms to your selection criteria will be displayed. The window will display all the data that is required, and in a reasonable order, but this can be modified.

There is an icon bar on this screen, to aid you.

To add new fields to or remove existing fields from the display, right-click on the grid header anywhere and select the option 'Field Chooser', or hit the appropriate icon on the toolbar.

To change the position of the fields in the grid, drag the required field to its new position and then release the mouse button.

You can change the way the data is sorted (the order the rows appears in the grid) in several ways. You can double-click on the column header to sort ascending on that field (low to high). You can then double click again on that field, and it will switch to descending (high to low). Double clicking again will remove the sort.

You could also right-click on the required field header, and choose ascending, descending or none from the pop-up menu.

You can sort on several fields at the same time by using one of the above methods on several of the fields, in the order you require. Each column will be marked to show that data has been sorted within it.

The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

Reprioritisation of data can be achieved by several methods. You can either reprioritise each line singly by right clicking and choosing re-prioritise line, or you can select several lines. This is done by using shift or control keys with the mouse click, then right-clicking and choosing 'Re-prioritise Selection' from the menu, or the corresponding button. Either way you will be taken to a screen to enter the new priority of the movement(s), then click OK. You will be shown the success or failure of the activity on a progress screen.

When you are finished, the data will be re-displayed with the new elements in place, and the WCS database will have been updated.

You can remove a task from the list of available tasks by setting the task to Error status. This is different to holding the task, as held tasks can still block P&D locations - Error tasks won’t. Simply right-click on the task you want setting to error status and choose the Set Error option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been set to error status and will be displayed in red. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

If you wish to print out details of the data in the list, either those selected or all the items in the list, use the print icon or options from the main WCS maintenance menu.

Picks are allocated to RDT users in groups and these groups are decided when the task is received from the WMS. To split a number of picks out of an existing group into a new group, select a number of picks in one group, then right-click and choose ‘Create Pick Group’. Alternatively, you can click on the icon on the icon bar. The picks will then be split into a new group.

Picks in different groups cannot be put into a new group together. Additionally, pick tasks in progress will not be changed to a new group.

'''Supervisor options'''

If you are a supervisor user (defined against your user name in the Users Maintenance screen), you also have the option of deleting tasks from the database. Simply right-click on the task you want removing from the database and choose the Delete option from the pop-up menu. The program will ask you for a reason - enter some descriptive text here. When OK is pressed, the task will have been deleted from the database. An audit record will have been written to the Exceptions log, visible by using the Exceptions Enquiry screen.

See also:

Select Data Window

Field Chooser

Miscellaneous

Re-prioritise Entry Window

Help

ToolBars

==== Re-prioritise Entry Window ====
When you have chosen lines to re-prioritise, you will be taken to this dialogue window, to enter the new priority of the lines.

[[Image:Maint5.png|200px]]

Once this is done, click OK. You will be shown the success or failure of the activity on a progress screen.

=== Goods Receipt Enquiry ===
This screen allows you to enquire on the Goods Receipt Preadvice file, showing all outstanding receiving tasks for the RDT users.

The form has two views, a detail/select view, and a grid view.

[[Image:Maint6.png|600px]]

[[Image:Maint7.png|600px]]

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Stock Take Enquiry ===
This screen allows you to enquire on the Stock Take file, showing all outstanding stock take tasks available to the RDT users.

The form has two views, a detail/select view, and a grid view.

[[Image:Maint8.png|600px]]

[[Image:Maint9.png|600px]]

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Shipment Packages Enquiry ===
The Shipment Packages Enquiry screen allows the user to see the packages that are available for the RDT Shipment Pallet Building module.

[[Image:Maint10.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint11.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

=== Shipment Pallets Enquiry ===
The Shipment Pallets Enquiry screen allows the user to see the pallets that have been built by the RDT Shipment Pallet Building module. These pallets will be available for Movement or Despatch, depending on the status of the pallet.

[[Image:Maint12.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint13.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

=== Deconsolidation Maintenance ===
The Deconsolidation Maintenance screen allows the user to see the stock that is ready for deconsolidation after picking. The screen also shows orders that are ready for despatch.

The screen allows the status of the tasks to be changed.

[[Image:Maint14.png|200px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint15.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

The screen allows tasks to be held or released. Select one or multiple tasks on the grid, and then press the hold/release button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

The screen allows tasks to have an error status set against them, or cleared. Select one or multiple tasks on the grid, and then press the Set/Clear Error button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

=== Picking Container Maintenance ===
The Picking Container Maintenance screen allows the user to see Picking Containers. The screen also shows orders that are ready for deconsolidation.

The screen allows the status of the containers to be changed.

[[Image:Maint16.png|600px]]

The screen starts by showing a filter, with a list of items that can be selected. The filter can be shown at any time by pressing the Filer option on the toolbar.

[[Image:Maint17.png|200px]]

Enter any search criteria here, and then press OK. The data will be refreshed, selecting only the data that matches the search criteria.

To refresh the data, press the refresh button on the toolbar.

The screen allows containers to be held or released. Select one or multiple containers on the grid, and then press the hold/release button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

The screen allows containers to have an error status set against them, or cleared. Select one or multiple containers on the grid, and then press the Set/Clear Error button on the toolbar. The screen will pop-up a selection box, asking you what task you want to perform, and a reason associated with it. This reason will be written to the Exceptions log.

=== Pick Summary Screen ===
The Pick Summary screen allows the user to see a summary of all the picking tasks available in the WCS.

On entry, the screen will be in ‘data select’ mode. Data is selected by entering the owner of the orders and the route. You can select asterisk (*) from the drop-down lists to select all the owners or routes.

Once the criteria have been selected, clicking the refresh button will display the selected data (‘Display’ mode) on a grid.

* Should any of the records on the route/load be in error, the status will be “Error” and the background colour of the whole line will be red. The fore-colour will be in white. The text will be in '''bold.'''
* Should any of the records on the route/load be held, the status will be “Held” and the background colour of the whole line will be red. The fore-colour will be in white. The text will be in '''bold'''.
* Should any of the records on the route/load be in progress, the status will be “In Progress” and the text of the whole line will be displayed in green and '''bold'''.
* Otherwise, the records will be put in default black, with no bold.

The colouring on the line will be decided in the order displayed above. Therefore, if there are tasks held, and there are some in progress, the line will be displayed as if all lines are held.

The grid allows single-line selection and re-sizing of columns and is scrollable.

Where multiple and different customer details are found for a load, ‘*’ (asterisk) is displayed in the Customer column.

The screen displays a status bar, showing the total number of outstanding tasks displayed in the grid. If no records are selected based on the criteria entered, the status bar will display “No records selected”.

Clicking the Refresh button will refresh the record set, based on the selection criteria already entered. The grid will then be re-displayed based on the new data selected.

Clicking the Select button will clear the grid and the screen will re-enter ‘Data Select’ mode and allow you to enter the selection criteria again.

Should you double-click on a line, the pick reprioritisation screen is displayed, showing the orders matching the route and load on the line chosen. This screen will then operate in the same way as the normal pick reprioritisation screen, but without allowing you to re-select data.

=== Field Chooser ===
This screen shows you the all the elements that you can display on the grid.

[[Image:Maint18.png|200px]]

To change the items displayed, check the box next to the fields you want to see, and uncheck those you don’t want to see (by left clicking).

If you are using the field chooser to modify a grid display, the grid display will change as you change the checks. When you have finished, close the window, with either the OK button, or just the ‘X’ in the top-right of the window. The CANCEL button will be greyed out - it is not necessary when the window is used in this way.

If you are using the field chooser to select a layout for a selection template, click the OK button when you are satisfied with the display for the template. If you are not satisfied, click the cancel button, or the ‘X’ in the top-right of the window. The template will revert to the layout it had before you entered.

=== Select Data Window ===
This screen is used to select the data that you require to see on the main window. There are two tabs on this window, a normal tab and an advanced tab.

Topics:

Select Data Window, Normal Tab

Select Data Window, Advanced Tab

==== Select Data Window, Normal Tab ====
This is the area where standard selection criteria can be entered, to retrieve movement information from the database. This is the screen that you will be brought into first.

[[Image:Maint19.png|600px]]

Each of the criteria can be ranged or entered singly, based on the type of data that is held in each field. These can be of several types:

* Character type
* Numeric type
* Selection boxes
* Numeric type (Special)
* Date

Validation exists for each type, so that if entry is incorrect, you will be informed of the correct way.

Standard selection criteria (and their selection types) are:

{| class="prettytable"
| Warehouse
| Selection box, Character type

|-
| Owner
| Character type

|-
| Stock
| Character type

|-
| Pallet
| Numeric type

|-
| Customer Pallet
| Character type

|-
| Priority
| Selection box, Character type

|-
| Source Location
| Character type

|-
| Destination Location
| Character type

|-
| Truck Type
| Selection Box, Character type

|-
| Date From
| Date

|-
| Date To
| Date

|}
For Movements, the following extra criteria are displayed:

{| class="prettytable"
| Audit Number
| Numeric type (Special)

|-
| Line number
| Numeric type (Special)

|-
| Movement Type
| Radio buttons, Character type

|}
For Picks, the following extra criteria are displayed:

{| class="prettytable"
| Route Code
| Character Type

|-
| Load Number
| Numeric Type

|-
| Order Number
| Character Type (Special)

|-
| Page Number
| Numeric Type

|-
| Sequence Number
| Numeric Type

|-
| Pick Type
| Radio Buttons, Character type

|}
When selection criteria are entered, clicking OK will select all information on movements in the database that conform to this.

Further information:

Selection Types

==== Select Data Window, Advanced Tab ====
This is the area where advanced selection criteria can be entered, to retrieve movement information from the database.

Each item on the grid is a line of selection criteria.

When you switch to the advanced tab, any criteria you have entered on the normal tab will be entered automatically on this screen. This is so you can use the previous screen to enter the initial criteria easily, then fine-tune on the more complicated screen.

To enter new lines, you can double click the left mouse button on the indicated line, and you will be taken to a selection box, showing all the elements you can use to select with. You will then be allowed to enter any values with which to select. These values follow the standard selection type rules you would normally use.

You can also right-click on any of the lines. This will allow you to insert a new line in this way. From the menu that pops up here, you can also edit the marked criteria, or delete it.

Rather than entering selection criteria from scratch every time, it is possible to retrieve selection templates previously saved, and use them. To do this, click the ‘Save’ button. These may then be loaded using the ‘Load’ button.

Standard wildcard operation is in effect for the elements whose type permit it (character).

Ranges and lists are also permitted.

When selection criteria are entered, clicking OK will select all information on movements in the database that conform to this.

Further information:

Selection Templates

==== Selection Templates ====
This screen is available from the 'Advanced' tab of the Select Movements window. It allows you to create, retrieve, modify, save or delete templates for movement retrieval.

Selection Templates allow you to save standard retrieval criteria for specific functions for later use, saving re-typing time.

To create a new template, simply add the selection criteria to the grid, in the same way as the advanced tab. When this has been entered, click the 'Save' button. You will then be prompted to save the template.

To retrieve an existing template, click the 'Load' button. You will then be prompted to find your template. When you have selected your template, click 'OK'. The template will then be displayed on the screen, for editing or use.

If a retrieved template has been edited, you should save your template, either back to its original name or as a new template (using the 'Save' button).

To delete a template, use the Load Template window. You will not be asked to confirm your selection.

Fields can be left blank in the advanced criteria, and can be saved as such in the template file. You will not, however be able to use the blank templates until valid data has been entered for them.

==== Selection Types ====
Selection types encompass the entry methods of the different types of fields, and what entries may be allowed in this type.

Further information:

Selection Types, Character Type

Selection Types, Numeric Type

Selection Types, Selection Box/Radio Buttons

Selection Types, Numeric Type (Special)

==== Selection Types, Character Type ====
When entering single selections or ranges, field must be surrounded by '"' (Double Quote).

Characters entered as range delimited by '-' (Hyphen).

Characters entered singly delimited by ',' (Comma).

Wildcards may be used in this type. So, an asterisk (*) may be used to signify many or no characters, and a question mark (?) may be used to signify a single character.

Note: If using wildcards, you may be required to end the string with an asterisk. This is to account for possible trailing spaces. The exception to this is the Special derivative of Character types. In this instance, the asterisk is always assumed.

Examples:

Selecting a single owner ABC:

Enter “ABC” in the field.

Selecting 2 owners, ABC and XYZ:

Enter “ABC”,”XYZ” in the field.

Selecting a range of owners from AAA to CCC:

Enter “AAA”-“CCC” in the field.

Selecting multiples of the above:

Entering

“AAA”-“CCC”,“XYZ”,“YYY”-“ZZZ”

will select any owners in the range AAA to CCC, any between YYY and ZZZ and the owner XYZ.

==== Selection Types, Numeric Type ====
Numbers entered as range delimited by '-' (Hyphen).

Numbers entered singly delimited by ',' (Comma).

Examples:

Selecting a single pallet 00008132

Enter 8132 in the field.

Selecting 2 pallets, 00008132 and 00020001:

Enter 8132,20001 in the field.

Selecting a range of pallets from 00000200 to 00005000:

Enter 200-5000 in the field.

Selecting multiples of the above:

Entering

200-5000,8132,10000-10500

will select any pallets in the range 00000200 to 00005000, any between 00010000 and 00010500 and the pallet 00008132.

==== Selection Types, Numeric Type (Special) ====
In cases like this, special validation may limit entry of ranges.

Audit Number/ Line number.

In this case, a range of audit numbers may be entered, or a range of audit numbers with a single line number, or a single audit number with a range of line numbers.

Examples:

Selecting a single pallet 00008132

Enter 8132 in the field.

Selecting 2 pallets, 00008132 and 00020001:

Enter 8132,20001 in the field.

Selecting a range of pallets from 00000200 to 00005000:

Enter 200-5000 in the field.

Selecting multiples of the above:

Entering

200-5000,8132,10000-10500

will select any pallets in the range 00000200 to 00005000, any between 00010000 and 00010500 and the pallet 00008132.

==== Selection Types, Selection Box/Radio Buttons ====
Data in fields like this will allow standard entry based on the selection types above, but will also allow you to select single values from a pop-up list.

Radio buttons will allow you to select from a fixed list of values. Only one of these may be selected at one time.

For advanced criteria, these items act similarly to character type selection, and will appear as such in the list of criteria.

== RDT Comms ==
Menu Items:

Current Exceptions

Employee Activity

Messages

=== Employee Activity ===
The Employees Analysis window shows a constantly updated list of all the RDTs available on the WCS system, showing their status. The window you are shown initially shows you:

* The RDT ID
* The employee code
* A brief description of their activity.

The screen will display RDT users with activities older than 10 minutes at the top of the list.

The RDT ID is the WCS’s identifier for the RDT. This is included for reporting and system purposes only.

The employee code is from the standing data table on the WCS server. It is updated continually from the WMS table. The RDT user enters this when they log on to their RDT.

The activity description shows the current task in which the RDT is engaged. The description can be:

* Receipt - receiving pallets into the warehouse from a pre-advised Goods Receipt.
* Pick - picking pallets for advised sales orders.
* Replenishment - replenishing pick faces from bulk locations.
* Putaway - Taking pallets from receipt bays to their designated place in the warehouse.
* Movement - Moving a pallet from one area to another.
* Stock Take - involved in an advised stock take cycle count.
* Marshalling - marshalling a sales order load.
* Loading - Loading a sales order.
* Disconnected - the RDT is not connected to the WCS server.
* Idle - not involved in any of the above activities.
* Error - a system error.

The status ‘Idle’ simply shows that the RDT is not linked to an activity that is part of the current functionality. The RDT may well be performing different activities (ad hoc moves, pallet enquiry, etc).

The status ‘Error’ shows that the RDT may not be communicating correctly with the WCS server, but still has a job outstanding against it. The system is designed to self-correct these errors in most instances, but manual intervention may be required. These error lines will be displayed in red, indicating that there may be a problem. To force the system to clear these problem users, right-click on the affected user and choose Clear Locks from the pop-up menu. The system will then clear any tasks the user may have locked, releasing them to the general pool of tasks once more.

To find more information about the current activity of any particular RDT, double-click the left mouse button on the appropriate line. This will take you to the Employee Analysis - Detail window. Alternatively, right-click on the item, and choose Display Details from the pop-up menu.

The screen is kept updated at all times every few seconds. This means that the most up-to-date information about your RDT users is at your fingertips at all times. The window can be re-sized, as can the width of the grid rows, to keep all information on the screen at all times.

Further information:

Detail Window

==== Detail Window ====
This window gives you more detail on the selected line. The window shows you:

* The Employee code and their registered name.
* A short description of the activity.
* A detailed description of the activity.

=== Current Exceptions ===
The Exceptions window shows any tasks completed, but with exceptions. Exceptions include such things as:

* Repositioning a movement or putaway
* Cancelling a movement, replenishment or putaway
* Changing the quantity on a pick
* Cancelling a pick, or picking to zero
* Exchanging pallets on pick, movements or replenishments
* Any Ad-hoc movement
* Setting a task to Error status
* Deleting a task.

If any of these events take place, a message is shown on the exceptions screen immediately, showing the employee, the RDT, a brief description of the error and a date and time. The window shows only exceptions within a specified time period. Double clicking on the line will give you greater detail about the task.

Further information:

Detail Window

=== Messages ===
This screen allows you to send messages to RDT users who are logged on. The list of logged-on RDT users is kept updated at all times, making sure that the users you are sending a message to are always correct. If a user connects or disconnects from the Wireless network, you will be informed on this screen.

Enter your message in the text box provided. You must enter a message.

Pick the users to whom you wish to send a message. The list shows the entire network, including registered companies, warehouses and users. You can pick users individually, or send messages to an entire warehouse, company or the whole network. Either click on your chosen recipient and click the ‘add’ (->) button, or simply drag the intended recipient to the recipients list. Double clicking on a user will give you some information about their current activity.

Once all the intended recipients have been chosen, simply click the ‘send’ button. You will be informed of the progress of the message, and its completion. Messages will appear on RDT terminals when the user next exits a function.

To get a message to a user quicker, set the urgent flag on this screen. The RDT user will then pick up the message the next time they press the ‘Enter’ key.

== System Tools Menu ==
Menu Items:

Re-logon

Change Warehouse

System Settings

Clear out Error log

Clear out Incoming/Outgoing log

Clear out WCS Database

Clear Out Deleted Items

Incoming Log

Outgoing Log

Error Log

Compact Database

Database Utilities

=== Change Warehouse ===
This option allows you to set and change the company code and warehouse id, for the enquiry and movement priority screens.

Note: You can blank the company and warehouse here - this will allow you to view the data for all companies and warehouses on the current database.

=== Clear Out Deleted Items ===
This option will clear out any items in the database marked for deletion, but not yet deleted. Tasks such as these would be created if the database is set not to delete tasks, or if Maintenance users have deleted tasks using the Pallet Movement Maintenance screen.

Related Topics:

WCS Settings

=== Clear out Error log ===
This option will clear down the error log, obeying the user-entered clear-down settings.

=== Clear out Incoming/Outgoing log ===
This option will clear down the incoming and outgoing logs, obeying the user-entered clear-down settings.

=== Clear out WCS Database ===
This option will clear down the entire WCS database, leaving only standing data untouched, obeying the user-entered clear-down settings.

=== Incoming Log ===
This option is used to view the log of all incoming data to the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Outgoing Log ===
This option is used to view the log of all outgoing data from the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Error Log ===
This option is used to view the error log for operations on the WCS server.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Compact Database ===
This option compresses the WCS database. It is a necessary requirement of SQL databases that this option be present. It can only be run if the database is closed. Close the database using the appropriate button, or choosing ‘Close Database’ from the ‘File’ menu.

=== System Settings ===
This option brings up a multiple panel window for maintaining system options. The tabs available are:

Rules, consisting of:

WCS Settings

Admin Defaults

Clear out Settings

Message Types

Maintenance Settings

See Also:

Rules Maintenance

==== WCS Settings ====
This allows you to modify the communication settings. The content of this form changes, depending on which WMS system you are linking to.

If the system is connecting using socket connections, the following details will be shown:

* WMS IP Address - This is the IP address of the WMS machine. It is in the standard telnet layout (4 numbers, separated by full stops.
* WMS -> WCS Local Port - This is the port that the WCS listens to for communications from the WMS.
* WCS -> WMS Remote Port - This is the port that the WMS listens to for communications from the WCS.

If the system being linked to is using Oracle Advanced Queues, the following options can be changed:

* Oracle Database Name
* User
* Password

Settings common to both connection systems that may be modified are:

* RDT -> WCS Local Port - This is the port that the WCS listens to for communications from RDTs.
* RDT Waiting Time - This is the amount of time that the RDT will wait before re-trying communications.
* WMS -> WCS Re-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.
* Default Company Code - This is the default company code that the RDT will log on to.
* 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.
* 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.
* 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.
* 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
** Exceptions

N.B. 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.

==== Clear out Settings ====
This option is used to enter the settings to control the clear-down options above.

You are prompted to enter the log directory, where details of the clear down’s success will be written.

For each clearable dataset, you can specify whether the clear down program will process this type, and the number of day’s data you wish to keep.

The datasets are:

* Database - Any tasks not actioned within the period specified will be deleted.
* Log Archive - The logs of previous clear down runs.
* Exceptions - Exception events raised from RDT actions.
* Activities - Activity journals of each RDT.
* Deleted Records - Any records marked as deleted (See WCS Settings tab)
* Incoming Log - The next three are cleared for the same period. They are the logs of all transmissions in the WCS.
* Outgoing Log
* Error log

==== Admin Defaults ====
If a user logs on to this program (WCS Maintenance) without having a group set for them, this screen maintains the options available for the user to access.

A list of available modules is shown each with a tick or cross against the module. A tick designates that the module is available, a cross, unavailable. Either double clicking on the item or right clicking, then selecting the appropriate availability can change the options.

Related Topics:

Users Maintenance

Groups Maintenance

Owners Maintenance

Warehouse Maintenance

==== Maintenance Settings ====
This allows you to maintain locations and lists for files used specifically by this program. The options are:

* Default Criteria Templates Folder - Criteria files for use in the Reprioritisation screens.
* Default Report Files Folder - Compiled reports.
* Default Reports Folder - Text files saved from reports will be saved here.

Each of these options includes a browse button, to allow you to pick the area Explorer-style. Each also has a default area.

A recent file list is displayed, showing all the WCS databases accessed by the program. The initial screen uses this when logging on the program. This can be switched off by un-checking the ‘Show File List At Startup’ box. To clear the list, press the ‘Clear List’ button.

Related Topics:

Selection Templates

Run Report

View Report

==== Message Types ====
This tab allows you to maintain the queue settings for Oracle systems.

* Incoming Queue
* Agent

Additionally, the queues available in the WMS should be set here, using the grid provided.

== Reports Menu ==
Menu Items:

Run Report

View Report

=== Run Report ===
This option shows you a screen of all registered reports in the WCS system. Double clicking on a report name will run the selection criteria screen. This allows you to enter the required criteria to select data for the report.

If you have a default company and warehouse, and the report requires these for selection, they will already be set to your defaults, otherwise they will be set to ‘*’ (asterisk), the wildcard character.

If you want to select all the data for that criterion, simply enter the wildcard character at the prompt. All fields can be set to the wildcard character.

Dates can be defaulted using the wildcard character, or set in a different way. If you enter ‘+’ (plus) and then a number, the date entered will be the number of days specified added to today’s date e.g. +15 will ad 15 days to today’s date. You can also enter ‘-‘ (minus) to take days away.

Once all criteria have been entered, the report will be run using the default report destination parameters.

Right clicking on a report will allow you to change the selection criteria and the destination parameters of the report, if the report writing option is available in your version of the WCS. Right clicking on an empty area of the window will allow you to create a new WCS report, if the report writing option is available in your version of the WCS.

=== View Report ===
View report allows you to see any reports saved as files. The WCS will edit the report in the Windows editor associated to the report type.

== SD Maintenance Menu ==
Menu Items:

Users Maintenance

Groups Maintenance

Warehouse Maintenance

Owners Maintenance

Aisles Maintenance

P&D Maintenance

RDT ID Maintenance

Printers Maintenance

Location Truck Checker

Activities Enquiry

Exceptions Enquiry

Truck Enquiry

Reason Code Enquiry

Pallet Type Enquiry

Update Truck Moves Seq

=== Users Maintenance ===
This is the Users Maintenance screen. This allows you to maintain system settings per user.

Users are partially maintained by the WMS, sending data records when an employee is added or deleted. The data sent by the WMS includes the company and warehouse, the employee ID, the description and the shift number. These can all be changed on this screen if desired.

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

This screen allows you to create a password for the user, if required, and create a link to a set of system parameters, via a group ID.

The screen automatically displays all the employees for your default company and warehouse. Changing your company and warehouse will close this screen. When it is next opened, it will display details on your new default company and warehouse. The Refresh button will also check for the new company code and warehouse id.

A lookup is provided for groups, so that you can pick your required group from the list. Once selected, a description is displayed for reference.

If you want to see the set-up of the group you have chosen, press the Edit Group button. You will be taken to the Groups Maintenance screen. You will only be shown the group you have chosen. You can make changes here.

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 user, the data will be displayed.

To navigate to other users 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 user, 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.

‘Works Only in Aisle’: These parameters affect 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.

The Supervisor check box allows the user some additional functionality within the maintenance functions - see Pallet Movement Maintenance for details. It also allows the user to clear locked users in some RDT screens.

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.

Related Topics

Groups Maintenance

Change Warehouse

Lookup Screens

ToolBars

=== Groups Maintenance ===
This is the Groups Maintenance screen. This allows you to maintain system settings for use on the Users Maintenance screen.

Users are partially maintained by the WMS, sending data records when an employee is added or deleted. The data sent by the WMS includes the company and warehouse, the employee ID, the description and the shift number. 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.

The explorer shows all the rules that apply at this level. To change a value, simply find the rule you wish to change and change the value.

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 group, 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 group, the data will be displayed.

To navigate to other groups 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 group, 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. You will only be allowed to delete groups records that are not currently in use.

Related Topics

Lookup Screens

ToolBars

Rules Maintenance

=== Warehouse Maintenance ===
This screen allows you to modify the system and default user settings of the Warehouse.

The screen has several tabs, allowing you to modify settings affecting different broad areas of the system:

The following is a description of the contents of the various settings that can be changed, loosely grouped by area, with some additional elements in greater detail.

'''General'''

Parameters that affect the way the system runs for the warehouse.

The ‘Action Password’ is prompted for whenever any modules are password-protected on the RDT.

The Aisle, Bay and Level lengths are used by the WCS to extract the data correctly from the location codes, so that the system can decide how to prioritise the tasks in the warehouse. These must replicate the values on the WMS, or the system will become unreliable when sending users to the next task.

‘Task Identifier’ controls how the RDT identifies individual pallets in the warehouse. The values are:

By Stock Code - the RDT modules will prompt for Location Code, Owner and Stock code.

By Customer’s Pallet Id - The RDT modules will prompt for Owner and Customer’s Pallet Id.

By System Pallet Id - The RDT modules will prompt for the WMS System Pallet Id.

The ‘Check Digits’ flag controls how the user identified that they are at a particular location. The RDT will either prompt for the user to scan or enter Check Digits for each location (enabled), scan or enter the location code (disabled) or either scan the location code or enter the check digits (Combo Check).

The ‘Move Efficient’ flag controls how tasks are assigned to each user in the warehouse. This is either by Priority/Location sequence, or simple by location sequence.

The ‘Block Stack’ flag controls whether pallets may be exchanged for others in the same location in the warehouse.

The ‘Exchange Replen’ flag controls whether, if the warehouse is set as Block Stack, whether replenishment moves can also be exchanged.

The ‘Allow Task Exchange’ flag controls whether the WCS looks for outstanding tasks in the WCS database before requesting the WMS to exchange a pallet.

The ‘Seamless Exchange’ flag controls whether the user must request to exchange a pallet with the Error key, or whether the exchange occurs seamlessly.

The ‘Mixed Stock’ flag controls whether the WCS allows pallets of mixed stock in the warehouse.

‘Customer Pallet No’ controls whether the RDT system will prompt for Customer Pallet Ids for pallets held in the warehouse.

The ‘WCS Generate Replenishment’ flag controls whether the WCS attempts to generate select replenishments via an Ad Hoc Move, or whether the WMS will reply with a move instead. Note: This should be left as enabled.

The ‘RDT Pop-up description’ flag controls whether the RDT automatically pops up a description of the Stock upon receipt and pick.

‘Measure Quantity’ and ‘Weights’ control whether the system prompts for Measure Quantities or Weights for pallets in the warehouse.

The ‘Multi-UOM processing’ flag control whether the RDT prompts for cases and units.

The flags ‘Pallet Enquiry Print Labels’ and ‘WCS Pallet Enquiry Label Format’ rules control whether the RDT pallet enquiry function is allowed to print labels, and what label format to use.

'''RDT Modules'''

Default modules allowed to RDT users, if the users are not assigned to a group. Please note: Some of these modules are bespoke and require certain WMS system set-up to be enabled. Please check your documentation as to which modules should be enabled.

'''Receipt'''

Parameters that affect the running of a Receipt module in the warehouse.

The ‘Receipt Type’ flag governs how the RDT Receipt module works on the RDT. ‘Check Receipt’ is used when the receipts are advised to a pallet detail level, and ‘Blind Receipt’ is when the receipts are advised to a stock detail level.

The ‘Selection Type’ flag governs how the RDT prompts for the Receipt you are receiving stock against. You can either enter the WMS reference (By GRN number) or the supplier’s reference (By Advice Note).

The ‘RDT Damages’ flag allows RDT Receipt users to specify stock as damaged.

The ‘Enter WMS Rotation’ flag allows the user to enter WMS Rotation during Goods Receipt.

The ‘Default Pallet Type’ flag controls whether the RDT prompts for a default pallet type to assign to all the pallets being received on a GRN in one session.

The ‘Enter Receipt Type’ flag controls whether the RDT user must enter a valid Receipt Type for the GRN.

The ‘Echo Putaway Location’ flag controls whether the RDT receipt process displays the location to which the pallet will be located, after the pallet is received.

The ‘Print Labels’ flag controls where/if pallet labels are printed during the receipt process. If the WCS is printing receipt labels, the flag ‘WCS Receipt Label Format’ defines the format being used.

The ‘Additional Pallets’ flag governs whether the RDT Receipt module allows the user to enter pallets that have not been advised by the WMS. This only affects Receipts that have been advised to a pallet detail level (Check Receipts).

The ‘Single Scan Entry’ flag governs whether the RDT Receipt process prompts for a single barcode scan when adding additional pallets. Please Note: As the single barcode can be in many formats for clients, this feature should only be enabled if the WCS has been modified to work with your Single Barcode format.

Next comes a number of validation checks that can be performed during RDT Goods Receipt. Those flags are:

* Receipt Pallet Count Check - The action the RDT is to take when the number of pallets received for a stock code is exceeded.
* Receipt Total Qty Stock Check - The action the RDT is to take when the total quantity of a stock code received is exceeded.
* Receipt Standard Qty Check (Stock) - The action the RDT is to take when a stock code is received with a non-standard pallet quantity.
* Receipt Pallet Qty Check (Pallet) - The action the RDT is to take when a pallet is received with a quantity that is not that preadvised. This supersedes the previous check.
* Receipt Non-Advised Stock - The action the RDT is to take when the user attempts to receive a stock code that was not preadvised.

The flags can have several values assigned to them, with different effects:

* No Check - No action taken.
* Informational Message - A message is displayed on the RDT, but the user is allowed to continue.
* Error - A message is displayed on the RDT and the user is not allowed to continue.
* Authorisation Required - A message is displayed on the RDT. The user is then required to obtain authorisation from a supervisor user to continue.

The ‘Enter Eurodate’ flag controls whether the user can enter a Eurodate instead of a manufacture date during the Receipt process. The ‘Enter Dates’ flag must also be enabled for this flag to work. Please Note: Only some Eurodate formats are supported. Ensure yours are before enabling this flag.

The ‘Enter Layers’ flag controls whether the RDT Receipt process prompts for the user to enter number of layers and loose cases on a pallet, rather than just the number of cases. Please Note: The WMS must be set up to allow the entry of layers, and to send the data to the WCS when the receipt is preadvised. If not, this flag should be disabled.

'''Putaway/Moves'''

The ‘Multi-pallet Putaway’ flag governs whether the RDT putaway process allows the user to scan more than one pallet to locate at a time.

The ‘Enable Extended Reposition Validation’ is an extended check added to putaways when the pallets are being repositioned.

The ‘Request Putaway Details at Scan’ flag controls whether the RDT putaway process requests a location for the pallet at the time of scanning by the putaway driver, rather than when the pallet is received. Please Note: The WMS’s putaway algorithm must support this type of processing for this flag to be enabled.

The ‘Reposition’ and ‘Cancellation’ flags control whether the RDT is allowed to reposition or cancel Move tasks in the warehouse. These functions can be password-protected.

'''Pick/Post Picking Activities'''

Parameters that affect the running of a Pick module in the warehouse.

The ‘Pick By’ flag controls what the RDT prompts for as confirmation that the correct item has been found for picking.

The ‘Continuous Part Picking’ flag controls whether the user is allowed to continue picking cases of other stock codes on to the same despatch pallet. If enabled, the user is prompted whether the pallet should be taken to the marshalling location, or to continue to the next case pick.

The ‘Pick Into Containers’ flag controls whether RDT Part Picking prompts for Picking Container IDs when part-picking.

The ‘Lost Label’ flag controls whether the user is allowed to confirm a picked pallet by visually checking the details of the pallet (stock code, batch, etc), rather than simply scanning the palled ID or stock code. This is optional.

‘Pick Location Error’ allows the user to cancel a Part Pick when they reach the pick location, before they are told to pick the pallet. This is to allow for damaged pick faces where stock is unavailable. This functionality can be password-protected.

The ‘Residual Stock Balance Enquiry’ flag controls whether the WCS checks the available quantity on the WMS pallet record at the time of picking, to ensure that the most up-to-date information is available to the picker at all times. This option can be password-protected.

If the ‘Use WMS Rotation’ 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.

The ‘Picker Replens’ flag controls whether the RDT user is allowed to pick up the replenishment move to the pick face for the pick they are currently completing. This functionality is not compatible with Pick Dependencies.

The ‘Pick Dependencies’ flag controls whether Part Picks are available to the pickers if a corresponding replenishment move is on the WCS. If enabled, the pick is not available.

The ‘Replen Dependency’ flag controls whether the WCS allows only one move into a specific location to be available to RDT users at a time.

The ‘Pick In Sequence’ rule controls the sequence orders are released for picking. This is based on the Drop sequence, interfaced from the WMS.

The ‘Pick Page Allocation’ flag controls how the WCS allocates Part Pick tasks to the users. ‘By Aisle’ means that the users are given tasks for an aisle for the current order or load.

‘Concurrent Picks’ controls whether the RDT Part Picking module allows the users to pick several orders or loads at the same time. This functionality has been enabled for use when Loads are being picked rather than Orders.

The ‘Lock Pick Header’ flag controls whether the RDT Full pallet picking option locks all picks for his area to him, or whether it would allow many users to access these picks.

The ‘Consolidation Group’ flag controls how the stock is consolidated during part picking.

The ‘Force Sky Picking’ rule controls whether part pick tasks from bulk area treated as sky picks.

The ‘Print Despatch Labels’ flag controls whether the WCS prints labels for the stock picked in the Part Picking module. The format used for the labels is defined in the ‘WCS Despatch Label Format’ field following. Clicking on the button shows an ‘Open File’ dialogue, allowing you to pick the format required. The format will have been created by OBS specifically for your use. The time when these labels are printed is controlled by the ‘Pick Label Prompt’ rule.

The ‘User Select Pick Location’ rule controls whether the user is allowed to specify the location from which to start picking.

The ‘Deconsolidation Method’ flag controls whether Deconsolidation tasks are processed by the WCS. The rule ‘Ad Hoc Deconsolidation’ controls whether deconsolidation tasks are sequenced manually or automatically by the system.

The ‘Loading Method’ flag controls whether the warehouse is loading pallets after picking, and the method by which loading is done.

'''Dual Cycling'''

Parameters that affect the running of Dual Cycling in the warehouse, and whether it is allowed.

‘Enable Dual Cycling’ enables the use of Dual Cycling in the warehouse. If the flag is enabled, other modules are made available to RDT users that interleave tasks in the most efficient way.

The ‘NADC Crossover Method’ flag controls how the RDT crosses over to another narrow aisle when in Narrow Aisle Dual Cycling (NADC). The values are:

* Manual - The RDT user chooses when to change aisle.
* Threshold - the RDT crosses over to complete moves higher than the threshold priority (‘NADC Threshold Priority’)
* Weighting - Future development - should not be enabled.

The ‘Send Aisle Status’ flag governs whether the WCS informs the WMS when Aisles are currently occupied with Trucks. For some systems, this can affect which locations are suggested for putaway. This message is only sent if the aisles are designated as Narrow Aisles, a parameter entered on Aisles Maintenance.

The ‘NADC Aisle Lock’ rule controls the point at which an aisle is locked to prevent other RDTs using the aisle

The ‘RDT DC Aisle Selection’ flag controls whether an RDT user is allowed to select the aisle range in which to work when using Narrow Aisle Dual Cycling. If the flag is enabled, the user is prompted for an aisle range in which to work. This range will default to the values entered against the user’s Employee Id on the Users Maintenance screen. If the flag is disabled, the user will not be given the opportunity to change their allocated range. In this instance, a range must be entered for the user.

The ‘NADC Skip Putaway’ flag controls whether an RDT NADC user is allowed to skip a putaway move and go straight back to picking from the aisle again.

Other flags on this screen are either for system use only, or are for future development. These should not be changed unless specifically instructed to do so by the OBS team.

'''Default Locations'''

Some default locations used by the system in some modules.

You can modify values on each tab by clicking on the relevant tab and changing the values in the required fields.

To choose the warehouse you want to look at or change, use the scrollbar on the bottom of the form to navigate to the record you want, or click on the lookup icon on the toolbar. This will display a screen of all the warehouses set up in the system.

You can get the data from the database again by clicking on the refresh button on the toolbar.

When you have completed changing the values, save the data by clicking on the Save button on the toolbar. It is not necessary to save changes in between moving from tab to tab.

'''Bespoke'''

Bespoke rules have been created for sites to control specific functionality for those sites only and are unlikely to be used anywhere else.

‘Bespoke Site Rule’ is a broad rule used to control the various site-specific rules created in the past under one value. The value of this rule is normally the company or site running the system.

The ‘Bespoke Kraft Batch’ rule controls extraction of batch data for Kraft.

The ‘Pick by Carton’ functionality replaces certain parts of the normal part picking functionality, by requiring the user to scan a stock code on each individual carton, as they are placed on the despatch pallet. This functionality requires many parameters to be set up for the warehouse, and must be enabled only by the WCS support team.

The ‘Encoded Sell-by dates’ flag controls whether sell-by dates are entered encoded into the system.

The ‘Allow Overpicking’ rule allows RF users to pick more than the requested amount.

The ‘Batch Delivery’ flag enables some processing to link to a bespoke delivery system.

See also:

Lookup Screens

ToolBars

Aisles Maintenance

Users Maintenance

Rules Maintenance

Barcode Maintenance

=== Owners Maintenance ===
This screen allows you to see the owners set up on the system, flags specific to the Owner, plus any rules set up for the Owner.

This maintenance form works very similarly to the Warehouses maintenance. All warehouse rules are replicated at an Owner level. Therefore, please see the warehouses maintenance section to see a description of the rules maintained. Any specific Owner rules and screen-specific functionality is listed in this section.

To set up rules for an Owner, the Owner must be set to Restrictive. This means that only certain members of the workforce can work for this Owner, as they will be allowed to operate in a different way to the rest of the warehouse.

Once the Owner is set to Restrictive, rules will be generated and you will be allowed to modify them.

An owner that is not restrictive inherits the rules of the warehouse. Therefore, any RDT users working for owners that are non-restrictive will get their settings from the Warehouse they logged in as, not the Owner. Additionally, they will also be given work to complete for other non-restrictive Owners.

See also:

Warehouse Maintenance

Lookup Screens

ToolBars

Rules Maintenance

Barcode Maintenance

=== Barcode Maintenance ===
This screen allows the users to define what barcodes will be extracted from UCC/EAN-128 barcodes at receipt of pallets into the system.

Click on the items required and save using the button provided.

See also:

Warehouse Maintenance

Owners Maintenance

=== Aisles Maintenance ===
This screen allows you to modify or add aisles for the warehouse.

To add new records, press the new button on the toolbar. Once you have entered your new aisle, 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 aisle, the data will be displayed.

To navigate to other aisles 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 an aisle, you may wish to change some parts of it. Simply click on your chosen field and edit it. Some fields have lookups enabled on them, denoted by the ‘!’ button to the right. Just click on this item to see a list of compatible data to enter here.

If aisle sequences or certain parameters are changed, the program will re-calculate the order of tasks in the warehouse for you.

Once you have made all your changes, press the save or OK button to save your data.

Related Topics:

Update Truck Moves Seq

=== P&D Maintenance ===
This screen allows you to modify or add P&Ds for the warehouse.

To add new records, press the new button on the toolbar. Once you have entered your new P&D 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 P&D, the data will be displayed.

To navigate to other P&D’s 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 P&D, 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 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.

=== RDT ID Maintenance ===
This screen allows you to modify RDT Ids in the system.

This is an optional setup 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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

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 aisle, the data will be displayed.

To navigate to other records 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 record, 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 button or OK button to save your data.

To delete a record, press the delete button on the toolbar, then confirm through the popup dialogue. You will only be allowed to delete RDT records that are not currently in use.

=== Printers Maintenance ===
This is the Printers maintenance screen. This allows you to change the name associated to a network printer.

Printers can be either networked windows printers, or direct TVP/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.

You can test a connection to a TCP/IP printer using the test connections and test file buttons. You may also identify block markers and characters for the file.

Related Topics

Lookup Screens

ToolBars

=== Location Truck Checker ===
This screen allows you to check which trucks are available to move between specified location types.

Click on a location type on the two boxes. Once you have chosen your location types to check, click the Check button. This will show you the compatible trucks between the two location types.

=== Activities Enquiry ===
This screen allows you to enquire on the RDT Activities file, showing all tasks completed by RDT users.

The form has two views, a detail/select view, and a grid view.

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Exceptions Enquiry ===
This screen allows you to enquire on the Exceptions file, showing all tasks completed with exceptions by RDT users.

The form has two views, a detail/select view, and a grid view.

Note: Data cannot be modified on the form.

The screen will start by prompting you for selection criteria to retrieve the data by.

If the item being entered is a character-based field (for example, stock code), the program will match all data that is similar. So, entering ‘A01’ in this field will match all stock codes that have the string ‘A01’ in them, like ‘A0101’, ‘AA012345’ or ‘B1763A01’.

If the item being entered is a numeric-based field (for example, quantity), the program will exactly match all data. So, entering ‘123’ in this field will match only records that have exactly 123 in quantity.

If the item being entered is a date-based field (for example, date from), the program will exactly match the date, or exactly match a date and time.

Dates must be entered in the standard database date format, in this case ‘DD/MM/YY’. The ‘slash’ separator must be entered.

Date and time entries must be entered as ‘DD/MM/YY hh:mm:ss’. The ‘space’ between the date and time must be entered, as must the ‘colon’ separator on the time portion.

Criteria may be entered from a lookup screen. This is available on fields with a ‘!’ button next to them. Simply press the lookup button to bring up a screen of all data.

Any number of criteria may be entered.

Once entered, press the ‘Find’ button to find data using the criteria entered. The screen will flip to the grid view, to show you all the data selected in a table.

In the grid view, you can change the width of each of the data columns. The screen will not remember your setting when next you use the screen. You can sort the data by clicking on the column header. You can sort the data in reverse order by shift- or control-clicking on the item in the header.

You can flip back to the detail view, by clicking on the appropriate tab.

Selection criteria can be added by pressing the ‘New Criteria’ button. This will blank the screen, and allow you to enter criteria for the selection.

To change the criteria entered, use the ‘Amend Criteria’ button. This will blank the screen, and display the current selection criteria.

If you wish to remove all criteria during entry or amendment, press the ‘Clear Criteria’ button. This will remove all previously entered criteria, and start from a blank screen.

To re-find data based on the current selection criteria, press the ‘Refresh’ button.

Related Topics

Lookup Screens

ToolBars

=== Truck Enquiry ===
This option is used to view the Truck Types standing data, sent from the WMS.

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 and whether the truck type is considered intrinsically safe.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Reason Code Enquiry ===
This option is used to view the Reason Codes standing data, sent from the WMS.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Pallet Type Enquiry ===
This option is used to view the Pallet Types standing data, sent from the WMS.

To sort the data, simply click on the title of the column you want sorted. The data will automatically sort in this order. To sort the data in reverse order, hold down the Shift key when you click on the column title.

=== Update Truck Moves Seq ===
This option is used to recalculate the sequences of the truck move tasks in the WCS, with relation to certain flags against the aisle being changed.

Related Topics:

Aisles Maintenance

=== Lookup Screens ===
All the lookup screens in the WCS have the same functionality. Generally, lookup screens are used to display quantities of data where a combo box may not show all the support data that is required. A lookup will provide this extra information.

When you enter the lookup screen, the data is displayed from top to bottom, alphabetically. If required, you can scroll the data using the scrollbar on the side. When you have chosen your line, you can return to the calling screen by:

Double clicking on the line

Pressing Return on the line

Selecting the line and pressing OK

To return to the calling screen without choosing data, simply press the cancel button.

To find specific data, you can press the first letter of the data you want. This will take you to the first occurrence of the data starting with that letter. Subsequent presses of the same key will move you on to the next occurrence.

Quickly typing the first few letters of the data you are looking for will refine the search, until you have found your data.

== Windows Menu ==
This menu is a standard windows menu. It includes the options:

* Cascade
* Tile Horizontal
* Tile Vertical
* Arrange Icons

The menu also includes a list of all opened windows, so the user can switch between them easily when necessary.

== Help ==
Shortcut: F1

This menu allows you to access the help files associated with the WCS Maintenance program and windows. It can also be accessed from the toolbar using the appropriate button. The help given is context-sensitive, so you should be directed straight to help about your current screen. If direct help is not available from this screen, you will be taken to a topic list, where you can choose from all the help available.

You can also see the version of the software you are running by clicking the About menu item.

== Miscellaneous ==
=== Refresh Screen ===
The 'Refresh' button can be used to re-find the data from the database, using your original selection criteria. This is useful if any changes have taken place on the data since you found it.

=== ToolBars ===
Toolbars can be modified using the standard Windows method of double clicking on a blank portion of the toolbar. This will bring up the toolbar modification window

Modifications can be made to several areas by adding from the left-hand window to the right-hand window.

You can change the position of the items in the toolbar.

You can add as many of the separator items as you like - there will always be more of them in the left-hand window!

=== Database Utilities ===
This program allows you to enquire and change any data on the system database. THIS OPTION IS ENABLE FOR SYSTEM MAINTENANCE ONLY, AND SHOULD NOT BE USED FOR ANY OTHER REASON. The DBUTILS program is separate and as such can be removed from the local functionality.

Usage of the program: Trained users only.

=== Rules Maintenance ===
This program uses a standard mechanism for maintaining rules in the system. This mechanism is described here.

The rules required are displayed in an explorer window, showing the rule groups on the left-hand pane, and the rules belonging to that group in the right-hand pane.

To find rules, click on the appropriate section in the left-hand pane. The rules will display on the right-hand pane. Should there be too many rules to display on one screen, the screen will provide a scroll-bar.

Rules can be broken down into several types:

Fixed Values - these will be displayed in a drop-down list, for you to select.

Text values - plain text for you to type the value in.

Numeric values - plain numeric values for you to type in.

Browse buttons - where the WCS requires a directory listing or file selection, a browse button is provided.

Database lookups - there the WCS requires a data value, a drop-down list is provided with the values allowed. There will also be a blank value on the list for you to select.

As each value is modified and you move to the next, the data will be saved.

Screen which contain Rules explorers:

Warehouse Maintenance

Groups Maintenance

Owners Maintenance

System Settings

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

Set-up Guide

2025-10-30T10:24:00Z

Anw: 291594 Truck Type Logon Validation

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


= 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 and whether the truck type is considered intrinsically safe.

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.

The RDT can also be marked as "Intrinsically Safe" for use with flammable goods. This optional setup will then prevent users from logging on with truck types that are NOT intrinsically safe for use with flammable goods.

== 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]]

Category:Glossaries

2025-07-22T11:22:30Z

Anw: Initial Creation

These pages are glossaries associated to Aptean TMS - Calidus Edition.

{{Note}}All glossaries are now held and maintained centrally within the CALIDUS Hub Assist.

Category:Templates

2025-07-22T11:21:53Z

Anw: Initial Creation

This page shows all templates used when creating pages in this Assist.

Template:WCS Glossary

2025-07-22T11:21:23Z

Anw: Interwiki

{{obs:WCS Glossary}}
<noinclude>
[[Category:Templates|{{PAGENAME}}]]
[[Category:Glossaries]]
</noinclude>

Template:WCS Glossary

2025-07-18T13:24:16Z

Anw: Interwiki

{{obs:WCS_Glossary}}

Template:WCS Glossary

2025-07-18T13:18:50Z

Anw: Interwiki

File:Diag1.PNG

2025-07-04T12:21:51Z

Anw: Anw reverted File:Diag1.PNG to an old version

Using WCS from WMS

2025-07-04T12:21:30Z

Anw: Minor correction

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=Using WCS from WMS Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= System Overview =

[[File:WCS-Overview.png|800px]]

== Operation ==
As can be seen from the diagram, Calidus 3''pl'' runs on a UNIX server, while Calidus 3''pl''-Mobile runs on a Windows Server in this implementation.

In the diagram, Calidus 3''pl'' has been split into three areas.

The non-shaded area is the manual Calidus 3''pl'' system, being the screens and methods currently used to enter and confirm tasks.

The wavy shaded area shows the portion of Calidus 3''pl'' that sends messages to the WMS interface. These are covered in great detail in following sections.

The dotted area contains Calidus 3''pl'' RDT update programs that automatically do the work of the confirmation processes in manual Calidus 3''pl''. For example, one of these processes might confirm movements; another might confirm orders as picked. They work by receiving confirmation of tasks completed from Calidus 3''pl''-Mobile. Those messages (of tasks to be completed, and confirmation of tasks completed) are sent by the interface.

Both systems have an interface; Calidus 3''pl''''s is referred to as the WMS interface, Calidus 3''pl''-Mobile's as the WCS interface. Both need transmitters (to send their messages) and receivers to get messages back. As can be seen from the diagram, Calidus 3''pl ''sends messages to Calidus 3''pl''-Mobile's receiver program, WCS Server through an Oracle Advance Queue. When messages are being sent back to Calidus 3''pl'', Calidus 3''pl''-Mobile's transmitter program, also WCS Server, sends messages to Calidus 3''pl ''by enqueuing messages on Oracle Advance Queues in the WMS database.

The third part of the interface consists of the Merge processes. In Calidus 3''pl'', these consists of many processes which we route messages to using the Queue Reader processes. These route the messages to the Merge processes (dotted area of the RDT update programs).

So, let's look at the progression of tasks through this system from start to finish. For this example, we'll use a simple housekeeping pallet movement.

When the task (move pallet 1 from A to B) is raised, the message is passed to the WMS Interface Queue. The Queue passes the information to the WCS Server. Note: Only when the message is fully processed is this removed from the queue, ensuring messages are never lost).

Once WCS's receiver has the message, merges the message to the database. This identifies the type of message (a pallet movement), and checks that everything is OK about the message''s contents. When satisfied of the contents, the task is put in the main WCS database, ready for use.

When an RDT user requests a task, and they are to be allocated movement tasks, WCS will allocate the closest movement to that user's location, or in priority order. In our example, this means they are given the movement we raised on Calidus 3''pl''. They are told to get the pallet 1 from location A and take it to location B, there scanning the check digits of the destination for confirmation.

Once they have completed the task, Calidus 3''pl''-Mobile sends a completion message to the Calidus 3''pl'' receiver queue.

The Queue Reader associated to the queue identifies the type of message, in our example, a movement completion message. The message is then routed to the correct RDT update process. Again, messages are only removed from the queue when correctly processed.

The RDT update process examines the contents of the message for validity, and then updates all the Calidus 3''pl'' data files that you would expect if it was confirmed manually in the Pallet Move Confirmation screen.

= RDT Control Processes =
== Menus ==
[[Image:Img1.png]]

The menu is normally located on the top flexible menu.

== System Parameters ==
In order to send RDT messages or tasks to Calidus 3''pl''-Mobile, the Calidus 3''pl'' system must be informed that the Interface to Calidus 3''pl''-Mobile is present. This is enabled via the 'RDT Interface' flag on system parameters.

[[Image:Img2.png]]

Click on the Default Locations tab to identify the default locations required.

[[Image:Img3.png]]

Build up location 3 (Q/A) is the default putaway location, if the putaway algorithm finds no locations. Location 6 is a Default Marshalling Location, used by pick list and allocation.

== Owner parameters ==
An RDT Interface flag also exists per Owner or Stockist. With this flag, we are able to determine whether, even if the warehouse allows RDT operations, the owner allows RDT operations.

[[Image:Img4.png]]

In all ways, this bank of screens operates in the same way as the System parameters screens, described above.

== RDT Status Maintenance Screen ==
This screen is the major control screen for RDTs in Calidus 3''pl''

[[Image:Img5.png]]

Each line controls not only the running of the update process in Calidus 3''pl'', but also the availability of the functions to standard Calidus 3''pl'' processing. So, for example, if the Pallet Receipt Update availability flag is 'Y', you have the ability to send receipt preadvice messages to WCS. If it is 'N', you can't send those messages.

The use of the availability flags in the system will be explained for each sending process described in the next section.

Use 'Start Interface' to start the RF interface programs.

Use 'Stop Interface' to stop the RF interface programs.

The light below these buttons indicates whether the interface is on or off.

'''The use of this screen should be limited to System Administrators only.'''

= SENDING DATA =
== Standing Data tables ==
See the C3PL-M Setup guide, for details of how this data is used in the Calidus 3''pl''-Mobile.

Various data tables on Calidus 3''pl'' need to be sent to Calidus 3''pl''-Mobile. These tables are:

* Employees
* Truck Types
* Pallet Types
* Location Types
* Reason Codes
* Receipt Types
* Aisles Status/Aisles
* Stock information

The maintenance screens for these tables can be found (by default) on the Warehouse maintenance menu. The exception to this is the Stock Maintenance screen, normally found on the Stock menu.

To perform an initial send of the data to Calidus 3''pl''-Mobile, enter the form and find data. Once found, click the Send button on the form, which will only be visible if the Interface flags for the owner and warehouse are enabled. The whole file will be sent.

Also, during normal use of the screens, any added or deleted data is sent to Calidus 3''pl''-Mobile, to keep the files accurate. Simply use the screen as normal, and the data will be sent, as long as the interface flags are turned on.

== Preadvices ==
Enter the preadvice as normal, either with or without pallet details.

Once all details have been entered, click the 'Send' button on the main preadvice screen. Tasks per pallet will be sent to Calidus 3''pl''-Mobile. You can only send preadvice records this way if the availability flag of the Pallet Receipt Update process is set to 'Y'.

[[Image:Img6.png]]

Sending the preadvices to Calidus 3''pl''-Mobile need only be done this way if the Goods had not been preadvised via EDI. In this process, all messages will be automatically sent to Calidus 3''pl''-Mobile on receipt of the EDI.

Once pallets have been received on Calidus 3''pl''-Mobile and sent back to Calidus 3''pl'' they will automatically be updated.

'''Note:''' In unexpected scenarios (e.g. unexpectedly received pallets) the Goods Receipt Note will NOT be automatically confirmed as received. The pallets, which have processed correctly, will have been confirmed but no action will have been taken on other pallets. You will still be able to put the correctly processed pallets away. In order to confirm the GRN fully, you must access the GR Confirmation screen and use the Confirm process there. Until this action is taken, the GRN will continue to appear on diagnostic reports. See section 5.2 for more details.

== Putaways ==
When the Goods Receipt has been processed on Calidus 3''pl''-Mobile, update messages are sent back to Calidus 3''pl''. The Pallet Receipt Update program, controlled by the RDT Start/Stop screen processes these. When the program processes the receipt messages, it will generate a putaway location for the pallet automatically. This is sent through to Calidus 3''pl''-Mobile as a putaway task.

If a location cannot be found for the pallet, the putaway location will default to the third build-up location on system parameters, the Q/A location.

If, however, you have the availability flag of the Pallet Receipt Update process set to 'N' and the flag for Movement/Putaway Update process set to 'Y', you can send putaway messages a different way.

When the flags are set up this way, preadvice messages can't be sent to WCS, but putaway messages can. When you have created the goods receipt in Calidus 3''pl'', enter locations as normal in Goods receipt confirmation.

[[Image:Img7.png]]

When the 'Confirm' option is chosen, the receipt is confirmed and then putaway messages are sent to Calidus 3''pl''-Mobile, with the locations that you specified.

Once the putaway messages have been processed, the pallets will be available in the system.

== Pallet Moves ==
Pallet movements sent to Calidus 3''pl''-Mobile are processed in almost exactly the same way as normal. Pallet movements are raised via the Pallet Movement Request screen as normal. In the Ticket Print screen, you will be prompted for two extra items:

[[Image:Img8.png]]
If you do not want to print the move ticket, enter 'No' at the appropriate prompt. You must then enter a priority for the messages. This priority will indicate how quickly the messages are processed in Calidus 3''pl''-Mobile. The values range from 2 (the highest) to 9 (the lowest).

After this entry, the request is processed as normal, but with movement messages being sent to Calidus 3''pl''-Mobile.

== Replens ==
Replenishments are processed in the same way as pallet movements.

== Picks ==
Pick tasks are sent to the RDTs at the normal pick list stage. This stage can be reached through a number of screens, the most common being the Pick Wave screen.

=== Pick Wave ===
Orders can be found and allocated to a Pick Wave, using this screen.

[[Image:Img9.png]]

Enter a default load then click 'Find Orders' to display the orders. Criteria can be entered here to narrow down the orders to be found.

Once found, assign the orders to the Load using the check box next to the order, then save.

[[Image:Img10.png]]
Click the 'Send to Alloc' button to allocate the load.

Once allocation is complete, the order can be pick listed using the 'Send To Pick' button.

[[Image:Img11.png]]

If the load is to be pre-assigned to one picker, the employee ID of this picker can be entered in the Picker field before sending to pick.

[[Image:Img12.png]]

The Marshalling location is the lane to which you wish the picked pallets to go. If one is not entered, the system will default the location to the Default Marshalling Location in the system parameters screen. The RDT priority affects how quickly the pick tasks will be allocated to a picker. As with other RDT process priorities, this can be set from 2 to 9, 2 being the highest priority.

When you have chosen the parameters, click the 'Generate Pick List' button. This will produce a paper pick list if desired, and will also transfer the pick tasks to Calidus 3pl-Mobile for completion.

=== Pick List ===
If you allocate and pick list by separate processes in the menus, you will be prompted to enter the extra parameters at the Pick List stage:

[[Image:Img13.png]]

The Marshalling location is the lane to which you wish the picked pallets to go. If one is not entered, the system will default the location to the Default Marshalling Location in the system parameters screen. The RDT priority affects how quickly the pick tasks will be allocated to a picker. As with other RDT process priorities, this can be set from 2 to 9, 2 being the highest priority.

When you have chosen the parameters, click the 'Generate Pick List' button. This will produce a paper pick list if desired, and will also transfer the pick tasks to Calidus 3pl-Mobile for completion.

== Pick Modifications ==
If you have short-picked an item or the pickers have not found some pallets, these tasks will be sent back to Calidus 3''pl'', and will reduce the amount picked. The shortfall must be appended onto the order. This is achieved by adding lines at pick confirmation, but without confirming the order.

First, find the order in the Pick confirmation by route/load/order screen:

[[Image:Img14.png]]

Select the required page of the order. You will be taken to the confirm screen.

[[Image:Img15.png]]

From here, append lines to the order as normal, but do not confirm the page. When saved, the appended pick task will be sent to Calidus 3''pl''-Mobile for processing. When completed, the task will be returned and updated automatically by Calidus 3''pl''.

Pick tasks that have been manually short-picked or confirmed will also be interfaced to Calidus 3pl-Mobile, to reduce or remove the pick tasks outstanding.

== Stock Check ==
Generate the stock check cycle as normal in the generation screen. For messages to be sent to Calidus 3''pl''-Mobile, the interface flag (either from owner or system parameters) must be set, and the stock check availability flag and owner check flags must also be set in the RDT start/stop screen.

[[Image:Img16.png]]

The cycle will either be a full stock check or a partial stock check. If neither, the stock check will be assumed to be a partial, or pre-advised, check.

Once stock details have been checked on the RDTs, the information is sent back to Calidus 3''pl'' and updated into the stock take count input screen.

[[Image:Img17.png]]

Once the data is checked for consistency, the cycle can be confirmed (using the 'Confirm' button), making it ready for updating, using the Stock Take Update screen.

[[Image:Img18.png]]

Good counts should be confirmed. If unsure about the counts, the cycle can be rejected or partially confirmed. In a partial confirmation, any records that were correct are confirmed, and any with modifications are left on the stock cycle.

= Receiving Procedures =
== Receipt Transaction Exceptions ==
[[Image:Img19.png]]
Message types allow you to choose which processes' messages you want to see on the report. A full list will be shown.

The error type allows you to choose from a range of message levels:

* Informational (type 'I') - Some processes write away messages to the report, showing successful completion of update. These are informational messages.
* Warning (type 'W') - Warnings show data that may need to be fixed, but the line has been updated anyway.
* Error (type 'E') - Errors show records that cannot be updated. The reason will be shown in the description. Data with errors must be entered and updated manually through the normal manual update screens.
* Debug messages (for support)
* All (type 'A') - All of the above.

You are prompted to choose a Date From. This will default to today's date.

[[Image:Img20.png]]

The 'Cleardown' button shows the parameters required so that the exceptions log can be cleared. This should be done on a regular basis. By default, no clear-down is done. If you choose to do the clear-down, you are prompted to enter a date. All data before this data will be deleted. Take care using this function as, once deleted, the exceptions data cannot be recovered.

== Diagnostics processes ==
In addition to the above report, several diagnostics reports exist that will aid in identifying possible problems:

* For GRNs:
* GRN's not putaway confirmed
* GR Discrepancies Report
* GRN's advised not confirmed
* For Orders:
* Order (status) report
* Unconfirmed Orders
* Unconfirmed Pick Pages Report
* For Moves:
* Unconfirmed Movements
* Outstanding Movements Report

Additionally, the Data Extraction Suite allows the user to design reports to examine all of this data.

Various enquiries exist in the system, which will also aid identification:

* All stock movements enquiries
* Customer Pallet ID Enquiry
* Pallet Enquiry
* Order Enquiry

File:WCS-Overview.png

2025-07-04T12:21:07Z

Anw:

WCS Common Activities Guide

2025-06-20T09:52:35Z

Anw: Categorisation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=WCS Common Activities Guide
|Reference=APT/WCS/TNG-COMM
|Version=1.2
|Date=22 July 2011
|Sysver=3.4
}}

= Introduction =

This document is intended to show many common activities within the WCS, with detailed instructions on how these extraneous tasks may be performed.

This document is intended for technical supervisors or IT staff.

Due to the nature of the subjects covered, this document is necessarily technical in nature.

= Remote Data Reporting =

The Calidus WCS database can be accessed for client reporting purposes using a Microsoft-standard ODBC data connection.

The suggested mechanism for accessing the data is:

# Create a link database
# Create an ODBC Data Source
# Get the data from the ODBC data source with Microsoft Excel

== Set-up Requirements ==

The Calidus WCS system must be set up for your data.

You must have access to the logging database. This document assumes that this has been created under a network drive X:

== Create a Link Database ==

In order to minimise the impact of the query on the Calidus WCS system, this should be performed on a link database. It is possible to access the database directly, but this is '''<u>not</u>''' recommended by OBSL.

Create a new Access database.

[[File:WCS-COMMON3.png]]

This database can be created locally (or your PC) if this is only being used by you, or can be created on any network machine (for example, the WCS Server) if used by many people.

[[File:WCS-COMMON-RemoteData4.png]]

In this case this has been called WCS-Reporting.mdb, created in My Documents

[[File:WCS-COMMON-RemoteData5.png]]

Choose Get External Data/Link Tables from the File menu.

[[File:WCS-COMMON-RemoteData6.png]]

Link to your Calidus WCS logging database. This is normally in X:\Log.mdb or X:\Log1.mdb.

[[File:WCS-COMMON-RemoteData7.png]]

Link the table 'RDT Activity'

[[File:WCS-COMMON-RemoteData8.png]]

Save your new database by closing Access.

== Create an ODBC Data Source ==

Choose Start/Settings/Control Panel/Administrative Tools/Data Sources (ODBC) from the Start menu.

If this option is unavailable on your PC, you must have an Administrator user do this for you.

[[File:WCS-COMMON-RemoteData9.png]]

Create a new System DSN

[[File:WCS-COMMON-RemoteData10.png]]

Choose 'Microsoft Access Driver (*.mdb)'.

If this option is unavailable on your PC, the Microsoft Data Access Components (MDAC) must be installed on your PC.

[[File:WCS-COMMON-RemoteData11.png]]

Ensure the Data Source Name is 8 characters or less.

Select your data source using the 'Select…' button.

[[File:WCS-COMMON-RemoteData12.png]]

Click 'OK' to save the new data source

[[File:WCS-COMMON-RemoteData13.png]]

== Access the Data in Microsoft Excel ==

Now that this is set up, you can access the Calidus WCS logging data from external sources. In this example, this is from Microsoft Excel, but could just as easily be from any ODBC-compliant reporting tool, such as Crystal Reports or Cognos Impromtu.

Open Excel and create a new workbook.

[[File:WCS-COMMON-RemoteData14.png]]

Choose Import External Data/New Database Query from the Data menu.

At this point, you may be prompted to install Microsoft Query for Excel. This may have to be completed by an Administrator.

[[File:WCS-COMMON-RemoteData15.png]]

Choose the WCS Reporting Data Source we set up earlier.

[[File:WCS-COMMON-RemoteData16.png]]

Choose the table to report. In this case, you will want the RDT Activity table.

[[File:WCS-COMMON-RemoteData17.png]]

Choose the data you want to filter.

[[File:WCS-COMMON-RemoteData18.png]]

Choose the Sort Order

[[File:WCS-COMMON-RemoteData19.png]]

Return the data back into Excel.

[[File:WCS-COMMON-RemoteData20.png]]

Choose the cell into which you want the data to be loaded.

[[File:WCS-COMMON-RemoteData21.png]]

Once the data is loaded in the form, you can filter and format the data in any way you want.

[[File:WCS-COMMON-RemoteData22.png]]

You can refresh the data by choosing Refresh Data from Data menu or the menu shown when right-clicking on the cells.

[[File:WCS-COMMON-RemoteData23.png]]

The sheet will retain its formatting.

You can then save this worksheet for running in the future.

== Adding Parameters ==

Parameters allow you to specify the data to be returned 'on the fly' by saying what you want it to match.

Choose Import External Data/Edit Query from the Data menu.

Keep hitting 'Next' until you get to the end of the query, then click on the 'View Data in Microsoft Query' option, before clicking Finish.

[[File:WCS-COMMON-RemoteData24.png]]

You will be taken into the Microsoft Query application.

[[File:WCS-COMMON-RemoteData25.png]]

Make sure the Auto-Query button (!) is not pressed in.

[[File:WCS-COMMON-RemoteData26.png]]

Choose the item you wish to parameterise.

[[File:WCS-COMMON-RemoteData27.png]]

Enter a prompt for the value.

[[File:WCS-COMMON-RemoteData28.png]]

Hit Enter. You will be prompted for an employee code in a popup box. Enter one.

[[File:WCS-COMMON-RemoteData29.png]]

You can now exit Microsoft Query and return the data to the Excel spreadsheet by clicking the X in the top corner.

[[File:WCS-COMMON-RemoteData30.png]]

The data is now selecting only the tasks relevant to employee IJ. Whenever you refresh the data, the Employee will be prompted:

[[File:WCS-COMMON-RemoteData31.png]]

You can add multiple parameters to a query. Each will be prompted for in turn.

{{Note}} You have full help on how Microsoft Query works, available using the Help button on the Query forms.

[[File:WCS-COMMON-RemoteData32.png]]

= Clearing Down Data =

After use for some time, data may need to be cleared down from the WCS databases.

The WCS generally has two databases:

* rdt1.mdb
* log1.mdb (optional)

As the Logging database contains details of all messages sent to and from the WCS, this is the most likely database to get very large.

You will be warned when starting WCS Maintenance whether the databases are getting close to their maximum size.

The WCS databases can only go to 2Gb in size. If they get to that size, the system will stop working as expected.

As mentioned, the most likely database to reach 2Gb is the Logging database, if the system has one. To find out where this is, check the WCS Maintenance form '''System Settings''' on the '''System Tools''' menu. Click the '''WCS Settings''' rule group, and check out the value of the last rule, '''Log Path'''. If it is set, the system uses a Logging database.

== Clearing Logging Information ==

=== Renaming the Logging Database ===

The easiest was to reset the database size is to rename the Logging database, following the procedures below:

# Ensure that all WCS Maintenance users are logged out.
# Stop the WCS Server (RDT users do not necessarily have to be logged out, but it is best practice to do so).
# Rename the logging database to a suitable name (for example, log2.mdb or log1_<date>.mdb).
# Re-start the WCS Server. This will create a new, empty logging database as it starts.

=== Clear Logging Files ===

Alternatively, run the clear-down options on WCS Maintenance:

* ''Clear Out Error Log''
* ''Clear Out Incoming and Outgoing Logs''

Both of these are available on the System Tools menu. Full details of this Cleardown process can be seen in the following section.

{{Note}} Once this is done, you need to compact and repair the logging database. Either:

* Stop and Start the WCS Server - it should compact the database automatically, if no WCS Maintenance users are logged on.

Or:

# Ensure that all WCS Maintenance user are logged out.
# Stop the WCS Server (again, RF users do not necessarily have to log out, but it is best practice to do so).
# Run Database Utilities from the '''''Start'''/WCS Utilities'' menu.
# Choose '''Compact Database''' from the ''Tools'' menu. Find the database and wait.
# When DBUtils comes back with a message that the database is compacted, re-start the WCS Server.

== Cleardown ==

The cleardown settings control how the database is cleared of old or redundant data.

=== Cleardown Settings ===

In normal circumstances, the main WCS database will never accrue redundant data as, when it is completed, it is deleted from the database. The Log files (incoming, outgoing and Error) can be cleared down to a smaller time, as they are really only needed for support.

The Activities and Exceptions files are there for your analysis of the work done and exceptions made by employees. It would normally be expected to want to keep between 1 and 3 months of data in these files

Reasonable general cleardown settings are:

[[File:WCS-COMMON-Cleardown33.png]]

=== Running Cleardown ===

The cleardown process is a manually run process, as and when you want to run it.

It leaves behind the days' amount of data in specified files according to the settings. The process can be scheduled instead, using the standard Windows scheduler.

When the process runs, it creates a new cleardown database in your Logs area (also a parameter set in this form), containing all the data that has been removed from the database. Each time cleardown is run, a new archive database is created, so I suggest that this process is run infrequently (perhaps once a month or less).

The data in from each cleardown run (in each archive database) is still accessible (for enquiry purposes) and the process for doing this can be seen later in this mail.

This process should '''<u>only</u>''' be set up and run on the Maintenance session that runs on the WCS Server machine, as the Cleardown database will be created on the machine that ran the process.

The process can be run in several ways:

[[File:WCS-COMMON-Cleardown34.png]]

* To clear down just the Error Log, choose the option Clear Out Error Log from the System Tools menu.
* To clear down just the Incoming and Outgoing logs, choose the option Clear Out Incoming and Outgoing Logs from the System Tools menu.
* To clear down just data marked for deletion in the database (i.e. data deleted by WCS Maintenance users), choose the option Clear Out Deleted Items from the System Tools menu.
* To clear down the all the WCS databases according to the Cleardown Settings, choose the option Clear Out WCS Database from the System Tools menu.

All space cleared in the database will be recovered the next time the WCS Server application is re-started.

= Archive Database Queries =

When you create a logging database copy or clear down data from the logging database, the users may need to enquire against it. The easiest way to set them up for this is to create an Archive database. This can be done by copying the existing WCS database rdt1 to a name like rdt1archive.

To access archive logging databases:

Start WCSMaintenance as normal.

Do not open the normal database (rdt1) but instead open the new database rdt1archive.

Log in as normal.

Click on '''System Tools'/'System Settings''' from the menu.

[[File:WCS-COMMON-Archive35.png]]

Click on the '''Rules''' tab and the '''WCS Settings''' group.

Click on the '''Log Path''' rule and enter the full file specification of the archive logging database you want to enquire on. Alternatively, use the Browse (...) button to the right of the '''Log Path''' rule to search for the archive logging database.

Click '''Apply''' and/or '''OK''' to close the form.

Close the database by choosing '''Close WCS Database''' from the '''File''' menu.

Open the Archive database again by choosing '''Open WCS Database''' from the '''File''' menu and choosing the archive database from the pop-up browser.

This Archive database will now show the logging data from the archive logging database chosen, allowing users to enquire and report against this information.

= Restricting WCS Maintenance User Access =

== Setting User Access ==

The first stage is to ensure all employees are sent across to Calidus 3pl-Mobile from Calidus 3pl. The procedure for this can be seen in the RDT Training Guide WMS v4, section 4.1.

This basically comprises typing SEND from the Employees Maintenance screen in WMS:

[[File:WCS-COMMON-AccessControl36.png]]

Once sent across, all users will be set by default to be RDT users. For any users that require WCS Maintenance access, the access type of that user must be modified, as below:

[[File:WCS-COMMON-AccessControl37.png]]

For users who require access to WCS Maintenance ONLY, choose type "Admin".

For users who require access to WCS Maintenance OR RDT functions, choose type "Either".

For users who require access to WCS Maintenance AND RDT functions at the same time, choose type "Both".

Click the save button when you are finished.

If a user is set to any of the options listed above, the menu options allowable for them are then limited by the group or, if they do not have one, by the system defaults (see section 5.2).

To set a Group, they must first be set up by the Groups Maintenance form (see section 5.3).

== Setting System Defaults ==

The system defaults are maintained on System Tools/System Settings.

[[File:WCS-COMMON-AccessControl38.png]]

Click the Rules tab, and then the 'Admin Defaults' group.

[[File:WCS-COMMON-AccessControl39.png]]

Each rule affects the menu items that can be seen and used within maintenance, if the user does not have a group.

{| class="wikitable" border="1"
! '''Rule'''
! '''Description'''
|-
| Change Warehouse
| If enabled, allows the user to change the default warehouse they can see.
|-
| Comms
| Allows the user full access to the RDT Comms menu. If this is enabled, the following option need not be.
|-
| Comms (Enquiry Only)
| Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.
|-
| Logs
| Allows the user access to the Logs Enquiry screens in the System Tools menu. That is: Incoming Log; Outgoing Log and; Error Log.
|-
| Report
| Allows the user access to the Reports menu
|-
| System Settings
| 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.
|-
| 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.
|-
| Standing Data (Enquiry Only)
| Allows the user access to the Enquiry screens only on the Standing Data menu. That is all the items on the menu in the second group on the menu list. The top and bottom groups will not be enabled.
|-
| 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.
|-
| Task (Enquiry Only)
| Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.
|-
| Clear-down Options
| Allows the user access to the Clear-Out options on the System Tools menu. NOTE: This should only be available for super-users.
|-
| Compact Database
| Allows the user access to the Compact Database option on the System Tools menu.
|}

== Setting Group Defaults ==

Groups are maintained by the Groups Maintenance screen, accessed from the Standing Data Maintenance menu.

[[File:WCS-COMMON-AccessControl40.png]]

Full help for maintaining and creating Groups can be found in the on-line help and the WCS Maintenance user Guide.

Click the Admin group to see the settings that affect the WCS Maintenance options available to users assigned to this group.

Each rule affects the menu items that can be seen and used within maintenance, if the user does not have a group.

{| class="wikitable" border="1"
! '''Rule'''
! '''Description'''
|-
| Change Warehouse
| If enabled, allows the user to change the default warehouse they can see.
|-
| Comms
| Allows the user full access to the RDT Comms menu. If this is enabled, the following option need not be.
|-
| Comms (Enquiry Only)
| Allows the user Enquiry-only access to the top 2 items on the RDT Comms menu.
|-
| Logs
| Allows the user access to the Logs Enquiry screens in the System Tools menu. That is: Incoming Log; Outgoing Log and; Error Log.
|-
| Report
| Allows the user access to the Reports menu
|-
| System Settings
| 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.
|-
| 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.
|-
| Standing Data (Enquiry Only)
| Allows the user access to the Enquiry screens only on the Standing Data menu. That is all the items on the menu in the second group on the menu list. The top and bottom groups will not be enabled.
|-
| 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.
|-
| Task (Enquiry Only)
| Allows the user access to all the screens on the Tasks menu, but for enquiry purposes only.
|-
| Clear-down Options
| Allows the user access to the Clear-Out options on the System Tools menu. NOTE: This should only be available for super-users.
|-
| Compact Database
| Allows the user access to the Compact Database option on the System Tools menu.
|}

= Failsafe WMS/WCS Recovery Process =

In the event of failure of any portion of the systems, a full-restart of all processes associated to RF processes will normally resolve the problem. The full process normally takes less than 15 minutes.

=== Summary of Steps ===

* Check running WMS Update Processes
* Check WMS Interfaces
* Re-start all WMS Update processes
* Re-start WCS-Server application
* Re-start WCS Server machine

=== Check running WMS Update processes ===

On the UNISON RDT Menu, run the RDT Start/Stop screen:

[[File:WCS-COMMON-FailsafeRecovery41.png]]

Should any of the processes be stopped, start them by entering START from the action prompt.

At this point, check with the operation that the problem has resolved. If not, move on to the next stage.

=== Check WMS Interfaces ===

On the UNISON RDT Menu, run the RDT Start/Stop screen:

[[File:WCS-COMMON-FailsafeRecovery41.png]]

Stop and start the WMS Interface processes by first entering KILL:

[[File:WCS-COMMON-FailsafeRecovery42.png]]

[[File:WCS-COMMON-FailsafeRecovery43.png]]

Re-start them by typing START.

[[File:WCS-COMMON-FailsafeRecovery44.png]]

At this point, check with the operation that the problem has resolved. If not, move on to the next stage.

=== Re-start all WMS Update processes ===

On the UNISON RDT Menu, run the RDT Start/Stop screen:

[[File:WCS-COMMON-FailsafeRecovery41.png]]

Stop the Update processes by entering STOP

[[File:WCS-COMMON-FailsafeRecovery45.png]]

Stop the WMS Interface processes by entering KILL:

[[File:WCS-COMMON-FailsafeRecovery46.png]]

[[File:WCS-COMMON-FailsafeRecovery47.png]]

Re-start them all by typing START.

[[File:WCS-COMMON-FailsafeRecovery48.png]]

[[File:WCS-COMMON-FailsafeRecovery49.png]]

[[File:WCS-COMMON-FailsafeRecovery50.png]]

At this point, check with the operation that the problem has resolved. If not, move on to the next stage.

=== Re-start WCS-Server application ===

Log on the WCS Server machine and locate the WCS-Server application:

[[File:WCS-COMMON-FailsafeRecovery51.png]]

To stop, click the X in the corner:

[[File:WCS-COMMON-FailsafeRecovery52.png]]

Enter the password.

[[File:WCS-COMMON-FailsafeRecovery53.png]]

Click OK

If any RDT users are connected, you will be prompted how long to wait before logging them off:

[[File:WCS-COMMON-FailsafeRecovery54.png]]

If you enter 0, the WCS-Server application will exit immediately without informing any connected RF users.

If you leave a positive number of minutes in here, the WCS-Server will commence a countdown on the screen, and will send each connected RF user a message, to exit the system immediately.

[[File:WCS-COMMON-FailsafeRecovery55.png]] [[File:WCS-COMMON-FailsafeRecovery56.png]]

[[File:WCS-COMMON-FailsafeRecovery57.png]] [[File:WCS-COMMON-FailsafeRecovery58.png]]

To restart the WCS-Server application, choose the application from the Start menu/Programs/Warehouse Control Server/WCS Server shortcut.

When the server restarts, the WCS will reconnect to any RDT users when they next press a key:

[[File:WCS-COMMON-FailsafeRecovery59.png]] [[File:WCS-COMMON-FailsafeRecovery60.png]]

{{Note}} If you are quick enough stopping and starting the WCS-Server application, the users will not know that the application has been re-started - they will simply continue to work as usual, as long as you get it re-started within 30 seconds.

At this point, check with the operation that the problem has resolved. If not, move on to the next stage. Also, contact OBSL support.

=== Re-start WCS Server machine ===

Ensure all users have logged off the system, including RF users and WCS Maintenance users.

Reboot the WCS Server machine.

When the machine has re-booted, restart the WCS application.

= Changing WCS/WMS Connectivity =

It is sometimes necessary to change the connectivity settings on the WMS and/or WCS (for example, a site move). The following is a standard process covering this procedure.

{{Note}} If the WCS IP address is being changed then a new authorisation code may be required. This can be requested from OBS Logistics.

=== Requirements ===

Before this process is started, you will need to know:

* The WMS IP address.
* The port number used to send messages from the WMS to the WCS.
* The port number used to send messages from the WCS to the WMS.

=== Stop the existing WMS - WCS Interface ===

Stop the existing WMS/WCS interface using the 'RDT Start/Stop Screen' (WHS7920). This is done by entering 'STOP' at the action prompt to stop the RF processes followed by entering 'KILL' at the action prompt to stop the interface. Once the RF processes and interface have been stopped, the screen should display all of the processes as status 0 (stopped). An example of this can be seen in the screenshot below:

[[File:WCS-COMMON-Connectivity61.png]]

The WCS should also display a message showing that there is no connection between the WCS and WMS:

[[File:WCS-COMMON-Connectivity62.png]]

=== Update the WCS Connection Settings ===

Stop the WCS Server application. Start a WCS Maintenance session and open the 'System Settings' screen which can be done by selecting the 'System Settings…' option from the 'System Tools' drop down list. This can be seen in the screenshot below:

[[File:WCS-COMMON-Connectivity63.png]]

Once the 'System Settings' screen has opened, select the 'Socket Settings' option before entering the WMS IP Address (WMS HostName), the WMS to WCS port number (WMS_WCS LocalPort) and WCS to WMS port number (WCS_WMS RemotePort) with the relevant values. An example is shown in the screenshot below:

[[File:WCS-COMMON-Connectivity64.png]]

=== Update the WMS Connection Settings ===

If the IP address of the WCS PC has changed then follow the steps below:

At a UNIX prompt on the WMS change directory to the RDT directory using the following command:

cd $RDT_LOCATION

Once in this directory, open the 'start_int' file. Once the 'start_int' file has been opened, locate the lines of code that contain the connection settings. An example of the code is displayed below:

nohup $RDT_LOCATION/wms_xmit3 $WMSWCS_MBX 1024 15000 10.43.0.124 0 1 1 0 60000 0

$RDT_LOCATION/ >>$RDT_LOCATION/wms_if_msgs.log &

nohup $RDT_LOCATION/wms_recv3 $RDT_LOCATION/rmp.ctrl 15001 1 0 5 $RDT_LOCATION >

>$RDT_LOCATION/wms_if_msgs.log &

Ensure that the IP address of the WCS PC (highlighted above in blue), the WMS to WCS port number (highlighted above in green) and the WCS to WMS port number (highlighted above in red) are populated correctly. If they are not correct, amend the values before saving the changes.

{{Note}} If the RDT directory ($RDT_LOCATION) or the 'start_int' program does not exist then contact OBS Logistics support.

=== Start the WCS and Interface ===

Start the WCS Server application, it should still show as no connection to the WMS. Start the WMS/WCS interface on the new machine using the 'RDT Start/Stop Screen' (WHS7920). This is done by entering 'START' at the action prompt. Once the RF processes and interface have been started, the screen should display all of the processes as status 1 (Running). An example of this can be seen in the screenshot below:

[[File:WCS-COMMON-Connectivity65.png]]

The WCS should also display a message showing that it is connected to the WMS:

[[File:WCS-COMMON-Connectivity66.png]]

The WCS should be available to use now.

= Appendices =
== WCS File Layout ==

'''RDT Activity table'''

[[File:WCS-COMMON67.png]]

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

External Data Access

2025-06-20T09:51:35Z

Anw: Categorisation

{{Doc_Title
|Client=Aptean
|System=WCS
|Title=External Data Access Guide
|Reference=UG 106181
|Version=11.1
|Date=24th November 2011
|Sysver=3.4
}}


= Summary =
The Calidus 3''pl''-Mobile database can be accessed for client reporting purposes using a Microsoft-standard ODBC data connection.

The suggested mechanism for accessing the data is:

# Create a link database
# Create an ODBC Data Source
# Get the data from the ODBC data source with Microsoft Excel

= Details =
== Set-up Requirements ==
The Calidus 3''pl''-Mobile system must be set up for your data.

You must have access to the logging database. This document assumes that this has been created under a network drive X:

== Create a Link Database ==
In order to minimise the impact of the query on the Calidus 3''pl''-Mobile system, this should be performed on a link database. It is possible to access the database directly, but this is '''not''' recommended by OBS.

Create a new Access database.

[[Image:DataAccess1.png]]

This database can be created locally (or your PC) if this is only being used by you, or can be created on any network machine (for example, the WCS Server) if used by many people.

[[Image:DataAccess2.png]]

In this case this has been called WCS-Reporting.mdb, created in My Documents

[[Image:DataAccess3.png]]

Choose Get External Data/Link Tables from the File menu.

[[Image:DataAccess4.png]]

Link to your Calidus 3''pl''-Mobile logging database. This is normally in X:\Log.mdb or X:\Log1.mdb.

[[Image:DataAccess5.png]]

Link the table ‘RDT Activity’

[[Image:DataAccess6.png]]

Save your new database by closing Access.

== Create an ODBC Data Source ==
Choose Start/Settings/Control Panel/Administrative Tools/Data Sources (ODBC) from the Start menu.

If this option is unavailable on your PC, you must have an Administrator user do this for you.

[[Image:DataAccess7.png]]

Create a new System DSN

[[Image:DataAccess8.png]]

Choose ‘Microsoft Access Driver (*.mdb)’.

If this option is unavailable on your PC, the Microsoft Data Access Components (MDAC) must be installed on your PC.

[[Image:DataAccess9.png]]

Ensure the Data Source Name is 8 characters or less.

Select your data source using the ‘Select…’ button.

[[Image:DataAccess10.png]]

Click ‘OK’ to save the new data source

[[Image:DataAccess11.png]]

== Access the Data in Microsoft Excel ==
Now that this is set up, you can access the Calidus 3''pl''-Mobile logging data from external sources. In this example, this is from Microsoft Excel, but could just as easily be from any ODBC-compliant reporting tool, such as Crystal Reports or Cognos Impromtu.

Open Excel and create a new workbook.

[[Image:DataAccess12.png]]

Choose Import External Data/New Database Query from the Data menu.

At this point, you may be prompted to install Microsoft Query for Excel. This may have to be completed by an Administrator.

[[Image:DataAccess13.png]]

Choose the WCS Reporting Data Source we set up earlier.

[[Image:DataAccess14.png]]

Choose the table to report. In this case, you will want the RDT Activity table.

[[Image:DataAccess15.png]]

Choose the data you want to filter.

[[Image:DataAccess16.png]]

Choose the Sort Order

[[Image:DataAccess17.png]]

Return the data back into Excel.

[[Image:DataAccess18.png]]

Choose the cell into which you want the data to be loaded.

[[Image:DataAccess19.png]]

Once the data is loaded in the form, you can filter and format the data in any way you want.

[[Image:DataAccess20.png]]

You can refresh the data by choosing Refresh Data from Data menu or the menu shown when right-clicking on the cells.

[[Image:DataAccess21.png]]

The sheet will retain its formatting.

You can then save this worksheet for running in the future.

== Adding Parameters ==
Parameters allow you to specify the data to be returned ‘on the fly’ by saying what you want it to match.

Choose Import External Data/Edit Query from the Data menu.

Keep hitting Next until you get to the end of the query, then click on the ‘View Data in Microsoft Query’ option, before clicking Finish.

[[Image:DataAccess22.png]]

You will be taken into the Microsoft Query application.

[[Image:DataAccess23.png]]

Make sure the Auto-Query button (!) is not pressed in.

[[Image:DataAccess24.png]]

Choose the item you wish to parameterise.

[[Image:DataAccess25.png]]

Enter a prompt for the value.

[[Image:DataAccess26.png]]

Hit Enter. You will be prompted for an employee code in a popup box. Enter one.

[[Image:DataAccess27.png]]

You can now exit Microsoft Query and return the data to the Excel spreadsheet by clicking the X in the top corner.

[[Image:DataAccess28.png]]

The data is now selecting only the tasks relevant to employee IJ. Whenever you refresh the data, the Employee will be prompted:

[[Image:DataAccess29.png]]

You can add multiple parameters to a query. Each will be prompted for in turn.

'''Note:''' You have full help on how Microsoft Query works, available using the Help button on the Query forms.

[[Image:DataAccess30.png]]

#
#:
#::
#:::
#::::
#:::::
#::::::
#:::::::
#:::::::# '''WCS File Layout'''

'''RDT Activity table'''

[[Image:DataAccess31.png]]
[[Category:FAQ]]

Changing the IP of an RF Unit

2025-06-06T11:40:26Z

Anw: Initial Creation

1. From the ‘Start’ menu, open the ‘Wavelink Studio’ option

[[File:WCS-CHANGE-IP-1.png|533x533px]]

2. When you click on ‘Wavelink Studio’ this will display the RF application icons

3. Press and hold (long hold) on the required RF icon (''the name is part of the configuration so will be different to the name displayed in the screen shot displayed below'')

[[File:WCS-CHANGE-IP-2.png|533x533px]]

4.    The configuration options for the chosen icon will be displayed.

5.    Enter the updated I.P. address in the ‘Host Address’ box and click the ‘Update’ button

6.    This will save the configuration change to the selected icon

[[File:WCS-CHANGE-IP-3.png|533x533px]]
[[Category:FAQ]]
[[Category:Technical Guides]]

File:WCS-CHANGE-IP-3.png

2025-06-06T11:39:37Z

Anw:

Change IP

File:WCS-CHANGE-IP-2.png

2025-06-06T11:38:48Z

Anw:

Change IP

File:WCS-CHANGE-IP-1.png

2025-06-06T11:37:59Z

Anw:

Change IP address

Main Page

2025-05-14T14:29:42Z

Anw: Updated

<div style="text-align: center;">[[Image:Calidus-Mobile.JPG]]</div>

* [[:Category:Documents]]

* [[:Category:WCS Training Guides]]
**[[Installation Guide]]
**[[Set-up Guide]]
**[[WCS Maintenance]]
**[[RDT Functionality]]
**[[Using WCS from WMS]]
**[[External Data Access]]
** [[Label Formats]]

* [[:Category:FAQ]]
* [[Did You Know]]

* [[:Category:Android|Android]]
** [[Installing Barcoders Android Server]]
** [[Android Setup Guide]]
** [[Android Usage Guide]]
** [[Android Development Guide]]
** [[Android Support Guide]]

* [[:Category:Technical Guides]]
**[[C-TMS Automotive RF Process]]

Did You Know

2025-05-14T14:28:52Z

Anw: Initial Creation

This guide is intended to help you discover features delivered with your ''CALIDUS'' system.

== ''CALIDUS'' WCS ==
Nothing yet!

== ''CALIDUS'' Assist ==
=== Searching for Help ===
Although all pages from your ''CALIDUS'' system link directly to the appropriate page in this ''CALIDUS'' Assist guide, you can search for help on anything in the system using the search bar. It depends on how you have ''CALIDUS'' Assist configured, but this search bar is normally either in the title at the top of the screen or in the toolbar on the left.

Did you know that you can activate this search at any time using a shortcut key combination? Hover over the Search bar now and you will see it tells you the hot-key combination, typically ALT-F or ALT-SHIFT-F. Hitting those keys together will activate the search box and you can type in what you're looking for. Be aware that these shortcuts are dependent on the browser that you are using, so check for compatibility first.

If you know the name of the page, just type it there and click the '''Go''' button. If you want to search for any text in the page, click the '''Search''' button instead, or just hit enter for ''CALIDUS'' Assist to do it for you. Typically, as you type, the search bar will quickly offer you some matches that might be what you're looking for - if it is, just click the suggestion and Assist will take you there.

Some tips on searching:

* If you enter multiple words (like "fixed drop scheduling") without quotes, the search routine will find you pages that match any of the words, but ordered in the most likely order (i.e. with most matches of most words)
* If there is a page called "fixed drop scheduling", you will be taken straight to it.
* If you enter your search with quotes i.e. "fixed drop scheduling", it will find that specific phrase in the pages, rather than any of the words.
* If you enter plus instead of space i.e. fixed+drop+scheduling, you will only get pages in the results that have all 3 words in them, anywhere in the page, in any order.
* You can also control partial word matching with as asterisk. So let's say you are searching for a parameter called AUTO_SCHED something-or-other. Searching for AUTO_SCHED will not bring back any results, as there are no full words or phrases like that. But if you enter AUTO_SCHED_* instead, it will search for words ''starting with'' "AUTO_SCHED" and bring you back some matches.

=== Searching Tables ===
A lot of the pages have tables of data on them - this can be a bit difficult to see what you're after. So, in the cases where there is a large amount of data in tables, we have made the tables searchable.

On top of the table will be a search box. Type in what you're looking for and the table will be filtered to show all of the matching rows - that is, rows where any column contains that text at all, anywhere. This filters as you type.

Note that some data will be always be shown, like headers, or rows that the writers of the page have decided must always be shown.

You can clear the text out of the search box and this will display everything again - do this by either deleting it or use the provided clear button to the right of the search box.

Have a go below - maybe try entering "ap", then "app", or enter "fruit" and see the way it works.

{| class="wikitable apt-searchable" id="dyk-search-table"
|-
! Fruit !! Some Text - this header row is always shown
|-
| Apple || Green apples
|-
| Orange || Not an apple
|-
| Pineapple || Also not
|-
| Grapefruit || Very big!
|- class="non-searchable"
| Banana || I like bananas, so I'm always going to show them
|-
| Kumquat || Interesting fruit
|-
| Grape || Small fruit
|-
| Tomato || Is this a fruit or a vegetable?
|}

=== Translating ===
The toolbox contains a link to Google Translate to translate the page into a language of your choice. Select the language from the drop-down list, and Google will translate the whole page for you.

There will be a banner at the top showing the translation options after you have selected a language - simply click the X on the banner to return to the standard page.

=== Printing and Exporting ===
You can export pages from ''CALIDUS'' Assist using the ''Print as PDF'' or ''Download as PFD'' link. Where this appears depends on the style the Assist is configured with, but by default this link will be in the ''Toolbox'' menu on the left of the screen, or on the tabs at the top right of the screen.

You can export categories as a full document in the same way - all pages in that category will be included in the PDF in the order in which they are listed in the category.

We've typically also included a link in the description of categories where this will export as a document, and we also add the {{DocLink|Did You Know}} button next to documents that you can download from the first page of Assist.

Main Page

2025-05-06T13:55:17Z

Anw: Minor change

Label Formats

2025-05-06T13:53:00Z

Anw: Initial Creation

= Introduction =

This document is intended to show the currently-available formats within the Calidus 3pl-Mobile WCS.

The pictures are shown to illustrate the formats only and are not intended as indications of functionality within the system.

Where restrictions on the formats' use are in place, these are listed with the formats.

= Receipt Label Formats =

These are used during the receiving process to label the pallets as they arrive. These formats can also be used during the pallet enquiry RDT process, although they may be missing some items.

== Zeb_6x4in_Rcpt_BHS.LBL ==

Format: Zebra

[[File:WCS-LABELS-2.png|800px]]

== Zeb_3x4in_Rcpt.LBL ==

Format: Zebra

[[File:WCS-LABELS-3.png|800px]]

== Zeb_3x4in_Rcpt2.LBL ==

Format: Zebra

[[File:WCS-LABELS-4.png|800px]]

== Zeb_4in_Rcpt2.LBL ==

Format: Zebra

[[File:WCS-LABELS-5.png|800px]]

== Zeb_4in_Rcpt.LBL ==

Format: Zebra

[[File:WCS-LABELS-6.png|800px]]

== Zeb_A5_Rcpt_106.LBL ==

Format: Zebra

Notes:

# DRAFT
# Only one line of SKU Description is available through WCS.

[[File:WCS-LABELS-7.png|800px]]

== Zeb_A5_Rcpt.LBL ==

Format: Zebra

[[File:WCS-LABELS-8.png|800px]]

== Zeb_4in_Rcpt2_UCC.LBL ==

Format: Zebra

[[File:WCS-LABELS-9.png|800px]]

== Zeb_A5_SSCC_Rcpt.LBL ==

Format: Zebra

Notes:

# DRAFT
# No Owner Name through WCS
# EURODATE is actually the Manufacture Date in the WCS.

[[File:WCS-LABELS-10.png|800px]]

== Zeb_4in_Rcpt2_UCC2.LBL ==

Format: Zebra

[[File:WCS-LABELS-11.png|800px]]

== Zeb_A5_SSCC_Rcpt2.lbl ==

Format: Zebra

Notes:

# DRAFT
# Produced By is fixed in the format, not variable.
# Best Before date format may not match the required format in WCS.
# First barcode type and length untested in WCS.

[[File:WCS-LABELS-12.png|800px]]

== CPCL_4x3in_RCPT3.LBL ==

Format: CPCL

[[File:WCS-LABELS-13.png|800px]]

== CPCL_4x4in_RCPT.LBL ==

Format: CPCL

Also CPCL_4x4in_RCPT_TNT.LBL

[[File:WCS-LABELS-14.png|800px]]

== Zeb_6x4in_Rcpt_NOK.lbl ==

Format: Zebra

[[File:WCS-LABELS-15.png|800px]]

Also available:

V2 - with Location code.

V4 - with Location code (Large).

== Zeb_6x4in_Rcpt_BHS3.lbl ==

Format: Zebra

[[File:WCS-LABELS-16.png|800px]]

== Zeb_4x4in_Rcpt_BARv0.1.LBL ==

[[File:WCS-LABELS-17.png|800px]]

== CPCL_4in_RCPT5.LBL ==

[[File:WCS-LABELS-18.png|800px]]

== CPCL_4x4in_Rcpt_TNT.LBL ==

[[File:WCS-LABELS-19.png|800px]]

= Pick label formatS =

Pick label formats are designed to be printed at the point of picking the stock, labelling the cartons picked, rather than at the point of despatch.

== CPCL_5x3in_Pick.LBL ==

Labels are set to print at point of pick. User is asked for how many labels to print (i.e. number of boxes). Labels are printed with a box count and pallet ID picked from. Label is bespoke and contains hard-coded data field identifiers (DFI) within the barcode.

Printer type: Mobile (CPCL)

Also CPCL_5x3in_Pick_PAG.LBL

[[File:WCS-LABELS-20.png|800px]]

== Zeb_4in_Pick_HDM.LBL ==

Format: Zebra

Notes:

# DRAFT
# Country of Origin (COO) is unavailable in WCS.
# Created On date may differ in format on WCS.
# Contact is the Customer Name on WCS.
# 1 of 1 is fixed on WCS.
# Hazardous information is not available in WCS.

[[File:WCS-LABELS-21.png|800px]]

== TNTUBCF8.LBL ==

Labels are set to print at point of pick. Each pick is done by carton (bespoke). Label is produced per carton. Label is bespoke (contains hard-coded data elements and a logo, which can't be printed through emulation software).

Printer type: Mobile (CPCL)

Format Name TNTUBCF8.LBL

[[File:WCS-LABELS-22.png|800px]]

== Zeb_6x4in_CRTN_DHLE.lbl ==

Format: Zebra

Notes:

# DRAFT
# Title is fixed text
# On WCS, Invoice and Delivery address are the same.
# Currently, "Distributor Logo" is fixed. Can also be a graphic.
# HU Number - Unassigned.
# Delivery Number is WMS Order Number.
# "Via" is Carrier and is not defined in WCS.
# On WCS, JJD Number is the picking container; on WMS, this is the Package Ref.

[[File:WCS-LABELS-23.png|800px]]

= DespatCh Label Formats =

Despatch label formats are designed to be placed on the pallet once it arrives at the marshalling bay. Generally, these labels contain customer information for the final delivery, or a general pallet id that references all the stock on the pallet (a picking container)

== Zeb_6x4in_Desp_CPW.LBL ==

Labels are set to print at point of taking to marshalling. Label is produced one per pallet.

Printer type: Zebra

[[File:WCS-LABELS-24.png|800px]]

== Zeb_6x4in_Desp2.LBL ==

Labels are set to print at point of taking to marshalling. Label is produced one per pick on the pallet.

Printer type: Zebra

[[File:WCS-LABELS-25.png|800px]]

== Zeb_4in_Desp.LBL ==

Format: Zebra

Notes:

# DRAFT
# Instructions are single line in WCS and fixed from the data sent from WMS.
# 1 of 1 is fixed on WCS.

[[File:WCS-LABELS-26.png|800px]]

== Zeb_4in_Desp2.LBL ==

Format: Zebra

[[File:WCS-LABELS-27.png|800px]]

== Zeb_size_ASN.LBL ==

Format: Zebra

Notes:

# DRAFT
# Sainsbury's fixed in label format.
# From: Fixed in WCS

[[File:WCS-LABELS-28.png|800px]]

== CPCL_6x4in_DESP.LBL ==

Format: CPCL

Also CPCL_6x4in_DESP_LUTT.LBL

[[File:WCS-LABELS-29.png|800px]]

== CPCL_6x4in_DESP2_LUTT.LBL ==

Format: CPCL

[[File:WCS-LABELS-30.png|800px]]

== Zeb_6x4in_Desp_NOK.lbl ==

Format: Zebra

[[File:WCS-LABELS-31.png|800px]]

= External PICK LABELS =

== NIJPickLabel.LBL ==

Label is printed at the point of marshalling. Label is in OCE format, which requires a defined label format LABEL_RF_PICKING. Data is then merged by the OCE print server.

Printer Type: Any (OCE format required)

Format Name NIJPickLabel.LBL

^define LABEL_RF_PICKING

^define PRINTER_{PrinterName}

^define OWNER_{OwnerCode}

^define LANGUAGE_EN

^field START_LABEL

^field OWNER_CODE

{OwnerCode}

^global ROUTE_CODE

{RouteCode}

^global LOAD_NUMBER

{LoadNo}

^global ORDER_NUM

{OrderNo}

^field SYSTEM_DATE

{SysDate}

^field SYSTEM_TIME

{SysTime}

^field PICK_STATUS

{PickStatus}

^field MARSHALLING_LOCATION

{MarshLoc}

^field EMPLOYEE_CODE

{Picker}

^field SELLERS_REFERENCE

{OrderRef1}

^field CUSTOMER_REFERENCE

{OrderRef2}

^field SHIP_TO_ADDRESS_1

{Name}

^field SHIP_TO_ADDRESS_2

{AddrLine1}

^field SHIP_TO_ADDRESS_3

{AddrLine2}

^field SHIP_TO_ADDRESS_4

{Town}

^field SHIP_TO_ADDRESS_5

{County}

^field SHIP_TO_COUNTRY_CODE

{Country}

^field SHIP_TO_ZIP_CODE

{PostCode}

^field PICKING_TEXT_1

{PickText}

^field ORDER_PRIO

{Prio}

^global TOTAL_NUMBER_OF_LABELS

1