TEST: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 60: Line 60:
= CHANGE REQUESTS =
= CHANGE REQUESTS =


== CR REF: ==
== CR REF: AR-A6LBE3 ==
=== Reporter ===
=== Reporter ===
 
Andrew Rowe
=== OBS Log Number ===
=== OBS Log Number ===
333070
=== Summary of request ===
RTB report has zero quantities when failure is at stop level 329671 is a program bug that doesn’t calculate the quantities correctly if multiple failure reasons are captured against a delivery. The fix involves checking the quantities recorded against each reason code.
Log 331450 is a problem with the data coming in from Microlise which was exposed by the fix for 329671; the fixed report looks for the quantity against the failure reason, but Microlise isn’t passing it in.


=== Summary of request ===
There is a solution, which is to amend the interface to check if a zero quantity is passed for a failure reason and assume that the quantity failed is the to-deliver quantity when updating the database. The data on the database will then be right and will appear correctly on the report.


=== Release notes ===
=== Release notes ===
A new system parameter called 'MIC_CALC_REASON_QTY' will need to be set to 'Y' for the appropriate cost centre.
If 'MIC_CALC_REASON_QTY' is 'Y' and the reason code is a type of 'FAILURE' and a non-zero quantity has not been provided, the quantity will be calculated as the despatched quantity of the item multiplied by -1 for a negative adjustment (with the assumption that only one reason code will be provided).
If 'MIC_CALC_REASON_QTY' is 'N', the quantity from the file will be used.


=== Set-up and configuration ===
=== Set-up and configuration ===
Path & Name: MIC_CALC_REASON_QTY
Setting Value: Y
Result: Sets the item reason quantity to the despatched quantity if a reason code is provided with a quantity of 0 instead of an accurate quantity and the type of reason code is ‘FAILURE’


Path & Name: MIC_CALC_REASON_QTY
Setting Value: N
Result: Existing functionality will set the item reason quantity to 0
== CR REF: JB-A3GDS9 ==


== CR REF: ==
=== Reporter ===
=== Reporter ===
Jeremy Brooks
=== OBS Log Number ===
330895
=== Summary of request ===
Review capability to provide web service access into Unison 414 has an MS Access database called DAVE that currently relies on manually run quiz reports. We are looking to replace this with a SQL backend and .net frontend and to remove the manually triggered reports and move to web services , if this is not possible or too expensive then need to understand any other options.


Suggested data required : o    Order line status…. Picker ref/Loader ref…. The intent here is to combine resource info and line detail to facilitate better status updates and productivity visibility.
Order Ref, Product code, Picker ID, Pick volume, Pick completion DTM, Loader ref, Loaded vol, Load completion DTM
=== Release notes ===
Add TEMP_CTRL to TRIP_DETAIL and ORDER_HEADER sections for LOTS records
=== Set-up and configuration ===
No set-up or configuration required
== CR REF: DS-A76DXR ==
=== Reporter ===
Denis Starodubov
=== OBS Log Number ===
=== OBS Log Number ===
333530
=== Summary of request ===
External Carriers pre-advice to be sent via EDI every few hours. At the moment external carriers such as Polarspeed get a pre-advice EDI message sent over every time trip set to En-route in CTMS, however this is end of day procedure at which point sometime it can be too late and therefore deliveries have to be moved to the next day by the carrier. The requirement is to have ability to send an EDI pre-advice (what orders are on the trip) at trip status such as Planned & Tendered utilising existing flows. Also, perhaps this can be manipulated by the carrier and how often the pre-advice sent over by CTMS, so this is fully automated process that can be tailored to our needs and developed as a blanket solution for all external carriers.
Benefits: External carriers get order detail pre-advice messages much sooner or as often as they require. That gives them ability to plan pickup and deliveries on time. This will improve delivery process and should eliminate late deliveries overall.
=== Release notes ==
The following changes will need to be made to the EDI process to produce an electronic manifest, for example:
Triggers:
Type = STATUS
Value = TENDERED (and/or ACCEPTED)
Parameters:
Param = PROCESS_INTERVAL
Value = 60
N.B. Changed to a parameter from a report value in FS.
The electronic manifest will be triggered as at present when the trip is updated to EN-ROUTE.


=== Summary of request ===
The electronic manifest will also be triggered when the trip is updated to a status listed for the EDI trigger and when an order is assigned to, or removed from, a trip that is EN-ROUTE or listed for the EDI trigger.


=== Release notes ===
The EDI parameter for the interval will be used to only send a new electronic manifest when a previous file has been sent for the trip when the interval has elapsed.


The EDI parameter will not be used when the trip is EN-ROUTE so that the external carrier is informed immediately of any changes at that status.
=== Set-up and configuration ===
=== Set-up and configuration ===
No set-up or configuration required




Line 87: Line 153:
= SUPPORT INCIDENTS =
= SUPPORT INCIDENTS =


== Customer Ref: ==
== Customer Ref: INC11247922 ==
=== OBS Log Number ===
=== OBS Log Number ===
 
330656
=== Reporter ===
=== Reporter ===
=== Summary of Call ===
=== Summary of Call ===
 
Inconsistency in the column count, extra column "lifts" in database
=== Detail of Fix ===
=== Detail of Fix ===
 
Change extract to always include lifts
=== Set-up and configuration ===
=== Set-up and configuration ===
A WCS change is required with this call


== Customer Ref: INC11277761 ==


== Customer Ref: ==
=== OBS Log Number ===
=== OBS Log Number ===
 
330751
=== Reporter ===
=== Reporter ===
Suzie Maskery
=== Summary of Call ===
Exports not running correctly
=== Detail of Fix ===
Data fixes to the following three reports for search criteria issues:


=== Summary of Call ===
Outbound Shortage


=== Detail of Fix ===
Receipt Scanning


Driver Scanning
=== Set-up and configuration ===
=== Set-up and configuration ===
An EPOD change is required with this call




= TID CHANGES =
= TID CHANGES =


== OBS Log Number: ==
== OBS Log Number: 331329 ==
 
=== Reporter ===
=== Reporter ===
 
Andy Rowe
=== Summary of Call ===
=== Summary of Call ===
 
Blank pages on BS RTB report
=== Detail of Fix ===
=== Detail of Fix ===
Stop collection orders being selected even when a delivery failure reason code has been used against it.
=== Set-up and configuration ===
No set-up or configuration is required


=== Set-up and configuration ===


== OBS Log Number: 332187 ==


== OBS Log Number: ==
=== Reporter ===
=== Reporter ===
 
Michelle Naumovski
=== Summary of Call ===
=== Summary of Call ===
 
Change to remove job swap validation
=== Detail of Fix ===
=== Detail of Fix ===
 
Add fix to epod functionality to resolve job swapping issues.  This fix relates to both the following logs: 332187 & 332188
=== Set-up and configuration ===
=== Set-up and configuration ===
A WCS change is required with the log




Line 136: Line 213:
= OBSL PRODUCT DEVELOPMENT =
= OBSL PRODUCT DEVELOPMENT =


== OBS Log Number: ==
== OBS Log Number: 334960 ==
 
=== Reporter ===
=== Reporter ===
 
Paul Roscoe
=== Summary of Call ===
=== Summary of Call ===
 
Main version of branched version 334939
=== Detail of Fix ===
=== Detail of Fix ===
This log has been raised to incorporate a branched version for log 334939 into the main version of the database package for export files.
=== Set-up and configuration ===
No set-up or configuration required


=== Set-up and configuration ===




Line 149: Line 229:
== WCS ==
== WCS ==


A WCS change is required for the following logs:
* 330656
* 332187


== EPOD/T2A ==
== EPOD/T2A ==


An EPOD/T2A change is required for the following logs:
* 330751


== MCS ==
== MCS ==


There are no MCS changes required.


== PORTAL/TTM ==
== PORTAL/TTM ==


There are no Portal/TTM changes required.


== EDI ==
== EDI ==
There are no EDI changes required.


</div>
</div>
[[Category:{{#var:Client}} PATCH]]
[[Category:{{#var:Client}} PATCH]]

Revision as of 15:34, 14 June 2016





Aptean Logo.png







OBS Logistics Ltd

Release Notes

CALIDUS TMS

8th May 2016 - 1.0
Reference: P091











































SUMMARY INTRODUCTION

INTRODUCTION

The main aim of this document is to provide CALIDUS TMS 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

C-TMS - Transport 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


TESTING PROCESS

TID'S AND RESOLUTION

If there are any areas of the functionality that are not acceptable or do not meet the requirement specified in the RIO 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

CR REF: AR-A6LBE3

Reporter

Andrew Rowe

OBS Log Number

333070

Summary of request

RTB report has zero quantities when failure is at stop level 329671 is a program bug that doesn’t calculate the quantities correctly if multiple failure reasons are captured against a delivery. The fix involves checking the quantities recorded against each reason code. Log 331450 is a problem with the data coming in from Microlise which was exposed by the fix for 329671; the fixed report looks for the quantity against the failure reason, but Microlise isn’t passing it in.

There is a solution, which is to amend the interface to check if a zero quantity is passed for a failure reason and assume that the quantity failed is the to-deliver quantity when updating the database. The data on the database will then be right and will appear correctly on the report.

Release notes

A new system parameter called 'MIC_CALC_REASON_QTY' will need to be set to 'Y' for the appropriate cost centre.

If 'MIC_CALC_REASON_QTY' is 'Y' and the reason code is a type of 'FAILURE' and a non-zero quantity has not been provided, the quantity will be calculated as the despatched quantity of the item multiplied by -1 for a negative adjustment (with the assumption that only one reason code will be provided).

If 'MIC_CALC_REASON_QTY' is 'N', the quantity from the file will be used.

Set-up and configuration

Path & Name: MIC_CALC_REASON_QTY

Setting Value: Y

Result: Sets the item reason quantity to the despatched quantity if a reason code is provided with a quantity of 0 instead of an accurate quantity and the type of reason code is ‘FAILURE’

Path & Name: MIC_CALC_REASON_QTY

Setting Value: N

Result: Existing functionality will set the item reason quantity to 0


CR REF: JB-A3GDS9

Reporter

Jeremy Brooks

OBS Log Number

330895

Summary of request

Review capability to provide web service access into Unison 414 has an MS Access database called DAVE that currently relies on manually run quiz reports. We are looking to replace this with a SQL backend and .net frontend and to remove the manually triggered reports and move to web services , if this is not possible or too expensive then need to understand any other options.

Suggested data required : o Order line status…. Picker ref/Loader ref…. The intent here is to combine resource info and line detail to facilitate better status updates and productivity visibility.

Order Ref, Product code, Picker ID, Pick volume, Pick completion DTM, Loader ref, Loaded vol, Load completion DTM

Release notes

Add TEMP_CTRL to TRIP_DETAIL and ORDER_HEADER sections for LOTS records

Set-up and configuration

No set-up or configuration required


CR REF: DS-A76DXR

Reporter

Denis Starodubov

OBS Log Number

333530

Summary of request

External Carriers pre-advice to be sent via EDI every few hours. At the moment external carriers such as Polarspeed get a pre-advice EDI message sent over every time trip set to En-route in CTMS, however this is end of day procedure at which point sometime it can be too late and therefore deliveries have to be moved to the next day by the carrier. The requirement is to have ability to send an EDI pre-advice (what orders are on the trip) at trip status such as Planned & Tendered utilising existing flows. Also, perhaps this can be manipulated by the carrier and how often the pre-advice sent over by CTMS, so this is fully automated process that can be tailored to our needs and developed as a blanket solution for all external carriers.

Benefits: External carriers get order detail pre-advice messages much sooner or as often as they require. That gives them ability to plan pickup and deliveries on time. This will improve delivery process and should eliminate late deliveries overall.

= Release notes

The following changes will need to be made to the EDI process to produce an electronic manifest, for example:

Triggers:

Type = STATUS

Value = TENDERED (and/or ACCEPTED)

Parameters:

Param = PROCESS_INTERVAL

Value = 60

N.B. Changed to a parameter from a report value in FS.

The electronic manifest will be triggered as at present when the trip is updated to EN-ROUTE.

The electronic manifest will also be triggered when the trip is updated to a status listed for the EDI trigger and when an order is assigned to, or removed from, a trip that is EN-ROUTE or listed for the EDI trigger.

The EDI parameter for the interval will be used to only send a new electronic manifest when a previous file has been sent for the trip when the interval has elapsed.

The EDI parameter will not be used when the trip is EN-ROUTE so that the external carrier is informed immediately of any changes at that status.

Set-up and configuration

No set-up or configuration required


SUPPORT INCIDENTS

Customer Ref: INC11247922

OBS Log Number

330656

Reporter

Summary of Call

Inconsistency in the column count, extra column "lifts" in database

Detail of Fix

Change extract to always include lifts

Set-up and configuration

A WCS change is required with this call

Customer Ref: INC11277761

OBS Log Number

330751

Reporter

Suzie Maskery

Summary of Call

Exports not running correctly

Detail of Fix

Data fixes to the following three reports for search criteria issues:

Outbound Shortage

Receipt Scanning

Driver Scanning

Set-up and configuration

An EPOD change is required with this call


TID CHANGES

OBS Log Number: 331329

Reporter

Andy Rowe

Summary of Call

Blank pages on BS RTB report

Detail of Fix

Stop collection orders being selected even when a delivery failure reason code has been used against it.

Set-up and configuration

No set-up or configuration is required


OBS Log Number: 332187

Reporter

Michelle Naumovski

Summary of Call

Change to remove job swap validation

Detail of Fix

Add fix to epod functionality to resolve job swapping issues. This fix relates to both the following logs: 332187 & 332188

Set-up and configuration

A WCS change is required with the log


OBSL PRODUCT DEVELOPMENT

OBS Log Number: 334960

Reporter

Paul Roscoe

Summary of Call

Main version of branched version 334939

Detail of Fix

This log has been raised to incorporate a branched version for log 334939 into the main version of the database package for export files.

Set-up and configuration

No set-up or configuration required


Additional Changes

WCS

A WCS change is required for the following logs:

  • 330656
  • 332187

EPOD/T2A

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

  • 330751

MCS

There are no MCS changes required.

PORTAL/TTM

There are no Portal/TTM changes required.

EDI

There are no EDI changes required.


Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=TEST&oldid=3177’