PATCH C-TMS 11.0 P021: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
Line 1,328: | Line 1,328: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 334812 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,335: | Line 1,335: | ||
|'''Reporter: ''' || Julie Scott | |'''Reporter: ''' || Julie Scott | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Re-book Functionality | ||
|- | |- | ||
|'''Detail of Fix''' || Alternate rebook functionality | |'''Detail of Fix''' || Alternate rebook functionality. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
Line 1,351: | Line 1,351: | ||
|'''Summary of Call'''|| Scheduling orders | |'''Summary of Call'''|| Scheduling orders | ||
|- | |- | ||
|'''Detail of Fix''' || If business type planning is active, the trip will only be created if the payment can be created if there is not a missing charge condition, for example. If business type planning is not active, the trip will be created if it is not being debriefed and there is not a missing chargeable condition, for example. If the missing chargeable condition is a TRACTOR or a TRAILER TYPE, the audit message will include the text: | |'''Detail of Fix''' || If business type planning is active, the trip will only be created if the payment can be created if there is not a missing charge condition, for example. | ||
If business type planning is not active, the trip will be created if it is not being debriefed and there is not a missing chargeable condition, for example. | |||
If the missing chargeable condition is a TRACTOR or a TRAILER TYPE, the audit message will include the text: | |||
'a CHARGE does not include the TRACTOR,' or 'a CHARGE does not include the TRAILER TYPE,'. | |||
The audit message will apply to the charges for the orders and the trips but it will only be displayed once if a total cost cannot be obtained. | |||
If there are multiple charges that are available for the parties, each individual charge will not be listed to ensure that the error message can be displayed on screen. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335395 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,370: | Line 1,380: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335421 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,383: | Line 1,393: | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335422 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,415: | Line 1,423: | ||
9. EX_ORDITEM | 9. EX_ORDITEM | ||
The database scripts will only be effective in | The database scripts will only be effective in specific databases. | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335560 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,428: | Line 1,435: | ||
|'''Reporter: ''' || MICHELLE NAUMOVSKI | |'''Reporter: ''' || MICHELLE NAUMOVSKI | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Showing CUST CLIENT CODES and shouldn't | ||
|- | |- | ||
|'''Detail of Fix''' || 1) Show correct LOV options for customer client code relevant to the customer on the order. | |'''Detail of Fix''' || 1) Show correct LOV options for customer client code relevant to the customer on the order. | ||
Line 1,437: | Line 1,444: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335576 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,449: | Line 1,456: | ||
If the new system parameter does not exist or it is set to 'N' then multiple files will be generated whenever the actual arrival or actual departure time is updated for the trip stop. | If the new system parameter does not exist or it is set to 'N' then multiple files will be generated whenever the actual arrival or actual departure time is updated for the trip stop. | ||
|- | |- | ||
|'''Set-up and Configuration''' || | |'''Set-up and Configuration''' || | ||
|} | |} | ||
<table border="1px" width="100%"> | |||
<tr> | |||
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td> | |||
</tr> | |||
<tr> | |||
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Result'''</font></td> | |||
</tr> | |||
<tr> | |||
<td>LOTS_PREVENT_MULTI_VLI_VUI</td> | |||
<td>SYSTEM</td> | |||
<td>Y</td> | |||
<td>The 'VLI' and 'VUI' files for LOTS/Portal will only be re-sent for an order on a trip should either of the actual arrival or actual departure times be set for the first time for the trip stop. A file can be sent twice for the same order on the same trip but only of the actual times are set separately. | |||
</td> | |||
</tr> | |||
<tr> | |||
<td>LOTS_PREVENT_MULTI_VLI_VUI</td> | |||
<td>SYSTEM</td> | |||
<td>N</td> | |||
<td>Multiple files will be generated whenever the actual arrival or actual departure time is updated for the trip stop.</td> | |||
</tr> | |||
</table> | |||
== Customer Ref: | == Customer Ref: 335694 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,466: | Line 1,501: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335799 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,489: | Line 1,524: | ||
|'''Summary of Call'''|| Automated Manifest at end of day (rwk) | |'''Summary of Call'''|| Automated Manifest at end of day (rwk) | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Reset sysdate parameters | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335903 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,509: | Line 1,543: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335913 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,518: | Line 1,552: | ||
|'''Summary of Call'''|| Segregate NZ & AUS trips while x docking | |'''Summary of Call'''|| Segregate NZ & AUS trips while x docking | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Amendment to Trip screen to remove the debug message and segregate the trips a user may select at cross dock | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 335924 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,537: | Line 1,571: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336145 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,546: | Line 1,580: | ||
|'''Summary of Call'''|| Add cost centre to Invoicing report (ORS) | |'''Summary of Call'''|| Add cost centre to Invoicing report (ORS) | ||
|- | |- | ||
|'''Detail of Fix''' || | |'''Detail of Fix''' || Segregate by cost centre | ||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336158 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,565: | Line 1,599: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336296 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,579: | Line 1,613: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336374 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,593: | Line 1,627: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336552 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,600: | Line 1,634: | ||
|'''Reporter: ''' || Julie Scott | |'''Reporter: ''' || Julie Scott | ||
|- | |- | ||
|'''Summary of Call'''|| | |'''Summary of Call'''|| Supporting Docs fail to ftp | ||
|- | |- | ||
|'''Detail of Fix''' || Fix parameters on FTP call for Supporting documents. | |'''Detail of Fix''' || Fix parameters on FTP call for Supporting documents. | ||
Line 1,607: | Line 1,641: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336580 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,621: | Line 1,655: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 336671 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,715: | Line 1,749: | ||
|'''Summary of Call'''|| Microlise Events files - failed by C-TMS | |'''Summary of Call'''|| Microlise Events files - failed by C-TMS | ||
|- | |- | ||
|'''Detail of Fix''' || New system parameter MIC_DIRECT_UPDATE_PRIORITY to control the population of actual arrival and delivery dates. Use new fields journeyDropRef to get stop sequence, and latitude and longitude to populate arrival and departure long and lat. | |'''Detail of Fix''' || New system parameter MIC_DIRECT_UPDATE_PRIORITY to control the population of actual arrival and delivery dates. | ||
Use new fields journeyDropRef to get stop sequence, and latitude and longitude to populate arrival and departure long and lat. | |||
|- | |- | ||
|'''Set-up and Configuration''' || | |'''Set-up and Configuration''' || | ||
|} | |} | ||
<table border="1px" width="100%"> | |||
<tr> | |||
<td colspan="4" bgcolor="silver"><font size="2">'''New Parameters'''</font></td> | |||
</tr> | |||
<tr> | |||
<td bgcolor="silver"><font size="2">'''Parameter Name'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Config Level'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td> | |||
<td bgcolor="silver"><font size="2">'''Result'''</font></td> | |||
</tr> | |||
<tr> | |||
<td>MIC_DIRECT_UPDATE_PRIORITY</td> | |||
<td>NSS</td> | |||
<td>MEP</td> | |||
<td>Indicates priority of population of Actual Deliver and Arrival. | |||
M - Manual | |||
E - EventExport | |||
P - PODPOC | |||
So using this order, if date populated by PODPOC message, and an EventExport message recieved with different date, the date will be over written. | |||
However, if the date was keyed in manually, it will not be overwritten</td> | |||
</tr> | |||
</table> | |||
== Customer Ref: INC14705705 == | == Customer Ref: INC14705705 == | ||
{| width="100%" | {| width="100%" | ||
Line 1,769: | Line 1,833: | ||
|'''Reporter: ''' || Graham Rothwell | |'''Reporter: ''' || Graham Rothwell | ||
|- | |- | ||
|'''Summary of Call'''|| Portal/ | |'''Summary of Call'''|| Portal/C-TMS error | ||
|- | |- | ||
|'''Detail of Fix''' || Always get schedule from trip for LOTS messages | |'''Detail of Fix''' || Always get schedule from trip for LOTS messages | ||
Line 1,790: | Line 1,854: | ||
|} | |} | ||
== Customer Ref: | == Customer Ref: 337184 == | ||
{| width="100%" | {| width="100%" | ||
|- | |- | ||
Line 1,855: | Line 1,919: | ||
|'''Summary of Call'''|| OOH SYD DAILY P/U Scheduling Query | |'''Summary of Call'''|| OOH SYD DAILY P/U Scheduling Query | ||
|- | |- | ||
|'''Detail of Fix''' || The scheduling engine has been changed to handle exceptional errors that invalidate the savepoints and thus do not rollback the data for orders that have been partially scheduled. The orders will then not be at SCHED_COLL status. The audit records will indicate that the order has been unsuccessfully scheduled. If an order is partially scheduled and it cannot be rolled back successfully, the order will remain at status SCHED_COLL but an appropriate audit record will be created for reference. The exceptional error is being triggered by a process external to the scheduling engine so the scheduling engine has been changed to account for such failures to ensure that the orders are reset if possible. | |'''Detail of Fix''' || The scheduling engine has been changed to handle exceptional errors that invalidate the savepoints and thus do not rollback the data for orders that have been partially scheduled. | ||
The orders will then not be at SCHED_COLL status. | |||
The audit records will indicate that the order has been unsuccessfully scheduled. | |||
If an order is partially scheduled and it cannot be rolled back successfully, the order will remain at status SCHED_COLL but an appropriate audit record will be created for reference. | |||
The exceptional error is being triggered by a process external to the scheduling engine so the scheduling engine has been changed to account for such failures to ensure that the orders are reset if possible. | |||
|- | |- | ||
|'''Set-up and Configuration''' || No set-up/configuration required | |'''Set-up and Configuration''' || No set-up/configuration required |