RDT Functionality - Revision history

Anw: Minor formatting change

2025-12-19T12:23:24Z

Minor formatting change

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

2025-10-30T11:14:33Z

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

← Older revision		Revision as of 13:14, 30 October 2025
Line 1:		Line 1:
	{{Doc_Title		{{Doc_Title
	\|Client=Aptean		\| Client = Aptean
	\|System=WCS		\| System = WCS
	\|Title=RDT Functionality Guide		\| Title = RDT Functionality Guide
	\|Reference=UG 106181		\| Reference = UG 106181
	\|Version=11.1		\| Version = 11.02
	\|Date=~~24th November 2011~~		\| Date = 30th October 2025
	\|Sysver=3.4		\| Sysver = 3.4
	}}		}}

Anw: 292219 - Pick Exchange Amendment

2025-10-30T11:05:50Z

292219 - Pick Exchange Amendment

← Older revision		Revision as of 13:05, 30 October 2025
Line 727:		Line 727:

	The audit trail (and all supporting files) will be maintained.		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.


Line 1,073:		Line 1,096:


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

Anw: 292218 - Narrow Aisle Part Pick Confirmation

2025-10-30T10:54:23Z

292218 - Narrow Aisle Part Pick Confirmation

← Older revision		Revision as of 12:54, 30 October 2025
Line 1,077:		Line 1,077:

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



Line 1,348:		Line 1,357:

	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:		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		* Reposition pallet at destination
	* Cancel movement at source		* Cancel movement at source
Line 1,356:		Line 1,363:

	See section [[#Movement Exceptions]] for details of Movement Exceptions.		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.



Line 1,707:		Line 1,717:
	==== NADC OUT ====		==== 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.		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 ====		==== 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.		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.

Anw: 291597 Extended Putaway Reposition Validation

2025-10-30T10:41:43Z

291597 Extended Putaway Reposition Validation

← Older revision		Revision as of 12:41, 30 October 2025
Line 641:		Line 641:
	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.		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 ===		=== Cancellation ===

Anw: 291594 Truck Type Logon Validation

2025-10-30T10:31:19Z

291594 Truck Type Logon Validation

← Older revision		Revision as of 12:31, 30 October 2025
Line 66:		Line 66:
	== RDT Logon ==		== 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.		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]].		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]].

Anw: Minor formatting change

2025-04-30T13:20:02Z

Minor formatting change

← Older revision		Revision as of 15:20, 30 April 2025
Line 1:		Line 1:
			{{Doc_Title
			\|Client=Aptean
			\|System=WCS
			\|Title=RDT Functionality Guide
			\|Reference=UG 106181
			\|Version=11.1
			\|Date=24th November 2011
			\|Sysver=3.4
			}}

			<!-- TOC -->
	= INTRODUCTION =		= 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.		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.

Anw: Added stock replens

2011-11-09T15:22:54Z

Added stock replens

← Older revision		Revision as of 17:22, 9 November 2011
Line 1,836:		Line 1,836:
	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.		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 =		= Bespoke RDT Modules =

Anw at 08:23, 20 October 2011

2011-10-20T08:23:09Z

@@ Line 1,017: / Line 1,017: @@
 This enquiry is also available from the Enquiries sub-menu from any other task.
 == Picking ==
@@ Line 1,836: / Line 1,848: @@
 * Uploading of batch files to WMS
 * Stock Moves (Combined Split)
 * Ad Hoc Putaway
@@ Line 1,971: / Line 1,982: @@
 When confirmed, the WMS is informed that the pallet is despatched.

Rhs at 14:18, 16 May 2011

2011-05-16T14:18:31Z

← Older revision		Revision as of 16:18, 16 May 2011
Line 1,032:		Line 1,032:

	=== Part-pallet Picking ===		=== Part-pallet Picking ===
	Part Picking covers both Case picking and Unit picking, if both the WCS and WMS are enabled for this. See section ~~4.10~~ for details of multiple UOM processing.		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.


Line 1,073:		Line 1,073:


	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 ~~(see 5.10)~~		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


Line 1,170:		Line 1,170:
	#* 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)		#* 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 ~~obtained in (5.7.4)~~ is ordered on the criteria (highest priority first):		# The list of suitable picks is ordered on the criteria (highest priority first):

	#		#
Line 2,030:		Line 2,030:
	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 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 ~~another document, reference 7~~.~~16 in 7.16~~		A full description of how to use the maintenance utility is available in C3PL-M Maintenance User Guide.


Line 2,047:		Line 2,047:


	== Logging ==		=='''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.		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.

Line 2,056:		Line 2,056:
	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 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 ~~section 7.4above~~) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.		Any activity by a WCS user is logged (see [[#Logging]]) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.


Line 2,062:		Line 2,062:
	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.		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 ~~section 7.4above~~) and can be recalled on a fully configurable enquiry screen, with complete selection criteria.		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.