PATCH C-TMS P046: Difference between revisions

From Calidus HUB
VisualWikitext
(Created page with "<div class="noprint"> {{#vardefine:ClientName|<br />}} {{#vardefine:System|''CALIDUS'' TMS}} {{#vardefine:Doc_Title|Release Notes}} {{#vardefine:Version|1.0}} {{#vardefine:Date|5...")
 
m (Text replacement - "<!-- TOC --> ↵<div class="noprint">" to "<!-- TOC --> ")
 
(27 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<div class="noprint">
<div class="noprint">
{{#vardefine:ClientName|<br />}}
{{#vardefine:Client|CTMS}}
{{#vardefine:System|''CALIDUS'' TMS}}
{{#vardefine:System|''CALIDUS'' TMS}}
{{#vardefine:Doc_Title|Release Notes}}
{{#vardefine:Doc_Title|Release Notes}}
Line 18: Line 18:
}}
}}
<!-- TOC -->  
<!-- TOC -->  
<div class="noprint">


= SUMMARY INTRODUCTION =
= SUMMARY INTRODUCTION =
Line 81: Line 80:
|}
|}
-->
-->
== Customer Ref:  ==
 
{| width="100%"
 
|-  
== Log Number: 00514663 ==
|width="30%"|'''OBS Log Number:''' || '''Reporter:'''  
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Drop numbers and times not reset
|-
|'''Detail of Fix''' || The trip will be validated and have its distances and times recalculated when a stop is deleted when its last order is unscheduled from the trip because it has been updated with a new scheduled date.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00498981 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Extend EPL_SERVICES_SUPPLIED to 255 characters
|-
|'''Detail of Fix''' || EPL_SERVICES_SUPPLIED and SCH_ORD_ITEMS.SERVICE_SUPPLIED has been altered to accommodate 255 characters.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00527152 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Orders sent to Paragon for an invalid run number
|-
|'''Detail of Fix''' || Orders and their locations will not advise Paragon via the API when they have a run number that is for a route code that does not send its orders to Paragon for planning.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00527157 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Resync error in API from Paragon
|-
|'''Detail of Fix''' || Some queries have been changed for greater efficiency for the import API from Paragon and the triggering of the haulage activity for MIS.
Additionally, extensive auditing has been added to the process to read the message from Paragon to review the efficiency of the process.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Log Number: 00520087 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Unable to import Fixed Routes
|-
|'''Detail of Fix''' || The record format and the field will be case sensitive to enable record formats with similar names to be processed.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00530171 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Recalculate the distance and time when an order is cancelled via the API
|-
|'''Detail of Fix''' || The trip will be validated and have its distances and times recalculated when a stop is deleted when its last order is unscheduled from the trip because it has been cancelled via the API.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00522350 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Updates to Epod Web Service Audit Screen
|-
|'''Detail of Fix''' || New field 'STATUS' has been added and previously existed column trip_id is renamed as reference and altered it as a LOV which gives a list of references from EWSA for better auditing purpose.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00534416 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Slow rate of processing the Paragon API for the runs (20978)
|-
|'''Detail of Fix''' || The orders will be unscheduled directly from the TMP trips to improve the rate of processing.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00529028 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Generate Paragon ID for UNKNOWN locations (20979)
|-
|'''Detail of Fix''' || The EDI parameter 'UPDATE_PARAGON_ID' for the 'API' process will be used to update the new locations for the orders with a Paragon ID and a delivery depot.
The UNKNOWN locations for the order will create new collection and delivery locations based on the postcode.
   
The Paragon ID will be based on the customer code and the location code.
The delivery depot for Paragon for the new location will be based on the planning depot for the planning region of the location for its postal region.
This planning depot will be used in preference to the depot code of the collection location for an order for a delivery, or to the depot code for the delivery location for an order for a collection.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Log Number: 00536205 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Import Fixed Routes to update the PAR_RUN decoded value
|-
|'''Detail of Fix''' || The decoded value for the 'PAR_RUN' for the fixed routes will be inserted, updated or deleted for the route.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00510487 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| No drop number provided for customers
|-
|'''Detail of Fix''' || A new system parameter called 'TRM_3PL_SCHEDULE_NO_DROP' will be available to configure with a value of 'Y' to enable the orders for a location without a drop number for the route for Paragon to be added to the temporary 'TMP' trip for pre-planning.
 
The 'DL' stops will be added as drop number '498' and the 'PK' stops will be added as drop number '499'.
 
When this system parameter is not active, those orders will continue to display the audit message 'Cannot pre-plan no drop number available'.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|TRM_3PL_SCHEDULE_NO_DROP
|SYSTEM
|Y
|The orders for a location without a drop number for the route for Paragon will be added to the temporary 'TMP' trip for pre-planning.
|-
|TRM_3PL_SCHEDULE_NO_DROP
|SYSTEM
|N
|The orders for a location without a drop number for the route for Paragon will not be added to the temporary 'TMP' trip for pre-planning, they will continue to display the audit message 'Cannot pre-plan no drop number available'.
|}
 
 
== Log Number: 00537843        ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| PCL trip created for a zero-drop number
|-
|'''Detail of Fix''' || The zero-drop numbers will be assessed with the 'Send to Paragon' flag to create either a PCL trip for a non-Paragon route or a TMP trip for a Paragon route.
 
The zero-drop numbers will be set as stop numbers 498 and 499 on the same TMP trip as the planned drop numbers.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|TRM_3PL_SCHEDULE_NO_DROP
|SYSTEM
|Y
|The orders for a location without a drop number for the route for Paragon will be added to the temporary 'TMP' trip for pre-planning.
|-
|-
|'''Summary of Call'''||  
|TRM_3PL_SCHEDULE_NO_DROP
|SYSTEM
|N
|The orders for a location without a drop number for the route for Paragon will not be added to the temporary 'TMP' trip for pre-planning, they will continue to display the audit message 'Cannot pre-plan no drop number available'.
|}
 
 
== Log Number: 00533620 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Total of Tyres in the Trip Waterfall screen
|-
|'''Detail of Fix''' || Change has been done to get_tyres function, to use the delivered quantity for Tyres(DL) column in waterfall screen, instead of what was planned to be delivered.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
|-
|'''Detail of Fix''' ||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|TRIP_OVERVIEW_CURRENT_TYRES
|SYSTEM
|N
|Use the current quantity of tyres in the Trip Waterfall screen (Y/N)
|}
|}
<!-- NEW PAGE -->  
== Customer Ref:  ==
{| width="100%"
== Log Number: 00539920 ==
|-  
{| width="100%"
|width="30%"|'''OBS Log Number:'''  || '''Reporter:'''  
|-
|width="30%"|'''Summary of Call'''|| Audit Paragon for the STP version
|-
|'''Detail of Fix''' || The auditing for Paragon will use the name of the EDI process to assess test 'AUDIT_WS' parameter.
 
The auditing will include the content of the message as well as the endpoint.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00542201 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Update merged TMP trip to be DELETED (24117)
|-
|'''Detail of Fix''' || The TMP trips will be revalidated when an order is transferred to another another run number.
 
When an order is unscheduled from a TMP trip because it has a new run number, any empty stops on that trip will be deleted and the distance and time will be recalculated for the remaining stops.
 
An empty trip will have status DELETED.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00479903 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| SCR 41: Always default removals from last inspected
|-
|'''Detail of Fix''' || Web service package changed not to send the product details for removals
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02578219 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Implement customer password standards in C-TMS instances
|-
|'''Detail of Fix''' || New Software for validation of user passwords by profile
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|USE_SECURITY_PROFILES
|SYSTEM
|Y
|Activate Security Profiles for users
|}
 
<!-- NEW PAGE -->
== Log Number: 00550569 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Orders for the collection desk are not scheduling
|-
|'''Detail of Fix''' || The 'DSK' trips for the collection desk will be assessed for the orders by schedule to create a new trip or to add the order with a new stop to an existing trip.
 
Any trips for the collection desk that have become empty of orders and stops except a 'CL' stop will be updated to have new stops for the orders.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00547839 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Planning screen slow to refresh
|-
|'''Detail of Fix''' || A system parameter exists called 'PLANNING_AUTO_SCHED_INACTIVE_DEPOTS' to store the inactive depots in quotation marks to accompany 'AUTO_SCHED_INACTIVE_DEPOTS' for the scheduling engine.
 
The quotation marks will enable the list to be assessed directly in the 'PLANNING' screen to exclude the orders for the inactive depots.
 
From and to locations for the collection and delivery orders will be checked against this list.
 
The number of orders will be reduced and the query of the unscheduled orders will be performed much more quickly.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00548540 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Increase the number of days in the range for the weekly Paragon keys
|-
|'''Detail of Fix''' || Increased number days a key spans
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00550047 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| New delivery dates should update Paragon with a milestone (24318)
|-
|'''Detail of Fix''' || The new schedule for the delivery date for the order will delete the order from the previous schedule in Paragon and add it to the new schedule in Paragon with its collection or delivery location as required.
The new system parameter 'OMS_UPDATE_SCHEDULE_TO_TRIP' will update the time windows for the orders that exist on a trip when the schedule of the trip is changed in the 'Planning' screen.
When this system parameter is set to 'Y', the time windows of the orders on the trip will be offset to match the number of days that have changed for the schedule of the 'RADIAL' trip.
An instruction to unschedule the order for the change of the delivery date will not occur when that date is offset with the schedule of the order itself.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00551639 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Create the Paragon ID for new orders
|-
|'''Detail of Fix''' || The Paragon ID and the delivery depot will be created for an existing location when it is used for an order.
 
The existing Paragon ID and the delivery depot will be retained for an existing location when it is used for an order.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00469937 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| SCR 14: Multiple contacts, identifying who gets the EPOD report
|-
|'''Detail of Fix''' || This functionality will change CTMS and CTL to allow the maintenance and selection of multiple contacts and allow the users to define which contacts will be used for the tracking link, for the work report email and for contact options on the mobile device.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00516374 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| SCR 44: Job Ticket to display a free-text field to add to service report to add "Actual Customer"
|-
|'''Detail of Fix''' || Development to display the 'Actual Customer' in CTL and on the epod pod note.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00554583 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Error handling in Paragon API import
|-
|'''Detail of Fix''' || A plan for either the current schedule or the next schedule can be imported via the Paragon API.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00555143 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Set PAR trips to use the time to depart from not arrive at the depot
|-
|'''Detail of Fix''' || The Paragon API interface for STP will set the planned arrival and departure times at the depot based on the values that are received:
 
Planned Arrival Time: TRIPSTART
 
Planned Departure Time: TRPSRCDEPOTDEP or TRPDSTDEPOTDEP
 
If the Planned Arrival Time is greater than or equal to the Planned Departure Time, then 30 minutes will be deducted from the Planned Departure Time to set the Planned Arrival Time.
   
At present, TRIPSTART equals TRPSRCDEPOTDEP and TRPDSTDEPOTDEP is NULL, therefore the Planned Arrival Time and the Start Time of the trip will become TRPSRCDEPOTDEP minus 30 minutes.
 
Those values will be consistent with the requirements from the recent conference call and they will account for any different values that are received from Paragon.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00555144 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Slow processing in the Waterfall screen
|-
|'''Detail of Fix''' || The Trip Waterfall screen will call only those functions that are required to display for the configured layout on the screen.
 
The rate of processing the queries will be quicker as will the navigation between the tab pages.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00554568 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Update Paragon with the LOC on the new schedule (24348)
|-
|'''Detail of Fix''' || Paragon should receive a LOC record for the location of the order when the order is placed on a new schedule for planning.
 
The order will be deleted for its old location and added for planning in Paragon.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00563001 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Delete old call for Paragon
|-
|'''Detail of Fix''' || The orders and their locations will advise Paragon to add, update or delete them when they are changed in CTMS.
 
Uses the old location when deleting the order from Paragon.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00567392 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Additional error handling for Paragon API for the STP version
|-
|'''Detail of Fix''' || Additional error handling is included to ensure that a locked trip does not prevent other trips being updated to TENDERED status as required.
   
The additional error handling exists for these post-update procedures:
 
&#45; Update the trips from PLANNED to TENDERED status for Fleet carriers.
 
&#45; Update the TENDERED trips for Fleet carriers with a rate.
 
&#45; Update the route code for trips for 3PL carriers.
 
&#45; Update the route code for trips for non-3PL carriers.
 
&#45; Update the trips for the 3PL carrier with a rate and set to TENDERED status.
 
&#45; Delete any empty trips for the current and future schedules.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00568624 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Paragon not receiving the data for special runs (GDSP03) &#45; (25103)
|-
|'''Detail of Fix''' || Excludes the early delivery date and time from the assessment of the current date and time for the schedule for Paragon.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00484537 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Paragon Count of non-tyre Products
|-
|'''Detail of Fix''' || A new reference called 'CALL.USER03' will be sent to Paragon for the STS databases.
 
Note that there will be a task to implement the new call for Paragon when Paragon is configured to use the data.
 
This reference will include the number of items that are not classed as tyres.
 
The tyres will be identified with a DU type that begins with the letter 'T'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00571947 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| New location for a variant address by ID
|-
|'''Detail of Fix''' || The variant addresses will not update the location for the ADDRESS_ID when a variant address is not found for the ADDRESS_EXT_REF.
 
The ADDRESS_ID is provided for permanent locations but it is not provided for temporary address.
 
The variant addresses can be provided with or without an ADDRESS_ID but they do require an ADDRESS_EXT_REF.
 
The unknown locations will continue to create a new location when a matching address for an existing location is not found.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00575228 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Work not going from Paragon to CTMS
|-
|'''Detail of Fix''' || A new EDI parameter called 'PAR_SCHEDULES' is available to assess the number of schedules in the future to retrieve from Paragon via the API.
 
This EDI parameter will be effective for the versions of the API by week and by day.
 
It is expected to be set for the EDI process that is called 'Get_Paragon'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00578389 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Work not going from Paragon to CTMS for STP
|-
|'''Detail of Fix''' || A new EDI parameter called 'PAR_SCHEDULES' is available to assess the number of schedules in the future to retrieve from Paragon via the API.
 
This EDI parameter will be effective for the versions of the API by week and by day.
 
It is expected to be set for the EDI processes that are called 'Get_Paragon' by depot.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02713995 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Weights incorrect
|-
|'''Detail of Fix''' || Development which introduces new column for called PACK_QUANTITY to store decimal values up to 2 digits for weights, so the whole weight can be seen without truncating the value.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Summary of Call'''||  
|USE_PACK_QUANTITY
|SYSTEM
|Y/N
|Use Decimal Pack quantity and allowed values will be (Y/N) which will control the additional functionality
|}
== Log Number: 00525198 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTL Call Logging &#45; Can't raise a top-up transfer against a service-only job
|-
|'''Detail of Fix''' || Fixed refresh of driver list for Top-Up transfers. Filtered out inactive drivers. Filtered out DELIVERED and FAILED orders from the Orders list.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00525182 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Additional messages sent after order completed
|-
|'''Detail of Fix''' || Added system parameter to prevent ORD/COL messages being sent after a DEL for the same order/trip
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
|-
|'''Detail of Fix''' ||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|PREVENT_ORD_COL_AFTER_DEL
|COST CENTRE
|Y
|Prevent ORDS and COLS after a DEL message
|}
|}
== Log Number: 00517921 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTMS-EPOD INTERFACE - Removal tyres have description/price of installed product
|-
|'''Detail of Fix''' || The Removal tyres now doesn't contain description, price or location.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00524462 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTMS EPOD Interface &#45; Tyre pressure and tread depth getting reset
|-
|'''Detail of Fix''' || Ignore any work type R records when updating tyres
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00524481 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Vehicle Search Webservice &#45; returning inspection wrong
|-
|'''Detail of Fix''' || Trailer search corrected
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00527142 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Epod Wrong product code being sent on the install line
|-
|'''Detail of Fix''' || Ensure that product code is updated when response received from epod.


EPOD DEVICE
Make sure that the item must be deleted first from the list, then can be re-added.
Ensured that the device will not allow creation of a new Install/Remove/Other line for a wheel position where that wheel position already exists on the job and is not deleted.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00527274 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TMS/EPOD. No Install lines for service &#45; prevents Elucid from applying charges
|-
|'''Detail of Fix''' || Ensure COL/DEL messages sent in correct sequence for all orders
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528183 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Issue with DEL message
|-
|'''Detail of Fix''' || Items not received back for debrief from epod have to deliver and delivered quantity set to 0
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528738 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TMS Fleet Inspection Missing service items
|-
|'''Detail of Fix''' || Added vehicle to items check to ensure items created for all vehicles
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528842 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Missing Van Stock Wheel
|-
|'''Detail of Fix''' || Added product to check when creating items
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528195 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Add the depot to the route details page in location maintenance screen.
|-
|'''Detail of Fix''' || The inbound process to update the routes from Paragon will be run for the extracted data for the current process.


Any other unprocessed records for the depot will not be processed.


= SUPPORT INCIDENTS =
The 'Location Maintenance' screen will display the delivery depot in the 'Route Dtls' tab page for these routes from Paragon.
<!--
 
== Customer Ref: ==
The records are sorted by 'Depot Number', 'Route Code' and 'Drop Number'.
{| width="100%"
|-
|-  
|'''Set-up and Configuration''' || No set-up/configuration required
|width="30%"|'''OBS Log Number:''' || '''Reporter:'''  
|}
== Log Number: 00530050 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| API Export &#45; COL sent after DEL
|-
|'''Detail of Fix''' || Change order messages processed in DP_EXPORT_EVENTS
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528762 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Missing COP225 in ORDER_SERVICES
|-
|'''Detail of Fix''' || Create additional services from epod
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00527603 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| TS3 upload
|-
|'''Detail of Fix''' || The system parameter 'PAR_AUDIT' can be set to 'Y' to include auditing of the import process in the STP version of the Paragon API.
 
The system parameter 'PARAGON_RUNNING' will be used to indicate if the STP version of the Paragon API is importing data &#45; it will not be editable by the users.
 
The import process in the STP version of the Paragon API will set the orders for manual scheduling when they are temporarily unscheduled from their temporary trips or their Paragon trips.
 
Then, those orders will not be reprocessed by the 3PL scheduling engine.
 
The 3PL scheduling engine will not start when the Paragon API is processing.
 
Then, these processes will not be updating concurrently any of the same trips and orders; plus the rate processing should be improved.
 
However, the import process in the STP version of the Paragon API will not wait should the 3PL scheduling engine be processing.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|PAR_AUDIT
|SYSTEM
|Y
|The STP version of the Paragon API will write audit records for the import process.
|-
|PAR_AUDIT
|SYSTEM
|N
|The STP version of the Paragon API will not write audit records for the import process.
|-
|PARAGON_RUNNING
|SYSTEM
|Y
|The STP version of the Paragon API is importing data.
|-
|-
|'''Summary of Call'''||  
|PARAGON_RUNNING
|SYSTEM
|N
|The STP version of the Paragon API is not importing data.
|}
 
== Log Number: 00524586 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Vehicle serviced at roadside should not change the location against that vehicle.
|-
|'''Detail of Fix''' || Fixes for new vehicle creation for call Logging and removed update on Current_location_id for RTC
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00528718 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Orders on wrong trip and incorrect drop numbers being retained for locations
|-
|'''Detail of Fix''' || Optimised the import process of the route details from Paragon.
 
The orders will be assigned to a trip for the advised route although the order in trip position 1 has not been used to create a new trip for the route.
The route details to update the drop numbers from Paragon for the locations will refer to the current archive id and they will not include any historic transactions that remain for the depot.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00533067 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| GDCOL runs not synching to CTMS (21886)
|-
|'''Detail of Fix''' || The 'DSK' trips will be assessed for the orders by schedule to create a new trip, or to add the order to an existing trip, for the run number for the depot.
 
An existing trip will either create a new stop or use an existing stop.
 
An order for a collection desk must be for a route of type 'COLLECT_DESK'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00533991 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Vehicle Maintenance Last Inspection field
|-
|'''Detail of Fix''' || Fixed C-TMS when performing the last inspection date calculation. If the inspection date was set as more than 1 month and the start date was for the first day of the month it was setting the end date for each period incorrectly.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00537198 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Ampersand characters not being 'escaped'
|-
|'''Detail of Fix''' || Ampersands in tyre serial numbers replaced with escaped value
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00524191 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Cancelling an order in CTL Call Logging should ask for and set Order Reason Codes
|-
|'''Detail of Fix''' || Amend TYRE_ORDS report to use Non Conformance reason codes. Users will need to create a new copy of the ORS extract to use the changes
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00538804 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Control records not being updated after send to Elucid
|-
|'''Detail of Fix''' || Ensure that all control records are updated in the correct code area
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00540264 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Orders with different depot starting point do not plan in Paragon (22118)
|-
|'''Detail of Fix''' || A new EDI parameter called 'USE_RUN_DEPOT' is available to use the depot for the route for the run number of the order in preference to the depot of the collection/delivery location of the RET/SLS/ order.
 
When this parameter is 'Y', the depot for the route for the run number will be the depot to send to Paragon via the API.
 
This parameter is expected to the set for the 'Paragon_Outbound' process.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00534016 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| FIA report showing tyre brands as 'other'
|-
|'''Detail of Fix''' || Fixed the issue by changing view to allow separate entries with OTHER manufacturers.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
|-
|'''Detail of Fix''' ||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|USE_PACK_QUANTITY
|SYSTEM
|Y/N
|Use Decimal Pack quantity and allowed values will be (Y/N) which will control the additional functionality
|}
== Log Number: 00538191 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Remaining characters not being escaped (exception ampersand)
|-
|'''Detail of Fix''' || Added CDATA when the new EDI parameter INCLUDE_CDATA_TAG is active, which will control the escaping of special characters like &.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00542256 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Customer export from Elucid
|-
|'''Detail of Fix''' || The customers from Elucid can store up to 255 characters for the 'SlaUrl' and 'PreferredBrand'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00538855 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Services Supplied Issue
|-
|'''Detail of Fix''' || Fixed the issue with the creation of unnecessary service_id records.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00536498 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Collection job not sent to ePOD
|-
|'''Detail of Fix''' || Collection job has been sent to EPOD for I(INSTALL) if services supplied doesn't include COP, MAJ and collection is sent for Van Stock lines.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00546323 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Call logging vehicle location
|-
|'''Detail of Fix''' || Fixed creation of rvcl for new vehicles in Call Logging.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00544876 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Vehicle config not allowing tyre position selection
|-
|'''Detail of Fix''' || Fixed the views to use RTC and out of sync issue of RT and RTC tables.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00546768 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Portal, jobs showing as Part Delivered
|-
|'''Detail of Fix''' || Only send Work Type R records to portal if the AKA code is populated
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00552783 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Collection job not sent to ePOD
|-
|'''Detail of Fix''' || Collection jobs will be sent for any order which contains Van stock which is not currently at the delivery location of the order
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00554263 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Optimization of the code: Fix for SCR-14 (469937)
|-
|'''Detail of Fix''' || The code has been modified to handle the issues that occurred in the previous versions.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00543998 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Elucid Interface 400/500 fixes
|-
|'''Detail of Fix''' || Improvements in Error Handling are required when messages are rejected due to 400 or 500 error.
|-
|'''Set-up and Configuration''' ||
|}
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|WS_NUM_OF_RETRIES_ALLOWED
|SYSTEM
|3
|Max number of times a record will be sent to a web service endpoint
|}
== Log Number: 00555163 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTL Order display for Orders with No Vehicle
|-
|'''Detail of Fix''' || Fixed v_ord_order_header to select orders differently.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00559726 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| 500 errors from elucid not updating int-xml_control table
|-
|'''Detail of Fix''' || Update number of tries on 500 errors
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00542530 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| EPOD, Twinning
|-
|'''Detail of Fix''' || Process Tyre Swaps to update correctly
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00560125 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Invalid Service codes sent to Elucid
|-
|'''Detail of Fix''' || Reinitialise counters when creating/updating services
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00561946 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Tyre Swap not swapping correct tyres (Twinning) UAT Ref 123
|-
|'''Detail of Fix''' || Add customer details to swap queries
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00562054 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Multiple Contacts &#45; Emails from Portal.
|-
|'''Detail of Fix''' || Added values to insert
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00564461 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Location screen issue
|-
|'''Detail of Fix''' || Fix to Location Screen
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00564569 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Missing email
|-
|'''Detail of Fix''' || Updated the logic to insert LOCATION details even when RecipientMobile/Phone is not supplied.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00563558 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Error On Incoming Message From ePOD
|-
|'''Detail of Fix''' || Amendment to tyre swapping to avoid failed to update service product.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00569051 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Issues with Trye Swap linked to 561946 (CT ID 123)
|-
|'''Detail of Fix''' || TYRE_SWAP and NEW_PRODUCT tags can appear at different levels in the inbound message code added to account for this
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00532043 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Incorrect times displaying
|-
|'''Detail of Fix''' || Stop times will be updated every time for epod mode DELTYPE
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00567195 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Config Change &#45; UAT ref 204
|-
|'''Detail of Fix''' || Updated Vehicle type passed in message from epod.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00570437 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Customer Upload not extracting email address correctly &#45; UAT 216
|-
|'''Detail of Fix''' || Updated the logic to update the email address of a contact even when other details are NULL.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00539653 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| PORTAL inspection depths UAT 59
|-
|'''Detail of Fix''' || Made the change to not to store 0 tread depth against the last known tyre details against that position.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00570824 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Authority Ref not appearing on some jobs. UAT 213
|-
|'''Detail of Fix''' || Add authority code to EPL_CODE_3 tag
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00572795 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Credit Limits
|-
|'''Detail of Fix''' || Check Customer on hold status when adding items to an order
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00573163 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Config issue on Epod device
|-
|'''Detail of Fix''' || Made the change to vehicle search to return values from RTC.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00580395 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Elucid Configuration &#45; proxy setup
|-
|'''Detail of Fix''' || Proxy value added for communication with Elucid
|-
|'''Set-up and Configuration''' ||
|}
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|ELUCID_API_PROXY
|System
|Y/N
|Use Proxy sever for Elucid
|}
|}
-->
== Log Number: 02792680 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Oracle financials OF extract R12 format (WREQ0087544)
|-
|'''Detail of Fix''' || The 'Tax Amount' for the 'R12' format will be included as '0' when the VAT code is 'Z' for 'Zero Rated'.
 
The invoices in the R12 format will be included by VAT code.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
 
 
= SUPPORT INCIDENTS =
<!--
== Customer Ref:  ==
== Customer Ref:  ==
{| width="100%"
{| width="100%"
Line 132: Line 1,339:
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
|}
|}
-->
== Log Number: 00538105 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Change Password option in ACC_CTRL
|-
|'''Detail of Fix''' || CHANGE_PW has been modified to not accept passwords with @ and "
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00549717 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Collection job not sent to ePOD
|-
|'''Detail of Fix''' || Fixed the issues reported in previous version about collection job not being sent in certain conditions.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 03529183 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Web Service order updates are failing to update the forecast (INC58464329)
|-
|'''Detail of Fix''' || The update process previously failed due to mismatched condition statements when records were submitted with action 'A'. Additionally, records with timestamps within a 2-minute interval (00:59:59 to 01:00:00) of an hour change were not properly handled, leading to query failures in identifying duplicate records.
Both issues have been resolved in the latest fix. The logic has been adjusted to handle order amendments and correct any mistakes from the previous version. Now, records within a 2-minute interval are selected irrespective of the hour, and a new check has been added to mark duplicate orders as ""CANCELLED"".
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02769136 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTMS Collection date (INC56773319)
|-
|'''Detail of Fix''' || Temporary variables for EARLY/LATE_AVAIL have been reset so that when an empty tag is provided it will not take the previously stored value.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}




Line 149: Line 1,404:
|}
|}
-->
-->
== OBS Log Number:  ==
 
{| width="100%"
 
|-  
== Log Number: 02766658 ==
|width="30%"|'''Cust Ref:'''  || '''Reporter:'''  
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Change Password option in ACC_CTRL
|-
|'''Detail of Fix''' || Access control has been modified to allow users to create usernames containing special characters, change passwords that may include special characters, and delete users with special characters in their names.
 
Access control has been modified to restrict @ and " in username and passwords while creating/updating.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00538412 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Data flow Review
|-
|'''Detail of Fix''' || Fixed C-TMS view to retrieve orders more efficiently. Fixed CTL customer services screen to filter by customer correctly.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02742281 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Planning screen slowing issues
|-
|'''Detail of Fix''' || Added quotes to schedule to improve speed
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00545159 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Order placed to wrong address on the same account (24348)
|-
|'''Detail of Fix''' || The EDI parameter for the 'API' process called 'UNSCHED_NEW_DATE' has been changed to be 'UNSCHED_NEW_DATA' to assess not only the new date but also the new location and the new run number.
 
The trips will be 'DELETED' should they become empty of orders.
 
The order will now be unscheduled and reset for the 3PL scheduling engine to reprocess to a new trip.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00543948 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Special Runs, change to del date
|-
|'''Detail of Fix''' || The auditing for the order when 'Trip XXX-XXXXXXXX moved to a different schedule from XXXXXX to XXXXXX' will be used to identify when the schedule of the order has been changed with its late delivery date when its trip has been moved to a new schedule.
   
Paragon will be updated with the new schedule for the order and its location for the run number of the route.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02764788 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Disable trailer type send to Paragon
|-
|'''Detail of Fix''' || Added the Disable Paragon check box to the trailer types tab page and to the new/edit screens.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02710742 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Webfleet integration
|-
|'''Detail of Fix''' || Added the exceptional handling to all the programs which contain the control record loops.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02690067 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Data being overridden / Removed
|-
|'''Detail of Fix''' || The 'DUN Inventory Transaction Report' will include the trunk trips that have been used in scanning to load and unload the items.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02818748 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTMS LOAD messages to JDA missing full order ref
|-
|'''Detail of Fix''' || When rebooked order is processed then only external ref is trimmed, for example _R1,_R2. And is also depends on parameter 'ORD_RBO_PREFIX'.
 
If external ref has anything followed after _R and if its not a number then the whole external ref is sent in SO_REF tag.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00534889 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Show Map function failing
|-
|'''Detail of Fix''' || HTML corrected
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
<!-- NEW PAGE -->
== Log Number: 02691631 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Paragon CSV Import Issues
|-
|'''Detail of Fix''' || Import logic has been amended to pick up NEW orders which have collection on schedule date. Previous error message has been altered to get a warning so user can choose to import collection orders or not.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02683404 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Paragon Import
|-
|'''Detail of Fix''' || The 'Loading Management' screen displays a new tick box called 'Include Completed Trips' to enable the trips to be included or excluded when they have a status of 'COMPLETED'.
 
This box will be ticked by default.
   
A new system parameter called 'PAR_DUN_TRUNK_CUTOFF_TIME' can be configured at the system level to set a cut-off time to apply to trunk trips to use the current schedule for the day.
The import process from Paragon for the 'DUN' format will refer to the new system parameter to offset the date to derive the schedule for the processing of the trunk trips.
 
If 'PAR_DUN_TRUNK_CUTOFF_TIME' is set to '04:00' and the current system time is '01:00' then the schedule will not be derived for the current date but for the previous date as if the process for the route/drop had been run on the previous evening."
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02910494 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Trunks for 27th were not generated
|-
|'''Detail of Fix''' || A new system parameter called 'PAR_DUN_TRUNK_OFFSET_DAYS' is available to store the number of days for which trunk trips will be assessed for the radial trips that are created by Paragon.
 
A default value of 4 days will be used but the number of days will be configurable to assess the non-working days for the depot.
 
This system parameter can be used to account for the non-working days during the period of the holiday seasons.
 
The system parameter 'PAR_DUN_TRUNK_CUTOFF_TIME' will start to assess the current date prior to the cutoff time, or from tomorrow after the cutoff time.
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
|-
|'''Summary of Call'''||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Detail of Fix''' ||
|PAR_DUN_TRUNK_OFFSET_DAYS
|SYSTEM
|NUMERIC
|The specified number of days will be used to assess the trunk trips for the radial trips to account for the non-working days in the calendar.
|-
|-
|'''Set-up and Configuration''' ||  
|PAR_DUN_TRUNK_OFFSET_DAYS
|SYSTEM
|NULL/NON-NUMERIC
|A default number of 4 days will be used as per the current functionality.
|}
|}


== Log Number: 00554721 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Planning screen new configuration in test environment
|-
|'''Detail of Fix''' || Fixed the Planning screen to allow the order schedule search dropdown list to change when the trip schedule search dropdown list changes.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00561665 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Planning screen new configuration in test environment
|-
|'''Detail of Fix''' || Fix to Planning screen to search orders correctly.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 02728730 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| XML file format is incorrect
|-
|'''Detail of Fix''' || Modified the code to extend the length of the fields.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00562331 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Customers are created without group and epod should be enabled
|-
|'''Detail of Fix''' || New EDI parameter called UPD_CUST_ENABLE_EPOD has been added to JAK_INBOUND_ORDERS which when set will enable EPOD for all new customers created and to existing customers if they are used to create orders.
|-
|'''Set-up and Configuration''' ||
|}


 
{| class="wikitable" border="1" width="100%"
= PRODUCT DEVELOPMENT =
|- bgcolor="silver"
<!--
!colspan="4" | New Parameters
== OBS Log Number:  ==
{| width="100%"
|-  
|width="30%"| '''Reporter:''' ||
|-
|'''Summary of Call'''||
|-
|-
|'''Detail of Fix''' ||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|UPD_CUST_ENABLE_EPOD
|EDI
|Default N
|When set to Y, then customers will have EPOD enabled.
|}
|}
-->
== OBS Log Number: ==
{| width="100%"
== Log Number: 00562303 ==
|-  
{| width="100%"
|width="30%"| '''Reporter:''' ||  
|-
|width="30%"|'''Summary of Call'''|| Not going through to CTMS
|-
|'''Detail of Fix''' || Uses the first ten characters of the driver ID from Paragon for a new driver ID in CTMS.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00560600 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Paragon not receiving the data for special runs &#45; GDSP03 &#45; (25103)
|-
|'''Detail of Fix''' || The next active day of the week will be used when the order is sent to Paragon and the advised day is in the past.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00553397 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| HERE Data Services
|-
|'''Detail of Fix''' || Updated the HERE processes to use new procedures
|-
|'''Set-up and Configuration''' ||
|}
 
{| class="wikitable" border="1" width="100%"
|- bgcolor="silver"
!colspan="4" | New Parameters
|-
|-
|'''Summary of Call'''||
!Parameter Name !! Config Level !! Setting Value !! Result
|-
|-
|'''Detail of Fix''' ||
|GEO_NLP_USE_ALTERNATE
|SYSTEM
|Y/N
|Alternate URL and Proxy will be used
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|GEO_NLP_ALT_PROXY
|SYSTEM
|IP address of Proxy
|IP Address for Proxy Server
|}
|}
== Log Number: 03008712 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| API Order duplicated for multiple stores with the same PO for the same store
|-
|'''Detail of Fix''' || Due to API concurrent processing (rare occurrence) duplicate orders were created, to resolve it the latest record is marked as failure with validation error and the earliest one is processed to create the order.
Additional change is made to avoid duplicate orders being created in same minute, ignoring time stamp on seconds.
Observed that duplicate orders were created with gap of 12 seconds so added logic to ignore seconds and consider only same hour and minute.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00565562 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Trips being stuck in planned status
|-
|'''Detail of Fix''' || Additional error handling is included to ensure that a locked trip does not prevent other trips being updated to TENDERED status as required.
The additional error handling exists for these post-update procedures:
Update the trips from PLANNED to TENDERED status for Fleet carriers.
Update the TENDERED trips for Fleet carriers with a rate.
Update the route code for trips for 3PL carriers.
Update the route code for trips for non-3PL carriers.
Update the trips for the 3PL carrier with a rate and set to TENDERED status.
Delete any empty trips for the current and future schedules.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00543919 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Address Update (24288)
|-
|'''Detail of Fix''' || A new EDI parameter called 'USE_VARIANT_ADDRESS' will be introduced to the 'API' process to control the new functionality to create new locations with temporary variant addresses: the new functionality will be active when the value of the EDI parameter is 'Y'.
The new functionality will apply to addresses that are provided for an external reference.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00540719 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Send to Paragon request (21702)
|-
|'''Detail of Fix''' || A new function called 'TRM_SEND_TO_PARAGON' is available for the users via their groups.
The new function called 'TRM_SEND_TO_PARAGON' will be used to display and enable the new menu option called 'Send to Paragon' in the trip tree in the 'Planning' screen.
The new option will be present between 'Re-send PO Message' and 'Debrief Trip' when it is enabled.
The system parameters called 'TRM_TREE_ROUTE' and 'TRM_TREE_FORMAT' will be assessed by a similar method to how they are assessed in the 'Planning' screen for the range of schedules for the order well.
These system parameters will be found that is active for a cost centre when the user has access to 'ALL' cost centres or to multiple cost centres.
Then the route code may be displayed in the specified format based on these system parameters.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00572113 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| API Key Incorrect for here Maps
|-
|'''Detail of Fix''' || API key updated
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00558723 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTL screen takes too long to load
|-
|'''Detail of Fix''' || Separated the views used by customer services and call logging.
I still recommend that we need to cleardown orders at status INVALID and that they will need to either cancel them or process them every day.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
<!-- NEW PAGE -->
== Log Number: 00577244 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Order issue in Paragon
|-
|'''Detail of Fix''' || Orders which are added to DSK or PCL trips will not advise Paragon to delete them from the planning unless they have been advised previously to add them to the planning.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}




Line 206: Line 1,824:
!Module Name !! Version No !! Description !! Log Number
!Module Name !! Version No !! Description !! Log Number
|-
|-
|  ||  ||  ||  
| ACC_CTRL.fmx || 2.57 || Access control maintenance || 02766658
|-
| ACC_CTRL.fmx || 2.59 || Access control maintenance || 00538105
|-
| ACC_CTRL.fmx || 2.63 || Access control maintenance || 02578219
|-
| ADM.sql || 5.16 || Administrator package containing various DB utils || 02578219
|-
| AT_GEO_CONTACT_469937.sql || 1.1 || AT Script || 00469937
|-
| AT_GEO_ROUTE_DTLS_00528718.sql || 1.1 || AT Script || 00528718
|-
| AT_INT_XML_CONTROL_543998.sql || 1.1 || AT Script || 00543998
|-
| AT_INT_XML_ORD_DETAILS_0271399 || 1.1 || AT Script || 02713995
|-
| AT_SCH_ORD_INFORMATION_469937.sql || 1.1 || AT Script || 00469937
|-
| AT_SCH_ORD_ITEMS_02713995.sql || 1.1 || AT Script || 02713995
|-
| AT_SCH_ORD_ITEMS_498981.sql || 1.1 || AT Script || 00498981
|-
| BDM.fmx || 2.110 || Business Data Form || 00548540
|-
| CHANGE_PW.fmx || 2.12 || Change Password || 02578219
|-
| CHANGE_PW.fmx || 2.13 || Change Password || 00538105
|-
| CT_SECURITY_PROFILES_02578219.sql || 1.1 || CT Script || 02578219
|-
| DATA_ADM_FUNCTION_540719.sql || 1.1 || Data Script || 00540719
|-
| DATA_ADM_MSEL_FORM_PARAM_02713995.sql || 1.1 || Data Script || 02713995
|-
| DATA_ADM_SYSTEM_PARAM_00510487.sql || 1.1 || Data Script || 00510487
|-
| DATA_ADM_SYSTEM_PARAM_00547839.sql || 1.1 || Data Script || 00547839
|-
| DATA_ADM_SYSTEM_PARAM_02578219.sql || 1.1 || Data Script || 02578219
|-
| DATA_ADM_SYSTEM_PARAM_02683404.sql || 1.1 || Data Script || 02683404
|-
| DATA_ADM_SYSTEM_PARAM_02713995.sql || 1.1 || Data Script || 02713995
|-
| DATA_ADM_SYSTEM_PARAM_02910494.sql || 1.1 || Data Script || 02910494
|-
| DATA_ADM_SYSTEM_PARAM_469937.sql || 1.1 || Data Script || 00469937
|-
| DATA_ADM_SYSTEM_PARAM_513456.sql || 1.3 || Data Script || 00553397
|-
| DATA_ADM_SYSTEM_PARAM_516374.sql || 1.2 || Data Script || 00516374
|-
| DATA_ADM_SYSTEM_PARAM_525182.sql || 1.1 || Data Script || 00525182
|-
| DATA_ADM_SYSTEM_PARAM_527603.sql || 1.1 || Data Script || 00527603
|-
| DATA_ADM_SYSTEM_PARAM_533620.sql || 1.1 || Data Script || 00533620
|-
| DATA_ADM_SYSTEM_PARAM_543998.sql || 1.1 || Data Script || 00543998
|-
| DATA_ADM_SYSTEM_PARAM_550047.sql || 1.1 || Data Script || 00550047
|-
| DATA_ADM_SYSTEM_PARAM_572113.sql || 1.1 || Data Script || 00572113
|-
| DATA_ADM_SYSTEM_PARAM_580395.sql || 1.1 || Data Script || 00580395
|-
| DATA_ADM_SYSTEM_PARAM_CONFIG_516374.sql || 1.2 || Data Script || 00516374
|-
| DATA_ADM_SYSTEM_PARAM_CONFIG_525182.sql || 1.1 || Data Script || 00525182
|-
| DATA_ADM_USER_PARAM_TYPE_02578219.sql || 1.3 || Data Script || 02578219
|-
| DATA_EDI_PROCESS_TRIGGERS_00538191.sql || 1.1 || Data Script || 00538191
|-
| DATA_EDI_PROCESS_TRIGGERS_545159.sql || 1.1 || Data Script || 00545159
|-
| DATA_EDI_PROCESS_TRIGGERS_562331.sql || 1.1 || Data Script || 00562331
|-
| DATA_IMP_FIELD_00520087.sql || 1.1 || Data Script || 00520087
|-
| DATA_ORACLE_PROFILES_02578219.sql || 1.3 || Data Script || 02578219
|-
| DATA_ORS_MASTER_DATA_02713995.sql || 1.3 || Data Script || 02713995
|-
| DATA_ORS_MASTER_DATA_524191.sql || 1.1 || Data Script || 00524191
|-
| DATA_ORS_SQL_524191.sql || 1.1 || Data Script || 00524191
|-
| DATA_SECURITY_PROFILES_02578219.sql || 1.1 || Data Script || 02578219
|-
| DP_3PL_SCHED.sql || 5.11 || 3PL Scheduling Engine Database Package || 00527603
|-
| DP_3PL_SCHED.sql || 5.12 || 3PL Scheduling Engine Database Package || 00533067
|-
| DP_3PL_SCHED.sql || 5.13 || 3PL Scheduling Engine Database Package || 00510487
|-
| DP_3PL_SCHED.sql || 5.14 || 3PL Scheduling Engine Database Package || 00537843
|-
| DP_3PL_SCHED.sql || 5.15 || 3PL Scheduling EngineDatabase Package || 00550569
|-
| DP_3PL_SCHED.sql || 5.16 || 3PL Scheduling Engine Database Package || 00555143
|-
| DP_CSV_DUN.sql || 5.56 || Client specific CSV extracts || 02690067
|-
| DP_CTMS_IMPORT.sql || 5.35 || API Import Database Package || 00514663
|-
| DP_CTMS_IMPORT.sql || 5.36 || API Import Database Package || 00527152
|-
| DP_CTMS_IMPORT.sql || 5.37 || API Import Database Package || 00530171
|-
| DP_CTMS_IMPORT.sql || 5.38 || API Import Database Package || 00529028
|-
| DP_CTMS_IMPORT.sql || 5.40 || API Import Database Package || 00542256
|-
| DP_CTMS_IMPORT.sql || 5.42 || API Import Database Package || 02713995
|-
| DP_CTMS_IMPORT.sql || 5.43 || API Import Database Package || 00545159
|-
| DP_CTMS_IMPORT.sql || 5.44 || API Import Database Package || 00551639
|-
| DP_CTMS_IMPORT.sql || 5.45 || API Import Database Package || 00562054
|-
| DP_CTMS_IMPORT.sql || 5.46 || API Import Database Package || 00563001
|-
| DP_CTMS_IMPORT.sql || 5.47 || API Import Database Package || 00564569
|-
| DP_CTMS_IMPORT.sql || 5.48 || API Import Database Package || 00543919
|-
| DP_CTMS_IMPORT.sql || 5.49 || API Import Database Package || 00570437
|-
| DP_CTMS_IMPORT.sql || 5.50 || API Import Database Package || 00571947
|-
| DP_CUST_SERV.sql || 1.86 || Customer Service Package || 00524586
|-
| DP_CUST_SERV.sql || 1.87 || Customer Service Package || 00546323
|-
| DP_CUST_SERV.sql || 1.89 || Customer Service Package || 00469937
|-
| DP_CUST_SERV.sql || 1.91 || Customer Service Package || 00572795
|-
| DP_EPOD_WEB_SERVICE.sql || 1.216 || EPOD Web Service || 00524462
|-
| DP_EPOD_WEB_SERVICE.sql || 1.217 || EPOD Web Service || 00524481
|-
| DP_EPOD_WEB_SERVICE.sql || 1.218 || EPOD Web Service || 00517921
|-
| DP_EPOD_WEB_SERVICE.sql || 1.220 || EPOD Web Service || 00527142
|-
| DP_EPOD_WEB_SERVICE.sql || 1.221 || EPOD Web Service || 00527274
|-
| DP_EPOD_WEB_SERVICE.sql || 1.222 || EPOD Web Service || 00498981
|-
| DP_EPOD_WEB_SERVICE.sql || 1.223 || EPOD Web Service || 00528183
|-
| DP_EPOD_WEB_SERVICE.sql || 1.224 || EPOD Web Service || 00528738
|-
| DP_EPOD_WEB_SERVICE.sql || 1.225 || EPOD Web Service || 00528842
|-
| DP_EPOD_WEB_SERVICE.sql || 1.226 || EPOD Web Service || 00528762
|-
| DP_EPOD_WEB_SERVICE.sql || 1.227 || EPOD Web Service || 00524586
|-
| DP_EPOD_WEB_SERVICE.sql || 1.228 || EPOD Web Service || 00533991
|-
| DP_EPOD_WEB_SERVICE.sql || 1.230 || EPOD Web Service || 00538855
|-
| DP_EPOD_WEB_SERVICE.sql || 1.231 || EPOD Web Service || 02713995
|-
| DP_EPOD_WEB_SERVICE.sql || 1.232 || EPOD Web Service || 00536498
|-
| DP_EPOD_WEB_SERVICE.sql || 1.233 || EPOD Web Service || 00479903
|-
| DP_EPOD_WEB_SERVICE.sql || 1.234 || EPOD Web Service || 00544876
|-
| DP_EPOD_WEB_SERVICE.sql || 1.235 || EPOD Web Service || 00549717
|-
| DP_EPOD_WEB_SERVICE.sql || 1.236 || EPOD Web Service || 00469937
|-
| DP_EPOD_WEB_SERVICE.sql || 1.238 || EPOD Web Service || 00516374
|-
| DP_EPOD_WEB_SERVICE.sql || 1.239 || EPOD Web Service || 00554263
|-
| DP_EPOD_WEB_SERVICE.sql || 1.241 || EPOD Web Service || 00552783
|-
| DP_EPOD_WEB_SERVICE.sql || 1.242 || EPOD Web Service || 00542530
|-
| DP_EPOD_WEB_SERVICE.sql || 1.243 || EPOD Web Service || 00560125
|-
| DP_EPOD_WEB_SERVICE.sql || 1.244 || EPOD Web Service || 00561946
|-
| DP_EPOD_WEB_SERVICE.sql || 1.245 || EPOD Web Service || 00563558
|-
| DP_EPOD_WEB_SERVICE.sql || 1.246 || EPOD Web Service || 00567195
|-
| DP_EPOD_WEB_SERVICE.sql || 1.247 || EPOD Web Service || 00532043
|-
| DP_EPOD_WEB_SERVICE.sql || 1.248 || EPOD Web Service || 00569051
|-
| DP_EPOD_WEB_SERVICE.sql || 1.249 || EPOD Web Service || 00539653
|-
| DP_EPOD_WEB_SERVICE.sql || 1.250 || EPOD Web Service || 00570824
|-
| DP_EPOD_WEB_SERVICE.sql || 1.251 || EPOD Web Service || 00573163
|-
| DP_EXPORT_EVENTS.sql || 5.34 || API Export Events Database Package || 00528842
|-
| DP_EXPORT_EVENTS.sql || 5.35 || API Export Events Database Package || 00530050
|-
| DP_EXPORT_EVENTS.sql || 5.36 || API Export Events Database Package || 00537198
|-
| DP_EXPORT_EVENTS.sql || 5.37 || API Export Events Database Package || 00538804
|-
| DP_EXPORT_EVENTS.sql || 5.38 || API Export Events Database Package || 00538191
|-
| DP_EXPORT_EVENTS.sql || 5.40 || API Export Events Database Package || 00543998
|-
| DP_EXPORT_EVENTS.sql || 5.41 || API Export Events Database Package || 00559726
|-
| DP_EXPORT_EVENTS.sql || 5.42 || API Export Events Database Package || 00580395
|-
| DP_NOKIA_LOC_PLAT.sql || 1.41 || Nokia Location Platform Interface || 00553397
|-
| DP_ORS_FUNCS.sql || 5.30 || Change to DOOD status function || 00524191
|-
| DP_PAR_API.sql || 5.19 || Paragon API Database Package || 00548540
|-
| DP_PAR_API.sql || 5.20 || Paragon API Database Package || 00562303
|-
| DP_PAR_API.sql || 5.21 || Paragon API Database Package || 00565562
|-
| DP_PAR_API.sql || 5.22 || Paragon API Database Package || 00575228
|-
| DP_PAR_API_STP.sql || 5.21 || STP Paragon API Database Package || 00527157
|-
| DP_PAR_API_STP.sql || 5.22 || STP Paragon API Database Package || 00528195
|-
| DP_PAR_API_STP.sql || 5.23 || STP Paragon API Database Package || 00527603
|-
| DP_PAR_API_STP.sql || 5.24 || STP Paragon API Database Package || 00528718
|-
| DP_PAR_API_STP.sql || 5.25 || STP Paragon API Database Package || 00534416
|-
| DP_PAR_API_STP.sql || 5.26 || STP Paragon API Database Package || 00539920
|-
| DP_PAR_API_STP.sql || 5.27 || STP Paragon API Database Package || 00540264
|-
| DP_PAR_API_STP.sql || 5.28 || STP Paragon API Database Package || 00542201
|-
| DP_PAR_API_STP.sql || 5.29 || STP Paragon API Database Package || 00554583
|-
| DP_PAR_API_STP.sql || 5.30 || STP Paragon API Database Package || 00555143
|-
| DP_PAR_API_STP.sql || 5.31 || STP Paragon API Database Package || 00562303
|-
| DP_PAR_API_STP.sql || 5.33 || STP Paragon API Database Package || 00563001
|-
| DP_PAR_API_STP.sql || 5.34 || STP Paragon API Database Package || 00560600
|-
| DP_PAR_API_STP.sql || 5.35 || STP Paragon API Database Package || 00567392
|-
| DP_PAR_API_STP.sql || 5.36 || STP Paragon API Database Package || 00568624
|-
| DP_PAR_API_STP.sql || 5.37 || STP Paragon API Database Package || 00484537
|-
| DP_PAR_API_STP.sql || 5.38 || STP Paragon API Database Package || 00578389
|-
| DP_TOMTOM.sql || 1.46 || TomTom Package || 02710742
|-
| DP_WEB_SERVICE_ORD.sql || 1.33 || Web Service Package || 03008712
|-
| DP_WEB_SERVICE_ORD.sql || 1.35 || Web Service Package || 03529183
|-
| EPOD_WSA.fmx || 1.13 || EPOD Web Service Audit Form || 00522350
|-
| IMP.sql || 5.234 || CSV Imports Package || 00520087
|-
| IMP.sql || 5.235 || CSV Imports Package || 00536205
|-
| INT_XML_IN.sql || 5.241 || Order Import Package || 02769136
|-
| INT_XML_IN.sql || 5.242 || Order Import Package || 00562331
|-
| INT_XML_MIC.sql || 5.158 || MIC interface || 02728730
|-
| INT_XML_OUT2.sql || 5.336 || Outbound XML Package || 02818748
|-
| INT_XML_OUT2.sql || 5.337 || Outbound XML Package || 00546768
|-
| INT_XML_OUT2.sql || 5.338 || Outbound XML Package || 00469937
|-
| INT_XML_OUT2.sql || 5.339 || Outbound XML Package || 00554263
|-
| LOAD_MAN.fmx || 1.29 || Load Management Form || 02683404
|-
| LOCATION.fmx || 2.207 || Location Maintenance || 00528195
|-
| LOCATION.fmx || 2.209 || Location Maintenance || 00469937
|-
| LOCATION.fmx || 2.209 || Location Maintenance || 00564461
|-
| nokmap.html || 1.11 || Maps Interface || 00534889
|-
| OF_INT.sql || 5.75 || Oracle Financials interface || 02792680
|-
| OMS.sql || 5.334 || Order package || 00527603
|-
| ORDERS.fmx || 2.456 || Order Screen || 02713995
|-
| ORDERS_WIDE.fmx || 1.53 || Orders Screen || 02713995
|-
| ORI_MAIN.fmx || 2.18 || Login Screen || 02578219
|-
| PAR.sql || 5.115 || Paragon Interface || 02683404
|-
| PAR.sql || 5.116 || Paragon Interface || 02910494
|-
| PAR_INT.fmx || 10.43 || Paragon Interface form || 02691631
|-
| PLANNING.fmx || 1.146 || Planning Screen || 02742281
|-
| PLANNING.fmx || 1.147 || Planning Screen || 00547839
|-
| PLANNING.fmx || 1.148 || Planning Screen || 00550047
|-
| PLANNING.fmx || 1.149 || Planning Screen || 00554721
|-
| PLANNING.fmx || 1.150 || Planning Screen || 00561665
|-
| PLANNING.fmx || 1.151 || Planning Screen || 00540719
|-
| RESOURCE.fmx || 2.200 || Resource Maintenance form || 02764788
|-
| T_SCH_HAULAGE_ACTIVITY_BIU.sql || 1.8 || Trigger || 00527157
|-
| TI_SCH_ORD_STATUS.sql || 1.29 || Trigger on SCH_ORD for status change || 00527152
|-
| TI_SCH_ORD_STATUS.sql || 1.30 || Trigger on SCH_ORD for status change || 00554568
|-
| TI_SCH_ORD_STATUS.sql || 1.31 || Trigger on SCH_ORD for status change || 00563001
|-
| TRG_LOCATIONS_UID.sql || 5.2 || Trigger || 00527152
|-
| TRG_LOCATIONS_UID.sql || 5.3 || Trigger || 00469937
|-
| TRG_LOCATIONS_UID.sql || 5.4 || Trigger || 00554568
|-
| TRG_LOCATIONS_UID.sql || 5.5 || Trigger || 00563001
|-
| TRG_SCH_ORD_AUDIT_LOCS.sql || 1.4 || Trigger || 00543948
|-
| TRG_SCH_ORD_AUDIT_LOCS.sql || 1.5 || Trigger || 00563001
|-
| TRG_SCH_ORD_AUDIT_LOCS.sql || 1.6 || Trigger || 00540719
|-
| TRG_SCH_ORD_CURRENT_DEPOT.sql || 5.6 || Trigger || 00527152
|-
| TRG_SCH_ORD_CURRENT_DEPOT.sql || 5.7 || Trigger || 00550047
|-
| TRG_SCH_ORD_CURRENT_DEPOT.sql || 5.8 || Trigger || 00554568
|-
| TRG_SCH_ORD_CURRENT_DEPOT.sql || 5.9 || Trigger || 00563001
|-
| TRG_SCH_ORDER_LINE_PAR.sql || 5.4 || Trigger || 00527152
|-
| TRG_SHA_TRUNK_TRIP.sql || 5.4 || Trigger || 00577244
|-
| TRG_SOL_XML.sql || 5.51 || Trigger || 00525182
|-
| TRG_SOL_XML.sql || 5.52 || Trigger || 00527274
|-
| TRIP_OVERVIEW.fmx || 1.76 || Trip Waterfall || 00555144
|-
| TRIP_OVERVIEW.sql || 5.17 || Trip Waterfall || 00533620
|-
| TRM.sql || 5.230 || Trip manipulation package || 00577244
|-
| V_CURRENT_DRIVER_LIST.sql || 1.4 || View || 00525198
|-
| V_DRIVER_ORDERS.sql || 1.4 || View || 00525198
|-
| V_GEO_CONTACT.sql || 1.2 || View || 00469937
|-
| V_ORD_ORDER_CONTACT.sql || 1.5 || View || 00469937
|-
| V_ORD_ORDER_HEADER.sql || 1.24 || View || 00538412
|-
| V_ORD_ORDER_HEADER.sql || 1.25 || View || 00544876
|-
| V_ORD_ORDER_HEADER.sql || 1.26 || View || 00555163
|-
| V_ORD_ORDER_HEADER_CS.sql || 1.2 || View || 00558723
|-
| V_TRIP_OVERVIEW.sql || 1.24 || Trip View || 00555144
|-
| V_TRIP_OVERVIEW_ORD.sql || 5.15 || Trip/Order View || 00555144
|-
| V_VEHICLE_DETAILS.sql || 5.7 || View || 00534016
|-
| V_VEHICLE_DETAILS.sql || 5.8 || View || 00544876
|-
|}
|}


Line 212: Line 2,229:


= ADDITIONAL CHANGES =
= ADDITIONAL CHANGES =
== WCS ==
== WCS ==


A WCS change is required for the following logs:
There is no WCS change required.
* Log
OR


There are no WCS changes required.


== EPOD/T2A ==
== EPOD/T2A ==


An ePOD/T2A change is required for the following logs:  
An ePOD change is required for the following logs:  
* Log
 
OR
* Log 570824 &#45; Epod server v4.5.1.12 (CTY Only)


There are no ePOD/T2A changes required.


== MCS ==
== CTL ==


An MCS change is required for the following logs:  
An CTL change is required for the following logs:  
* Log
 
OR
* Log 525198
* Log 538412
* Log 469937
* Log 558723
* Log 572795


There are no MCS changes required.


== PORTAL/TTM ==
== PORTAL/TTM ==


A Portal change is required for the following logs:
There is no Portal change required.
* Log
 
OR


There are no Portal changes required.
== Manual ==


== EDI ==
'''Note:''' Version 5.22.1.1 of DP_PAR_API will need to be installed in the MAR databases.


An EDI change is required for the following logs:
'''Note:''' Version 5.38.1.1 of DP_PAR_API_STP will need to be installed in the STS databases.
* Log
OR


There are no EDI changes required.
'''Note:''' Nokmap.html should be released to /u03/######/webint/html.




</div>
</div>
[[Category:{{#var:Client}} PATCH]]
[[Category:{{#var:Client}} PATCH]]

Latest revision as of 12:55, 26 June 2025




Aptean Logo.png









Release Notes

CALIDUS TMS

5th Apr 2024 - 1.0
Reference: P046











































SUMMARY INTRODUCTION

INTRODUCTION

The main aim of this document is to provide CALIDUS TMS users with the level of detail required to accurately test all software included in the patch. The document also contains set-up and configuration details to enable the user to configure the system correctly for the new functionality to work.


GLOSSARY OF TERMS

Term Meaning
C-TMS Transport Management System
C-WMS Warehouse Management System
CR Change Request
C-WCS Warehouse Control System
C-ePOD Electronic Proof of Delivery
C-MCS Mobile Control System
C-TTM Track and Trace Management
EDI Electronic Data Interchange
TID Testing Issue Development, or Log


TESTING PROCESS

TIDs AND RESOLUTION

If there are any areas of the functionality that are not acceptable or do not meet the requirement specified in the Change Request then these should be expressed by raising a TID.


FINAL 'END TO END' TESTING

Prior to release to a production database, a full 'End to End' test is required on the test system by all sites using the database. Once this is signed off, a release date can be arranged.


AUTHORISATION

Authorisation from nominated release personnel only will be required when requesting a release to a production environment


CHANGE REQUESTS

Log Number: 00514663

Summary of Call Drop numbers and times not reset
Detail of Fix The trip will be validated and have its distances and times recalculated when a stop is deleted when its last order is unscheduled from the trip because it has been updated with a new scheduled date.
Set-up and Configuration No set-up/configuration required


Log Number: 00498981

Summary of Call Extend EPL_SERVICES_SUPPLIED to 255 characters
Detail of Fix EPL_SERVICES_SUPPLIED and SCH_ORD_ITEMS.SERVICE_SUPPLIED has been altered to accommodate 255 characters.
Set-up and Configuration No set-up/configuration required


Log Number: 00527152

Summary of Call Orders sent to Paragon for an invalid run number
Detail of Fix Orders and their locations will not advise Paragon via the API when they have a run number that is for a route code that does not send its orders to Paragon for planning.
Set-up and Configuration No set-up/configuration required


Log Number: 00527157

Summary of Call Resync error in API from Paragon
Detail of Fix Some queries have been changed for greater efficiency for the import API from Paragon and the triggering of the haulage activity for MIS.

Additionally, extensive auditing has been added to the process to read the message from Paragon to review the efficiency of the process.

Set-up and Configuration No set-up/configuration required


Log Number: 00520087

Summary of Call Unable to import Fixed Routes
Detail of Fix The record format and the field will be case sensitive to enable record formats with similar names to be processed.
Set-up and Configuration No set-up/configuration required


Log Number: 00530171

Summary of Call Recalculate the distance and time when an order is cancelled via the API
Detail of Fix The trip will be validated and have its distances and times recalculated when a stop is deleted when its last order is unscheduled from the trip because it has been cancelled via the API.
Set-up and Configuration No set-up/configuration required


Log Number: 00522350

Summary of Call Updates to Epod Web Service Audit Screen
Detail of Fix New field 'STATUS' has been added and previously existed column trip_id is renamed as reference and altered it as a LOV which gives a list of references from EWSA for better auditing purpose.
Set-up and Configuration No set-up/configuration required


Log Number: 00534416

Summary of Call Slow rate of processing the Paragon API for the runs (20978)
Detail of Fix The orders will be unscheduled directly from the TMP trips to improve the rate of processing.
Set-up and Configuration No set-up/configuration required


Log Number: 00529028

Summary of Call Generate Paragon ID for UNKNOWN locations (20979)
Detail of Fix The EDI parameter 'UPDATE_PARAGON_ID' for the 'API' process will be used to update the new locations for the orders with a Paragon ID and a delivery depot.

The UNKNOWN locations for the order will create new collection and delivery locations based on the postcode.

The Paragon ID will be based on the customer code and the location code.

The delivery depot for Paragon for the new location will be based on the planning depot for the planning region of the location for its postal region.

This planning depot will be used in preference to the depot code of the collection location for an order for a delivery, or to the depot code for the delivery location for an order for a collection.

Set-up and Configuration No set-up/configuration required


Log Number: 00536205

Summary of Call Import Fixed Routes to update the PAR_RUN decoded value
Detail of Fix The decoded value for the 'PAR_RUN' for the fixed routes will be inserted, updated or deleted for the route.
Set-up and Configuration No set-up/configuration required


Log Number: 00510487

Summary of Call No drop number provided for customers
Detail of Fix A new system parameter called 'TRM_3PL_SCHEDULE_NO_DROP' will be available to configure with a value of 'Y' to enable the orders for a location without a drop number for the route for Paragon to be added to the temporary 'TMP' trip for pre-planning.

The 'DL' stops will be added as drop number '498' and the 'PK' stops will be added as drop number '499'.

When this system parameter is not active, those orders will continue to display the audit message 'Cannot pre-plan no drop number available'.

Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
TRM_3PL_SCHEDULE_NO_DROP SYSTEM Y The orders for a location without a drop number for the route for Paragon will be added to the temporary 'TMP' trip for pre-planning.
TRM_3PL_SCHEDULE_NO_DROP SYSTEM N The orders for a location without a drop number for the route for Paragon will not be added to the temporary 'TMP' trip for pre-planning, they will continue to display the audit message 'Cannot pre-plan no drop number available'.


Log Number: 00537843

Summary of Call PCL trip created for a zero-drop number
Detail of Fix The zero-drop numbers will be assessed with the 'Send to Paragon' flag to create either a PCL trip for a non-Paragon route or a TMP trip for a Paragon route.

The zero-drop numbers will be set as stop numbers 498 and 499 on the same TMP trip as the planned drop numbers.

Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
TRM_3PL_SCHEDULE_NO_DROP SYSTEM Y The orders for a location without a drop number for the route for Paragon will be added to the temporary 'TMP' trip for pre-planning.
TRM_3PL_SCHEDULE_NO_DROP SYSTEM N The orders for a location without a drop number for the route for Paragon will not be added to the temporary 'TMP' trip for pre-planning, they will continue to display the audit message 'Cannot pre-plan no drop number available'.


Log Number: 00533620

Summary of Call Total of Tyres in the Trip Waterfall screen
Detail of Fix Change has been done to get_tyres function, to use the delivered quantity for Tyres(DL) column in waterfall screen, instead of what was planned to be delivered.
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
TRIP_OVERVIEW_CURRENT_TYRES SYSTEM N Use the current quantity of tyres in the Trip Waterfall screen (Y/N)


Log Number: 00539920

Summary of Call Audit Paragon for the STP version
Detail of Fix The auditing for Paragon will use the name of the EDI process to assess test 'AUDIT_WS' parameter.

The auditing will include the content of the message as well as the endpoint.

Set-up and Configuration No set-up/configuration required


Log Number: 00542201

Summary of Call Update merged TMP trip to be DELETED (24117)
Detail of Fix The TMP trips will be revalidated when an order is transferred to another another run number.

When an order is unscheduled from a TMP trip because it has a new run number, any empty stops on that trip will be deleted and the distance and time will be recalculated for the remaining stops.

An empty trip will have status DELETED.

Set-up and Configuration No set-up/configuration required


Log Number: 00479903

Summary of Call SCR 41: Always default removals from last inspected
Detail of Fix Web service package changed not to send the product details for removals
Set-up and Configuration No set-up/configuration required


Log Number: 02578219

Summary of Call Implement customer password standards in C-TMS instances
Detail of Fix New Software for validation of user passwords by profile
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
USE_SECURITY_PROFILES SYSTEM Y Activate Security Profiles for users


Log Number: 00550569

Summary of Call Orders for the collection desk are not scheduling
Detail of Fix The 'DSK' trips for the collection desk will be assessed for the orders by schedule to create a new trip or to add the order with a new stop to an existing trip.

Any trips for the collection desk that have become empty of orders and stops except a 'CL' stop will be updated to have new stops for the orders.

Set-up and Configuration No set-up/configuration required


Log Number: 00547839

Summary of Call Planning screen slow to refresh
Detail of Fix A system parameter exists called 'PLANNING_AUTO_SCHED_INACTIVE_DEPOTS' to store the inactive depots in quotation marks to accompany 'AUTO_SCHED_INACTIVE_DEPOTS' for the scheduling engine.

The quotation marks will enable the list to be assessed directly in the 'PLANNING' screen to exclude the orders for the inactive depots.

From and to locations for the collection and delivery orders will be checked against this list.

The number of orders will be reduced and the query of the unscheduled orders will be performed much more quickly.

Set-up and Configuration No set-up/configuration required


Log Number: 00548540

Summary of Call Increase the number of days in the range for the weekly Paragon keys
Detail of Fix Increased number days a key spans
Set-up and Configuration No set-up/configuration required


Log Number: 00550047

Summary of Call New delivery dates should update Paragon with a milestone (24318)
Detail of Fix The new schedule for the delivery date for the order will delete the order from the previous schedule in Paragon and add it to the new schedule in Paragon with its collection or delivery location as required.

The new system parameter 'OMS_UPDATE_SCHEDULE_TO_TRIP' will update the time windows for the orders that exist on a trip when the schedule of the trip is changed in the 'Planning' screen.

When this system parameter is set to 'Y', the time windows of the orders on the trip will be offset to match the number of days that have changed for the schedule of the 'RADIAL' trip.

An instruction to unschedule the order for the change of the delivery date will not occur when that date is offset with the schedule of the order itself.

Set-up and Configuration No set-up/configuration required


Log Number: 00551639

Summary of Call Create the Paragon ID for new orders
Detail of Fix The Paragon ID and the delivery depot will be created for an existing location when it is used for an order.

The existing Paragon ID and the delivery depot will be retained for an existing location when it is used for an order.

Set-up and Configuration No set-up/configuration required


Log Number: 00469937

Summary of Call SCR 14: Multiple contacts, identifying who gets the EPOD report
Detail of Fix This functionality will change CTMS and CTL to allow the maintenance and selection of multiple contacts and allow the users to define which contacts will be used for the tracking link, for the work report email and for contact options on the mobile device.
Set-up and Configuration No set-up/configuration required


Log Number: 00516374

Summary of Call SCR 44: Job Ticket to display a free-text field to add to service report to add "Actual Customer"
Detail of Fix Development to display the 'Actual Customer' in CTL and on the epod pod note.
Set-up and Configuration No set-up/configuration required


Log Number: 00554583

Summary of Call Error handling in Paragon API import
Detail of Fix A plan for either the current schedule or the next schedule can be imported via the Paragon API.
Set-up and Configuration No set-up/configuration required


Log Number: 00555143

Summary of Call Set PAR trips to use the time to depart from not arrive at the depot
Detail of Fix The Paragon API interface for STP will set the planned arrival and departure times at the depot based on the values that are received:

Planned Arrival Time: TRIPSTART

Planned Departure Time: TRPSRCDEPOTDEP or TRPDSTDEPOTDEP

If the Planned Arrival Time is greater than or equal to the Planned Departure Time, then 30 minutes will be deducted from the Planned Departure Time to set the Planned Arrival Time.

At present, TRIPSTART equals TRPSRCDEPOTDEP and TRPDSTDEPOTDEP is NULL, therefore the Planned Arrival Time and the Start Time of the trip will become TRPSRCDEPOTDEP minus 30 minutes.

Those values will be consistent with the requirements from the recent conference call and they will account for any different values that are received from Paragon.

Set-up and Configuration No set-up/configuration required


Log Number: 00555144

Summary of Call Slow processing in the Waterfall screen
Detail of Fix The Trip Waterfall screen will call only those functions that are required to display for the configured layout on the screen.

The rate of processing the queries will be quicker as will the navigation between the tab pages.

Set-up and Configuration No set-up/configuration required


Log Number: 00554568

Summary of Call Update Paragon with the LOC on the new schedule (24348)
Detail of Fix Paragon should receive a LOC record for the location of the order when the order is placed on a new schedule for planning.

The order will be deleted for its old location and added for planning in Paragon.

Set-up and Configuration No set-up/configuration required


Log Number: 00563001

Summary of Call Delete old call for Paragon
Detail of Fix The orders and their locations will advise Paragon to add, update or delete them when they are changed in CTMS.

Uses the old location when deleting the order from Paragon.

Set-up and Configuration No set-up/configuration required


Log Number: 00567392

Summary of Call Additional error handling for Paragon API for the STP version
Detail of Fix Additional error handling is included to ensure that a locked trip does not prevent other trips being updated to TENDERED status as required.

The additional error handling exists for these post-update procedures:

- Update the trips from PLANNED to TENDERED status for Fleet carriers.

- Update the TENDERED trips for Fleet carriers with a rate.

- Update the route code for trips for 3PL carriers.

- Update the route code for trips for non-3PL carriers.

- Update the trips for the 3PL carrier with a rate and set to TENDERED status.

- Delete any empty trips for the current and future schedules.

Set-up and Configuration No set-up/configuration required


Log Number: 00568624

Summary of Call Paragon not receiving the data for special runs (GDSP03) - (25103)
Detail of Fix Excludes the early delivery date and time from the assessment of the current date and time for the schedule for Paragon.
Set-up and Configuration No set-up/configuration required


Log Number: 00484537

Summary of Call Paragon Count of non-tyre Products
Detail of Fix A new reference called 'CALL.USER03' will be sent to Paragon for the STS databases.

Note that there will be a task to implement the new call for Paragon when Paragon is configured to use the data.

This reference will include the number of items that are not classed as tyres.

The tyres will be identified with a DU type that begins with the letter 'T'.

Set-up and Configuration No set-up/configuration required


Log Number: 00571947

Summary of Call New location for a variant address by ID
Detail of Fix The variant addresses will not update the location for the ADDRESS_ID when a variant address is not found for the ADDRESS_EXT_REF.

The ADDRESS_ID is provided for permanent locations but it is not provided for temporary address.

The variant addresses can be provided with or without an ADDRESS_ID but they do require an ADDRESS_EXT_REF.

The unknown locations will continue to create a new location when a matching address for an existing location is not found.

Set-up and Configuration No set-up/configuration required


Log Number: 00575228

Summary of Call Work not going from Paragon to CTMS
Detail of Fix A new EDI parameter called 'PAR_SCHEDULES' is available to assess the number of schedules in the future to retrieve from Paragon via the API.

This EDI parameter will be effective for the versions of the API by week and by day.

It is expected to be set for the EDI process that is called 'Get_Paragon'.

Set-up and Configuration No set-up/configuration required


Log Number: 00578389

Summary of Call Work not going from Paragon to CTMS for STP
Detail of Fix A new EDI parameter called 'PAR_SCHEDULES' is available to assess the number of schedules in the future to retrieve from Paragon via the API.

This EDI parameter will be effective for the versions of the API by week and by day.

It is expected to be set for the EDI processes that are called 'Get_Paragon' by depot.

Set-up and Configuration No set-up/configuration required


Log Number: 02713995

Summary of Call Weights incorrect
Detail of Fix Development which introduces new column for called PACK_QUANTITY to store decimal values up to 2 digits for weights, so the whole weight can be seen without truncating the value.
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
USE_PACK_QUANTITY SYSTEM Y/N Use Decimal Pack quantity and allowed values will be (Y/N) which will control the additional functionality


Log Number: 00525198

Summary of Call CTL Call Logging - Can't raise a top-up transfer against a service-only job
Detail of Fix Fixed refresh of driver list for Top-Up transfers. Filtered out inactive drivers. Filtered out DELIVERED and FAILED orders from the Orders list.
Set-up and Configuration No set-up/configuration required


Log Number: 00525182

Summary of Call Additional messages sent after order completed
Detail of Fix Added system parameter to prevent ORD/COL messages being sent after a DEL for the same order/trip
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
PREVENT_ORD_COL_AFTER_DEL COST CENTRE Y Prevent ORDS and COLS after a DEL message


Log Number: 00517921

Summary of Call CTMS-EPOD INTERFACE - Removal tyres have description/price of installed product
Detail of Fix The Removal tyres now doesn't contain description, price or location.
Set-up and Configuration No set-up/configuration required


Log Number: 00524462

Summary of Call CTMS EPOD Interface - Tyre pressure and tread depth getting reset
Detail of Fix Ignore any work type R records when updating tyres
Set-up and Configuration No set-up/configuration required


Log Number: 00524481

Summary of Call Vehicle Search Webservice - returning inspection wrong
Detail of Fix Trailer search corrected
Set-up and Configuration No set-up/configuration required


Log Number: 00527142

Summary of Call Epod Wrong product code being sent on the install line
Detail of Fix Ensure that product code is updated when response received from epod.

EPOD DEVICE Make sure that the item must be deleted first from the list, then can be re-added. Ensured that the device will not allow creation of a new Install/Remove/Other line for a wheel position where that wheel position already exists on the job and is not deleted.

Set-up and Configuration No set-up/configuration required


Log Number: 00527274

Summary of Call TMS/EPOD. No Install lines for service - prevents Elucid from applying charges
Detail of Fix Ensure COL/DEL messages sent in correct sequence for all orders
Set-up and Configuration No set-up/configuration required


Log Number: 00528183

Summary of Call Issue with DEL message
Detail of Fix Items not received back for debrief from epod have to deliver and delivered quantity set to 0
Set-up and Configuration No set-up/configuration required


Log Number: 00528738

Summary of Call TMS Fleet Inspection Missing service items
Detail of Fix Added vehicle to items check to ensure items created for all vehicles
Set-up and Configuration No set-up/configuration required


Log Number: 00528842

Summary of Call Missing Van Stock Wheel
Detail of Fix Added product to check when creating items
Set-up and Configuration No set-up/configuration required


Log Number: 00528195

Summary of Call Add the depot to the route details page in location maintenance screen.
Detail of Fix The inbound process to update the routes from Paragon will be run for the extracted data for the current process.

Any other unprocessed records for the depot will not be processed.

The 'Location Maintenance' screen will display the delivery depot in the 'Route Dtls' tab page for these routes from Paragon.

The records are sorted by 'Depot Number', 'Route Code' and 'Drop Number'.

Set-up and Configuration No set-up/configuration required


Log Number: 00530050

Summary of Call API Export - COL sent after DEL
Detail of Fix Change order messages processed in DP_EXPORT_EVENTS
Set-up and Configuration No set-up/configuration required


Log Number: 00528762

Summary of Call Missing COP225 in ORDER_SERVICES
Detail of Fix Create additional services from epod
Set-up and Configuration No set-up/configuration required


Log Number: 00527603

Summary of Call TS3 upload
Detail of Fix The system parameter 'PAR_AUDIT' can be set to 'Y' to include auditing of the import process in the STP version of the Paragon API.

The system parameter 'PARAGON_RUNNING' will be used to indicate if the STP version of the Paragon API is importing data - it will not be editable by the users.

The import process in the STP version of the Paragon API will set the orders for manual scheduling when they are temporarily unscheduled from their temporary trips or their Paragon trips.

Then, those orders will not be reprocessed by the 3PL scheduling engine.

The 3PL scheduling engine will not start when the Paragon API is processing.

Then, these processes will not be updating concurrently any of the same trips and orders; plus the rate processing should be improved.

However, the import process in the STP version of the Paragon API will not wait should the 3PL scheduling engine be processing.

Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
PAR_AUDIT SYSTEM Y The STP version of the Paragon API will write audit records for the import process.
PAR_AUDIT SYSTEM N The STP version of the Paragon API will not write audit records for the import process.
PARAGON_RUNNING SYSTEM Y The STP version of the Paragon API is importing data.
PARAGON_RUNNING SYSTEM N The STP version of the Paragon API is not importing data.


Log Number: 00524586

Summary of Call Vehicle serviced at roadside should not change the location against that vehicle.
Detail of Fix Fixes for new vehicle creation for call Logging and removed update on Current_location_id for RTC
Set-up and Configuration No set-up/configuration required


Log Number: 00528718

Summary of Call Orders on wrong trip and incorrect drop numbers being retained for locations
Detail of Fix Optimised the import process of the route details from Paragon.

The orders will be assigned to a trip for the advised route although the order in trip position 1 has not been used to create a new trip for the route.

The route details to update the drop numbers from Paragon for the locations will refer to the current archive id and they will not include any historic transactions that remain for the depot.

Set-up and Configuration No set-up/configuration required


Log Number: 00533067

Summary of Call GDCOL runs not synching to CTMS (21886)
Detail of Fix The 'DSK' trips will be assessed for the orders by schedule to create a new trip, or to add the order to an existing trip, for the run number for the depot.

An existing trip will either create a new stop or use an existing stop.

An order for a collection desk must be for a route of type 'COLLECT_DESK'.

Set-up and Configuration No set-up/configuration required


Log Number: 00533991

Summary of Call Vehicle Maintenance Last Inspection field
Detail of Fix Fixed C-TMS when performing the last inspection date calculation. If the inspection date was set as more than 1 month and the start date was for the first day of the month it was setting the end date for each period incorrectly.
Set-up and Configuration No set-up/configuration required


Log Number: 00537198

Summary of Call Ampersand characters not being 'escaped'
Detail of Fix Ampersands in tyre serial numbers replaced with escaped value
Set-up and Configuration No set-up/configuration required


Log Number: 00524191

Summary of Call Cancelling an order in CTL Call Logging should ask for and set Order Reason Codes
Detail of Fix Amend TYRE_ORDS report to use Non Conformance reason codes. Users will need to create a new copy of the ORS extract to use the changes
Set-up and Configuration No set-up/configuration required


Log Number: 00538804

Summary of Call Control records not being updated after send to Elucid
Detail of Fix Ensure that all control records are updated in the correct code area
Set-up and Configuration No set-up/configuration required


Log Number: 00540264

Summary of Call Orders with different depot starting point do not plan in Paragon (22118)
Detail of Fix A new EDI parameter called 'USE_RUN_DEPOT' is available to use the depot for the route for the run number of the order in preference to the depot of the collection/delivery location of the RET/SLS/ order.

When this parameter is 'Y', the depot for the route for the run number will be the depot to send to Paragon via the API.

This parameter is expected to the set for the 'Paragon_Outbound' process.

Set-up and Configuration No set-up/configuration required


Log Number: 00534016

Summary of Call FIA report showing tyre brands as 'other'
Detail of Fix Fixed the issue by changing view to allow separate entries with OTHER manufacturers.
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
USE_PACK_QUANTITY SYSTEM Y/N Use Decimal Pack quantity and allowed values will be (Y/N) which will control the additional functionality


Log Number: 00538191

Summary of Call Remaining characters not being escaped (exception ampersand)
Detail of Fix Added CDATA when the new EDI parameter INCLUDE_CDATA_TAG is active, which will control the escaping of special characters like &.
Set-up and Configuration No set-up/configuration required


Log Number: 00542256

Summary of Call Customer export from Elucid
Detail of Fix The customers from Elucid can store up to 255 characters for the 'SlaUrl' and 'PreferredBrand'.
Set-up and Configuration No set-up/configuration required


Log Number: 00538855

Summary of Call Services Supplied Issue
Detail of Fix Fixed the issue with the creation of unnecessary service_id records.
Set-up and Configuration No set-up/configuration required


Log Number: 00536498

Summary of Call Collection job not sent to ePOD
Detail of Fix Collection job has been sent to EPOD for I(INSTALL) if services supplied doesn't include COP, MAJ and collection is sent for Van Stock lines.
Set-up and Configuration No set-up/configuration required


Log Number: 00546323

Summary of Call Call logging vehicle location
Detail of Fix Fixed creation of rvcl for new vehicles in Call Logging.
Set-up and Configuration No set-up/configuration required


Log Number: 00544876

Summary of Call Vehicle config not allowing tyre position selection
Detail of Fix Fixed the views to use RTC and out of sync issue of RT and RTC tables.
Set-up and Configuration No set-up/configuration required


Log Number: 00546768

Summary of Call Portal, jobs showing as Part Delivered
Detail of Fix Only send Work Type R records to portal if the AKA code is populated
Set-up and Configuration No set-up/configuration required


Log Number: 00552783

Summary of Call Collection job not sent to ePOD
Detail of Fix Collection jobs will be sent for any order which contains Van stock which is not currently at the delivery location of the order
Set-up and Configuration No set-up/configuration required


Log Number: 00554263

Summary of Call Optimization of the code: Fix for SCR-14 (469937)
Detail of Fix The code has been modified to handle the issues that occurred in the previous versions.
Set-up and Configuration No set-up/configuration required


Log Number: 00543998

Summary of Call Elucid Interface 400/500 fixes
Detail of Fix Improvements in Error Handling are required when messages are rejected due to 400 or 500 error.
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
WS_NUM_OF_RETRIES_ALLOWED SYSTEM 3 Max number of times a record will be sent to a web service endpoint


Log Number: 00555163

Summary of Call CTL Order display for Orders with No Vehicle
Detail of Fix Fixed v_ord_order_header to select orders differently.
Set-up and Configuration No set-up/configuration required


Log Number: 00559726

Summary of Call 500 errors from elucid not updating int-xml_control table
Detail of Fix Update number of tries on 500 errors
Set-up and Configuration No set-up/configuration required


Log Number: 00542530

Summary of Call EPOD, Twinning
Detail of Fix Process Tyre Swaps to update correctly
Set-up and Configuration No set-up/configuration required


Log Number: 00560125

Summary of Call Invalid Service codes sent to Elucid
Detail of Fix Reinitialise counters when creating/updating services
Set-up and Configuration No set-up/configuration required


Log Number: 00561946

Summary of Call Tyre Swap not swapping correct tyres (Twinning) UAT Ref 123
Detail of Fix Add customer details to swap queries
Set-up and Configuration No set-up/configuration required


Log Number: 00562054

Summary of Call Multiple Contacts - Emails from Portal.
Detail of Fix Added values to insert
Set-up and Configuration No set-up/configuration required


Log Number: 00564461

Summary of Call Location screen issue
Detail of Fix Fix to Location Screen
Set-up and Configuration No set-up/configuration required


Log Number: 00564569

Summary of Call Missing email
Detail of Fix Updated the logic to insert LOCATION details even when RecipientMobile/Phone is not supplied.
Set-up and Configuration No set-up/configuration required


Log Number: 00563558

Summary of Call Error On Incoming Message From ePOD
Detail of Fix Amendment to tyre swapping to avoid failed to update service product.
Set-up and Configuration No set-up/configuration required


Log Number: 00569051

Summary of Call Issues with Trye Swap linked to 561946 (CT ID 123)
Detail of Fix TYRE_SWAP and NEW_PRODUCT tags can appear at different levels in the inbound message code added to account for this
Set-up and Configuration No set-up/configuration required


Log Number: 00532043

Summary of Call Incorrect times displaying
Detail of Fix Stop times will be updated every time for epod mode DELTYPE
Set-up and Configuration No set-up/configuration required


Log Number: 00567195

Summary of Call Config Change - UAT ref 204
Detail of Fix Updated Vehicle type passed in message from epod.
Set-up and Configuration No set-up/configuration required


Log Number: 00570437

Summary of Call Customer Upload not extracting email address correctly - UAT 216
Detail of Fix Updated the logic to update the email address of a contact even when other details are NULL.
Set-up and Configuration No set-up/configuration required


Log Number: 00539653

Summary of Call PORTAL inspection depths UAT 59
Detail of Fix Made the change to not to store 0 tread depth against the last known tyre details against that position.
Set-up and Configuration No set-up/configuration required


Log Number: 00570824

Summary of Call Authority Ref not appearing on some jobs. UAT 213
Detail of Fix Add authority code to EPL_CODE_3 tag
Set-up and Configuration No set-up/configuration required


Log Number: 00572795

Summary of Call Credit Limits
Detail of Fix Check Customer on hold status when adding items to an order
Set-up and Configuration No set-up/configuration required


Log Number: 00573163

Summary of Call Config issue on Epod device
Detail of Fix Made the change to vehicle search to return values from RTC.
Set-up and Configuration No set-up/configuration required


Log Number: 00580395

Summary of Call Elucid Configuration - proxy setup
Detail of Fix Proxy value added for communication with Elucid
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
ELUCID_API_PROXY System Y/N Use Proxy sever for Elucid


Log Number: 02792680

Summary of Call Oracle financials OF extract R12 format (WREQ0087544)
Detail of Fix The 'Tax Amount' for the 'R12' format will be included as '0' when the VAT code is 'Z' for 'Zero Rated'.

The invoices in the R12 format will be included by VAT code.

Set-up and Configuration No set-up/configuration required



SUPPORT INCIDENTS

Log Number: 00538105

Summary of Call Change Password option in ACC_CTRL
Detail of Fix CHANGE_PW has been modified to not accept passwords with @ and "
Set-up and Configuration No set-up/configuration required


Log Number: 00549717

Summary of Call Collection job not sent to ePOD
Detail of Fix Fixed the issues reported in previous version about collection job not being sent in certain conditions.
Set-up and Configuration No set-up/configuration required


Log Number: 03529183

Summary of Call Web Service order updates are failing to update the forecast (INC58464329)
Detail of Fix The update process previously failed due to mismatched condition statements when records were submitted with action 'A'. Additionally, records with timestamps within a 2-minute interval (00:59:59 to 01:00:00) of an hour change were not properly handled, leading to query failures in identifying duplicate records.

Both issues have been resolved in the latest fix. The logic has been adjusted to handle order amendments and correct any mistakes from the previous version. Now, records within a 2-minute interval are selected irrespective of the hour, and a new check has been added to mark duplicate orders as ""CANCELLED"".

Set-up and Configuration No set-up/configuration required


Log Number: 02769136

Summary of Call CTMS Collection date (INC56773319)
Detail of Fix Temporary variables for EARLY/LATE_AVAIL have been reset so that when an empty tag is provided it will not take the previously stored value.
Set-up and Configuration No set-up/configuration required



TID CHANGES

Log Number: 02766658

Summary of Call Change Password option in ACC_CTRL
Detail of Fix Access control has been modified to allow users to create usernames containing special characters, change passwords that may include special characters, and delete users with special characters in their names.

Access control has been modified to restrict @ and " in username and passwords while creating/updating.

Set-up and Configuration No set-up/configuration required


Log Number: 00538412

Summary of Call Data flow Review
Detail of Fix Fixed C-TMS view to retrieve orders more efficiently. Fixed CTL customer services screen to filter by customer correctly.
Set-up and Configuration No set-up/configuration required


Log Number: 02742281

Summary of Call Planning screen slowing issues
Detail of Fix Added quotes to schedule to improve speed
Set-up and Configuration No set-up/configuration required


Log Number: 00545159

Summary of Call Order placed to wrong address on the same account (24348)
Detail of Fix The EDI parameter for the 'API' process called 'UNSCHED_NEW_DATE' has been changed to be 'UNSCHED_NEW_DATA' to assess not only the new date but also the new location and the new run number.

The trips will be 'DELETED' should they become empty of orders.

The order will now be unscheduled and reset for the 3PL scheduling engine to reprocess to a new trip.

Set-up and Configuration No set-up/configuration required


Log Number: 00543948

Summary of Call Special Runs, change to del date
Detail of Fix The auditing for the order when 'Trip XXX-XXXXXXXX moved to a different schedule from XXXXXX to XXXXXX' will be used to identify when the schedule of the order has been changed with its late delivery date when its trip has been moved to a new schedule.

Paragon will be updated with the new schedule for the order and its location for the run number of the route.

Set-up and Configuration No set-up/configuration required


Log Number: 02764788

Summary of Call Disable trailer type send to Paragon
Detail of Fix Added the Disable Paragon check box to the trailer types tab page and to the new/edit screens.
Set-up and Configuration No set-up/configuration required


Log Number: 02710742

Summary of Call Webfleet integration
Detail of Fix Added the exceptional handling to all the programs which contain the control record loops.
Set-up and Configuration No set-up/configuration required


Log Number: 02690067

Summary of Call Data being overridden / Removed
Detail of Fix The 'DUN Inventory Transaction Report' will include the trunk trips that have been used in scanning to load and unload the items.
Set-up and Configuration No set-up/configuration required


Log Number: 02818748

Summary of Call CTMS LOAD messages to JDA missing full order ref
Detail of Fix When rebooked order is processed then only external ref is trimmed, for example _R1,_R2. And is also depends on parameter 'ORD_RBO_PREFIX'.

If external ref has anything followed after _R and if its not a number then the whole external ref is sent in SO_REF tag.

Set-up and Configuration No set-up/configuration required


Log Number: 00534889

Summary of Call Show Map function failing
Detail of Fix HTML corrected
Set-up and Configuration No set-up/configuration required


Log Number: 02691631

Summary of Call Paragon CSV Import Issues
Detail of Fix Import logic has been amended to pick up NEW orders which have collection on schedule date. Previous error message has been altered to get a warning so user can choose to import collection orders or not.
Set-up and Configuration No set-up/configuration required


Log Number: 02683404

Summary of Call Paragon Import
Detail of Fix The 'Loading Management' screen displays a new tick box called 'Include Completed Trips' to enable the trips to be included or excluded when they have a status of 'COMPLETED'.

This box will be ticked by default.

A new system parameter called 'PAR_DUN_TRUNK_CUTOFF_TIME' can be configured at the system level to set a cut-off time to apply to trunk trips to use the current schedule for the day.

The import process from Paragon for the 'DUN' format will refer to the new system parameter to offset the date to derive the schedule for the processing of the trunk trips.

If 'PAR_DUN_TRUNK_CUTOFF_TIME' is set to '04:00' and the current system time is '01:00' then the schedule will not be derived for the current date but for the previous date as if the process for the route/drop had been run on the previous evening."

Set-up and Configuration No set-up/configuration required


Log Number: 02910494

Summary of Call Trunks for 27th were not generated
Detail of Fix A new system parameter called 'PAR_DUN_TRUNK_OFFSET_DAYS' is available to store the number of days for which trunk trips will be assessed for the radial trips that are created by Paragon.

A default value of 4 days will be used but the number of days will be configurable to assess the non-working days for the depot.

This system parameter can be used to account for the non-working days during the period of the holiday seasons.

The system parameter 'PAR_DUN_TRUNK_CUTOFF_TIME' will start to assess the current date prior to the cutoff time, or from tomorrow after the cutoff time.

Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
PAR_DUN_TRUNK_OFFSET_DAYS SYSTEM NUMERIC The specified number of days will be used to assess the trunk trips for the radial trips to account for the non-working days in the calendar.
PAR_DUN_TRUNK_OFFSET_DAYS SYSTEM NULL/NON-NUMERIC A default number of 4 days will be used as per the current functionality.


Log Number: 00554721

Summary of Call Planning screen new configuration in test environment
Detail of Fix Fixed the Planning screen to allow the order schedule search dropdown list to change when the trip schedule search dropdown list changes.
Set-up and Configuration No set-up/configuration required


Log Number: 00561665

Summary of Call Planning screen new configuration in test environment
Detail of Fix Fix to Planning screen to search orders correctly.
Set-up and Configuration No set-up/configuration required


Log Number: 02728730

Summary of Call XML file format is incorrect
Detail of Fix Modified the code to extend the length of the fields.
Set-up and Configuration No set-up/configuration required


Log Number: 00562331

Summary of Call Customers are created without group and epod should be enabled
Detail of Fix New EDI parameter called UPD_CUST_ENABLE_EPOD has been added to JAK_INBOUND_ORDERS which when set will enable EPOD for all new customers created and to existing customers if they are used to create orders.
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
UPD_CUST_ENABLE_EPOD EDI Default N When set to Y, then customers will have EPOD enabled.


Log Number: 00562303

Summary of Call Not going through to CTMS
Detail of Fix Uses the first ten characters of the driver ID from Paragon for a new driver ID in CTMS.
Set-up and Configuration No set-up/configuration required


Log Number: 00560600

Summary of Call Paragon not receiving the data for special runs - GDSP03 - (25103)
Detail of Fix The next active day of the week will be used when the order is sent to Paragon and the advised day is in the past.
Set-up and Configuration No set-up/configuration required


Log Number: 00553397

Summary of Call HERE Data Services
Detail of Fix Updated the HERE processes to use new procedures
Set-up and Configuration
New Parameters
Parameter Name Config Level Setting Value Result
GEO_NLP_USE_ALTERNATE SYSTEM Y/N Alternate URL and Proxy will be used
GEO_NLP_ALT_PROXY SYSTEM IP address of Proxy IP Address for Proxy Server


Log Number: 03008712

Summary of Call API Order duplicated for multiple stores with the same PO for the same store
Detail of Fix Due to API concurrent processing (rare occurrence) duplicate orders were created, to resolve it the latest record is marked as failure with validation error and the earliest one is processed to create the order.

Additional change is made to avoid duplicate orders being created in same minute, ignoring time stamp on seconds.

Observed that duplicate orders were created with gap of 12 seconds so added logic to ignore seconds and consider only same hour and minute.

Set-up and Configuration No set-up/configuration required


Log Number: 00565562

Summary of Call Trips being stuck in planned status
Detail of Fix Additional error handling is included to ensure that a locked trip does not prevent other trips being updated to TENDERED status as required.

The additional error handling exists for these post-update procedures:

Update the trips from PLANNED to TENDERED status for Fleet carriers.

Update the TENDERED trips for Fleet carriers with a rate.

Update the route code for trips for 3PL carriers.

Update the route code for trips for non-3PL carriers.

Update the trips for the 3PL carrier with a rate and set to TENDERED status.

Delete any empty trips for the current and future schedules.

Set-up and Configuration No set-up/configuration required


Log Number: 00543919

Summary of Call Address Update (24288)
Detail of Fix A new EDI parameter called 'USE_VARIANT_ADDRESS' will be introduced to the 'API' process to control the new functionality to create new locations with temporary variant addresses: the new functionality will be active when the value of the EDI parameter is 'Y'.

The new functionality will apply to addresses that are provided for an external reference.

Set-up and Configuration No set-up/configuration required


Log Number: 00540719

Summary of Call Send to Paragon request (21702)
Detail of Fix A new function called 'TRM_SEND_TO_PARAGON' is available for the users via their groups.

The new function called 'TRM_SEND_TO_PARAGON' will be used to display and enable the new menu option called 'Send to Paragon' in the trip tree in the 'Planning' screen.

The new option will be present between 'Re-send PO Message' and 'Debrief Trip' when it is enabled.

The system parameters called 'TRM_TREE_ROUTE' and 'TRM_TREE_FORMAT' will be assessed by a similar method to how they are assessed in the 'Planning' screen for the range of schedules for the order well.

These system parameters will be found that is active for a cost centre when the user has access to 'ALL' cost centres or to multiple cost centres.

Then the route code may be displayed in the specified format based on these system parameters.

Set-up and Configuration No set-up/configuration required


Log Number: 00572113

Summary of Call API Key Incorrect for here Maps
Detail of Fix API key updated
Set-up and Configuration No set-up/configuration required


Log Number: 00558723

Summary of Call CTL screen takes too long to load
Detail of Fix Separated the views used by customer services and call logging.

I still recommend that we need to cleardown orders at status INVALID and that they will need to either cancel them or process them every day.

Set-up and Configuration No set-up/configuration required


Log Number: 00577244

Summary of Call Order issue in Paragon
Detail of Fix Orders which are added to DSK or PCL trips will not advise Paragon to delete them from the planning unless they have been advised previously to add them to the planning.
Set-up and Configuration No set-up/configuration required



MODULES DELIVERED

Module Name Version No Description Log Number
ACC_CTRL.fmx 2.57 Access control maintenance 02766658
ACC_CTRL.fmx 2.59 Access control maintenance 00538105
ACC_CTRL.fmx 2.63 Access control maintenance 02578219
ADM.sql 5.16 Administrator package containing various DB utils 02578219
AT_GEO_CONTACT_469937.sql 1.1 AT Script 00469937
AT_GEO_ROUTE_DTLS_00528718.sql 1.1 AT Script 00528718
AT_INT_XML_CONTROL_543998.sql 1.1 AT Script 00543998
AT_INT_XML_ORD_DETAILS_0271399 1.1 AT Script 02713995
AT_SCH_ORD_INFORMATION_469937.sql 1.1 AT Script 00469937
AT_SCH_ORD_ITEMS_02713995.sql 1.1 AT Script 02713995
AT_SCH_ORD_ITEMS_498981.sql 1.1 AT Script 00498981
BDM.fmx 2.110 Business Data Form 00548540
CHANGE_PW.fmx 2.12 Change Password 02578219
CHANGE_PW.fmx 2.13 Change Password 00538105
CT_SECURITY_PROFILES_02578219.sql 1.1 CT Script 02578219
DATA_ADM_FUNCTION_540719.sql 1.1 Data Script 00540719
DATA_ADM_MSEL_FORM_PARAM_02713995.sql 1.1 Data Script 02713995
DATA_ADM_SYSTEM_PARAM_00510487.sql 1.1 Data Script 00510487
DATA_ADM_SYSTEM_PARAM_00547839.sql 1.1 Data Script 00547839
DATA_ADM_SYSTEM_PARAM_02578219.sql 1.1 Data Script 02578219
DATA_ADM_SYSTEM_PARAM_02683404.sql 1.1 Data Script 02683404
DATA_ADM_SYSTEM_PARAM_02713995.sql 1.1 Data Script 02713995
DATA_ADM_SYSTEM_PARAM_02910494.sql 1.1 Data Script 02910494
DATA_ADM_SYSTEM_PARAM_469937.sql 1.1 Data Script 00469937
DATA_ADM_SYSTEM_PARAM_513456.sql 1.3 Data Script 00553397
DATA_ADM_SYSTEM_PARAM_516374.sql 1.2 Data Script 00516374
DATA_ADM_SYSTEM_PARAM_525182.sql 1.1 Data Script 00525182
DATA_ADM_SYSTEM_PARAM_527603.sql 1.1 Data Script 00527603
DATA_ADM_SYSTEM_PARAM_533620.sql 1.1 Data Script 00533620
DATA_ADM_SYSTEM_PARAM_543998.sql 1.1 Data Script 00543998
DATA_ADM_SYSTEM_PARAM_550047.sql 1.1 Data Script 00550047
DATA_ADM_SYSTEM_PARAM_572113.sql 1.1 Data Script 00572113
DATA_ADM_SYSTEM_PARAM_580395.sql 1.1 Data Script 00580395
DATA_ADM_SYSTEM_PARAM_CONFIG_516374.sql 1.2 Data Script 00516374
DATA_ADM_SYSTEM_PARAM_CONFIG_525182.sql 1.1 Data Script 00525182
DATA_ADM_USER_PARAM_TYPE_02578219.sql 1.3 Data Script 02578219
DATA_EDI_PROCESS_TRIGGERS_00538191.sql 1.1 Data Script 00538191
DATA_EDI_PROCESS_TRIGGERS_545159.sql 1.1 Data Script 00545159
DATA_EDI_PROCESS_TRIGGERS_562331.sql 1.1 Data Script 00562331
DATA_IMP_FIELD_00520087.sql 1.1 Data Script 00520087
DATA_ORACLE_PROFILES_02578219.sql 1.3 Data Script 02578219
DATA_ORS_MASTER_DATA_02713995.sql 1.3 Data Script 02713995
DATA_ORS_MASTER_DATA_524191.sql 1.1 Data Script 00524191
DATA_ORS_SQL_524191.sql 1.1 Data Script 00524191
DATA_SECURITY_PROFILES_02578219.sql 1.1 Data Script 02578219
DP_3PL_SCHED.sql 5.11 3PL Scheduling Engine Database Package 00527603
DP_3PL_SCHED.sql 5.12 3PL Scheduling Engine Database Package 00533067
DP_3PL_SCHED.sql 5.13 3PL Scheduling Engine Database Package 00510487
DP_3PL_SCHED.sql 5.14 3PL Scheduling Engine Database Package 00537843
DP_3PL_SCHED.sql 5.15 3PL Scheduling EngineDatabase Package 00550569
DP_3PL_SCHED.sql 5.16 3PL Scheduling Engine Database Package 00555143
DP_CSV_DUN.sql 5.56 Client specific CSV extracts 02690067
DP_CTMS_IMPORT.sql 5.35 API Import Database Package 00514663
DP_CTMS_IMPORT.sql 5.36 API Import Database Package 00527152
DP_CTMS_IMPORT.sql 5.37 API Import Database Package 00530171
DP_CTMS_IMPORT.sql 5.38 API Import Database Package 00529028
DP_CTMS_IMPORT.sql 5.40 API Import Database Package 00542256
DP_CTMS_IMPORT.sql 5.42 API Import Database Package 02713995
DP_CTMS_IMPORT.sql 5.43 API Import Database Package 00545159
DP_CTMS_IMPORT.sql 5.44 API Import Database Package 00551639
DP_CTMS_IMPORT.sql 5.45 API Import Database Package 00562054
DP_CTMS_IMPORT.sql 5.46 API Import Database Package 00563001
DP_CTMS_IMPORT.sql 5.47 API Import Database Package 00564569
DP_CTMS_IMPORT.sql 5.48 API Import Database Package 00543919
DP_CTMS_IMPORT.sql 5.49 API Import Database Package 00570437
DP_CTMS_IMPORT.sql 5.50 API Import Database Package 00571947
DP_CUST_SERV.sql 1.86 Customer Service Package 00524586
DP_CUST_SERV.sql 1.87 Customer Service Package 00546323
DP_CUST_SERV.sql 1.89 Customer Service Package 00469937
DP_CUST_SERV.sql 1.91 Customer Service Package 00572795
DP_EPOD_WEB_SERVICE.sql 1.216 EPOD Web Service 00524462
DP_EPOD_WEB_SERVICE.sql 1.217 EPOD Web Service 00524481
DP_EPOD_WEB_SERVICE.sql 1.218 EPOD Web Service 00517921
DP_EPOD_WEB_SERVICE.sql 1.220 EPOD Web Service 00527142
DP_EPOD_WEB_SERVICE.sql 1.221 EPOD Web Service 00527274
DP_EPOD_WEB_SERVICE.sql 1.222 EPOD Web Service 00498981
DP_EPOD_WEB_SERVICE.sql 1.223 EPOD Web Service 00528183
DP_EPOD_WEB_SERVICE.sql 1.224 EPOD Web Service 00528738
DP_EPOD_WEB_SERVICE.sql 1.225 EPOD Web Service 00528842
DP_EPOD_WEB_SERVICE.sql 1.226 EPOD Web Service 00528762
DP_EPOD_WEB_SERVICE.sql 1.227 EPOD Web Service 00524586
DP_EPOD_WEB_SERVICE.sql 1.228 EPOD Web Service 00533991
DP_EPOD_WEB_SERVICE.sql 1.230 EPOD Web Service 00538855
DP_EPOD_WEB_SERVICE.sql 1.231 EPOD Web Service 02713995
DP_EPOD_WEB_SERVICE.sql 1.232 EPOD Web Service 00536498
DP_EPOD_WEB_SERVICE.sql 1.233 EPOD Web Service 00479903
DP_EPOD_WEB_SERVICE.sql 1.234 EPOD Web Service 00544876
DP_EPOD_WEB_SERVICE.sql 1.235 EPOD Web Service 00549717
DP_EPOD_WEB_SERVICE.sql 1.236 EPOD Web Service 00469937
DP_EPOD_WEB_SERVICE.sql 1.238 EPOD Web Service 00516374
DP_EPOD_WEB_SERVICE.sql 1.239 EPOD Web Service 00554263
DP_EPOD_WEB_SERVICE.sql 1.241 EPOD Web Service 00552783
DP_EPOD_WEB_SERVICE.sql 1.242 EPOD Web Service 00542530
DP_EPOD_WEB_SERVICE.sql 1.243 EPOD Web Service 00560125
DP_EPOD_WEB_SERVICE.sql 1.244 EPOD Web Service 00561946
DP_EPOD_WEB_SERVICE.sql 1.245 EPOD Web Service 00563558
DP_EPOD_WEB_SERVICE.sql 1.246 EPOD Web Service 00567195
DP_EPOD_WEB_SERVICE.sql 1.247 EPOD Web Service 00532043
DP_EPOD_WEB_SERVICE.sql 1.248 EPOD Web Service 00569051
DP_EPOD_WEB_SERVICE.sql 1.249 EPOD Web Service 00539653
DP_EPOD_WEB_SERVICE.sql 1.250 EPOD Web Service 00570824
DP_EPOD_WEB_SERVICE.sql 1.251 EPOD Web Service 00573163
DP_EXPORT_EVENTS.sql 5.34 API Export Events Database Package 00528842
DP_EXPORT_EVENTS.sql 5.35 API Export Events Database Package 00530050
DP_EXPORT_EVENTS.sql 5.36 API Export Events Database Package 00537198
DP_EXPORT_EVENTS.sql 5.37 API Export Events Database Package 00538804
DP_EXPORT_EVENTS.sql 5.38 API Export Events Database Package 00538191
DP_EXPORT_EVENTS.sql 5.40 API Export Events Database Package 00543998
DP_EXPORT_EVENTS.sql 5.41 API Export Events Database Package 00559726
DP_EXPORT_EVENTS.sql 5.42 API Export Events Database Package 00580395
DP_NOKIA_LOC_PLAT.sql 1.41 Nokia Location Platform Interface 00553397
DP_ORS_FUNCS.sql 5.30 Change to DOOD status function 00524191
DP_PAR_API.sql 5.19 Paragon API Database Package 00548540
DP_PAR_API.sql 5.20 Paragon API Database Package 00562303
DP_PAR_API.sql 5.21 Paragon API Database Package 00565562
DP_PAR_API.sql 5.22 Paragon API Database Package 00575228
DP_PAR_API_STP.sql 5.21 STP Paragon API Database Package 00527157
DP_PAR_API_STP.sql 5.22 STP Paragon API Database Package 00528195
DP_PAR_API_STP.sql 5.23 STP Paragon API Database Package 00527603
DP_PAR_API_STP.sql 5.24 STP Paragon API Database Package 00528718
DP_PAR_API_STP.sql 5.25 STP Paragon API Database Package 00534416
DP_PAR_API_STP.sql 5.26 STP Paragon API Database Package 00539920
DP_PAR_API_STP.sql 5.27 STP Paragon API Database Package 00540264
DP_PAR_API_STP.sql 5.28 STP Paragon API Database Package 00542201
DP_PAR_API_STP.sql 5.29 STP Paragon API Database Package 00554583
DP_PAR_API_STP.sql 5.30 STP Paragon API Database Package 00555143
DP_PAR_API_STP.sql 5.31 STP Paragon API Database Package 00562303
DP_PAR_API_STP.sql 5.33 STP Paragon API Database Package 00563001
DP_PAR_API_STP.sql 5.34 STP Paragon API Database Package 00560600
DP_PAR_API_STP.sql 5.35 STP Paragon API Database Package 00567392
DP_PAR_API_STP.sql 5.36 STP Paragon API Database Package 00568624
DP_PAR_API_STP.sql 5.37 STP Paragon API Database Package 00484537
DP_PAR_API_STP.sql 5.38 STP Paragon API Database Package 00578389
DP_TOMTOM.sql 1.46 TomTom Package 02710742
DP_WEB_SERVICE_ORD.sql 1.33 Web Service Package 03008712
DP_WEB_SERVICE_ORD.sql 1.35 Web Service Package 03529183
EPOD_WSA.fmx 1.13 EPOD Web Service Audit Form 00522350
IMP.sql 5.234 CSV Imports Package 00520087
IMP.sql 5.235 CSV Imports Package 00536205
INT_XML_IN.sql 5.241 Order Import Package 02769136
INT_XML_IN.sql 5.242 Order Import Package 00562331
INT_XML_MIC.sql 5.158 MIC interface 02728730
INT_XML_OUT2.sql 5.336 Outbound XML Package 02818748
INT_XML_OUT2.sql 5.337 Outbound XML Package 00546768
INT_XML_OUT2.sql 5.338 Outbound XML Package 00469937
INT_XML_OUT2.sql 5.339 Outbound XML Package 00554263
LOAD_MAN.fmx 1.29 Load Management Form 02683404
LOCATION.fmx 2.207 Location Maintenance 00528195
LOCATION.fmx 2.209 Location Maintenance 00469937
LOCATION.fmx 2.209 Location Maintenance 00564461
nokmap.html 1.11 Maps Interface 00534889
OF_INT.sql 5.75 Oracle Financials interface 02792680
OMS.sql 5.334 Order package 00527603
ORDERS.fmx 2.456 Order Screen 02713995
ORDERS_WIDE.fmx 1.53 Orders Screen 02713995
ORI_MAIN.fmx 2.18 Login Screen 02578219
PAR.sql 5.115 Paragon Interface 02683404
PAR.sql 5.116 Paragon Interface 02910494
PAR_INT.fmx 10.43 Paragon Interface form 02691631
PLANNING.fmx 1.146 Planning Screen 02742281
PLANNING.fmx 1.147 Planning Screen 00547839
PLANNING.fmx 1.148 Planning Screen 00550047
PLANNING.fmx 1.149 Planning Screen 00554721
PLANNING.fmx 1.150 Planning Screen 00561665
PLANNING.fmx 1.151 Planning Screen 00540719
RESOURCE.fmx 2.200 Resource Maintenance form 02764788
T_SCH_HAULAGE_ACTIVITY_BIU.sql 1.8 Trigger 00527157
TI_SCH_ORD_STATUS.sql 1.29 Trigger on SCH_ORD for status change 00527152
TI_SCH_ORD_STATUS.sql 1.30 Trigger on SCH_ORD for status change 00554568
TI_SCH_ORD_STATUS.sql 1.31 Trigger on SCH_ORD for status change 00563001
TRG_LOCATIONS_UID.sql 5.2 Trigger 00527152
TRG_LOCATIONS_UID.sql 5.3 Trigger 00469937
TRG_LOCATIONS_UID.sql 5.4 Trigger 00554568
TRG_LOCATIONS_UID.sql 5.5 Trigger 00563001
TRG_SCH_ORD_AUDIT_LOCS.sql 1.4 Trigger 00543948
TRG_SCH_ORD_AUDIT_LOCS.sql 1.5 Trigger 00563001
TRG_SCH_ORD_AUDIT_LOCS.sql 1.6 Trigger 00540719
TRG_SCH_ORD_CURRENT_DEPOT.sql 5.6 Trigger 00527152
TRG_SCH_ORD_CURRENT_DEPOT.sql 5.7 Trigger 00550047
TRG_SCH_ORD_CURRENT_DEPOT.sql 5.8 Trigger 00554568
TRG_SCH_ORD_CURRENT_DEPOT.sql 5.9 Trigger 00563001
TRG_SCH_ORDER_LINE_PAR.sql 5.4 Trigger 00527152
TRG_SHA_TRUNK_TRIP.sql 5.4 Trigger 00577244
TRG_SOL_XML.sql 5.51 Trigger 00525182
TRG_SOL_XML.sql 5.52 Trigger 00527274
TRIP_OVERVIEW.fmx 1.76 Trip Waterfall 00555144
TRIP_OVERVIEW.sql 5.17 Trip Waterfall 00533620
TRM.sql 5.230 Trip manipulation package 00577244
V_CURRENT_DRIVER_LIST.sql 1.4 View 00525198
V_DRIVER_ORDERS.sql 1.4 View 00525198
V_GEO_CONTACT.sql 1.2 View 00469937
V_ORD_ORDER_CONTACT.sql 1.5 View 00469937
V_ORD_ORDER_HEADER.sql 1.24 View 00538412
V_ORD_ORDER_HEADER.sql 1.25 View 00544876
V_ORD_ORDER_HEADER.sql 1.26 View 00555163
V_ORD_ORDER_HEADER_CS.sql 1.2 View 00558723
V_TRIP_OVERVIEW.sql 1.24 Trip View 00555144
V_TRIP_OVERVIEW_ORD.sql 5.15 Trip/Order View 00555144
V_VEHICLE_DETAILS.sql 5.7 View 00534016
V_VEHICLE_DETAILS.sql 5.8 View 00544876


ADDITIONAL CHANGES

WCS

There is no WCS change required.


EPOD/T2A

An ePOD change is required for the following logs:

  • Log 570824 - Epod server v4.5.1.12 (CTY Only)


CTL

An CTL change is required for the following logs:

  • Log 525198
  • Log 538412
  • Log 469937
  • Log 558723
  • Log 572795


PORTAL/TTM

There is no Portal change required.


Manual

Note: Version 5.22.1.1 of DP_PAR_API will need to be installed in the MAR databases.

Note: Version 5.38.1.1 of DP_PAR_API_STP will need to be installed in the STS databases.

Note: Nokmap.html should be released to /u03/######/webint/html.


Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=PATCH_C-TMS_P046&oldid=12146’