View source for FS 295993 MY-8QPDRH Location and CD Scanning

<div class="noprint">
{{#vardefine:Client|EXL}}
{{#vardefine:ClientName|DHL}}
{{#vardefine:System|''CALIDUS'' Mobile}}
{{#vardefine:Doc_Title|Location and CD Scanning}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|15th March 2012}}
{{#vardefine:Reference|295993 MY-8QPDRH}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}} 

<!-- TOC --> 
<div class="noprint">
= Functional Overview  =

== Client Requirement  ==
'''Change Request Summary:'''

Location & Check Digit scanning functionality required in WCS

'''Change Request Details:'''

At present the system will not recognise the location code and check digit if the barcode contains both. The requirement is to be able to recognise barcodes containing both the location code and the check digits as well as what it’s currently setup as. 

Operations are ideally after an option that would let us to ALL the following
#Scan the location OR
#Manually enter the check digits OR
#Scan the location AND check digit combined.

Benefits identified as a result of the change:

:To help with the load scanning functionality.

Additional functionality was requested to be added to this change, by Mo Yasin of the Coventry site, as follows:

:Add support for "Pick By Quantity".

== Solution Overview  ==
A new value will be added to the drop-down list for the "Bespoke Site Rule" rule on ''CALIDUS'' Mobile. The new value will allow the RDT/WCS to recognise the location code when a barcode is scanned that contains both the location and check digit values combined. 
The new "Bespoke Site Rule" value will work in all scanning of locations and check digits, regardless of the setting of the Owner/Warehouse "Check Digits?" rule. 

Currently when the "Check Digits?" rule is set to "Combo Check", the user can either scan the location code or manually enter the check digits. 

At present, if the user scans a barcode containing both the location code and check digits then the RDT/WCS will not recognise the location code. 

If the "Bespoke Site Rule" is set to the new value then the system will be changed to extract the first x characters from the barcode where x is equal to the "Aisle Length", "Bay Length" and "Level length" values added together, i.e. the length of the location code values. 

{{Note}} It is assumed that the barcode values containing the combined location code and check digit values do not contain any location delimiters, e.g. "/", "\", "-", ":", etc.

At present, the site have the "Bespoke Site Rule" set to "DHL EXEL Whitwood" in order to utilise functionality to remove the leading "00" from SSCC values where the SSCC value is in a UCC-128 barcode format but the barcode itself is not a UCC-128 barcode.

The new "Bespoke Site Rule" value will remove the two leading zeros ("00" or "(00)") from the SSCC value (Customer Pallet) when the barcode format is not UCC-128.

{{Note}} If the barcode format is not UCC-128 but the SSCC value does not contain two leading zeros at the start of the value then nothing will be removed from the SSCC value. Also, the two leading zeros will only be removed if the user scans the SSCC value. If the user manually enters a SSCC value with two leading zeros, e.g. "001234567890123456", then this will value be accepted and the leading zeros will not be removed.

The bespoke functionality to remove the two leading zeros from the SSCC value will be utilised whenever the RDT prompts the user to enter a customer pallet value including:
* Goods Receipt
* Putaway
* Part Picking
* Picking
* Pallet Moves
* Replenishments
* Stock Moves
* Select Move
* Stock Transfer
* Ad Hoc Pallet Moves
* Stock Take
* Bulk PI
* Pallet Enquiry
* Move Enquiry

The operation want picks to be assigned to users in descending order of quantity to be picked. The existing rule "Picks by Quantity" currently orders the picks in "Picked Quantity" sequence. This will be modified to order the picks in "Picked Quantity" then "To Pick Quantity" sequence, both descending. This will ensure that the incomplete picks are always passed to the user in "To Pick Quantity" sequence, as the Picked Quantity for these incomplete picks (in the way that the operation's system is configured) will always be zero.

{{Note}} This affects only Pick Allocation By Order Page. 

== Scope  ==
* This change will be made to version 4.14 of the ''CALIDUS'' Mobile system only.
{{Note}} There is existing functionality controlled by the Bespoke Site Rule when set to the Whitwood site as follows:
* Location and Check Digit functionality:
** to control Barcode Type
** to extract the CD and location from the same barcode content
* SSCC (Customer Pallet) scanning in all modules:
** to ensure that CODE-128 barcodes are used as well as UCC-128 barcodes
** to remove extraneous parentheses ("(" and ")") from the barcode
** to validate that these barcodes always begin with "00"
* Multi-field scanning in Receipt
** Changing the title of the scanning box displayed
** giving an error given when scanning the wrong barcode types
** allowing CODE-128 and UCC-128 barcode types instead of UCC-128 only
* Check Receipt SSCC scanning functionality, forcing blind quantity entry
* Stock Barcode types (limiting UCC Stock barcodes to AI type 24 only)
* Login Password (forcing only entry of I2of5 barcode types only)

Mo Yasin of the Coventry operation confirmed that only the following functionality was required:
* Location and Check Digit functionality:
** to control Barcode Type
** to extract the CD and location from the same barcode content
* SSCC (Customer Pallet) scanning in all modules:
** to ensure that CODE-128 barcodes are used as well as UCC-128 barcodes
** to remove extraneous parentheses ("(" and ")") from the barcode
** to validate that these barcodes always begin with "00"
All other functionality would not be used, although it has been noted that certain owners and warehouses set up their operation already use:
* Check Receipt
* Multi-field scanning.
None of the Whitwood bespoke functionality other than that required by the operation will be added to the new Coventry Bespoke Site rule.

<!-- NEW PAGE --> 

= Set-up  =

== Pre-requisites  ==
A valid and connected ''CALIDUS'' Mobile system.

== Menu Structure  ==
N/A

== Data  ==
* The Warehouse or Owner "Bespoke" Rule "Bespoke Site Rule" set to the new value of "DHL Coventry".
* The Warehouse or Owner "Bespoke" Rule "Pick By Quantity" set to "Enabled".
* The Warehouse or Owner "General" Rule "Check Digits?" set to "Combo Check".
* The Warehouse or Owner "General" Rules "Aisle Length", "Bay Length" and "Level Length" set to the correct values for the operation.
* The Warehouse or Owner "Pick" Rule "Pick Page Allocation" set to "By Order Page".
{{Note}} These rules should be set against all Warehouses in the system and all Owners that have been set up as restricted Owners (i.e. the owners that have their own rule set).

<!-- NEW PAGE --> 
= Functional Description  =
== Database ==
A new value will be added to the rule category associated to the Bespoke rule "Bespoke Site Rule". This will be set to value "COV" and will have the human-readable text "DHL Coventry".

== WCS Server Changes ==
The operation want picks to be assigned to users in descending order of quantity to be picked. The existing rule "Picks by Quantity" currently orders the picks in "Picked Quantity" sequence. This will be modified to order the picks in "Picked Quantity" then "To Pick Quantity" sequence, both descending. 

The existing function PickSelect in module RDT_Pick will be modified. The flag "FLAG_PICKS_BY_QUANTITY" controls the existing functionality, which sorts the data as follows:
*Picking.[User Order] ASC,
*Picking.[order number] ASC,
*Picking.[Picked Qty] DESC,
*picking.[page number] ASC,
*picking.[seq number] ASC
This will be modified to:
*Picking.[User Order] ASC,
*Picking.[order number] ASC,
*Picking.[Picked Qty] DESC,
*'''Picking.[To Pick Qty] DESC,'''
*picking.[page number] ASC,
*picking.[seq number] ASC

{{Note}} The sorting under rule setting "Regroup Order by Stock" should also be amended in this way.

== RDTMenu1 Changes ==
The procedure InputProcessor_SetValue in module InputProcessorModRDT_Fields will be modified. 

For Customer Pallet fields (FIELD_PALLET_CUST), a new section will be added for bespoke site rule "COV". This will act as follows:
 
If the entry has been scanned in any barcode type, the process will:
* Check for a leading "00" or "(00)". 
** If there is, remove these leading 2 or 4 characters, then extract the following 18 characters as the Customer Pallet data. 
** If there is not, accept the data scanned without modification.
If the entry has not been scanned (i.e. keyed), the data entered will be accepted without modification.

For Check Digit fields (FIELD_CD), a new section will be added for bespoke site rule "COV". This will act as follows:

If the entry has been scanned in any barcode type, the process will perform the following:
* The values of the Aisle, Bay and Level Length rules active for that Warehouse and Owner will be retrieved and added together, to give a location length.
* The first characters (up to the location length calculated) will be removed from the entered data, and the remaining returned as the Check Digit. 
If the entry has not been scanned (i.e. keyed), the data entered will be accepted without modification.

For Location fields (FIELD_LOCATION, FIELD_LOCATION_CONFIRMATION), a new section will be added for bespoke site rule "COV". This will act as follows:

The process will perform the following:
* The values of the Aisle, Bay and Level Length rules active for that Warehouse and Owner will be retrieved and added together, to give a location length.
* For FIELD_LOCATION, or if the data has been scanned, the first characters (up to the location length calculated) will be extracted from the entered data and returned.
* For non-scan entry (i.e. keyed) of type FIELD_LOCATION_CONFIRMATION, the first characters (up to the location length calculated) will be removed from the entered data, and the remaining returned.

As this is completed at an Input level rather than at the process level, this change will be active in any process that requires:
*Location Entry
*Check Digit Entry
*Location Confirmation by Combo Check.
*Cust Pallet Entry

<!-- MEDIA LANDSCAPE YES --> 

= Appendix A: TEST PLAN  =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=To test the functionality created here
|MenuAccess=Main menu
|Prerequisites=Set up as in the [[#Set-up|Set-up]] section 
|Objective=To test: allocating picks by Quantity; Location/CD entry and confirmation and; Customer Pallet Entry.
}} 
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=WCS Maintenance
|Notes= 
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check that the Warehouse "Bespoke" rule "Bespoke Site Rule" can be set to the value "DHL Coventry" and saved.
|Result=The data can be changed and saved.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check that the Owner "Bespoke" rule "Bespoke Site Rule" can be set to the value "DHL Coventry" and saved.
|Result=The data can be changed and saved.
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}} 

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Allocate Picks by Quantity
|Notes=Set up ''CALIDUS'' Mobile as specified and allocated and pick list an order with several part picks across several stock codes, ensuring all have different pick quantities.
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start part picking and complete the order to pick.
|Result=The picks will be allocated to the user in descending pick amount.
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}} 
<!-- NEW PAGE --> 
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Customer Pallet and Location/CD Entry
|Notes=Set up ''CALIDUS'' Mobile as specified and ensure that you have multiple tasks of the following types available: 
*    Goods Receipt
*    Putaway
*    Part Picking
*    Picking (Full Pallet)
*    Pallet Moves
*    Replenishments
*    Stock Moves
*    Select Move
*    Stock Take
{{Note}} As the changes have been completed at an input rather than process level, it is necessary to test only one example of data input of Cust Pallet, Location, Check Digit and Location Confirmation. 
}}{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start a putaway and scan a pallet barcode with no leading zeroes.
|Result=The data is accepted as-is
|Remarks=
|PassFail=
}} 
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a pallet barcode with leading "00" or "(00)"
|Result=The leading zeroes are removed
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) a barcode with no leading zeroes.
|Result=The data is accepted as-is
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Key a pallet barcode with leading "00" or "(00)"
|Result=The data is accepted as-is
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode with the location only in it
|Result=The location should be accepted
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode with the location and check digit in it
|Result=The location should be accepted
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode with the check digit only in it
|Result=The system should display an error (location invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode with a different location and check digit in it
|Result=The system should display an error (location invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) an invalid check digit.
|Result=The system should display an error (check digit invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) any location code, valid or invalid.
|Result=The system should display an error (check digit invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) the valid check digit.
|Result=The check digit should be accepted.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Reposition a putaway and scan a location barcode containing only a location.
|Result=The system should prompt for a check digit.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Backout and scan a location barcode containing only a check digit or invalid location 
|Result=The system should display an error (location invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) an invalid location.
|Result=The system should display an error (location invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter (key) a valid location.
|Result=The system should prompt for a check digit.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode containing only a location
|Result=The system should display an error (check digit invalid).
|Remarks=
|PassFail=
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter an invalid check digit 
|Result=The system should display an error (check digit invalid).
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan a location barcode containing a valid location and check digit.
|Result=The system should accept the check digit.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Reposition another putaway. Enter a valid location. Enter (key) a valid check digit. 
|Result=The system should accept the check digit.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=As the changes have been completed at an input rather than process level, it is necessary to test only one example of data input of Cust Pallet, Location, Check Digit and Location Confirmation. However, the following areas and functionality may also be tested:
*    Goods Receipt
** Blind Receipt
** Check Receipt
*    Putaway
*    Part Picking
*    Picking (Full Pallet)
*    Pallet Moves
** Reposition
*    Replenishments
*    Stock Moves
*    Select Move
*    Ad Hoc Pallet Moves
*    Stock Take
*    Bulk PI
*    Pallet Enquiry
*    Move Enquiry 
*    Location Enquiry
|Result=As Expected
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}} 

<!-- MEDIA LANDSCAPE NO --> 
{{Doc_Appendix
|Appendix=B
|Estimate=Y
|Glossary=WCS
|Ref1=EST 295993 MY-8QPDRH Location & CD Scanning v1.0.doc
|RefV1=1.0
|RefDate1=31/01/2012
|REQ=0
|EST=1
|FS=1.25
|TS=0
|DEV=3.25
|ST=1.75
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Phil Harding
|Rev1Title=OBS Project Manager
|Rev2=Mo Yasin
|Rev2Title=Client Representative
}}</div> 
[[Category:{{#var:Client}} FS]]