PATCH C-TMS P045: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 88: Line 88:
|width="30%"|'''Summary of Call'''|| REF: 19874 - 3PL Scheduling Engine failing with a null stop number
|width="30%"|'''Summary of Call'''|| REF: 19874 - 3PL Scheduling Engine failing with a null stop number
|-
|-
|'''Detail of Fix''' || "1. Any depot that is listed in the system parameter 'AUTO_SCHED_INACTIVE_DEPOTS' will not be processing its orders in the 3PL scheduling engine.
|'''Detail of Fix''' ||
 
1. Any depot that is listed in the system parameter 'AUTO_SCHED_INACTIVE_DEPOTS' will not be processing its orders in the 3PL scheduling engine.
These orders will be marked for manual scheduling and they will have an audit message 'The depot is inactive for scheduling, order cannot be scheduled'.
These orders will be marked for manual scheduling and they will have an audit message 'The depot is inactive for scheduling, order cannot be scheduled'.
   
   
2. If a drop number cannot be derived for the location for the route, then an order for that location will not be scheduled.
2. If a drop number cannot be derived for the location for the route, then an order for that location will not be scheduled.
A default drop number cannot be applied for the position of the trip stop.
A default drop number cannot be applied for the position of the trip stop.
These orders will be marked for manual scheduling and they will have an audit message 'Cannot pre-plan no drop number available'."
These orders will be marked for manual scheduling and they will have an audit message 'Cannot pre-plan no drop number available'.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 126: Line 128:
|width="30%"|'''Summary of Call'''|| REF: 19873 - Failures in STP API orders and 3PL scheduling
|width="30%"|'''Summary of Call'''|| REF: 19873 - Failures in STP API orders and 3PL scheduling
|-
|-
|'''Detail of Fix''' || "The orders are assigned by the 3PL scheduling engine to trip stops based on their activity at those stops.
|'''Detail of Fix''' || The orders are assigned by the 3PL scheduling engine to trip stops based on their activity at those stops.
The orders will be loaded or unloaded at a stop.
The orders will be loaded or unloaded at a stop.


Line 132: Line 134:
Corrected the logic which caused unique constraint violated error.
Corrected the logic which caused unique constraint violated error.


The API for the orders will prevent an attempt to create duplicate locations."
The API for the orders will prevent an attempt to create duplicate locations.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 165: Line 167:
|width="30%"|'''Summary of Call'''|| SCR 13: Add Default Vehicle to Driver
|width="30%"|'''Summary of Call'''|| SCR 13: Add Default Vehicle to Driver
|-
|-
|'''Detail of Fix''' || "A new column is added to RES_PERSON to store Default vehicle ID.
|'''Detail of Fix''' || A new column is added to RES_PERSON to store Default vehicle ID.
The CTMS system is modified to allow the technicians to have a default vehicle.
The CTMS system is modified to allow the technicians to have a default vehicle.


The CTL Call Logging screen will use this information to default the vehicle for the driver, if that driver has no current trip."
The CTL Call Logging screen will use this information to default the vehicle for the driver, if that driver has no current trip.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 190: Line 192:
|width="30%"|'''Summary of Call'''|| Generate Warehouse Charges from Contracts
|width="30%"|'''Summary of Call'''|| Generate Warehouse Charges from Contracts
|-
|-
|'''Detail of Fix''' || "The 'WAREHOUSE' non-standard tariffs will depend on a condition of 'MANUAL' or 'MONTHLY FEE'.
|'''Detail of Fix''' || The 'WAREHOUSE' non-standard tariffs will depend on a condition of 'MANUAL' or 'MONTHLY FEE'.
A 'MANUAL' condition means that the charge will apply only in the 'Warehouse' screen.
A 'MANUAL' condition means that the charge will apply only in the 'Warehouse' screen.
A 'MONTHLY FEE' condition means that the charge will apply only in the monthly generation of the charges."
A 'MONTHLY FEE' condition means that the charge will apply only in the monthly generation of the charges.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 236: Line 238:
|width="30%"|'''Summary of Call'''|| SCR 17: Add Vehicle ODO details to send to Elucid
|width="30%"|'''Summary of Call'''|| SCR 17: Add Vehicle ODO details to send to Elucid
|-
|-
|'''Detail of Fix''' || "This change will change the way that the CTL books jobs for adding taking stock to a technician whilst on a job.
|'''Detail of Fix''' || This change will change the way that the CTL books jobs for adding taking stock to a technician whilst on a job.


Link with SCR-17 & 28 "
Link with SCR-17 & 28
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 249: Line 251:
|width="30%"|'''Summary of Call'''|| SCR: 28 Vehicles Unique per Customer
|width="30%"|'''Summary of Call'''|| SCR: 28 Vehicles Unique per Customer
|-
|-
|'''Detail of Fix''' || "This change will change the way that customer vehicle data is stored. This will now be by customer.
|'''Detail of Fix''' || This change will change the way that customer vehicle data is stored. This will now be by customer.


Link this with SCR-17 – 479895 and SCR-21 – 479896 and SCR- 20 – 467382 and SCR- 16 - 469939"
Link this with SCR-17 – 479895 and SCR-21 – 479896 and SCR- 20 – 467382 and SCR- 16 - 469939
|-
|-
|'''Set-up and Configuration''' ||
|'''Set-up and Configuration''' ||
Line 262: Line 264:
|width="30%"|'''Summary of Call'''|| SCR: 35 Services Supplied at Job Level
|width="30%"|'''Summary of Call'''|| SCR: 35 Services Supplied at Job Level
|-
|-
|'''Detail of Fix''' || "This change will change the way that CTMS stores and generates services supplied.
|'''Detail of Fix''' || This change will change the way that CTMS stores and generates services supplied.
Currently, the EPOD device has been configured to prompt for some services supplied at a vehicle level, as opposed to at the tyre position level (i.e. Installation or Other Work).
Currently, the EPOD device has been configured to prompt for some services supplied at a vehicle level, as opposed to at the tyre position level (i.e. Installation or Other Work).
CTMS will recognise this and add the services supplied from vehicle-level entries."
CTMS will recognise this and add the services supplied from vehicle-level entries.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 330: Line 332:
|width="30%"|'''Summary of Call'''|| Set system parameter CFX_CARRIER so it can be configured at a cost centre level
|width="30%"|'''Summary of Call'''|| Set system parameter CFX_CARRIER so it can be configured at a cost centre level
|-
|-
|'''Detail of Fix''' || "CFX_CARRIER is changed to make it configurable by CARRIER instead of SYSTEM.  The programs using the parameter are also changed accordingly.
|'''Detail of Fix''' || CFX_CARRIER is changed to make it configurable by CARRIER instead of SYSTEM.  The programs using the parameter are also changed accordingly.


User can configure CARRIER level data instead of SYSTEM level."
User can configure CARRIER level data instead of SYSTEM level.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 365: Line 367:
|width="30%"|'''Summary of Call'''|| Report required in ORS for trips. Need to be able to stipulate start location and end location.
|width="30%"|'''Summary of Call'''|| Report required in ORS for trips. Need to be able to stipulate start location and end location.
|-
|-
|'''Detail of Fix''' || "New ORS type has been created called ‘TRIP_LOCS’ which has 5 columns
|'''Detail of Fix''' || New ORS type has been created called ‘TRIP_LOCS’ which has 5 columns


SCHED_NAME - Range - Required
SCHED_NAME - Range - Required
Line 381: Line 383:


User Notes :In order to get unique records, user can use the sort and group_by tick box in the screen.
User Notes :In order to get unique records, user can use the sort and group_by tick box in the screen.
As Load and Unload locations are the selection criteria they can be discarded from the report by not including them, it can be done by unticking the Inc tick box."
As Load and Unload locations are the selection criteria they can be discarded from the report by not including them, it can be done by unticking the Inc tick box.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 403: Line 405:
|width="30%"|'''Summary of Call'''|| Release for DEV-20 for 02592042
|width="30%"|'''Summary of Call'''|| Release for DEV-20 for 02592042
|-
|-
|'''Detail of Fix''' || "CTMS will create the vehicle axles and tyres when the job is completed and create the inspections based on the callout.
|'''Detail of Fix''' || CTMS will create the vehicle axles and tyres when the job is completed and create the inspections based on the callout.
The CTMS part master data will be updated whenever the parts are selected or used in CTMS and EPOD.
The CTMS part master data will be updated whenever the parts are selected or used in CTMS and EPOD.
EDI Jobs creation is needed for the triggers."
EDI Jobs creation is needed for the triggers.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 493: Line 495:
|width="30%"|'''Summary of Call'''|| Update the PARAGON_ID for the main location for a customer
|width="30%"|'''Summary of Call'''|| Update the PARAGON_ID for the main location for a customer
|-
|-
|'''Detail of Fix''' || "The 'PARAGON_ID' for the location can be set when the customer itself is updated without any address information being provided via the customer API.
|'''Detail of Fix''' || The 'PARAGON_ID' for the location can be set when the customer itself is updated without any address information being provided via the customer API.
   
   
This functionality requires the EDI parameter 'UPDATE_PARAGON_ID' to be set to 'Y' for the 'API' process."
This functionality requires the EDI parameter 'UPDATE_PARAGON_ID' to be set to 'Y' for the 'API' process.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 528: Line 530:
|width="30%"|'''Summary of Call'''|| Include decode STOP_TYPE in Trip Waterfall
|width="30%"|'''Summary of Call'''|| Include decode STOP_TYPE in Trip Waterfall
|-
|-
|'''Detail of Fix''' || "The decoded values of 'STOP_TYPE' will be used in the Trip Waterfall screen to replace the codes for the stop types with descriptions, for example, 'Start Up' for 'SU'.
|'''Detail of Fix''' || The decoded values of 'STOP_TYPE' will be used in the Trip Waterfall screen to replace the codes for the stop types with descriptions, for example, 'Start Up' for 'SU'.
The codes will be used by default when the decoded values do not exist."
The codes will be used by default when the decoded values do not exist.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 540: Line 542:
|width="30%"|'''Summary of Call'''|| Amend Trip Locations in Trip Waterfall
|width="30%"|'''Summary of Call'''|| Amend Trip Locations in Trip Waterfall
|-
|-
|'''Detail of Fix''' || "Trip Locations in waterfall is amended to use Location when stop is RDC or town when others.
|'''Detail of Fix''' || Trip Locations in waterfall is amended to use Location when stop is RDC or town when others.


Stop Type is removed from Trip Locations as its already present in Trip Stops."
Stop Type is removed from Trip Locations as its already present in Trip Stops.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
Line 564: Line 566:
|width="30%"|'''Summary of Call'''|| Development for Supporting Documentation
|width="30%"|'''Summary of Call'''|| Development for Supporting Documentation
|-
|-
|'''Detail of Fix''' || "New columns for consumer and carton packaging are added for the Supporting Documentation for the invoicing.
|'''Detail of Fix''' || New columns for consumer and carton packaging are added for the Supporting Documentation for the invoicing.
These documents will include the new columns:
These documents will include the new columns:


Line 590: Line 592:
Cargowise Detail SD6
Cargowise Detail SD6


Payment Details"
Payment Details
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required

Revision as of 15:52, 16 October 2023




Aptean Logo.png










Release Notes

CALIDUS TMS

17th Oct 2023 - 1.0
Reference: P045











































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

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

Log Number: 00478672

Summary of Call REF: 19874 - 3PL Scheduling Engine failing with a null stop number
Detail of Fix

1. Any depot that is listed in the system parameter 'AUTO_SCHED_INACTIVE_DEPOTS' will not be processing its orders in the 3PL scheduling engine. These orders will be marked for manual scheduling and they will have an audit message 'The depot is inactive for scheduling, order cannot be scheduled'.

2. If a drop number cannot be derived for the location for the route, then an order for that location will not be scheduled. A default drop number cannot be applied for the position of the trip stop. These orders will be marked for manual scheduling and they will have an audit message 'Cannot pre-plan no drop number available'.

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


Log Number: 00480177

Summary of Call REF: 19538 - API orders timing out and taking too long to process
Detail of Fix An index has been added to the order import process for the customer reference.
Set-up and Configuration No set-up/configuration required


Log Number: 02595605

Summary of Call Tractor Information for BI
Detail of Fix Scripts prepared for MIS_EXTRACT data to include RES_TRACTOR
Set-up and Configuration No set-up/configuration required


Log Number: 00474273

Summary of Call REF: 19873 - Failures in STP API orders and 3PL scheduling
Detail of Fix The orders are assigned by the 3PL scheduling engine to trip stops based on their activity at those stops.

The orders will be loaded or unloaded at a stop.

DP_CTMS_IMPORT is modified the error message where it said DEP/DEL address cannot be NULL when ext_ref is not found be reported with a better message. Corrected the logic which caused unique constraint violated error.

The API for the orders will prevent an attempt to create duplicate locations.

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


Log Number: 00464750

Summary of Call SCR 05: Show vehicle and technician
Detail of Fix Display driver name in CTL
Set-up and Configuration No set-up/configuration required


Log Number: 00464795

Summary of Call SCR 44: Job Ticket to display a free-text field to add to service report to add "Actual Customer"
Detail of Fix Development to display the 'Actual Customer' in CTL and on the epod pod note.
Set-up and Configuration No set-up/configuration required


Log Number: 02592042

Summary of Call SCR 13: Add Default Vehicle to Driver
Detail of Fix A new column is added to RES_PERSON to store Default vehicle ID.

The CTMS system is modified to allow the technicians to have a default vehicle.

The CTL Call Logging screen will use this information to default the vehicle for the driver, if that driver has no current trip.

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


Log Number: 00479896

Summary of Call SCR 21: Top-Up Transfers
Detail of Fix Development for Top-up transfers. Allows the creation of Top-up transfer orders.
Set-up and Configuration No set-up/configuration required


Log Number: 00477098

Summary of Call Generate Warehouse Charges from Contracts
Detail of Fix The 'WAREHOUSE' non-standard tariffs will depend on a condition of 'MANUAL' or 'MONTHLY FEE'.

A 'MANUAL' condition means that the charge will apply only in the 'Warehouse' screen. A 'MONTHLY FEE' condition means that the charge will apply only in the monthly generation of the charges.

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


Log Number: 00487971

Summary of Call Ref: 20145 - Mismatches in Waterfall Screen
Detail of Fix The orders on the TMP trips for the routes that are being planned by the Paragon API for version STP will be reset to UNSCHEDULED status before they are replanned or not planned.
Set-up and Configuration


Log Number: 00467382

Summary of Call SCR 20: New Vehicle - don't specify type
Detail of Fix CTMS will create the vehicle axles and tyres when the job is completed and create the inspections based on the callout.
Set-up and Configuration No set-up/configuration required


Log Number: 00469939

Summary of Call SCR 16: Allow searching for local tyres when offline.
Detail of Fix The CTMS part master data will be updated whenever the parts are selected or used in CTMS and EPOD.
Set-up and Configuration No set-up/configuration required


Log Number: 00479895

Summary of Call SCR 17: Add Vehicle ODO details to send to Elucid
Detail of Fix This change will change the way that the CTL books jobs for adding taking stock to a technician whilst on a job.

Link with SCR-17 & 28

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


Log Number: 00479887

Summary of Call SCR: 28 Vehicles Unique per Customer
Detail of Fix This change will change the way that customer vehicle data is stored. This will now be by customer.

Link this with SCR-17 – 479895 and SCR-21 – 479896 and SCR- 20 – 467382 and SCR- 16 - 469939

Set-up and Configuration


Log Number: 00479899

Summary of Call SCR: 35 Services Supplied at Job Level
Detail of Fix This change will change the way that CTMS stores and generates services supplied.

Currently, the EPOD device has been configured to prompt for some services supplied at a vehicle level, as opposed to at the tyre position level (i.e. Installation or Other Work). CTMS will recognise this and add the services supplied from vehicle-level entries.

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


Log Number: 00484535

Summary of Call EDI Parameter PREVENT_RESEND_ORDER
Detail of Fix EDI parameter used to prevent rebooked order being sent if the original order has already been sent
Set-up and Configuration No set-up/configuration required


Log Number: 00491708

Summary of Call Release task to for SCR-28 and 17
Detail of Fix Amendments to SCR 17 & 28
Set-up and Configuration No set-up/configuration required


Log Number: 00479894

Summary of Call SCR:42 Outside Stores/Depot Hubs to be used
Detail of Fix This change will change the CTL Call Logging screen to identify the start of the technician’s trip based on their own defined hub location, and to identify the pickup location of the order based on the product selected.
Set-up and Configuration No set-up/configuration required


Log Number: 00479897

Summary of Call SCR: 29 Enter Van Stock
Detail of Fix Change to add new Item types for Van Stock, Fit Other and Services only etc.
Set-up and Configuration


Log Number: 00493457

Summary of Call Release task for additional changes to SCR 28
Detail of Fix Created for re-release of SCR-28 for the issue reported of missing location in RTC which needs a fix in DP_CUST_SERV.pck and DP_EPOD_WEB_SERVICE to update the current_location_id on RTC
Set-up and Configuration No set-up/configuration required


Log Number: 02665941

Summary of Call Set system parameter CFX_CARRIER so it can be configured at a cost centre level
Detail of Fix CFX_CARRIER is changed to make it configurable by CARRIER instead of SYSTEM. The programs using the parameter are also changed accordingly.

User can configure CARRIER level data instead of SYSTEM level.

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


Log Number: 00499175

Summary of Call CTL Top-up transfers
Detail of Fix Release views for ctl Top-up transfers
Set-up and Configuration No set-up/configuration required


Log Number: 00498787

Summary of Call Amendment to TYRE_INSP for SCR-28
Detail of Fix The ORS type TYRE_INSP has been amended to join the tractor specifically to the tractor for the customer of the order at all levels of the report.
Set-up and Configuration No set-up/configuration required


Log Number: 00467514

Summary of Call Report required in ORS for trips. Need to be able to stipulate start location and end location.
Detail of Fix New ORS type has been created called ‘TRIP_LOCS’ which has 5 columns

SCHED_NAME - Range - Required

TRIP_ID

LOAD_LOC - Value - Required

UNLOAD_LOC - Value - Required

ROUTE_CODE


This ORS will give data about all the trips that went between 2 locations.

User Notes :In order to get unique records, user can use the sort and group_by tick box in the screen. As Load and Unload locations are the selection criteria they can be discarded from the report by not including them, it can be done by unticking the Inc tick box.

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


Log Number: 00504598

Summary of Call SCR29 Fix for 479897
Detail of Fix Fix to send ePod collections correctly.
Set-up and Configuration No set-up/configuration required


Log Number: 00497703

Summary of Call Release for DEV-20 for 02592042
Detail of Fix CTMS will create the vehicle axles and tyres when the job is completed and create the inspections based on the callout.

The CTMS part master data will be updated whenever the parts are selected or used in CTMS and EPOD. EDI Jobs creation is needed for the triggers.

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


Log Number: 00495690

Summary of Call WREQ0087544: Finance File Interfaced to Oracle v1.00
Detail of Fix Program change, new fields added to extract
Set-up and Configuration No set-up/configuration required


Log Number: 00512651

Summary of Call The Paragon ID is not updated for the locations via the API
Detail of Fix New EDI parameter called UPDATE_PARAGON_ID is created for API process when set to Y will update the Pargon_ID for geo_location as per the creation of new location.
Set-up and Configuration No set-up/configuration required


Log Number: 00510378

Summary of Call Add all the preferences at the order level to the Trip Waterfall screen
Detail of Fix The preferences in order level is made available for configuration. 10 order status are added to PREFERENCE_STATUS table if not already present before.
Set-up and Configuration No set-up/configuration required


Log Number: 00515979

Summary of Call Ref: 20978: Paragon inactive depots
Detail of Fix The ORD and LOC records will not be sent to Paragon when they are for an inactive depot.
Set-up and Configuration No set-up/configuration required


Log Number: 00481577

Summary of Call Management of the Hub Locations and the Empty Trip Stops
Detail of Fix New functionality added to prevent the deletion of empty stops and depot locations
Set-up and Configuration


Log Number: 00517175

Summary of Call INT_XML_CONTROL
Detail of Fix Add new index to table
Set-up and Configuration No set-up/configuration required


Log Number: 00515770

Summary of Call Audit customers in import
Detail of Fix The customer and order import processes via the API will include a message in the audit log when a process starts and when some data has been extracted.
Set-up and Configuration No set-up/configuration required


Log Number: 00516754

Summary of Call Update the PARAGON_ID for the main location for a customer
Detail of Fix The 'PARAGON_ID' for the location can be set when the customer itself is updated without any address information being provided via the customer API.

This functionality requires the EDI parameter 'UPDATE_PARAGON_ID' to be set to 'Y' for the 'API' process.

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


Log Number: 00507384

Summary of Call Provide authorisation for the required field for the ORS
Detail of Fix Removed the existing Req All and Req None buttons. Created a new function called 'Ors_Edit_Req_field' which can be made accessible by user groups to enable the user to edit the 'Req' field. When an authorized user tries to edit the 'Req' field then a warning will appear to the unauthorised user of the possible consequences and advise the user to confirm the amendment of report with the system manager.
Set-up and Configuration No set-up/configuration required


Log Number: 00517964

Summary of Call Paragon API updates
Detail of Fix The tractor will be updated for an existing trip without restriction based on the end time of the shift.
Set-up and Configuration No set-up/configuration required


Log Number: 00517796

Summary of Call Include decode STOP_TYPE in Trip Waterfall
Detail of Fix The decoded values of 'STOP_TYPE' will be used in the Trip Waterfall screen to replace the codes for the stop types with descriptions, for example, 'Start Up' for 'SU'.

The codes will be used by default when the decoded values do not exist.

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


Log Number: 00518000

Summary of Call Amend Trip Locations in Trip Waterfall
Detail of Fix Trip Locations in waterfall is amended to use Location when stop is RDC or town when others.

Stop Type is removed from Trip Locations as its already present in Trip Stops.

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


Log Number: 00516565

Summary of Call Post Trigger error in Planning
Detail of Fix Delivery_type_id is updated to length 35 in Orders and Planning screen to avoid the POST-QUERY trigger error.
Set-up and Configuration No set-up/configuration required


Log Number: 00492872

Summary of Call Development for Supporting Documentation
Detail of Fix New columns for consumer and carton packaging are added for the Supporting Documentation for the invoicing.

These documents will include the new columns:

Added the 'Pick Qty' to these formats and the export file:

Cargowise Detail SD1

Cargowise Detail SD2

Cargowise Detail SD3

Cargowise Detail SD5

Cargowise Detail SD6

Payment Details


Added the 'Consumable Charges' to these formats and the export file:

Cargowise Detail SD1

Cargowise Detail SD2

Cargowise Detail SD6

Payment Details

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


Log Number: 00346696

Summary of Call Inspection Required Issue
Detail of Fix Updated f_last_inspection function to set a default date when it is NULL.
Set-up and Configuration No set-up/configuration required


Log Number: 00521650

Summary of Call Additional changes for 492872 - Development for Supporting Documentation
Detail of Fix PAYMENT_DTLS export type has been modified to display SCREENING Charge as last column with corresponding value which was missing in previous version.
Set-up and Configuration No set-up/configuration required


Log Number: 00516019

Summary of Call Update Paragon keys
Detail of Fix Keys updated with correct dates and master key values
Set-up and Configuration No set-up/configuration required


Log Number: 00501535

Summary of Call Include auditing for Paragon API
Detail of Fix Added auditing to packages to know what’s been sent to paragon through API and also when the RUN_NUMBER is changed.
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


PRODUCT DEVELOPMENT

Log Number: 00474454

Summary of Call Missing auditing for COL export events in the API
Detail of Fix The web service audit records will be created for the COL events as well as the VLI, VLD and VUI events.
Set-up and Configuration No set-up/configuration required


Log Number: 00489063

Summary of Call Revert tier for pallet storage
Detail of Fix The tier for the 'Warehouse' screen will revert to 'WAREHOUSE'.
Set-up and Configuration No set-up/configuration required


Log Number: 00482059

Summary of Call Enable RET orders to be added to PCL trips in the 3PL scheduling engine
Detail of Fix Code change - changed the DP_3PL-SCHED package to allow RET orders to be added to PCL trips
Set-up and Configuration No set-up/configuration required


Log Number: 00489611

Summary of Call Duplication with TMS Orders
Detail of Fix Any orders that are locked will not be submitted to the 3PL scheduling engine until they have been unlocked.
Set-up and Configuration No set-up/configuration required


Log Number: 00481867

Summary of Call Include the Send to Paragon flag in the import process for Fixed Routes
Detail of Fix Send To Paragon flag added to Import

Any new order lines should trigger an update to the Paragon API when the order is UNSCHEDULED not INVALID.

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


Log Number: 00497948

Summary of Call Main version for DP_CARRIER_API
Detail of Fix Changes from branched version incorporated into main version

The functionality that is controlled by the system parameter 'CARRIER_API_MANIFEST_READY_TIME': setting it to a time will allow the bookingDate to refer to the packed date or the created date of the order instead of the late delivery date.

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_C-TMS_P045&oldid=10853’