PATCH C-TMS P043: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 225: | Line 225: | ||
|width="30%"|'''Summary of Call'''|| Export Work Type | |width="30%"|'''Summary of Call'''|| Export Work Type | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || EPL_DIRECTION is based on the work type for the order item. | ||
It will be R for Removal or I for Installation. | It will be R for Removal or I for Installation. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 237: | Line 237: | ||
|width="30%"|'''Summary of Call'''|| Order Item Reason Codes | |width="30%"|'''Summary of Call'''|| Order Item Reason Codes | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Trip stops will be updated with actual times for a service job as well as a collection job or a delivery job. | ||
Order lines and items will be maintained for the deliveries and services. | Order lines and items will be maintained for the deliveries and services. | ||
The format 'OMS-SEQ' will be used for new items with the next sequence number being obtained for that format. | The format 'OMS-SEQ' will be used for new items with the next sequence number being obtained for that format. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 285: | Line 285: | ||
|width="30%"|'''Summary of Call'''|| Update fails into Elucid from CTMS | |width="30%"|'''Summary of Call'''|| Update fails into Elucid from CTMS | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || A new EDI parameter called 'SEND_DEL_TYPE_CODE' can be set to 'Y' to send the code for the delivery type as 'TMS_DELIVERY_TYPE'. | ||
The EDI parameter 'DEL_ALL_ACT_QTY' can be used to assess the delivered quantities for the order items. | The EDI parameter 'DEL_ALL_ACT_QTY' can be used to assess the delivered quantities for the order items. | ||
Line 295: | Line 295: | ||
An appropriate message will be generated for when a 'DEL' message cannot be sent with respect to those parameters. | An appropriate message will be generated for when a 'DEL' message cannot be sent with respect to those parameters. | ||
Auditing has been reinstated for trip and order events. | Auditing has been reinstated for trip and order events. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 306: | Line 306: | ||
|width="30%"|'''Summary of Call'''|| The CAN messages are being re-sent. | |width="30%"|'''Summary of Call'''|| The CAN messages are being re-sent. | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || 'CAN' messages will be sent once. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 328: | Line 328: | ||
|width="30%"|'''Summary of Call'''|| Convert CTL items to format OMS-SEQ to match EPOD item | |width="30%"|'''Summary of Call'''|| Convert CTL items to format OMS-SEQ to match EPOD item | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || A new system parameter called 'OMS_SEQ_CTL_ITEM_FORMAT' will be used to identify the format of the order items when they are created in CTL. | ||
The format 'OMS-SEQ' will be used when the system parameter is 'Y'. | The format 'OMS-SEQ' will be used when the system parameter is 'Y'. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 341: | Line 341: | ||
|width="30%"|'''Summary of Call'''|| EPOD Services and Prices | |width="30%"|'''Summary of Call'''|| EPOD Services and Prices | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Removed default start and end times of '00' to send to EPOD. | ||
Sends price to EPOD with a default value of 0.00. | Sends price to EPOD with a default value of 0.00. | ||
Line 362: | Line 362: | ||
Uses default DU type and product type for new order lines for products from EPOD. | Uses default DU type and product type for new order lines for products from EPOD. | ||
Creates services based on the delivery type and the vehicle type for CALLOUT orders. | Creates services based on the delivery type and the vehicle type for CALLOUT orders. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 373: | Line 373: | ||
|width="30%"|'''Summary of Call'''|| Secure FTP | |width="30%"|'''Summary of Call'''|| Secure FTP | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Code has been added to the package DP_INT_XML_MIC2 to enable SFTP in TMSDEV, able to do SFTP now. | ||
A record will need to be added as a known host in the database to enable SFTP. | A record will need to be added as a known host in the database to enable SFTP. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 397: | Line 397: | ||
|width="30%"|'''Summary of Call'''|| Inbound Scanning Loose Items | |width="30%"|'''Summary of Call'''|| Inbound Scanning Loose Items | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The order items can be reused on later orders once they have been scanned through cross-docking. | ||
Checks whether the scanned item exists on the same order on which it was planned before checking to see if the item has been seen in the network before - these items can be scanned on their current planned orders. | Checks whether the scanned item exists on the same order on which it was planned before checking to see if the item has been seen in the network before - these items can be scanned on their current planned orders. | ||
If the item has been scanned on a different order, checks if the item is found to have been through the network on other orders | If the item has been scanned on a different order, checks if the item is found to have been through the network on other orders. These items cannot be scanned. | ||
If the item is only planned onto one other order, the item will be moved from that order to the order indicated by the scan as normal. | If the item is only planned onto one other order, the item will be moved from that order to the order indicated by the scan as normal. | ||
This validation will apply to the 831 and 835 messages from WCS, the standard and the faster scanning processes will include this validation. | This validation will apply to the 831 and 835 messages from WCS, the standard and the faster scanning processes will include this validation. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 438: | Line 438: | ||
|width="30%"|'''Summary of Call'''|| LFE Carrier Change | |width="30%"|'''Summary of Call'''|| LFE Carrier Change | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Service levels will be decoded using 'CARRIER_API_SERVICE_LEVEL' for the carrier of the trip and they will be added to the Carrier API message. | ||
A new system parameter called 'CARRIER_API_MANIFEST_READY_TIME' for the system will be used to set the cut-off time in format 'HH24:MI' to assess the ready times. | A new system parameter called 'CARRIER_API_MANIFEST_READY_TIME' for the system will be used to set the cut-off time in format 'HH24:MI' to assess the ready times. | ||
Line 444: | Line 444: | ||
A default value of '18:00' will be used should the system parameter not be set or if it is set with an invalid format for the time. | A default value of '18:00' will be used should the system parameter not be set or if it is set with an invalid format for the time. | ||
The Ready Time will be adjusted to account for the cut-off time when the order is packed in advance of the delivery date of the order. | The Ready Time will be adjusted to account for the cut-off time when the order is packed in advance of the delivery date of the order. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 521: | Line 521: | ||
|width="30%"|'''Summary of Call'''|| On inspection update | |width="30%"|'''Summary of Call'''|| On inspection update | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Added EPL_WORK_COMPLETE for the service status. | ||
The service status is C when there is no action or the work is complete, otherwise it is P. | The service status is C when there is no action or the work is complete, otherwise it is P. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 544: | Line 544: | ||
|width="30%"|'''Summary of Call'''|| Amend driver shift patterns screen | |width="30%"|'''Summary of Call'''|| Amend driver shift patterns screen | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Adding new shift manually instead of via display shifts. | ||
Default database parameters such as depot in the detail screen. | Default database parameters such as depot in the detail screen. | ||
Update message 'all drivers' should read 'all selected drivers'. | |||
Update message 'all drivers' should read 'all selected drivers'. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 557: | Line 559: | ||
|width="30%"|'''Summary of Call'''|| Failure Notifications for Customer Imports | |width="30%"|'''Summary of Call'''|| Failure Notifications for Customer Imports | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Reports separately these items for the API customer import from Elucid: | ||
RecipientAddress | RecipientAddress | ||
RecipientCompany | RecipientCompany | ||
InvoiceCompany | |||
InvoiceCompany | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 594: | Line 598: | ||
|width="30%"|'''Summary of Call'''|| LOTS Installation for Customer Imports | |width="30%"|'''Summary of Call'''|| LOTS Installation for Customer Imports | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The customers will be stored with a LOTS customer based on the buyer from Elucid when LOTS is active when the EDI parameter CUST_LOTS_ID is Y. | ||
The customers will be stored with a LOTS customer based on the customer in the standard import process when LOTS is active when the EDI parameter CUST_LOTS_ID is Y. | The customers will be stored with a LOTS customer based on the customer in the standard import process when LOTS is active when the EDI parameter CUST_LOTS_ID is Y. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 607: | Line 611: | ||
|width="30%"|'''Summary of Call'''|| Order Auditing | |width="30%"|'''Summary of Call'''|| Order Auditing | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The auditing is not being triggered by CTL orders. | ||
The booking process has been changed to perform the auditing instead to create the vehicle record for the order. | The booking process has been changed to perform the auditing instead to create the vehicle record for the order. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 620: | Line 624: | ||
|width="30%"|'''Summary of Call'''|| Service Report | |width="30%"|'''Summary of Call'''|| Service Report | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The EPL_OFFICE_INSTRUCTIONS item in the EPOD_JOB section is included when the order on the trip has an order to action. | ||
order to action. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 643: | Line 646: | ||
|width="30%"|'''Summary of Call'''|| Number of tyres | |width="30%"|'''Summary of Call'''|| Number of tyres | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The order line quantity will be incremented or decremented when the quantities for the order items is added or adjusted. | ||
These quantities will be for the ordered quantity or the despatched quantity as appropriate. | These quantities will be for the ordered quantity or the despatched quantity as appropriate. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 700: | Line 703: | ||
|width="30%"|'''Summary of Call'''|| Cross Dock Scanning | |width="30%"|'''Summary of Call'''|| Cross Dock Scanning | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Added new EDI_PROCESS for customer, which calls the new function - fn_load_trunks to avoid ford scanning. | ||
Setup: | Setup: | ||
Create a new EDI Process for that particular customer along with its cost center. | Create a new EDI Process for that particular customer along with its cost center. | ||
Add the function (TRM.fn_load_trunks) in the report values and run the EDI process every 5 minutes. | |||
Add the function (TRM.fn_load_trunks) in the report values and run the EDI process every 5 minutes. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 781: | Line 785: | ||
|width="30%"|'''Summary of Call'''|| Change for fleet inspections for EPOD | |width="30%"|'''Summary of Call'''|| Change for fleet inspections for EPOD | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Services are only sent to EPOD for a CALLOUT. | ||
Customer vehicles are only stored as order vehicles for a CALLOUT. | |||
Customer vehicles are only stored as order vehicles for a CALLOUT. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 793: | Line 798: | ||
|width="30%"|'''Summary of Call'''|| Order with tyre value of 0 | |width="30%"|'''Summary of Call'''|| Order with tyre value of 0 | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Does not update DELIVERED or FAILED orders to be ON-HOLD, when an order is validated when the customer account is on hold. | ||
Does not update ON-HOLD, DELIVERED or FAILED orders to be SCHEDULED or UNSCHEDULED when a service is added to the order. | |||
Does not update ON-HOLD, DELIVERED or FAILED orders to be SCHEDULED or UNSCHEDULED when a service is added to the order. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 816: | Line 822: | ||
|width="30%"|'''Summary of Call'''|| Change to addresses | |width="30%"|'''Summary of Call'''|| Change to addresses | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Includes an EPOD_CUSTOMER_INVOICE section within the EPOD_CUSTOMER section in the EPOD_JOB SECTION for the service jobs when the new system parameter called EPOD_CUSTOMER_INVOICE is set to Y. | ||
For release with issue 301 for EPOD. | For release with issue 301 for EPOD. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 840: | Line 846: | ||
|width="30%"|'''Summary of Call'''|| Trips showing as Part Delivered | |width="30%"|'''Summary of Call'''|| Trips showing as Part Delivered | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The new order items will be created with a planned quantity and a despatched quantity to match the advised delivered quantity. | ||
These items will be for vehicles that have been inspected and that have had parts supplied | These items will be for vehicles that have been inspected and that have had parts supplied | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 913: | Line 919: | ||
|width="30%"|'''Summary of Call'''|| Driver not being sent to ePOD | |width="30%"|'''Summary of Call'''|| Driver not being sent to ePOD | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || System parameter EPOD_SEND_DRIVER can be set to N to send the EPL_USER_ID as a null value instead of the driver's username. | ||
A default value of Y will apply to continue to send the driver's username. | A default value of Y will apply to continue to send the driver's username. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 926: | Line 932: | ||
|width="30%"|'''Summary of Call'''|| Callout orders not getting sent to ePOD | |width="30%"|'''Summary of Call'''|| Callout orders not getting sent to ePOD | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Applied NVL to the fields EPL_PRODUCT_QTY_CASE and EPL_MILEAGE so that if the values are blank it'll update to 0. | ||
EPL_SIZE will be assessed as a character not a number. | EPL_SIZE will be assessed as a character not a number. | ||
Added the trip ID to the audit log for exceptional error handling. | Added the trip ID to the audit log for exceptional error handling. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 963: | Line 969: | ||
|width="30%"|'''Summary of Call'''|| API Customer Import Amendments for Elucid | |width="30%"|'''Summary of Call'''|| API Customer Import Amendments for Elucid | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Amendments to the customer import for Elucid including: | ||
1. Using the Buyer for the location for the MAIN address | 1. Using the Buyer for the location for the MAIN address | ||
2. Creating an account for a new customer. | 2. Creating an account for a new customer. | ||
3. Inserting or updating customers, locations and contacts. | |||
3. Inserting or updating customers, locations and contacts. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 978: | Line 986: | ||
|width="30%"|'''Summary of Call'''|| API Customer Import - Exceptional Error Handling for Elucid | |width="30%"|'''Summary of Call'''|| API Customer Import - Exceptional Error Handling for Elucid | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The customer group name will be truncated to 35 characters but the customer name will remain at 50 characters. | ||
Locations for customers and customer groups will available to use. | Locations for customers and customer groups will available to use. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,002: | Line 1,010: | ||
|width="30%"|'''Summary of Call'''|| ORS failing in CTL | |width="30%"|'''Summary of Call'''|| ORS failing in CTL | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Changed the datatype of the field t_det_sel to CLOB to mitigate the error in the package. Added storage limit exception to the form and package. So, the user is advised to use limited records to produce the report. Added a new parameter to the CTL procedure DP_REPORT.P_GEN_ORS_SQL_CTL to display the err_msg in CTL. It needs to be tested in CTL as it involves the procedure DP_REPORT.P_GEN_ORS_SQL_CTL. | ||
Also, modified the code to mitigate the string concatenation too long error. | Also, modified the code to mitigate the string concatenation too long error. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,026: | Line 1,034: | ||
|width="30%"|'''Summary of Call'''|| Invalid order lines preventing trips moving to ACCEPTED status | |width="30%"|'''Summary of Call'''|| Invalid order lines preventing trips moving to ACCEPTED status | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || A new system parameter called 'WCS_RETAIN_EMPTY_LINES' can be set to 'Y' to retain any empty order lines that have been created after their items have been deleted during the order confirmation process. | ||
These order lines will not have a despatched quantity. | These order lines will not have a despatched quantity. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,072: | Line 1,080: | ||
|width="30%"|'''Summary of Call'''|| Changes containing trunk version of DP_EPOD_WEB_SERVICE | |width="30%"|'''Summary of Call'''|| Changes containing trunk version of DP_EPOD_WEB_SERVICE | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Phase 2 of webfleet integration including free text message requires, working hours request, drive card message, incorrect address, incorrect contact, next delivery. | ||
Delete orders not finished in overnight job, move future trips to the correct schedule. | Delete orders not finished in overnight job, move future trips to the correct schedule. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,095: | Line 1,103: | ||
|width="30%"|'''Summary of Call'''|| Additional Changes to Planning and Waterfall screen | |width="30%"|'''Summary of Call'''|| Additional Changes to Planning and Waterfall screen | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Changes to Planning and Waterfall screen and allocate resources | ||
2 new parameters SHOW_CARRIER_NAME and ALLOC_RESOURCE to be set to Y | 2 new parameters SHOW_CARRIER_NAME and ALLOC_RESOURCE to be set to Y | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,108: | Line 1,116: | ||
|width="30%"|'''Summary of Call'''|| Additional Changes Part 2 | |width="30%"|'''Summary of Call'''|| Additional Changes Part 2 | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Part 2 of additional changes. Parameter CANCEL_STATUS_CHK must be set to Y | ||
Parameter CANCEL_STATUS_CHK must be set to Y | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,181: | Line 1,188: | ||
|width="30%"|'''Summary of Call'''|| Trip audit missing items | |width="30%"|'''Summary of Call'''|| Trip audit missing items | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The update of the following information for the trip will be audited separately: | ||
Owning Depot | Owning Depot | ||
Line 1,191: | Line 1,198: | ||
Seal Number | Seal Number | ||
Note that the 'Tractor ID' may be set to 'SUB-CONTRACT' when the 'Sub Contractor' box is ticked for the trip. | Note that the 'Tractor ID' may be set to 'SUB-CONTRACT' when the 'Sub Contractor' box is ticked for the trip. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,246: | Line 1,253: | ||
|width="30%"|'''Summary of Call'''|| Payments - Currency Code not set | |width="30%"|'''Summary of Call'''|| Payments - Currency Code not set | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || A new function is available in CTMS: | ||
The currency code will be returned to set for the Portal order that is being entered. | The currency code will be returned to set for the Portal order that is being entered. | ||
This currency code will be present to calculate the payments when the order is scheduled. | This currency code will be present to calculate the payments when the order is scheduled. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,283: | Line 1,290: | ||
|width="30%"|'''Summary of Call'''|| Orders not consolidating on stops | |width="30%"|'''Summary of Call'''|| Orders not consolidating on stops | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Customers that do not allow consolidated orders on delivery trips will assess overlapping available order time windows for their trip stops. | ||
A new system parameter called 'TRM_CONSOL_ORDER_AFTER_XDOCK' can be set to 'Y' if the customers do not want to assess these available order time windows against the other orders on the loading trip stop when the order has been collected previously. | A new system parameter called 'TRM_CONSOL_ORDER_AFTER_XDOCK' can be set to 'Y' if the customers do not want to assess these available order time windows against the other orders on the loading trip stop when the order has been collected previously. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,296: | Line 1,303: | ||
|width="30%"|'''Summary of Call'''|| Customer Upload bug | |width="30%"|'''Summary of Call'''|| Customer Upload bug | ||
|- | |- | ||
|'''Detail of Fix''' || Call Logging changes for booking releases, Issue 6 changes etc | |'''Detail of Fix''' || Call Logging changes for booking releases, Issue 6 changes etc. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,318: | Line 1,325: | ||
|width="30%"|'''Summary of Call'''|| Batch Order creation, Order reference does not enable Alpha entry on numeric | |width="30%"|'''Summary of Call'''|| Batch Order creation, Order reference does not enable Alpha entry on numeric | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Modified the package OMS.create_order_from_template to mitigate the numeric conversion error which is restricting the user from creating orders in the ORDER TEMPLATE screen. | ||
This change also contains the solution for case 02160908. | This change also contains the solution for case 02160908. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,352: | Line 1,359: | ||
|width="30%"|'''Summary of Call'''|| Warehouse screen | |width="30%"|'''Summary of Call'''|| Warehouse screen | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The ad-hoc services will be stored as a payment and then it can be updated. | ||
The payments, bulk packaging and services will be audited as they are created and updated. | The payments, bulk packaging and services will be audited as they are created and updated. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,398: | Line 1,405: | ||
|width="30%"|'''Summary of Call'''|| CFX inbound interface incorrect | |width="30%"|'''Summary of Call'''|| CFX inbound interface incorrect | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The PLANNED and TENDERED trips will be updated to ACCEPTED. | ||
An audit message will be created should the trip status fail to update. | An audit message will be created should the trip status fail to update. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,476: | Line 1,483: | ||
|width="30%"|'''Summary of Call'''|| Cty Vehicle view | |width="30%"|'''Summary of Call'''|| Cty Vehicle view | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Added location name and axle config description. | ||
CTL release required alongside CTMS release | CTL release required alongside CTMS release | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,505: | Line 1,512: | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
|width="30%"|'''Summary of Call'''|| Review inactive flags that are not being referenced | |width="30%"|'''Summary of Call'''|| Review inactive flags that are not being referenced - delivery type-service level | ||
|- | |- | ||
|'''Detail of Fix''' || Inactive flag has been reviewed to make it consistent throughout the database for DEL_TYPE and SERVICE_LEVEL | |'''Detail of Fix''' || Inactive flag has been reviewed to make it consistent throughout the database for DEL_TYPE and SERVICE_LEVEL | ||
Line 1,529: | Line 1,536: | ||
|width="30%"|'''Summary of Call'''|| Wait for API response | |width="30%"|'''Summary of Call'''|| Wait for API response | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || A new EDI parameter should be set up to enable to wait for a response or 'send and forget'. | ||
EDI parameter called SEND_AND_FORGET should be set up for process name API, which when set to Y, it will stop waiting for response and vice versa. | |||
EDI parameter called SEND_AND_FORGET should be set up for process name API, which when set to Y, it will stop waiting for response and vice versa. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,541: | Line 1,549: | ||
|width="30%"|'''Summary of Call'''|| Temperature violation during trip validation | |width="30%"|'''Summary of Call'''|| Temperature violation during trip validation | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || The error message regarding temperature violation during trip validation was noted for the case 322452. | ||
There is a query (actually more than one) that will not find a record and issue this error message but it can never select a record without the trailer being known. | There is a query (actually more than one) that will not find a record and issue this error message but it can never select a record without the trailer being known. | ||
In that sense change is made to display this error message only when trailer type is known and if not then it should be suppressed. | In that sense change is made to display this error message only when trailer type is known and if not then it should be suppressed. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,555: | Line 1,564: | ||
|width="30%"|'''Summary of Call'''|| Wallet File | |width="30%"|'''Summary of Call'''|| Wallet File | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || https has to be used in 19c databases – change is to use the wallet file. | ||
Changed https calls to include system parameters called HTTPS_WALLET_FILE and HTTPS_PASSWORD for secure call. | Changed https calls to include system parameters called HTTPS_WALLET_FILE and HTTPS_PASSWORD for secure call. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required |