PATCH CTMS 11.0 P029: Difference between revisions

From Calidus HUB
VisualWikitext
(Created page with "<div class="noprint"> {{#vardefine:Client|OBS}} {{#vardefine:ClientName|OBS Logistics Ltd}} {{#vardefine:System|''CALIDUS'' WMS}} {{#vardefine:Doc_Title|Release Notes}} {{#vardef...")
 
No edit summary
Line 178: Line 178:
|}
|}
-->
-->
== OBS Log Number: ==
 
== OBS Log Number: 348304 ==
{| width="100%"
{| width="100%"
|-
|width="30%"| '''Reporter:''' ||
|-
|-
|'''Summary of Call'''||  
|width="30%"|'''Summary of Call'''|| TID: MAR/PACK to set Asset Id
|-
|-
|'''Detail of Fix''' ||
|'''Detail of Fix''' || Set pallet id when creating order items
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 348301 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| ORD Message - no weight
|-
|'''Detail of Fix''' || Pack message wipes out the planned weight, ensure the line weight is not removed if it has been populated
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 348405 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Relay emails via client server.
|-
|'''Detail of Fix''' || Add Login Credentials for Email
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 348245 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| PRECALL Issue with release
|-
|'''Detail of Fix''' || Retain booking status on orders
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 349914 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Issue with resource allocation
|-
|'''Detail of Fix''' || Correct issue with drivers available times
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350258 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TomTom WEBFLEET: Data not sent
|-
|'''Detail of Fix''' || Change from using trailer to tractor as more generic.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350198 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Issue with directs
|-
|'''Detail of Fix''' || Allow directs to be sent to PTV based on group name.
|-
|'''Set-up and Configuration''' ||
|}
 
 
<table border="1px" width="100%">
<tr>
<td colspan="3" bgcolor="silver"><font size="2">'''Registry/Rules Settings'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Path &amp; Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>PTV_RO_GROUP_NAME</td>
<td>'N'</td>
<td>Flag to indicate that unscheduled orders are to be selected by group name</td>
</tr>
 
</table>
 
 
== OBS Log Number: 350364 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| PTV Route Optimiser Import Issues
|-
|'''Detail of Fix''' || Half file upload error count when using pairs. Also fix trip schedule.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== OBS Log Number: 350414 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| PTV RO: Plan opening times over midnight
|-
|'''Detail of Fix''' || Set second opening and closing times when over midnight.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350197 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Issue with breaks and Off Duty
|-
|'''Detail of Fix''' || Correct layover time on trip stops
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350476 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TMS/WMS Interface STD Pallet Qty Error
|-
|'''Detail of Fix''' || Standard pallet qty calculation fix
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350332 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Error on Orders Screen
|-
|'''Detail of Fix''' || Changes to the Orders screen to prevent an error occuring in the fast screen when the system tries to update the packing quantity on the order line.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== OBS Log Number: 350632 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TMS / WCS Loading
|-
|'''Detail of Fix''' || The WMS-TMS interface will set the current location of the order items when the corresponding sales order is pick confirmed and/or pack confirmed.
 
The current location will be obtained from the bay number of the despatching trip or by default from the WMS parameters called DEFAULT_BAY_LOCATION.
 
This default parameter will need to be created for the despatching depot with a valid grid location that is known as a WCS location.
|-
|'''Set-up and Configuration''' ||
|}
 
 
<table border="1px" width="100%">
<tr>
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>DEFAULT_BAY_LOCATION</td>
<td>WMS Interface</td>
<td>A WCS ‘grid’ location</td>
<td>This default location will be used for the current location of the order items when they are created via the ‘MAR’ and ‘PACK’ messages in the WMS-TMS interface should the despatching trip not have a bay location.</td>
</tr>
 
<tr>
<td>DEFAULT_BAY_LOCATION</td>
<td>WMS Interface</td>
<td>NULL</td>
<td>No default value will be available.</td>
</tr>
</table>
 
 
== OBS Log Number: 350657 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| WMS-TMS Interface Current Item Location
|-
|'''Detail of Fix''' || The transport order items need to trigger a 441 message for WCS when they are created via the WMS-TMS interface as well as when they are updated with a new trip despatch bay location.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350467 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Planning Screen trip filter
|-
|'''Detail of Fix''' || Add trip prefix to trip filters, and shift code to PTV RO planning
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350849 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Despatch bay trigger in multi-depots
|-
|'''Detail of Fix''' || The current location of the order items will be updated to the despatch bay for the trip as advised for loading. 
 
WCS will be informed in which depot the loading will occur, the latest trip in a depot that contains the despatch bay will be used.
 
The latest trip being a trip that has not been given an actual departure time from the depot.
 
This is to ensure that the depot is identified should the order be cross-docked through multiple depots and the same despatch bays are being used in those depots.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 350847 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Order Interface
|-
|'''Detail of Fix''' || Based on system parameter GEO_TOMTOM_SEND_CUST_REF customer ref will be sent instead of delivery type
|-
|'''Set-up and Configuration''' ||
|}
 
 
<table border="1px" width="100%">
<tr>
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>GE0_TOMTOM_SEND_CUST_REF</td>
<td>SYSTEM</td>
<td>Y</td>
<td>Send customer ref not delivery type ID to TomTom</td>
</tr>
 
</table>
 
== OBS Log Number: 350942 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TOMTOM - Set to EN-ROUTE status
|-
|'''Detail of Fix''' || Set trips to En-ROUTE from ACCEPTED via TomTom based on system parameter GEO_TOMTOM_TRIP_EN-ROUTE
|-
|'''Set-up and Configuration''' ||
|}
 
 
<table border="1px" width="100%">
<tr>
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>GEO_TOMTOM_TRIP_EN-ROUTE</td>
<td>SYSTEM</td>
<td>Y/N</td>
<td>Will change trip status from ACCEPTED to EN-ROUTE via TomTom</td>
</tr>
 
</table>
 
 
== OBS Log Number: 351038 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| WMS-TMS interface collection times
|-
|'''Detail of Fix''' || This new logic for the transport orders via the WMS-TMS interface from the sales orders will be based on a new WMS parameter called APPLY_COLL_OFFSET being set to Y in the despatching depot/warehouse in TMS.
 
This WMS parameter can be set for the ORD/ORDA message type 101 in the Locations maintenance screen for the depot (it is not required at the customer level because the schedule rules will be created at the customer level).
|-
|'''Set-up and Configuration''' ||
|}
 
 
<table border="1px" width="100%">
<tr>
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>APPLY_COLL_OFFSET</td>
<td>Location WMS Parameter</td>
<td>Y</td>
<td>The collection/available time windows for the transport order will be based on schedule rules should they exist for the cost centre, customer, service level and location zones.
The location zones will be based on the delivery locations for the customer groups in WMS.
The delivery date of the corresponding sales order will be used to assess when the collection date will be.
</td>
</tr>
 
<tr>
<td>APPLY_COLL_OFFSET</td>
<td>Location WMS Parameter</td>
<td>N</td>
<td>The collection/available time windows for the transport order will be based on the booking date of the corresponding sales order.</td>
</tr>
 
</table>
 
 
== OBS Log Number: 351388 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Hold MAR order messages when exclude r/l
|-
|'''Detail of Fix''' || Assesses the presence of a storage location on the picking containers for MAR messages by route/load as well as by sales order and for packs.
 
Control records by sales order will be placed on hold if they are missing, a later control record by route/load will then omit the sales orders with missing storage locations and process the ones that do have them.
 
Control records by sales order will be actioned if they are not missing and there is a later control record by route/load that will then process the sales order.
 
The WCS despatch bay locations for the marshalling racking will be created automatically for the marshalling racking as well as the marshalling location for the MAR and PACK messages.
 
The WMS Status in the Planning screen will display the date and time when the status was last updated.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 351440 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Enable the 441 message to delete items
|-
|'''Detail of Fix''' || Transport order items that are deleted after they have sent a 441 message to WCS as a loading request will send a new 441 message to WCS to delete the previous request.
 
The WMS-TMS interface will not delete any transport order items that have been updated as successfully loaded at the depot with a reason code of SL, UL, OL or ML.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== OBS Log Number: 351922 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| WMS-TMS interface staying at PROCESSING
|-
|'''Detail of Fix''' || If an exceptional error occurs during processing the record status of the control record will be updated to FAILURE from PROCESSING and the control record will need to be reprocessed after the error message has been reviewed.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
|}


Revision as of 16:29, 22 August 2018





Aptean Logo.png







OBS Logistics Ltd

Release Notes

CALIDUS WMS

8th May 2016 - 1.0
Reference: PPatch without the P e.g. 091











































SUMMARY INTRODUCTION

INTRODUCTION

The main aim of this document is to provide CALIDUS WMS users with the level of detail required to accurately test all software included in the patch. The document also contains set-up and configuration details to enable the user to configure the system correctly for the new functionality to work.


GLOSSARY OF TERMS

Term Meaning
C-TMS Transport Management System
C-WMS Warehouse Management System
CR Change Request
C-WCS Warehouse Control System
C-ePOD Electronic Proof of Delivery
C-MCS Mobile Control System
C-TTM Track and Trace Management
EDI Electronic Data Interchange
TID Testing Issue Development, or Log


TESTING PROCESS

TIDs AND RESOLUTION

If there are any areas of the functionality that are not acceptable or do not meet the requirement specified in the Change Request then these should be expressed by raising a TID.


FINAL 'END TO END' TESTING

Prior to release to a production database, a full 'End to End' test is required on the test system by all sites using the database. Once this is signed off, a release date can be arranged.


AUTHORISATION

Authorisation from nominated release personnel only will be required when requesting a release to a production environment


CHANGE REQUESTS

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required


SUPPORT INCIDENTS

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required


TID CHANGES

OBS Log Number:

Cust Ref: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration


OBSL PRODUCT DEVELOPMENT

OBS Log Number: 348304

Summary of Call TID: MAR/PACK to set Asset Id
Detail of Fix Set pallet id when creating order items
Set-up and Configuration No set-up/configuration required


OBS Log Number: 348301

Summary of Call ORD Message - no weight
Detail of Fix Pack message wipes out the planned weight, ensure the line weight is not removed if it has been populated
Set-up and Configuration No set-up/configuration required


OBS Log Number: 348405

Summary of Call Relay emails via client server.
Detail of Fix Add Login Credentials for Email
Set-up and Configuration No set-up/configuration required


OBS Log Number: 348245

Summary of Call PRECALL Issue with release
Detail of Fix Retain booking status on orders
Set-up and Configuration No set-up/configuration required


OBS Log Number: 349914

Summary of Call Issue with resource allocation
Detail of Fix Correct issue with drivers available times
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350258

Summary of Call TomTom WEBFLEET: Data not sent
Detail of Fix Change from using trailer to tractor as more generic.
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350198

Summary of Call Issue with directs
Detail of Fix Allow directs to be sent to PTV based on group name.
Set-up and Configuration


Registry/Rules Settings
Path & Name Setting Value Result
PTV_RO_GROUP_NAME 'N' Flag to indicate that unscheduled orders are to be selected by group name


OBS Log Number: 350364

Summary of Call PTV Route Optimiser Import Issues
Detail of Fix Half file upload error count when using pairs. Also fix trip schedule.
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350414

Summary of Call PTV RO: Plan opening times over midnight
Detail of Fix Set second opening and closing times when over midnight.
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350197

Summary of Call Issue with breaks and Off Duty
Detail of Fix Correct layover time on trip stops
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350476

Summary of Call TMS/WMS Interface STD Pallet Qty Error
Detail of Fix Standard pallet qty calculation fix
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350332

Summary of Call Error on Orders Screen
Detail of Fix Changes to the Orders screen to prevent an error occuring in the fast screen when the system tries to update the packing quantity on the order line.
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350632

Summary of Call TMS / WCS Loading
Detail of Fix The WMS-TMS interface will set the current location of the order items when the corresponding sales order is pick confirmed and/or pack confirmed.

The current location will be obtained from the bay number of the despatching trip or by default from the WMS parameters called DEFAULT_BAY_LOCATION.

This default parameter will need to be created for the despatching depot with a valid grid location that is known as a WCS location.

Set-up and Configuration


New Parameters
Parameter Name Config Level Setting Value Result
DEFAULT_BAY_LOCATION WMS Interface A WCS ‘grid’ location This default location will be used for the current location of the order items when they are created via the ‘MAR’ and ‘PACK’ messages in the WMS-TMS interface should the despatching trip not have a bay location.
DEFAULT_BAY_LOCATION WMS Interface NULL No default value will be available.


OBS Log Number: 350657

Summary of Call WMS-TMS Interface Current Item Location
Detail of Fix The transport order items need to trigger a 441 message for WCS when they are created via the WMS-TMS interface as well as when they are updated with a new trip despatch bay location.
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350467

Summary of Call Planning Screen trip filter
Detail of Fix Add trip prefix to trip filters, and shift code to PTV RO planning
Set-up and Configuration No set-up/configuration required


OBS Log Number: 350849

Summary of Call Despatch bay trigger in multi-depots
Detail of Fix The current location of the order items will be updated to the despatch bay for the trip as advised for loading.

WCS will be informed in which depot the loading will occur, the latest trip in a depot that contains the despatch bay will be used.

The latest trip being a trip that has not been given an actual departure time from the depot.

This is to ensure that the depot is identified should the order be cross-docked through multiple depots and the same despatch bays are being used in those depots.

Set-up and Configuration No set-up/configuration required


OBS Log Number: 350847

Summary of Call Order Interface
Detail of Fix Based on system parameter GEO_TOMTOM_SEND_CUST_REF customer ref will be sent instead of delivery type
Set-up and Configuration


New Parameters
Parameter Name Config Level Setting Value Result
GE0_TOMTOM_SEND_CUST_REF SYSTEM Y Send customer ref not delivery type ID to TomTom


OBS Log Number: 350942

Summary of Call TOMTOM - Set to EN-ROUTE status
Detail of Fix Set trips to En-ROUTE from ACCEPTED via TomTom based on system parameter GEO_TOMTOM_TRIP_EN-ROUTE
Set-up and Configuration


New Parameters
Parameter Name Config Level Setting Value Result
GEO_TOMTOM_TRIP_EN-ROUTE SYSTEM Y/N Will change trip status from ACCEPTED to EN-ROUTE via TomTom


OBS Log Number: 351038

Summary of Call WMS-TMS interface collection times
Detail of Fix This new logic for the transport orders via the WMS-TMS interface from the sales orders will be based on a new WMS parameter called APPLY_COLL_OFFSET being set to Y in the despatching depot/warehouse in TMS.

This WMS parameter can be set for the ORD/ORDA message type 101 in the Locations maintenance screen for the depot (it is not required at the customer level because the schedule rules will be created at the customer level).

Set-up and Configuration


New Parameters
Parameter Name Config Level Setting Value Result
APPLY_COLL_OFFSET Location WMS Parameter Y The collection/available time windows for the transport order will be based on schedule rules should they exist for the cost centre, customer, service level and location zones.

The location zones will be based on the delivery locations for the customer groups in WMS. The delivery date of the corresponding sales order will be used to assess when the collection date will be.

APPLY_COLL_OFFSET Location WMS Parameter N The collection/available time windows for the transport order will be based on the booking date of the corresponding sales order.


OBS Log Number: 351388

Summary of Call Hold MAR order messages when exclude r/l
Detail of Fix Assesses the presence of a storage location on the picking containers for MAR messages by route/load as well as by sales order and for packs.

Control records by sales order will be placed on hold if they are missing, a later control record by route/load will then omit the sales orders with missing storage locations and process the ones that do have them.

Control records by sales order will be actioned if they are not missing and there is a later control record by route/load that will then process the sales order.

The WCS despatch bay locations for the marshalling racking will be created automatically for the marshalling racking as well as the marshalling location for the MAR and PACK messages.

The WMS Status in the Planning screen will display the date and time when the status was last updated.

Set-up and Configuration No set-up/configuration required


OBS Log Number: 351440

Summary of Call Enable the 441 message to delete items
Detail of Fix Transport order items that are deleted after they have sent a 441 message to WCS as a loading request will send a new 441 message to WCS to delete the previous request.

The WMS-TMS interface will not delete any transport order items that have been updated as successfully loaded at the depot with a reason code of SL, UL, OL or ML.

Set-up and Configuration No set-up/configuration required


OBS Log Number: 351922

Summary of Call WMS-TMS interface staying at PROCESSING
Detail of Fix If an exceptional error occurs during processing the record status of the control record will be updated to FAILURE from PROCESSING and the control record will need to be reprocessed after the error message has been reviewed.
Set-up and Configuration No set-up/configuration required


MODULES DELIVERED

Module Name Version No Description Log Number


ADDITIONAL CHANGES

WCS

A WCS change is required for the following logs:

  • Log

OR

There are no WCS changes required.

EPOD/T2A

An ePOD/T2A change is required for the following logs:

  • Log

OR

There are no ePOD/T2A changes required.

MCS

An MCS change is required for the following logs:

  • Log

OR

There are no MCS changes required.

PORTAL/TTM

A Portal change is required for the following logs:

  • Log

OR

There are no Portal changes required.

EDI

An EDI change is required for the following logs:

  • Log

OR

There are no EDI changes required.


Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=PATCH_CTMS_11.0_P029&oldid=6295’