PATCH C-TMS 11.0 P025: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 92: | Line 92: | ||
|'''Summary of Call'''|| Invoice amendments | |'''Summary of Call'''|| Invoice amendments | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Invoice Amendments | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 106: | Line 106: | ||
|'''Summary of Call'''|| Stairwalker required on orders | |'''Summary of Call'''|| Stairwalker required on orders | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Functionality to allow Stairwalkers to be requested and applied to trips | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 132: | Line 132: | ||
|'''Reporter: ''' || Colin Lowe | |'''Reporter: ''' || Colin Lowe | ||
|- | |- | ||
|'''Summary of Call'''|| Customer standard | |'''Summary of Call'''|| Customer standard instructions | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Default special instructions from a new customer level standard | |'''Detail of Change/Fix''' || Default special instructions from a new customer level standard instructions on new orders. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 160: | Line 160: | ||
|'''Reporter: ''' || Emlyn Phipps | |'''Reporter: ''' || Emlyn Phipps | ||
|- | |- | ||
|'''Summary of Call'''|| RIO:Messages from CTMS to PRL | |'''Summary of Call'''|| RIO: Messages from CTMS to PRL | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Allow PRL to | |'''Detail of Change/Fix''' || Allow PRL to receive and send XML messages to C-TMS | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 174: | Line 174: | ||
|'''Reporter: ''' || Denis Starodubov | |'''Reporter: ''' || Denis Starodubov | ||
|- | |- | ||
|'''Summary of Call'''|| RIO:Suppress | |'''Summary of Call'''|| RIO: Suppress C-TMS resource on LOAD msg | ||
|- | |- | ||
|'''Detail of Change/Fix''' || | |'''Detail of Change/Fix''' || Do not include resource details in XML outbound message based on the value of system parameter | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 190: | Line 190: | ||
|'''Summary of Call'''|| SCR-01 Import Upload of CSV from OTM | |'''Summary of Call'''|| SCR-01 Import Upload of CSV from OTM | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Changes to generic CSV order import (ORD_LINE_ITM) to | |'''Detail of Change/Fix''' || Changes to generic CSV order import (ORD_LINE_ITM) to accommodate the new OTM requirements. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 230: | Line 230: | ||
|'''Reporter: ''' || Hiren Patel | |'''Reporter: ''' || Hiren Patel | ||
|- | |- | ||
|'''Summary of Call'''|| RIO: | |'''Summary of Call'''|| RIO: Require POD Information | ||
|- | |- | ||
|'''Detail of Change/Fix''' || A new EDI process will need to be setup to process the POD_INFO files to be transferred to DHL Link. The FTP Server will need to be setup unless the existing flow for TRIPXML files can be used: this directory structure is used for LOAD, CITD and Electronic Manifest files | |'''Detail of Change/Fix''' || A new EDI process will need to be setup to process the POD_INFO files to be transferred to DHL Link. The FTP Server will need to be setup unless the existing flow for TRIPXML files can be used: this directory structure is used for LOAD, CITD and Electronic Manifest files. | ||
A POD_INFO file will be generated for each order and it will contain its current trip and debrief information with a vertical bar as a fixed delimiter. Note that if multiple signatories have been recorded, e.g. the order has been delivered at different times, these signatories will be listed together. | A new system parameter OMS_CREATE_POD will need to be configured for the appropriate customers of the orders to generate the POD_INFO files. The POD_INFO files will be triggered when the delivered quantity of an order line is changed and the order line has not been zero packed. The delivered quantity will be compared to the despatched, packed or ordered quantity of the order line to assess the status of the order as SUCCESS, FAILED, PART DELIVERED or PART UNDELIVERED. | ||
Note that a status of PRE DELIVERY will be used should a control record be generated and then the delivered quantity be removed. A POD_INFO file will be generated for each order and it will contain its current trip and debrief information with a vertical bar as a fixed delimiter. Note that if multiple signatories have been recorded, e.g. the order has been delivered at different times, these signatories will be listed together. | |||
The EDI process will use the following report values: | The EDI process will use the following report values: | ||
1. | 1. | ||
Title: Process Name | Title: Process Name | ||
Name: P_PROCESS_NAME | Name: P_PROCESS_NAME | ||
Value: POD_INFO | Value: POD_INFO | ||
2. | 2. | ||
Title: Package Name | Title: Package Name | ||
Name: PROCESS | Name: PROCESS | ||
Value: DP_CSV_POD.P_PROCESS_CSV_POD | Value: DP_CSV_POD.P_PROCESS_CSV_POD | ||
Line 261: | Line 269: | ||
|'''Reporter: ''' || Sarah Howells | |'''Reporter: ''' || Sarah Howells | ||
|- | |- | ||
|'''Summary of Call'''|| RIO:LRS Order Cancellation Update | |'''Summary of Call'''|| RIO: LRS Order Cancellation Update | ||
|- | |- | ||
|'''Detail of Change/Fix''' || Send CAN message when booking ref not populated | |'''Detail of Change/Fix''' || Send CAN message when booking ref not populated |