PATCH C-TMS P041: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 184: | Line 184: | ||
= | = BUGS = | ||
<!-- | <!-- | ||
== OBS Log Number: == | == OBS Log Number: == | ||
Line 198: | Line 198: | ||
|} | |} | ||
--> | --> | ||
== | |||
{| width="100%" | |||
|- | == Log Number: 00246275 == | ||
|width="30%"|''' | {| width="100%" | ||
|- | |- | ||
|'''Summary of Call'''|| | |width="30%"|'''Summary of Call'''|| TMS Error codes not informative | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Added validation to all numeric datatypes for Inbound EDI orders | ||
|- | |- | ||
|'''Set-up and Configuration''' || | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Log Number: 00248627 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Report invalid file formats for inbound EDI files | |||
|- | |||
|'''Detail of Fix''' || The files with invalid formats are reported and are then moved to Failed directory. | |||
Added validation to the Fields 'LENGTH, WIDTH, HEIGHT' wrt case 00246275. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01833551 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Invoicing is slow to complete | |||
|- | |||
|'''Detail of Fix''' || The new system parameter ‘INV_ACT_PMNTS_DAYS’ can be used to specify a number of days prior to the period end date or the current date to assess the payments for the next invoice. | |||
For example, 31 days may be specified to reduce the number of payments to assess for the next invoice. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01839826 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Invoices not generated | |||
|- | |||
|'''Detail of Fix''' || The new system parameter INV_SET_PERIOD can be set to Y to enable the invoice to have default values for the period based on the current date and to generate multiple invoices per day for the same accounts. | |||
If this system parameter is not set to Y, the invoices will calculate the period for the invoice based on the previous invoice. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01832615 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Missing data from Tablet solution | |||
|- | |||
|'''Detail of Fix''' || Comments will be added for the reason codes other than 'SC' to indicate the actual departure date and time and the user name for a collection. | |||
Comments will be added for the reason code 'SC' to indicate the actual departure date and time and the user name for a collection. | |||
Comments will be added for the reason code 'SD' to indicate the planned arrival date and time and the user name for an automatic delivery. | |||
Trips and orders will be updated as delivered when assets are scanned for collection and the carrier requires auto-debriefing of deliveries. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01841755 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| ORS Report - not using timezones | |||
|- | |||
|'''Detail of Fix''' || A database script is created to amend EX_ORDHEAD, to modify the dates to use Local time zones for CHANGED_DATE, POD_DATE and PACKED_DATE | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 00246967 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| End session dropping it early session | |||
|- | |||
|'''Detail of Fix''' || The Three forms TRIPSUM, TRIP_PLAN, and PLANNING are modified so that the trip stops will be found for the matching Load and Unload locations and the planned times for the stops and the orders. Any empty stops then will be assessed and used only when they match the planned times, the functionality depends on this system parameter 'UPDATE_ORDERS_TO_TRIP' set to 'Y' for NHSBT. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01834724 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Two trips having the same consignment | |||
|- | |||
|'''Detail of Fix''' || A new system parameter 'WCS_SPLIT_ORDER_BY_TRIP' can be set to 'Y' to allow an order to be split when its items are loaded on different trips for delivery. | |||
Multiple new orders then will be used to store the items as they are loaded on separate trips for delivery. | |||
The same new order will be used when this system parameter is set to 'N' to retain the existing functionality. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01784809 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Orders not rating for account ACC when landing in C-TMS | |||
|- | |||
|'''Detail of Fix''' || Consolidated payments can be created by DU category or DU Type for the order revenue. | |||
Orders can be consolidated and rated when not all their DU categories or DU Types require rating. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01924442 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Web service orders | |||
|- | |||
|'''Detail of Fix''' || Amendments for the web service orders: | |||
1. Writes to EPOD_WEB_SERVICE_AUDIT using an autonomous function | |||
2. Writes to EPOD_WEB_SERVICE_AUDIT at the start with a status of REC for the received message - ACK and NAK will also be stored later | |||
3. Excluded CANCELLED orders from the queries | |||
4. Included NOWAIT on FOR UPDATE in one place | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01896927 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Incorrect POD data | |||
|- | |||
|'''Detail of Fix''' || The EDI parameter 'ALLOW_INCREMENT_DSPD' will control if an order can include further despatches from a 'DSPD' message. | |||
The default value will be 'N'. | |||
If this parameter is 'Y', the order can be incremented with further despatch information. | |||
If this parameter is 'N', the order can be updated with despatch information. | |||
This parameter will only be active for orders that have not been packed to generate carrier labels. | |||
Orders that have not been packed or that have been updated manually only with packed and despatched quantities can be incremented or updated as per the value of the parameter. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01910732 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Paragon import failing | |||
|- | |||
|'''Detail of Fix''' || The Paragon import process includes extra auditing for clearer analysis of the problem. | |||
If an order fails to be added to a radial trip, the attempt will be reversed and the user will be informed in the audit message. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 01932657 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| Order Import for NRHEAVY_Order_Import | |||
|- | |||
|'''Detail of Fix''' || Sequence number updated correctly | |||
The format of the child locations will be validated before a new location is created with a new address for the customer for the imported order. | |||
For example, the next location will be 'LONDON/01450' when exists 'LONDON/01449' as the highest sequential number for that 12-character format. | |||
'LONDON/147' will be excluded from that formatting should it exist. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||
== Log Number: 00251450 == | |||
{| width="100%" | |||
|- | |||
|width="30%"|'''Summary of Call'''|| WMS Params do not show in Location Maintenance for the first location that is found | |||
|- | |||
|'''Detail of Fix''' || The WMS Params records will be getting display whenever a location has any parameters. | |||
|- | |||
|'''Set-up and Configuration''' || No set-up/configuration required | |||
|} | |||