PATCH C-TMS 11.0 P026: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 132: | Line 132: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Integrate with new customer | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The | |'''Detail of Change/Fix''' || The customer carrier will be integrated into C-TMS. The gazetteer import process will need to be setup and imported using the customer format name. Both the Postcode and Service files must be present for a new gazetteer to be imported successfully. The new system parameter CARR_GAZ_POSTCODE_FORMAT will need to store the gazetteer format(s) that provide the postcode without distinction between the outer and inner sections of the postode. The new tab pages, import processes and report will need to be authorised for the appropriate user groups. The customer carrier will need to be configured for its label and manifest formats, and tracking references. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 272: | Line 272: | ||
|'''Reporter: ''' || Jakub Adamski | |'''Reporter: ''' || Jakub Adamski | ||
|- | |- | ||
|'''Summary of Call'''|| RIO:Additional fields to extract suite | |'''Summary of Call'''|| RIO: Additional fields to extract suite | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Changes to ORS to allow reporting on order references | |'''Detail of Change/Fix''' || Changes to ORS to allow reporting on order references | ||
Line 474: | Line 474: | ||
|'''Summary of Call'''|| Scheduling engine changes for SG - NZ | |'''Summary of Call'''|| Scheduling engine changes for SG - NZ | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Changes to network routing for international orders to use cost centre of carrier instead of order. | |'''Detail of Change/Fix''' || Changes to network routing for international orders to use cost centre of carrier instead of order. | ||
Assess the delivery zone of the TRUNK and LINEHAUL routes for when there are multiple valid airport routes and to ensure that orders can be transported to a non-local airport for the delivery depot. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 498: | Line 500: | ||
|width="30%"|'''OBS Log Number:'''|| 345281 | |width="30%"|'''OBS Log Number:'''|| 345281 | ||
|- | |- | ||
|'''Reporter: ''' || | |'''Reporter: ''' || Ian Gaunt | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Indexation factor not being included | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Correct adjusted base cost on Supplier Invoice | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 514: | Line 516: | ||
|'''Reporter: ''' || Daniel Hammond | |'''Reporter: ''' || Daniel Hammond | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Orders unscheduling from collection | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Amendment to Paragon import process for the HCR environment to procedure at the end of the file load that does not leave any paragon orders at sched_coll status. If order is a not a collection from an RDC, i.e. a collection from a BRANCH for a return to a depot then the order is retained on the radial trip. | |'''Detail of Change/Fix''' || Amendment to Paragon import process for the HCR environment to procedure at the end of the file load that does not leave any paragon orders at sched_coll status. If order is a not a collection from an RDC, i.e. a collection from a BRANCH for a return to a depot then the order is retained on the radial trip. | ||
Line 521: | Line 523: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: Jersey Manifest == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 535: | Line 537: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: Jersey Manifest == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 544: | Line 546: | ||
|'''Summary of Call'''|| Jersey Manifest following Invoice run | |'''Summary of Call'''|| Jersey Manifest following Invoice run | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Changes to finance process to allow multiple VAT codes | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 582: | Line 584: | ||
|width="30%"|'''OBS Log Number:'''|| 344482 | |width="30%"|'''OBS Log Number:'''|| 344482 | ||
|- | |- | ||
|'''Reporter: ''' || | |'''Reporter: ''' || Michelle | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Portal Import NOT working | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Remove check on last field as might not be applicable. | |'''Detail of Change/Fix''' || Remove check on last field as might not be applicable. | ||
Line 591: | Line 593: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: LABEL print == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 612: | Line 614: | ||
|'''Reporter: ''' || Michelle | |'''Reporter: ''' || Michelle | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Genesearch outbound query | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Allow audit of FTP send. | |'''Detail of Change/Fix''' || Allow audit of FTP send. | ||
Line 644: | Line 646: | ||
|'''Summary of Call'''|| MSD POD files | |'''Summary of Call'''|| MSD POD files | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Add headers to celesio POD files | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 672: | Line 674: | ||
|'''Summary of Call'''|| CTMS Group Name to LOTS | |'''Summary of Call'''|| CTMS Group Name to LOTS | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Change to Lots message to omit | |'''Detail of Change/Fix''' || Change to Lots message to omit TMS group name | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 698: | Line 700: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Customer Labels | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The | |'''Detail of Change/Fix''' || The customer ID will be set when the files are imported and the latest version will be available for selection when configuring the carrier label format. The manifest and label will display the customer reference of the CTMS order and not the delivery point reference. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 714: | Line 716: | ||
|'''Summary of Call'''|| Paragon re-spin leaving blank drops | |'''Summary of Call'''|| Paragon re-spin leaving blank drops | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Even when the trip in C-TMS already matches the paragon route then still delete any empty stops and update times. | |'''Detail of Change/Fix''' || Even when the trip in C-TMS already matches the paragon route then still delete any empty stops and update times. Empty trips will be deleted when the system parameter PAR_SET_ALL_FROM_NEW is set to Y. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 728: | Line 730: | ||
|'''Summary of Call'''|| DS - APPFUV Auto Scheduling | |'''Summary of Call'''|| DS - APPFUV Auto Scheduling | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Changes to auto scheduling | |'''Detail of Change/Fix''' || Changes to auto scheduling | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 754: | Line 756: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Customer Label DS-ALBGDV | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The customer labels and electronic manifests will be consistent: | |'''Detail of Change/Fix''' || The customer labels and electronic manifests will be consistent: | ||
Weight has been rounded up to the next highest whole number. | Weight has been rounded up to the next highest whole number. | ||
Line 764: | Line 766: | ||
The account postcode is from the originating depot of the order and not the despatching depot should the order be crossdocked. | The account postcode is from the originating depot of the order and not the despatching depot should the order be crossdocked. | ||
The 2D barcode text does not mention customer name. The 2D barcode will contain the same data that is printed on the label. | The 2D barcode text does not mention customer name. The 2D barcode will contain the same data that is printed on the label. | ||
The Customer Express tracking number for the shipment can be based on a 9 or 10 digit number: | The Customer Express tracking number for the shipment can be based on a 9 or 10 digit number: | ||
The tracking number will always be 9 digits left padded with zeroes and with the 10th digit as a check digit. | The tracking number will always be 9 digits left padded with zeroes and with the 10th digit as a check digit. | ||
Line 776: | Line 778: | ||
The changes to the outbound EDI files will only present for electronic manifests for carriers that have a customer specific label format. | The changes to the outbound EDI files will only present for electronic manifests for carriers that have a customer specific label format. | ||
The other files for LOTS, LOAD, CITD, Microlise, etc. will not be changed. | The other files for LOTS, LOAD, CITD, Microlise, etc. will not be changed. | ||
The WEIGHT in the electronic manifest files will not be rounded up at the DU type level because the weights will be subtotalled and rounded up to the next highest whole number by external mapping. | The WEIGHT in the electronic manifest files will not be rounded up at the DU type level because the weights will be subtotalled and rounded up to the next highest whole number by external mapping. | ||
Line 814: | Line 816: | ||
|'''Summary of Call'''|| DS-ANXH4Z | |'''Summary of Call'''|| DS-ANXH4Z | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Change to DU Tracking details in CARR MANF ORS extract | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 826: | Line 828: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Customer 2D barcode | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Update to | |'''Detail of Change/Fix''' || Update to customer label format to fix the 2d barcode | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 842: | Line 844: | ||
|'''Summary of Call'''|| DS-ANXH4Z export data | |'''Summary of Call'''|| DS-ANXH4Z export data | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Use child locations in carr manf extract where required | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 854: | Line 856: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Customer label printing SQL error | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Fix to enable the | |'''Detail of Change/Fix''' || Fix to enable the customer label to work for paragon trips | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 882: | Line 884: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Customer 1D barcode | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Customer 1D barcode additional space fix | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 898: | Line 900: | ||
|'''Summary of Call'''|| DS-ANXH4Z extract | |'''Summary of Call'''|| DS-ANXH4Z extract | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Change to qty calculation on CARR_MANF ORS extract | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 926: | Line 928: | ||
|'''Summary of Call'''|| Resource maintenance - Gazeteer deletion | |'''Summary of Call'''|| Resource maintenance - Gazeteer deletion | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The unused gazetteer versions can be deleted for the different label formats | |'''Detail of Change/Fix''' || The unused gazetteer versions can be deleted for the different label formats. | ||
The current version of the routing data will be obtained from the mapped format should it differ to the label format for the carrier. | |||
This current version will be used to obtain the routing data for the carrier labels and manifest reports. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 996: | Line 1,002: | ||
|'''Summary of Call'''|| TID - Manifest Print formatting fields | |'''Summary of Call'''|| TID - Manifest Print formatting fields | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Correct printed time on report | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,010: | Line 1,016: | ||
|'''Summary of Call'''|| TID - Schedule Engine Issues | |'''Summary of Call'''|| TID - Schedule Engine Issues | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The Home Delivery Network Schedule version of the scheduling engine has been changed to calculate the next available date and time of the order and its early delivery date and time when it reaches its delivery depot based on the 'SCHED_ENG_DELIVERY' system parameters. | |'''Detail of Change/Fix''' || The Home Delivery Network Schedule version of the scheduling engine has been changed to calculate the next available date and time of the order and its early delivery date and time when it reaches its delivery depot based on the 'SCHED_ENG_DELIVERY' system parameters. | ||
The current available date and time of the order will be used in the assessment based on when the order will arrive at the delivery depot. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,024: | Line 1,032: | ||
|'''Summary of Call'''|| TID - Access to SMTP server | |'''Summary of Call'''|| TID - Access to SMTP server | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Remove & characters from message processing package | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,082: | Line 1,090: | ||
|'''Summary of Call'''|| MCS Despatch supress Completion of Trip | |'''Summary of Call'''|| MCS Despatch supress Completion of Trip | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Suppress completion of a trip by MCS based on flags on location | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,106: | Line 1,114: | ||
|'''Summary of Call'''|| Customer Services Portal - CTMS Packages | |'''Summary of Call'''|| Customer Services Portal - CTMS Packages | ||
|- | |- | ||
|'''Detail of Change/Fix''' || New customer services functions and database views. | |'''Detail of Change/Fix''' || New customer services functions and database views. | ||
A new system parameter called ASSEMBLY_DU_TYPE can be configured by cost centre to store a default DU type for assembly. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,118: | Line 1,128: | ||
|'''Summary of Call'''|| Enhanced DPS Integration | |'''Summary of Call'''|| Enhanced DPS Integration | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Changes to PTV Route Optimiser for | |'''Detail of Change/Fix''' || Changes to PTV Route Optimiser for customer including Revenue, Priority and Banned Days. Need to manually configure vehicle types and groups, delivery zones and schedules etc. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,178: | Line 1,188: | ||
|'''Summary of Call'''|| Pallet ID not populating Item Entry | |'''Summary of Call'''|| Pallet ID not populating Item Entry | ||
|- | |- | ||
|'''Detail of Change/Fix''' || The order items for the orders that are created via Portal will be updated to have an identifier and a pallet/asset based on the OMS reference and a count of the number of items. | |'''Detail of Change/Fix''' || The order items for the orders that are created via Portal will be updated to have an identifier and a pallet/asset based on the OMS reference and a count of the number of items. | ||
This functionality will be controlled by the system parameters ORD_CREATE_PORTAL_ITEMS_IDS and EPOD_PREVENT_ASSET_TRACKING when they are both set to Y and active for the cost centre of the order. | |||
The new wide Order Details screen will be used to generate items for the order lines when the system parameter OMS_STD_ITEMS is set to Y and active for the cost centre of the order. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required |