View source for FS 369101 UAT-67 Cage Confirmation Scans

<div class="noprint">
{{#vardefine:Client|DHLT}}
{{#vardefine:ClientName|DHL}}
{{#vardefine:System|''CALIDUS'' MCS}}
{{#vardefine:SystemCode|MCS}}
{{#vardefine:Doc_Title|Cage Confirmation Scans}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|5th February 2020}}
{{#vardefine:Reference|369101 UAT-67}}
{{#vardefine:Year|2020}}
{{ #vardefine: Figure | 0 }}{{ #vardefine: Example | 0 }}
<!--
Sample Xref:
{{Xref
|Type=Figure
|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}
|Text=Data Upload - Import screen.}}
-->
</div>
{{Doc_TitleNew
|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  ==
When pallet building at C3 consolidation centre users need to have an additional check to make sure the items are physically loaded to the correct pallet by scanning and confirming pallet ID. OBS advised this will be a change to add a validation making each item scanned require a positive scan on the cage/pallet label.


== Solution Overview  ==
The MCS pallet building process will be made configurable by location (i.e. RDC) to force confirmation of the pallet after every scan.

This is expected to be enabled for Cherwell 3 (the consolidation centre) but not for the warehouses (i.e. Cherwell 1), which will continue with the process as now.


== Scope  ==
This change will be applied to system version 2 of C-MCS linking to system version 11.35 on HCRTST and once approved will be promoted to HCRPRD.

This change to the functionality will be controlled by a new location parameter. This will default to disabled, to retain current system functionality. DHL operational and project staff are responsible for configuring the location to the new pallet building process.

This change mentions the label printing process, which is undergoing a slight change (under SCR 369080 MCS Scan Printer). This functionality is not being developed as part of this change and will be developed separately.


== Impact ==
<!-- Identify the potential consequences of the changes described in this Functional Specification.

Relating to the scope of work, document any identified dependencies necessary to maintain consistency of the solution.  Highlight those not addressed within this solution specification.

Include any considered and related opportunities for improvement not addressed within this solution specification. -->
As decided by the customer. At locations where the customer chooses to enable this functionality, the users will be required to scan a package and a pallet in combination for every package that is palletised through MCS Pallet Building. 


<!-- NEW PAGE --> 
= CONFIGURATION SET-UP  =
== Pre-requisites  ==
C-MCS must be configured and connected to a configured C-TMS system.


== Menu Structure  ==
N/A


== Data  ==
<!-- Document any configuration data set up necessary to enable or control the solution e.g. the new report will be added to the standing data to allow it to be selected from the standard reports form. The selection criteria for the report will be (insert selection criteria). -->
At each location that requires it, the MCS Configuration must be changed so that the flag "Pallet Building Process" is set to "Single" (the new process) from the default "Continuous" value.

[[File:FS_369101_Location.PNG|border|600px]]
{{Xref|Type=Figure|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}|Text=Locations maintenance - MCS tab}}

It is expected that this will be configured only at the DHLCHER3 location. However, the operation or project team could enable this at any location if they desire.


== Implementation Advice ==
None


<!-- NEW PAGE --> 
= FUNCTIONAL DESCRIPTION =
== Locations Maintenance ==
The C-TMS Locations Maintenance form will be modified to add a new drop-down list, labelled as "Pallet Building Process". This will default to the value "Continuous". 

[[File:FS_369101_Location.PNG|border|600px]]
{{Xref|Type=Figure|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}|Text=Locations maintenance - MCS tab}}


== MCS Pallet Building ==
The Cherwell 1 Pallet Building process is expected to continue with the normal process, as follows:
* The user will select the Pallet Building option.
* The user will scan a package.
* MCS will display the package details and suggest any pallets.
* If an open pallet is suitable, the user can scan the pallet label in the Pallet text box, and MCS will confirm that the package is on this pallet.
* If no open pallets are available and suggested, the user can create a new pallet with the '''New Pallet''' button.
* When pressed, MCS will prompt them to scan a new pre-printed pallet label. When confirmed, MCS will confirm that the package is on this pallet.
* MCS will stick to this pallet.
* MCS will prompt to scan a package again.
* When scanned, the package will be automatically added to the current pallet.
* To change pallets, the user will be able to click the '''Change Pallet''' button.


<gallery widths=200px heights=320px perrow=3>
Image:FS_369101_Pallet_Building1.PNG|''Pallet Building - start''
Image:FS_369101_Pallet_Building2.PNG|''Package scanned, pallets suggested''
Image:FS_369101_Pallet_Building3.PNG|''Pallet confirmed, stuck to pallet''
</gallery>
{{Xref|Type=Figure|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}|Text=Cherwell 1 Pallet Building process}}


The Cherwell 3 Pallet Building process will be configured to use the new process, as follows:
* The user will select the Pallet Building option.
* The user will scan a package.
* MCS will display the package details and suggest any pallets.
* If an open pallet is suitable, the user can scan the pallet label in the Pallet text box, and MCS will confirm that the package is on this pallet.
* If no open pallets are available and suggested, the user can create a new pallet with the '''New Pallet''' button.
* When pressed, MCS will prompt them to select a printer. {{Note}} This printer selection process is being changed under SCR 369080. When selected and confirmed, MCS will print the pallet label to the printer and will confirm that the package is on this pallet.
* MCS will '''not''' stick to this pallet - it will be blanked.
* MCS will prompt to scan a package again.
* From this point, the user will work through the same process each time, as from the second step above.

<gallery widths=200px heights=320px perrow=3>
Image:FS_369101_Pallet_Building1.PNG|''Pallet Building - start''
Image:FS_369101_Pallet_Building2.PNG|''Package scanned, pallets suggested''
Image:FS_369101_Pallet_Building1.PNG|''Pallet confirmed, '''not''' stuck to pallet''
</gallery>
{{Xref|Type=Figure|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}|Text=Cherwell 3 Pallet Building process}}


<!-- NEW PAGE --> 
= TECHNICAL NOTES =
== Modules Changed ==
<!-- List the modules or objects that will be changed by this development -->
{| class="wikitable" border="1" width="100%"
|-bgcolor="#FFFF99"
! width="20%" | Module Name || width="40%" | Module Type || width="40%" | Notes
|-
| LOCATION.fmb || C-TMS Form || &nbsp;
|-
| DP_MCS || C-TMS Package || &nbsp;
|-
| V_MCS_SITE || C-TMS View || &nbsp;
|-
| (As required) || SQL || Database modification script.
|-
| VMcsSiteDAL1.cs	|| MCS Server code	|| &nbsp;
|-
| VMcsSiteDAL1_Gen.cs	|| MCS Server code	|| &nbsp;
|-
| VMcsSite1_Gen.cs	|| MCS Server code	|| &nbsp;
|-
| McsDatabase.js	|| MCS Device code	|| &nbsp;
|-
| m004a01t_uc_pallets.js	|| MCS Device code	|| &nbsp;
|}


== Table Updates ==
Table GEO_LOCATION will change to add the following field:
{| class="wikitable" border="1" width="100%"
|-bgcolor="#FFFF99"
! width="20%" | Name || width="10%" | Type || width="10%" | Nullable || width="10%" | Default || width="10%" | Storage || width="40%" | Comments
|-
| MCS_PALLET_BUILD_PROCESS || VARCHAR2(1) || N || N || &nbsp; || &nbsp;
|}


== Developer Notes ==
To achieve this, we must make the following changes:
*	New Location configuration required (i.e. applicable for C3, not C1). "Pallet Building Process", values "Continuous" (default) or "Single" (new process).
**	Modify C-TMS Location form MCS tab.
**	Modify DB table
**	Modify V_MCS_SITE
**	Modify MCS to add the new flag.
*	In MCS Pallet Building:
**	After palletising a package, check the new location flag is "Single". If so, blank the package information and selected pallet and return to the package prompt.


=== C-TMS Database Changes ===
The existing view V_MCS_SITE will be modified to return new MCS location flag, as follows:

 CREATE OR REPLACE VIEW V_MCS_SITE AS
 SELECT DEPOT SIT_DEPOT, LOCATION_ID SIT_LOCATION_ID, LOCATION_NAME SIT_LOCATION_NAME,
 MCS_PRINT_PALLET_LABEL SIT_PALLET_LABEL, 
 MCS_PALLET_CLOSURE SIT_PALLET_CLOSURE,
 MCS_PALLET_SEAL_REQD SIT_PALLET_SEAL_REQD, 
 MCS_TRANS_SHIP SIT_TRANS_SHIP,
 MCS_PALLET_BUILD_PROCESS SIT_PALLET_BUILD_PROCESS,
 NVL(UPDATED_DATE,CREATED_DATE) SIT_UPDATED_DATE
 FROM GEO_LOCATION
 WHERE DEPOT = 'RDC'
 AND NVL(MCS_ACTIVE,'N') = 'Y'
 ORDER BY LOCATION_ID

This change and the database table change will be added to a database modification script, to be used during implementation.


=== C-TMS Locations Form Changes ===
The C-TMS Locations Maintenance form will be modified to add a new drop-down list, labelled as "Pallet Building Process". This will default in the database to a value of "C". 

The field will be added under the existing "Pallet Building Validation" field.

The drop-down list will be populated with the descriptions of the field values below:
* "C" - Continuous (the default value).
* "S" - Single.

The following existing fields will be moved to the right in a new column:
* Set Trip Status at Receipt.
* Set Trip Status at Despatch.


[[File:FS_369101_Location.PNG|border|600px]]
{{Xref|Type=Figure|Num={{ #vardefineecho: Figure| {{ #expr: {{ #var: Figure}} + 1 }} }}|Text=Locations maintenance - MCS tab changes}}


=== MCS DAL Changes ===
At login, MCS must receive the location (depot) configuration flags from C-TMS.
*	SIT_PALLET_BUILD_PROCESS - this flag controls whether pallets built through C-MCS at this location will stick to a pallet (C), or will require pallet confirmation after each scan (S).

These will be received as part of the logon procedure.

The location configuration flags will be received on the list of depots received when calling V_MCS_SITE and will be stored on the local database in new fields. The new flag will be accessible under the MCS.App object directly i.e. MCS.App.SIT_PALLET_BUILD_PROCESS.


Affected code modules:
*	VMcsSiteDAL1.cs - add the new fields as XML tags.
*	VMcsSiteDAL1_Gen.cs - add the new flags to the read data.
*	VMcsSite1_Gen.cs - add the new fields.
*	McsDatabase.js - add the new flag.


=== MCS Pallet Building Screen ===
Pallet building package information to be changed to:
*	when package palletised, return to initial prompt, only if configured to do so.

The process will check MCS.App.SIT_PALLET_BUILD_PROCESS. If set to "C", it will work as now. If set to "S", it will:
*	Reset the selected pallet ID.
*	Reset the pallet ID field.
*	Clear the package display.
*	Return to the package prompt.

This will occur at the end of the following events:
*	On entering a valid pallet for a new package scan.
*	On creating a new pallet.

Function funAddItemToPalletCallback is usually called in response to adding packages to pallets, and currently resets the displayed items. Modifying this process should cover all eventualities.


Affected code modules:
*	m004a01t_uc_pallets.js


<!-- MEDIA LANDSCAPE YES --> 
= TEST PLAN  =
{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Confirm pallet after each package in pallet building.
|MenuAccess=Pallet Building
|Prerequisites=A configured C-TMS and MCS.
|Objective=Test that; locations can be configured to confirm pallet after each package and; pallet building confirms the pallet after each package at configured locations only.
}} {{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=C-TMS Location Form
|Notes=&nbsp;
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check existing MCS-enabled locations, that the Pallet Building Process is set to "Continuous".
|Result=All existing MCS-enabled locations have the value set to "Continuous" on the screen and "C" in the database.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Change a location to Pallet Building Process "Single". Save and re-find.
|Result=The location value should be saved as "S" and shown as "Single" in the Locations form.
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}} 
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=MCS Pallet Building
|Notes=Ensure that there are two locations configured, one with Continuous process and one with Single process.
Ensure that there are multiple packages on an order, planned through both locations.
}} <!--INSERT TESTS HERE --> {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=On a site configured to Single process, start pallet building and scan a package.
|Result=The package details are displayed. Any suitable pallets are shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Create a new pallet and confirm.
|Result=The device shows a message that the package is on the pallet. The package details are blanked, the pallet is removed and the device is prompting for package again.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan another package.
|Result=The package details are displayed. Any suitable pallets are shown, including the new pallet.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter the new pallet and confirm.
|Result=The device shows a message that the package is on the pallet. The package details are blanked, the pallet is removed and the device is prompting for package again.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=On a site configured to Continuous process, start pallet building and scan a package.
|Result=The package details are displayed. Any suitable pallets are shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Create a new pallet and confirm.
|Result=The device shows a message that the package is on the pallet. The package details are blanked, but the pallet remains. The device is prompting for package again.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Scan another package.
|Result=The device shows a message that the package is on the pallet. The package details are blanked, but the pallet remains. The device is prompting for package again.
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}} 

<!-- MEDIA LANDSCAPE NO --> 
{{Doc_AppendixNew
|Appendix=A
|Estimate=Y
|Glossary=MCS
|Ref1=[[SCR 369080 MCS Scan Printer]]
|RefV1=1.0
|RefDate1=24/01/2020
|REQ=0
|EST=0.25
|FS=1.00
|TS=0.00
|DEV=4.25
|ST=2.00
|IMP=0.50
|PM=0.50
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Julie Scott
|Rev1Title=OBS Project Manager
|Rev2=Paul Kurze
|Rev2Title=Customer Representative
}}</div> 
[[Category:{{#var:Client}} FS]]
[[Category:{{#var:SystemCode}}]]