PATCH C-TMS 11.0 P028: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 859: | Line 859: | ||
|} | |} | ||
--> | --> | ||
== OBS Log Number: | |||
== OBS Log Number: 348299 == | |||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
|''' | |width="30%"|'''Reporter: ''' || Tony Walker | ||
|- | |- | ||
|''' | |'''Summary of Call'''|| TID: Import Decodes Carrier Lookup | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Detail of Fix''' || Add a look up to the carrier type decode and prevent a look up when there is not data available | ||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348300 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: TMS Interface Errors screen | |||
|- | |||
|'''Detail of Fix''' || Update interface errors screen to catch errors for returned from executed block | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348303 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: Interface Errors on MAR msg | |||
|- | |||
|'''Detail of Fix''' || Change labels to show correct use of error fields. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 346769 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: Import Decodes fixes | |||
|- | |||
|'''Detail of Fix''' || The WCS_IN import decode type will have a list of values in the Imports Maintenance screen based on the reason codes of type ITEM_NON_CON to validate the entries. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 346772 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: UNLOAD message | |||
|- | |||
|'''Detail of Fix''' || A database script will alter a database table to extend the length of the event type for the TMS-WMS interface control records. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 346777 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: WMS Parameters and Contacts | |||
|- | |||
|'''Detail of Fix''' || New message events for WMS_INT_FAIL for the WMS-TMS interface records. | |||
Message requests can be setup in TMS: | |||
Message type: WMS_INT_FAIL | |||
Medium: SMS or EMAIL | |||
Trigger: ORD, ORDA, ALC, PLIST, LOA, PACK or MAR | |||
Subject: Order Creation, Order Amendment, Allocation, Pick List, Pick Confirmation, Pack Confirmation or Despatch Confirmation | |||
Format: <ERR_MSAGE> (this will insert the error message in the EMAIL or SMS) | |||
Triggers can also be setup for DBAI (database connectivity problems between WMS and TMS) or DBAO (database connectivity problems between TMS and WMS). | |||
Each message trigger is optional. | |||
These message events can be reviewed in the Medium Audit page in the Messaging Maintenance screen where the message events will also be setup in TMS. | |||
The interface records themselves can be reviewed in the TMS-WMS and WMS-TMS pages in the Interface Errors screen as usual. | |||
The owner in WMS can be setup to have an email address per interface message type and these addresses will be used to send emails for failed processes in WMS should they exist. | |||
If they do not exist the equivalent message requests in TMS will be used (excepting database connectivity problems which must be generated out of the processing database). | |||
If email or SMS are not setup a user will not be informed of any problems with the processing of the interface records. | |||
Note that the database connectivity problems will require the message to be setup for MTS_OWNER user to control the message request and the recipients. | |||
For this reason the WMS Params page in the Location Maintenance screen can be used to store the contacts for new 199 (WMS to TMS) and 299 (TMS to WMS) message types. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 346778 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: Booking Reference in TMS | |||
|- | |||
|'''Detail of Fix''' || The booking reference will be updated from TMS to WMS as well as from WMS to TMS. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 346789 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Tony Walker | |||
|- | |||
|'''Summary of Call'''|| TID: PACK message | |||
|- | |||
|'''Detail of Fix''' || Changes have been made to the TMS-WMS interface including: | |||
1. Include parameter DEFAULT_PACKAGE_TYPE for PACK messages when the package type is not known. | |||
2. Include parameter INC_MANDATED_CARRIER to orders to have a mandated carrier from the carrier of the sales order. Uses import decode WMS_CARRIER_MAPPING. | |||
3. Set the actual weight not the planned weight an added item at pick/pack. | |||
4. Set the actual despatched quantity of order lines for pick/pack to then calculate the actual despatched RPE quantity. | |||
5. Only sets the order unpacked order lines to be zero packed if the order has been updated with actual pick containers. | |||
6. An order line with zero planned quantity will be deleted for ORD/ORDA messages. | |||
7. An order line with zero planned and packed quantity will be deleted for LOA messages. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347517 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - SMS reply webservice case sensitive | |||
|- | |||
|'''Detail of Fix''' || Accept sms replies in upper and lower case | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347576 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - CSV Import with commas | |||
|- | |||
|'''Detail of Fix''' || Import orders files will fail the set of data for the advised order reference across the ORDER_AND_LINE and LINE row types should the data be invalid at either level. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347580 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - CSV Import not setting PRECALL | |||
|- | |||
|'''Detail of Fix''' || Change order validation so NOT BOOKED booking status can be changed to PRECALL id appropriate. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347612 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - Schedule Engine - Order Audit | |||
|- | |||
|'''Detail of Fix''' || Changes to prevent additional audit records from being created | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347650 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - release from CS - dates problem | |||
|- | |||
|'''Detail of Fix''' || Only update the delivery windows for Domestic if current windows are a slot. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347653 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - Save in CS generates audit records | |||
|- | |||
|'''Detail of Fix''' || Treat NULL as no change and 0 as delete. Also ensure audit changes only. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347654 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - ORA error from view | |||
|- | |||
|'''Detail of Fix''' || Return maximum values in view when bigger than CAST size. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348000 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID: Labels long customer name | |||
|- | |||
|'''Detail of Fix''' || Ensure labels do not wrap to a second page when name is too long. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348012 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID: PRECALL issue with release / offer | |||
|- | |||
|'''Detail of Fix''' || Add PRECALL status to SMS/EMAIL process | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348056 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID-Additional audit for CS visibility | |||
|- | |||
|'''Detail of Fix''' || Additional auditing for CS | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348072 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Suzanne Woodcock | |||
|- | |||
|'''Summary of Call'''|| TID: Collection failure on multi-trip | |||
|- | |||
|'''Detail of Fix''' || Testing development plus amendments following Daves testing | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348084 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dominic Murphy | |||
|- | |||
|'''Summary of Call'''|| TID: Manifest Barcode size change | |||
|- | |||
|'''Detail of Fix''' || Changed barcorde encoding to enabled scanning | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348143 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID: X-Dock Planning - 1 day rule | |||
|- | |||
|'''Detail of Fix''' || Allow cross dock process to update delivery windows as required for final scheduling | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348158 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID: manual X-Dock Planning-Form Change | |||
|- | |||
|'''Detail of Fix''' || Changes to Manual cross docking to allow dates to be set based on schedules and delivery windows to be updated | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347510 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Paul Jones | |||
|- | |||
|'''Summary of Call'''|| Populate booking_status column (issue) | |||
|- | |||
|'''Detail of Fix''' || Don't set booking status if booking offered messages not active | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347790 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| 405 Messages not being generated. | |||
|- | |||
|'''Detail of Fix''' || Write all outbound Rf messages to msg log. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347862 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| Issues with Label Printing | |||
|- | |||
|'''Detail of Fix''' || Changes to label | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347880 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| Label date is in the past | |||
|- | |||
|'''Detail of Fix''' || The collection/job date for UKMail consignments will be offset by the required number of days: | |||
The greatest value of the new system parameter 'CARR_SRVCE_LEVEL_OFFSET_DAYS' for the cost centre of the order and the carrier service level of the route for the trip. | |||
Note that if the system parameter is not set, a default value of 1 day will be used to compare to the carrier service level. | |||
The calculated collection/job date will be moved backwards to the previous working day of the route. | |||
AAM is expected to set the carrier service level to 0 and the system parameter to 0: the collection/job date will then match the planned trip stop date for their overnight deliveries. | |||
HCR is expected to set the carrier service level to 0 but not set the system parameter and thus use the existing default value of 1 for the system parameter that will not be configured: the collection/job date will then be the previous date to the planned trip stop date for their next day deliveries. | |||
Therefore, not setup changes will be requried for HCR. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347881 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| Issues with HB3 Item Interface | |||
|- | |||
|'''Detail of Fix''' || The 'PROC_ITEM_FIX' import process has been changed to enable dealerships to be identified based on a decoded location when the file is first processed and when the failed file is reprocessed. | |||
The dealership must exist decoded to a location for the order to the identified. The dealership can be stored up to 15 characters in length and decoded to a location up to 12 characters in length. | |||
The OMS reference will be stored for the interface audit file when the order is created or updated successfully when the file is first processed or the file is reprocessed. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347908 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| Planning configure layout no oversize | |||
|- | |||
|'''Detail of Fix''' || Add Oversize to the Order well in the Planning screen | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347910 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| LOTS message trigger/CSV upload | |||
|- | |||
|'''Detail of Fix''' || Prevent updates of the external reference on existing orders which then trigger LOTS messages. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348536 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Dave Meir | |||
|- | |||
|'''Summary of Call'''|| TID - Webservice status return to spec | |||
|- | |||
|'''Detail of Fix''' || Use Trip status for web service calls based on the value of system parameter WS_USE_TRIP_STATUS | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 348282 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Matthew Tipping | |||
|- | |||
|'''Summary of Call'''|| Loading Mgt screen. Hardcoded Trip sheet | |||
|- | |||
|'''Detail of Fix''' || Add additional menu item to print a trip sheet, specified in the TRIP_SHEET system parameter | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== OBS Log Number: 347849 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Reporter: ''' || Paul Roscoe | |||
|- | |||
|'''Summary of Call'''|| Control records for manifests for trips | |||
|- | |||
|'''Detail of Fix''' || A control record for the electronic manifest will be generated for the trip when the first order is assigned to the trip. | |||
Any change of trip status or addition of an order to the trip will then generate a new electronic manifest with any changes. | |||
The file will be generated if the PROCESS_INTERVAL is set to a number of minutes, no minutes or the EDI parameter does not exist (assessed as no minutes). | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |} | ||