PATCH C-TMS P039: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 150: Line 150:
|}
|}
-->
-->
== OBS Log Number:  ==
 
{| width="100%"
|-
|width="30%"|'''Cust Ref:'''  || '''Reporter:'''
|-
|'''Summary of Call'''||
|-
|'''Detail of Fix''' ||
|-
|'''Set-up and Configuration''' ||
|}


== Log Number: 00378509 ==
== Log Number: 00378509 ==
Line 167: Line 157:
|width="30%"|'''Summary of Call'''|| C-TMS not translating all the data
|width="30%"|'''Summary of Call'''|| C-TMS not translating all the data
|-
|-
|'''Detail of Fix''' || "A 4933 order will be replaced by a 4987 order.
|'''Detail of Fix''' || A 4933 order will be replaced by a 4987 order.


The 4933 order will be unscheduled from all its trips.
The 4933 order will be unscheduled from all its trips.


The 4987 order will be scheduled on the same trips as
The 4987 order will be scheduled on the same trips as the 4933 order had previously.
the 4933 order had previously.
 
A valid 4987 order will be scheduled if the trip stops are identified as the 4933 order is unscheduled.
 
An INVALID 4987 will not be scheduled.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01572881 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Bug fixes around location zone setup in TMS
|-
|'''Detail of Fix''' || A change has been made for the OR3 interface to assess the location zones and schedule rules for a generic WEB_CUST customer for the group of customers when the actual customer of the order does not have its own schedule rules to apply to the calculation of the collection time windows of the order when it is validated.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01572900 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| EDI interface error in TMS
|-
|'''Detail of Fix''' || The inbound EDI order process will assess the items and their contents and not specifically the commodity code.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01575387 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| WOC to WCS Messages
|-
|'''Detail of Fix''' || Control flow of messages from WOC to WCS
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01573388 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Query on funtionality
|-
|'''Detail of Fix''' || I have made a change to the Print Labels screen in the Orders screen to ensure that the labels are reprinted, repacked or produced for the first time for an order.
 
The user will see the appropriate text in an information message.
 
The default carrier must exist for an unscheduled order to reprint labels as per the development.
 
Selected labels can only be reprinted if the delivery carrier has not been changed.
 
All labels will either be reprinted or repacked and printed depending on the comparison between the current carrier and the previous carrier.
 
Labels can be reprinted for an unscheduled order for the default carrier.
 
Labels can be reprinted for a scheduled order if the delivery carrier has not been changed, otherwise the order will be repacked and the labels printed for the new carrier.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01574638 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Booking Status
|-
|'''Detail of Fix''' || Added system params to allow the Booking Status and Order Status fields to be defaulted to the value specified.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01576597 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| XML no of chars does not match TMS no of chars
|-
|'''Detail of Fix''' || The limit for the maximum line size when extracting XML data has been extended.
 
Up to 2000 characters can be stored.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00195537 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Error On New Order Form When Moving To Tab Add Detail
|-
|'''Detail of Fix''' || The 'Original From' and 'Final To' location fields in the 'ORDERS' and 'ORDERS_WIDE' screens will have the same list of values as the 'Collect From' and 'Deliver To' location fields when the system parameter 'GEO_SUBURB' is 'Y' or 'N'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01566301 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Debrief issue
|-
|'''Detail of Fix''' || The system parameter TRM_PREVENT_ALL_DEBRIEF will be effective when the user pages or scrolls up or down.
 
When this parameter is Y, the actual dates and times for the trip stops will not be defaulted.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 00198413 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Interface errors screen - warning messages
|-
|'''Detail of Fix''' || The new EDI parameter 'NO_UPDATE_DEPOT_ADDR' when set to 'Y' will be used to prevent the user being warned that the RDC location will not be updated when not all the address data has been provided.


A valid 4987 order will be scheduled if the trip stops
Further validation error messaging has been included for the address data when new locations are being created or addresses are being updated.
are identified as the 4933 order is unscheduled.


An INVALID 4987 will not be scheduled."
Multiple trailer types and contacts can be added to the locations.
 
The trailer types must exist and he fill factor must be numeric.
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Set-up and Configuration''' || No set-up/configuration required
|}
|}
== Log Number: 01598292 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Updates to loading and delivery documents
|-
|'''Detail of Fix''' || Fixes to customer specific delivery and loading reports
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01605971 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Vehicle types not sent to PTV
|-
|'''Detail of Fix''' || The group for the vehicle type of the order will be sent to Logix/PTV as decoded by 'LOGIC_VEH_GROUPS'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01618702 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| C-TMS Locations export data
|-
|'''Detail of Fix''' || The 'Location Export' file does not include a double quotation mark that would cause the data to be displayed in the wrong column.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01619171 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Oracle Error from calc distance and time
|-
|'''Detail of Fix''' || The calculation for the distance and time for trip stops has been amended.
Cross-docked orders from a collection location will retain the fixed stop times when they are set and non-fixed trip stops will perform the calculation.
If the collection trip contains a fully scheduled order that has been planned for cross-docking, new orders can be planned on that trip.
Auto-planned orders will continue to use the time windows for their trip stops when advised.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01633444 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Fixed route generation
|-
|'''Detail of Fix''' || The customer scheduling engine will create unique trip stops even if overlapping dates exist for the fixed route.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01630455 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Message processing
|-
|'''Detail of Fix''' || The format of the email addresses of the recipients of the messages will be validated before attempting to send an email.
The email address must contain an at sign and a full stop.
The email address cannot contain a semi-colon, a forward slash or a space otherwise the sending of the email will fail.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01634680 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| INC38355978 CTMS not generating POD files to Connected View for 3rd party carrier orders
|-
|'''Detail of Fix''' || The POD flag for the order will be set to Y for a carrier POD message.
When the POD flag for the order is set to Y, a POD messages for Connected View will be generated.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01727033 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Genersearch_outbound EDI
|-
|'''Detail of Fix''' || The 'LOTS' files will be copied for the customers who require them.
They will not be generated and sent until a valid EDI process exists with the correct FTP details and a connection that can be opened, and a local directory structure that exists to store and process the files.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01638058 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Stops not being created though successfully processed
|-
|'''Detail of Fix''' || The delivery orders can be planned onto the same route for the schedule as part of the initial plan in Paragon or as part of a re-spin process.
The delivery orders will not be trunked for delivery to another specific depot for the delivery location if they are already available at the planning depot.
The delivery orders will be trunked from delivery from another cross-docked depot.
The specific depot for the delivery location is stored as a delivery slot.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01720493 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Trunk trips
|-
|'''Detail of Fix''' || The trunk trips will be created specifically for the orders as they are processed based on the next loading and unloading activities at the RDC locations that have been planned for the delivery of the order.
The number of trunk trips that are created based on the slots for the RDC locations and that are then deleted because they are not used in the final plan for the delivery of the orders will then be reduced.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01729869 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Amendments identified during UAT
|-
|'''Detail of Fix''' || Amendments on Carrier Rules following UAT
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01581859 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| CTL issues
|-
|'''Detail of Fix''' || Fixed and sent to test. To reproduce it you need a weight of 1 and a qty of say 3. Or something that produces a recurring fraction. The solution is to perform the division within the .net code as oracledataaccess seems unable to cope with it.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01582929 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Customer details for CANCELLATION orders
|-
|'''Detail of Fix''' || Reduce the validation for Invalid Orders
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01558743 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Latency in using Trip (Waterfall) for allocation resource
|-
|'''Detail of Fix''' || The 'Trip Waterfall' screen displays the trips and resources for allocation for the specified parameters.
The queries for the trip blocks and the tab blocks will be made when they are required.
The 5 trip blocks by trip status in the 'ALL' tab page will be refreshed when the screen is opened for the default schedule, when the schedule or other filters are changed, and when the tab page is re-opened from another tab page or a called screen.
The 5 tab pages for the specified trip status will be refreshed when the tab page is opened and when the tab page is re-opened from a called screen.
The 'Alloc Resource' button and menu option will call the 'Allocate Resources' screen (TRIP_RES) when a crew or a driver is not required for the resource allocation.
These resources for the driver, tractor and trailer for the carrier of the trip will be displayed for selection.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Log Number: 01582547 ==
{| width="100%"
|-
|width="30%"|'''Summary of Call'''|| Invoicing
|-
|'''Detail of Fix''' || Changes to exclude the year from the start of the invoice number
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}


Revision as of 13:43, 28 May 2021





Aptean Logo.png










Release Notes

CALIDUS TMS

25th May 2021 - 1.0
Reference: P039











































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


DEVELOPMENT

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required


SUPPORT INCIDENTS

Customer Ref:

OBS Log Number: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required


BUGS

Log Number: 00378509

Summary of Call C-TMS not translating all the data
Detail of Fix A 4933 order will be replaced by a 4987 order.

The 4933 order will be unscheduled from all its trips.

The 4987 order will be scheduled on the same trips as the 4933 order had previously.

A valid 4987 order will be scheduled if the trip stops are identified as the 4933 order is unscheduled.

An INVALID 4987 will not be scheduled.

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


Log Number: 01572881

Summary of Call Bug fixes around location zone setup in TMS
Detail of Fix A change has been made for the OR3 interface to assess the location zones and schedule rules for a generic WEB_CUST customer for the group of customers when the actual customer of the order does not have its own schedule rules to apply to the calculation of the collection time windows of the order when it is validated.
Set-up and Configuration No set-up/configuration required


Log Number: 01572900

Summary of Call EDI interface error in TMS
Detail of Fix The inbound EDI order process will assess the items and their contents and not specifically the commodity code.
Set-up and Configuration No set-up/configuration required


Log Number: 01575387

Summary of Call WOC to WCS Messages
Detail of Fix Control flow of messages from WOC to WCS
Set-up and Configuration No set-up/configuration required


Log Number: 01573388

Summary of Call Query on funtionality
Detail of Fix I have made a change to the Print Labels screen in the Orders screen to ensure that the labels are reprinted, repacked or produced for the first time for an order.

The user will see the appropriate text in an information message.

The default carrier must exist for an unscheduled order to reprint labels as per the development.

Selected labels can only be reprinted if the delivery carrier has not been changed.

All labels will either be reprinted or repacked and printed depending on the comparison between the current carrier and the previous carrier.

Labels can be reprinted for an unscheduled order for the default carrier.

Labels can be reprinted for a scheduled order if the delivery carrier has not been changed, otherwise the order will be repacked and the labels printed for the new carrier.

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


Log Number: 01574638

Summary of Call Booking Status
Detail of Fix Added system params to allow the Booking Status and Order Status fields to be defaulted to the value specified.
Set-up and Configuration No set-up/configuration required


Log Number: 01576597

Summary of Call XML no of chars does not match TMS no of chars
Detail of Fix The limit for the maximum line size when extracting XML data has been extended.

Up to 2000 characters can be stored.

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


Log Number: 00195537

Summary of Call Error On New Order Form When Moving To Tab Add Detail
Detail of Fix The 'Original From' and 'Final To' location fields in the 'ORDERS' and 'ORDERS_WIDE' screens will have the same list of values as the 'Collect From' and 'Deliver To' location fields when the system parameter 'GEO_SUBURB' is 'Y' or 'N'.
Set-up and Configuration No set-up/configuration required


Log Number: 01566301

Summary of Call Debrief issue
Detail of Fix The system parameter TRM_PREVENT_ALL_DEBRIEF will be effective when the user pages or scrolls up or down.

When this parameter is Y, the actual dates and times for the trip stops will not be defaulted.

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


Log Number: 00198413

Summary of Call Interface errors screen - warning messages
Detail of Fix The new EDI parameter 'NO_UPDATE_DEPOT_ADDR' when set to 'Y' will be used to prevent the user being warned that the RDC location will not be updated when not all the address data has been provided.

Further validation error messaging has been included for the address data when new locations are being created or addresses are being updated.

Multiple trailer types and contacts can be added to the locations.

The trailer types must exist and he fill factor must be numeric.

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


Log Number: 01598292

Summary of Call Updates to loading and delivery documents
Detail of Fix Fixes to customer specific delivery and loading reports
Set-up and Configuration No set-up/configuration required


Log Number: 01605971

Summary of Call Vehicle types not sent to PTV
Detail of Fix The group for the vehicle type of the order will be sent to Logix/PTV as decoded by 'LOGIC_VEH_GROUPS'.
Set-up and Configuration No set-up/configuration required


Log Number: 01618702

Summary of Call C-TMS Locations export data
Detail of Fix The 'Location Export' file does not include a double quotation mark that would cause the data to be displayed in the wrong column.
Set-up and Configuration No set-up/configuration required


Log Number: 01619171

Summary of Call Oracle Error from calc distance and time
Detail of Fix The calculation for the distance and time for trip stops has been amended.

Cross-docked orders from a collection location will retain the fixed stop times when they are set and non-fixed trip stops will perform the calculation.

If the collection trip contains a fully scheduled order that has been planned for cross-docking, new orders can be planned on that trip.

Auto-planned orders will continue to use the time windows for their trip stops when advised.

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


Log Number: 01633444

Summary of Call Fixed route generation
Detail of Fix The customer scheduling engine will create unique trip stops even if overlapping dates exist for the fixed route.
Set-up and Configuration No set-up/configuration required


Log Number: 01630455

Summary of Call Message processing
Detail of Fix The format of the email addresses of the recipients of the messages will be validated before attempting to send an email.

The email address must contain an at sign and a full stop.

The email address cannot contain a semi-colon, a forward slash or a space otherwise the sending of the email will fail.

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


Log Number: 01634680

Summary of Call INC38355978 CTMS not generating POD files to Connected View for 3rd party carrier orders
Detail of Fix The POD flag for the order will be set to Y for a carrier POD message.

When the POD flag for the order is set to Y, a POD messages for Connected View will be generated.

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


Log Number: 01727033

Summary of Call Genersearch_outbound EDI
Detail of Fix The 'LOTS' files will be copied for the customers who require them.

They will not be generated and sent until a valid EDI process exists with the correct FTP details and a connection that can be opened, and a local directory structure that exists to store and process the files.

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


Log Number: 01638058

Summary of Call Stops not being created though successfully processed
Detail of Fix The delivery orders can be planned onto the same route for the schedule as part of the initial plan in Paragon or as part of a re-spin process.

The delivery orders will not be trunked for delivery to another specific depot for the delivery location if they are already available at the planning depot.

The delivery orders will be trunked from delivery from another cross-docked depot.

The specific depot for the delivery location is stored as a delivery slot.

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


Log Number: 01720493

Summary of Call Trunk trips
Detail of Fix The trunk trips will be created specifically for the orders as they are processed based on the next loading and unloading activities at the RDC locations that have been planned for the delivery of the order.

The number of trunk trips that are created based on the slots for the RDC locations and that are then deleted because they are not used in the final plan for the delivery of the orders will then be reduced.

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


Log Number: 01729869

Summary of Call Amendments identified during UAT
Detail of Fix Amendments on Carrier Rules following UAT
Set-up and Configuration No set-up/configuration required


Log Number: 01581859

Summary of Call CTL issues
Detail of Fix Fixed and sent to test. To reproduce it you need a weight of 1 and a qty of say 3. Or something that produces a recurring fraction. The solution is to perform the division within the .net code as oracledataaccess seems unable to cope with it.
Set-up and Configuration No set-up/configuration required


Log Number: 01582929

Summary of Call Customer details for CANCELLATION orders
Detail of Fix Reduce the validation for Invalid Orders
Set-up and Configuration No set-up/configuration required


Log Number: 01558743

Summary of Call Latency in using Trip (Waterfall) for allocation resource
Detail of Fix The 'Trip Waterfall' screen displays the trips and resources for allocation for the specified parameters.

The queries for the trip blocks and the tab blocks will be made when they are required.

The 5 trip blocks by trip status in the 'ALL' tab page will be refreshed when the screen is opened for the default schedule, when the schedule or other filters are changed, and when the tab page is re-opened from another tab page or a called screen.

The 5 tab pages for the specified trip status will be refreshed when the tab page is opened and when the tab page is re-opened from a called screen.

The 'Alloc Resource' button and menu option will call the 'Allocate Resources' screen (TRIP_RES) when a crew or a driver is not required for the resource allocation.

These resources for the driver, tractor and trailer for the carrier of the trip will be displayed for selection.

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


Log Number: 01582547

Summary of Call Invoicing
Detail of Fix Changes to exclude the year from the start of the invoice number
Set-up and Configuration No set-up/configuration required



PRODUCT DEVELOPMENT

OBS Log Number:

Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration No set-up/configuration required


MODULES DELIVERED

Module Name Version No Description Log Number
ACC.sql 5.82 Accounts package 01638635
AT_CARRIER_RULES_DU_TYPE_01640571.sql 1.3 AT Script 01640571
AT_CARRIER_RULES_PRODUCT_TYPE_01640571.sql 1.4 AT Script 01640571
CARRIER_RULES.fmx 1.15 Carrier Rules Maintenance Screen 01640571
CT_ORG_CUST_CUT_OFFS.sql 1.1 CT Script 01636354
CT_SEQ_FIXED_TRACK.sql 1.1 CT Script 01592591
CT_WMS_PRODUCT_XREF_01559665.sql 1.2 CT Script 01559665
CUST_COST.fmx 2.137 Customer Maintenance form 01636354
DATA_1_IMP_IMPORT_TYPE_01559665.sql 1.1 Data Script 01559665
DATA_1_ORS_SQL_01587702.sql 1.1 Data Script 01587702
DATA_2_ORS_MASTER_DATA_01587702.sql 1.1 Data Script 01587702
DATA_ADM_LOG_PROG_NAME_378509.sql 1.1 Data Script 00378509
DATA_ADM_SYSTEM_PARAM_01573976.sql 1.1 Data Script 01573976
DATA_ADM_SYSTEM_PARAM_01574638.sql 1.1 Data Script 01574638
DATA_ADM_SYSTEM_PARAM_01575387.sql 1.1 Data Script 01575387
DATA_ADM_SYSTEM_PARAM_01576048.sql 1.1 Data Script 01576048
DATA_ADM_SYSTEM_PARAM_01592591.sql 1.1 Data Script 01592591
DATA_ADM_SYSTEM_PARAM_01631034.sql 1.1 Data Script 01631034
DATA_ADM_SYSTEM_PARAM_01636354.sql 1.1 Data Script 01636354
DATA_ADM_SYSTEM_PARAM_01640571.sql 1.1 Data Script 01640571
DATA_ADM_SYSTEM_PARAM_CONFIG_01573976.sql 1.1 Data Script 01573976
DATA_ADM_SYSTEM_PARAM_CONFIG_01576048.sql 1.1 Data Script 01576048
DATA_I_ADM_SYSTEM_PARAM_01590895.sql 1.1 Data Script 01590589
DATA_I_ADM_SYSTEM_PARAM_CONFIG_01590895.sql 1.1 Data Script 01590589
DATA_I_ORS_MASTER_DATA_01568006.sql 1.1 Data Script 01568006
DATA_I_ORS_MASTER_DATA_01611368.sql 1.1 Data Script 01611368
DATA_IMP_FIELD_01559665.sql 1.1 Data Script 01559665
DATA_IMP_IMPORT_TYPE_REC_TYPE_01559665.sql 1.1 Data Script 01559665
DATA_ORS_MASTER_DATA_00194616.sql 1.1 Data Script 00194616
DATA_ORS_MASTER_DATA_01559665.sql 1.2 Data Script 01559665
DATA_ORS_MASTER_DATA_01580000.sql 1.1 Data Script 01580000
DATA_ORS_MASTER_DATA_01638635.sql 1.1 Data Script 01638635
DATA_ORS_SQL_00194616.sql 1.1 Data Script 00194616
DATA_ORS_SQL_01559665.sql 1.2 Data Script 01559665
DATA_REP_REPORT_01561481.sql 1.1 Data Script 01561481
DATA_REP_REPORT_PARAM_01561481.sql 1.1 Data Script 01561481
DATA_RES_LABEL_FORMATS_01560840.sql 1.1 Data Script 01560840
DELIVERY_DOCS.rep 1.2 Delivery Docs Report 01582929
DELIVERY_DOCS.rep 1.3 Delivery Docs Report 01598292
DP_ASSET_SCANNING.sql 5.56 Tag to Asset Scanning 01596335
DP_CARRIER.sql 1.93 Carrier Management 01560840
DP_CSV_GEN.sql 1.6 Generic CVS package 01561481
DP_CSV2.sql 5.79 Second CSV extract package 01618702
DP_EDI1214.sql 5.3 Database Package 01592591
DP_EDI1214.sql 5.4 Database Package 01631677
DP_EPOD_WEB_SERVICE.sql 1.133 EPOD Web Service 01575864
DP_IMP.sql 5.41 Imports Package 01592591
DP_INT_XML_CARPOD.sql 5.8 Inbound EDI Carrier POD Interface 01634680
DP_INT_XML_CFX.sql 1.4 Database Package 01612846
DP_INT_XML_CFX.sql 1.2 Database Package 00194616
DP_LOGIX_CONFIG.sql 1.19 PTV Interface 01605971
DP_LOGIX_DOM.sql 1.15 Logix Procedures 01605971
DP_NOKIA_LOC_PLAT.sql 1.34 Nokia Location Platform Interface 01622110
DP_NOKIA_LOC_PLAT.sql 1.33 Nokia Location Platform Interface 01592379
DP_REPORTS.sql 5.63 Reports package 01598884
DP_REPORTS.sql 5.64 Reports package 00211385
DP_SCHEDULING_ENGINE.sql 5.171 Scheduling Package 01640571
DP_SCHEDULING_ENGINE.sql 5.172 Scheduling Package 01729869
DP_SCHEDULING_NHSBT.sql 1.7 Client specific scheduling package 01633444
DP_SHIPMENT.sql 5.32 Shipment Code package 00378509
DP_WCS_IF.sql 5.26 WCS Package 01575387
DP_WEB_SERVICE_ENQUIRY.sql 1.4 Database Package 01592379
DP_WEB_SERVICE_ENQUIRY.sql 1.5 Database Package 01622110
HCR_LOADING_SHEET.rep 1.7 Customer Loading Sheet 01598884
IMP.sql 5.203 CSV Imports Package 01559665
IMPORTS_EXEC.fmx 10.29 Import executions 01580510
INT_XML_IN.sql 5.214 Order Import Package 01572900
INT_XML_IN.sql 5.216 Order Import Package 00198413
INT_XML_IN.sql 5.218 Order Import Package 01636354
INT_XML_IN.sql 5.215 Order Import Package 01582929
INT_XML_IN.sql 5.217 Order Import Package 01598292
INT_XML_MIC.sql 5.153 MIC interface 01584725
INT_XML_OUT2.sql 5.312 Outbound XML Package 01576048
INT_XML_OUT2.sql 5.314 Outbound XML Package 01581745
INT_XML_OUT2.sql 5.315 Outbound XML Package 01571516
INT_XML_OUT2.sql 5.316 Outbound XML Package 01573976
INT_XML_OUT2.sql 5.317 Outbound XML Package 01590589
INT_XML_OUT2.sql 5.318 Outbound XML Package 01727033
LOADING_LIST.rep 1.2 Loading List Report 01582929
LOADING_LIST.rep 1.3 Loading List Report 01598292
MSG_CONSTRUCTOR.sql 5.19 E-mail construction 01630455
OF_INT.sql 5.64 Oracle Financials interface 01582547
OMS.sql 5.239 Order package 01580373
OMS.sql 5.243 Order package 01729869
OMS.sql 5.238 Order package 01572881
OMS.sql 5.240 Order package 01631034
OMS.sql 5.242 Order package 01636354
ORDERS.fmx 2.438 Order Screen 00195537
ORDERS.fmx 2.437 Order Screen 01573388
ORDERS_WIDE.fmx 1.35 Orders Screen 00195537
ORS.fmx 1.31 Oracle Reporting suite 00211385
PAR.sql 5.110 Paragon Interface 01638058
PAR.sql 5.112 Paragon Interface 01720493
PAR.sql 5.111 Paragon Interface 01634690
PLANNING.fmx 1.117 Planning Screen 01575989
PLANNING.fmx 1.118 Planning Screen 01631034
T_SCH_ORD_COMMENTS.sql 1.3 Trigger 01576597
TI_SCH_ORD_STATUS.sql 1.20 Trigger on SCH_ORD for status change 01592591
TI_SCH_TRIP_AUDIT.sql 5.6 Trigger 01616829
TRG_INT_XML_ORD_TRAILER_BI.sql 1.2 Trigger 00198413
TRG_ORG_CUST_CUT_OFFS_IA.sql 1.2 Trigger 01636354
TRG_SCH_ORD_ITEM_REASONS_FIXED.sql 1.1 Trigger 01592591
TRG_SCH_ORD_ITEMS.sql 5.6 Trigger 01616829
TRG_SCH_ORD_NON_CONF_XML_INT.sql 5.12 Trigger 01573976
TRG_SCH_ORD_NON_CONFORM_FIXED.sql 1.1 Trigger 01592591
TRG_SCH_ORD_REFERENCE_AI.sql 1.2 Trigger on SCH_ORD_REFERENCE 01636291
TRG_SCH_TRIP_XML_GEN.sql 5.22 Trigger 01571516
TRG_SHA_LOTS.sql 5.6 Trigger 01590589
TRG_SHA_XML_GEN.sql 5.14 Trigger 01571516
TRG_STS_XML_GEN.sql 5.12 Trigger 01571516
TRIP_OVERVIEW.fmx 1.64 Trip Waterfall 01558743
TRIP_PLAN.fmx 1.279 Trip Planning Screen 01575989
TRIP_RES.fmx 1.26 Resource Allocation 01558743
TRIPDTL.fmx 2.230 Trip Debrief 01592591
TRIPDTL.fmx 2.227 Trip Debrief 01566301
TRIPSUM.fmx 2.445 Trip Manipulation screen 01575989
TRM.sql 5.202 Trip manipulation package 01619171
V_ORD_INC_INV.sql 1.12 View 01638635
V_ORD_ORDER_LINE_ITEM_PROD.sql 1.4 View 01581859
XML.sql 5.14 XML file upload 01576597


ADDITIONAL CHANGES

WCS

A WCS change is required for the following logs:

  • Log

OR

There are no WCS changes required.

EPOD/T2A

An ePOD/T2A change is required for the following logs:

  • Log

OR

There are no ePOD/T2A changes required.

MCS

An MCS change is required for the following logs:

  • Log

OR

There are no MCS changes required.

PORTAL/TTM

A Portal change is required for the following logs:

  • Log

OR

There are no Portal changes required.

EDI

An EDI change is required for the following logs:

  • Log

OR

There are no EDI changes required.


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