SCR 366598 - MCS Product Changes

Small Change Request (Analysis)
Project/Log Number: PROD / 366598	Date: 28/01/2020
Requested By: Tony Walker	Prepared By: Tony Walker

Change Category (SCE_WMS, CTMS, EPOD, PORTAL, etc): MCS

Describe the Change Being Requested: Add the following functionality: Auto-close pallets on despatch confirm. Debrief all stop types at a location. Allow removal of packages from pallets by scanning the item twice. Auto-remove damaged items from onward trips. Already completed.

Describe the Reason for the Change (new requirement, s/w fix, problem management etc): As follows: Pallets that remain OPEN are suggested for pallet building. If the pallet is no longer physically at that location, the pallet should not be available for pallet building. Trip stops can either be debriefed if they are start-up (SU) or close (CL) stops, unless further functionality is enabled. This existing functionality also changes status, completes other stops, prior trips, etc, so is undesirable when loading/unloading at stops other than the originating depot. For example, shunt trips picking up from multiple depots, external/other depot carrier pickup, etc. There is no way of removing items from a pallet through the device. Damaged items are unlikely to be on-forwarded, and most likely would require re-packaging, re-labelling etc. Therefore the original item should not be suggested for any subsequent receipt or despatch on subsequent trips.

Describe all Alternatives Considered: Alternatives are manual only: Manually close pallets before despatch. Manually debrief stops. Manually remove packages using the CTMS Shipment Pallet screen. Manually remove all damaged items from order before continuing. Given that C-MCS is supposed to help automate the operations that use it, these basic steps should also be automatic.

List Program and Change Summary Required to Implement this Change: As follows: Auto-close pallets on despatch confirm Add a new cost centre-level system parameter "MCS_AUTO_CLOSE_PALLETS", defaulting to "N". Modify existing procedure FN_DESP_CONF. If the new parameter is set, do the following: "N" - nothing "Y" - close the pallet at the point of despatch. Existing procedure FN_UPDATE_PALLET_STATUS does this, and includes a number of checks. This may either be used directly (if the checks are appropriate and have not already been completed as part of procedure FN_DESP_CONF) or a parameter added to remove any already-completed redundant checks from the process. If a new procedure is added, the existing version of the procedure (without the parameter) must be preserved (calling the new version), as this is called from C-MCS directly. Debrief all stop types at a location I.e. without Receipt/Despatch Only flag required to be set. A location flag already exists to control this functionality - "Debrief Stop" - GEO_LOCATION.MCS_DEBRIEF_STOP_TIMES. This needs to be added to the package code. In the C-TMS screen, default this flag to "N". If set to "Y", always debrief all stops found for this location and action (i.e. for Loading, SU/PK, for Despatch, DL/CL). Allow removal of packages from pallets by scanning the item twice Add a new cost centre-level system parameter "MCS_REMOVE_PACKAGE", defaulting to "N" When a package is scanned onto a pallet on which it already exists, an error is returned from the package to say that the item is already on the pallet. If the new system parameter MCS_REMOVE_PACKAGE is set to "Y", MCS should offer the user the choice of removing the package from the pallet. If confirmed, MCS should call DP_MCS_SCANNING.FN_REMOVE_FROM_PALLET, and confirm with the user (if sucessful) that the item has been removed from the pallet. Auto-remove damaged items from onward trips No longer required - already completed.

Describe Risks to be Considered for this Change: Existing operations using C-MCS may be affected by this additional functionality - see Implications section.

Estimate Dev/Test Effort (in days) Needed to Implement this Change: SCR Analysis: 1.0 DEV: 3.0 TEST: 1.5

Describe the Implications to other Customers: Existing operations using C-MCS may be affected by this additional functionality (LFS specifically, but also DHLT/HCR/HC-CHER, TDL). Care must be taken to implement these changes so that, if not configured to do as described above, the application still works in the same way.

Requestor Sign off: Approve Reject Defer

Justification of Approval, Rejection, or Deferral: