PATCH CTMS P037: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 307: Line 307:
|}
|}
-->
-->
== Customer Ref: ==
 
== Customer Ref: Resource Screen ==
{| width="100%"
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''  || '''Reporter:'''
|-
|-
|'''Summary of Call'''||  
|width="30%"|'''OBS Log Number:'''|| 364730
|-
|-
|'''Detail of Fix''' ||
|'''Summary of Call'''|| Trip Resource screen
|-
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|'''Detail of Fix''' || The allocation of resources to trips will display a long error message when the trailer is being validated.                                                                                                   
 
The crew and diary versions also have been changed.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: Trunk Trip ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 369482
|-
|'''Summary of Call'''|| Different trunk trip comment for INV_TRA
|-
|'''Detail of Fix''' || Amended comment for the item reason to include the text 'different trunk trip' for an unload scan as well as a load scan using RDT.                                                                                   
 
This format will enable Inventory Transactions to be identified for trunk trips.                                                                                 
 
Inventory Transactions will include items on the scanned trunk trip or the planned trunk trip as long as the item has not been scanned on a different trunk trip. 
 
Orders which originate in an RDC will be assessed for a trunk trip.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Customer Ref: TMS characts to epod ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 370023
|-
|'''Summary of Call'''|| Limit charaters from TMS to EPOD to 40
|-
|'''Detail of Fix''' || The EPL_DESCRIPTION and EPL_CONTAINER_PACKAGE_DESC items will only contain a maximum of 40 characters.                                                         
 
Any text that is longer than 40 characters in length in C-TMS will be truncated for display in EPOD.                                                             
 
These changes apply to the main version of the outbound EPOD files.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: N/A ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 370926
|-
|'''Summary of Call'''|| System speed and performance
|-
|'''Detail of Fix''' || Improve speed of the domestic scheduling loops by using a date range to select orders.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: INC32503211 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 371795
|-
|'''Summary of Call'''|| Unable to export data
|-
|'''Detail of Fix''' || Amendment to parcel carriers data select to improve performance.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: MCS ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 371819
|-
|'''Summary of Call'''|| MCS - Performance
|-
|'''Detail of Fix''' || The scanning of pallets into a trans-ship depot will display the resources of the radial delivery trip to redirect the pallet for loading.                                                                             
 
This data should be displayed promptly on screen.                                                           
 
A new reason code NONR will be available for Freight Not Received to retain the order on the deivery trip and its tracking references as order items.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: MCS ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 371993
|-
|'''Summary of Call'''|| MCS Speed
|-
|'''Detail of Fix''' || Fix to speed up MCS trans ship process.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: INC33347016 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 373102
|-
|'''Summary of Call'''|| CTMS Revenue Issue
|-
|'''Detail of Fix''' || Amendment to standard invoice generation process to correctly populate the period from/to dates ahead of invoice validation.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: ORS Report ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 372062
|-
|'''Summary of Call'''|| SCHED_ORDS ORS report - start / stop
|-
|'''Detail of Fix''' || The ORS master data has been changed for the 'MORT' database to include a DATETIME format for the SCHED_ORDS report for the Start Time and End Time for the trips.                                                                                                   
 
The ORS master data has been changed for the 'MORT' database to include a range of values for the SCHED_ORDS and TRIPS reports for the Schedule for the trips.                                                                                                       
 
The text 'SYSSCHED' has been introduced for the fields for the schedules for selection.                                                                     
 
This text can include a number of offset days, for example, 'SYSSCHED-1' or 'SYSSCHED+1'.                                                                       
 
If the report includes a range of schedules, the specified schedules will be assessed to ensure that they are sequential for the report to select any data.                                                       
 
For example, 'SYSSCHED-1' must be earlier than 'SYSSCHED' or 'SYSSCHED+1' or a specified schedule such as '200421' where 'SYSSCHED-1' translates as '200420'.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Customer Ref: Direct email ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 372371
|-
|'''Summary of Call'''|| INVOICING Issue >20 SLB (following lines)
|-
|'''Detail of Fix''' || Changes to file format to accomdate >20 SLBs
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: DU Type ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 372455
|-
|'''Summary of Call'''|| DU Type for mandated carriers
|-
|'''Detail of Fix''' || The schceduling engine will assess the orders with a mandated carrier with reference to the type of carrier and its DU types.                                                                                           
 
A carrier type of PARCEL requires its orders to be assigned to PCL trips to derive the carrier service level from the carrier route, then the label can be printed for the carrier.                                                                                     
 
The ordered DUs must be listed for the carrier shipment information for the order to be assigned to a trip for the carrier.                                                                                   
 
The order will not be assigned to another type of trip for the mandated carrier.                                                                                   
 
A carrier type not of PARCEL can assign its orders to other types of trips when it contains DUs that are not of the PARCEL category.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
== Customer Ref: No Ref ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 372610
|-
|'''Summary of Call'''|| TMP files
|-
|'''Detail of Fix''' || The POD_INFO files will be generated when an order on a delivery trip for a customer with system parameter OMS_CREATE_POD set to Y is debriefed with some stock being delivered.                                                                                             
 
If the order has been debriefed but its delivery trip stop has not yet been debriefed and the EDI parameter CHECK_STOP_TIMES is set to Y, the order will not be included in a file at that time.                                                                             
 
An empty TMP file will not be generated on the server.                                                                                                     
 
If the order has been debriefed but its delivery trip stop has been debriefed, the order will be included in a file.                                                                                                     
 
The file will be archived and transferred as required.                                                       
 
A TMP file will not remain on the server.
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: No Ref ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 372612
|-
|'''Summary of Call'''|| C-TMS ORS tables
|-
|'''Detail of Fix''' || Actual distance added to ORS, populated from microlise
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
 
== Customer Ref: INC32181522 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 370887
|-
|'''Summary of Call'''|| CTMS won't give user an option to retain
|-
|'''Detail of Fix''' || Changes to the order screen to prompt the user to save packing details before unscheduling an order
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
 
== Customer Ref: INC32202627 ==
{| width="100%"
|-
|width="30%"|'''OBS Log Number:'''|| 370965
|-
|'''Summary of Call'''|| Has auto scheduled MSD/H61 orders
|-
|'''Detail of Fix''' || Amendment to Scheduling engine to prevent orders being scheduled onto Van fleet trunk trips
|-
|'''Set-up and Configuration''' || No set-up/configuration required
|}
|}


Revision as of 15:20, 19 June 2020





Aptean Logo.png







OBS Logistics Ltd

Release Notes

CALIDUS TMS

15th June 2020 - 1.0
Reference: P037











































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

Customer Ref: PO44010941382

OBS Log Number: 369552
Summary of Call Allow Pallet Opening
Detail of Fix The seal number is displayed with the consignment number and the air waybill number in the Shipment Pallets screen.

The seal number will be removed for a pallet that is opened.

The seal number itself will be deleted when it contains no pallets or loose items.

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


Customer Ref: Email / SMS Delivery

OBS Log Number: 370562
Summary of Call Email / SMS Delivery
Detail of Fix SMS and emails will be sent to the recipients of the orders based on the formats of the SMS_EMAIL messages for the appropriate medium of SMS or EMAIL.

The data will be converted for the new PO_REF, DEL_DATE_AM and DEL_DAY_AM formats.

PO_REF will be obtained from a reference of that type for the order.

AM will be translated as AM for the morning or PM for the afternoon for the arrival time of the trip stop at the location.

Orders that are on the trip when the status is updated will be assessed for the single message event by trip.

Any orders that are assigned to a trip at the required status will be assessed individually for the single message by order and trip.

Added collection orders can trigger a message event for an EN-ROUTE trip but delivery orders cannot.

System parameter SEND_SMS_EMAIL when Y only triggers message events at ACCEPTED trip status.

When set to a specific trip status, the message event will be triggered at that trip status instead.

System parameter TRM_SEND_PRE_DELIVERY_MSG when Y will trigger message events at TENDERED and EN-ROUTE trip status.

These message events must be formatted at the appropriate trip status to be sent.

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


Customer Ref: Driver Documentation

OBS Log Number: 370563
Summary of Call Driver Documentation
Detail of Fix New Driver Documents for Loading and Delivery
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0035756

OBS Log Number: 366572
Summary of Call GSN:Change to data sent out
Detail of Fix Changes to the Microlise flow to send Child locations and sub haulier type and receive signatures from Microlise at order level
Set-up and Configuration No set-up/configuration required


Customer Ref: New Field

OBS Log Number: 369101
Summary of Call HAM-MCS-Cage Confirmation Scans
Detail of Fix The Location Maintenance screen will display a new field for MCS called Pallet Building Process with values Continuous or Single to select.

These values are stored in new decode MCS_PALLET_BUILD_PROCESS.

Continuous will be the default value.

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


Customer Ref: WREQ0038434

OBS Log Number: 369921
Summary of Call Modification to MLS interface
Detail of Fix Changes to the MLS interface for direct shipments and additional warehouses
Set-up and Configuration No set-up/configuration required


Customer Ref: Trip Sheet

OBS Log Number: 370252
Summary of Call DUN Trip Sheet - Font size
Detail of Fix Increase font size and align fields in new recyclable uplift section.
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0039173

OBS Log Number: 370545
Summary of Call GSN:Remove the iForce code (368669)
Detail of Fix The system parameter ZET_INC_SSCC_PREFIX will only apply to the 05050210 items and not the 202 items.

The 00 prefix will be added to the 0505210 items for files from C-TMS to ZETES and removed for the files from ZETES to C-TMS when the length of the order item is 18 digits.

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


Customer Ref: WREQ0039012

OBS Log Number: 370827
Summary of Call GSN:Populate Carrier field in CTMS
Detail of Fix Changes to allow Carrier field to be viewed in the order well
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0040219

OBS Log Number: 371513
Summary of Call GSN:Update to FCA POD file
Detail of Fix The 'CLICK_OUTBOUND' report will assess the different types of despatch units for the order items to determine if any contents of those order items will be included in the report.

If any of the 'CRT', 'PLT' or 'UKN' items include contents, the contents will not be included in the extract - this is consistent with the 'LSE' items.

Contents will only be shown for items which are NOT 'CRT', 'PLT', 'UKN' or LSE. If the SUPPRESS_ASSETS parameter is Y, the item contents will be included for the other DU types.

If the SUPPRESS_ASSETS parameter is N, only the items will be included.

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


Customer Ref: WREQ0041335

OBS Log Number: 372123
Summary of Call Allow invoices to be resent
Detail of Fix A new function called FN_RE_SEND_INVOICE is available to authorise for a user to enable invoices to be re-sent in an export file.

A new button called Release will be displayed in the Invoice Summary screen to enable the user to remove the invoice from the export file.

A new button called Re-Send will be displayed in the Invoice Exports screen to enable the user to re-send a processed export file.

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


Customer Ref: WREQ0042286

OBS Log Number: 372581
Summary of Call Gradual restart of operations
Detail of Fix New parameter added to use the slot data when exporting to Paragon (DUN format only).
Set-up and Configuration No set-up/configuration required


Customer Ref: Chargeable MNX

OBS Log Number: 370371
Summary of Call CTMS data
Detail of Fix Changes to MIS , tables added
Set-up and Configuration No set-up/configuration required


SUPPORT INCIDENTS

Customer Ref: Resource Screen

OBS Log Number: 364730
Summary of Call Trip Resource screen
Detail of Fix The allocation of resources to trips will display a long error message when the trailer is being validated.

The crew and diary versions also have been changed.

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


Customer Ref: Trunk Trip

OBS Log Number: 369482
Summary of Call Different trunk trip comment for INV_TRA
Detail of Fix Amended comment for the item reason to include the text 'different trunk trip' for an unload scan as well as a load scan using RDT.

This format will enable Inventory Transactions to be identified for trunk trips.

Inventory Transactions will include items on the scanned trunk trip or the planned trunk trip as long as the item has not been scanned on a different trunk trip.

Orders which originate in an RDC will be assessed for a trunk trip.

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


Customer Ref: TMS characts to epod

OBS Log Number: 370023
Summary of Call Limit charaters from TMS to EPOD to 40
Detail of Fix The EPL_DESCRIPTION and EPL_CONTAINER_PACKAGE_DESC items will only contain a maximum of 40 characters.

Any text that is longer than 40 characters in length in C-TMS will be truncated for display in EPOD.

These changes apply to the main version of the outbound EPOD files.

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


Customer Ref: N/A

OBS Log Number: 370926
Summary of Call System speed and performance
Detail of Fix Improve speed of the domestic scheduling loops by using a date range to select orders.
Set-up and Configuration No set-up/configuration required


Customer Ref: INC32503211

OBS Log Number: 371795
Summary of Call Unable to export data
Detail of Fix Amendment to parcel carriers data select to improve performance.
Set-up and Configuration No set-up/configuration required


Customer Ref: MCS

OBS Log Number: 371819
Summary of Call MCS - Performance
Detail of Fix The scanning of pallets into a trans-ship depot will display the resources of the radial delivery trip to redirect the pallet for loading.

This data should be displayed promptly on screen.

A new reason code NONR will be available for Freight Not Received to retain the order on the deivery trip and its tracking references as order items.

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


Customer Ref: MCS

OBS Log Number: 371993
Summary of Call MCS Speed
Detail of Fix Fix to speed up MCS trans ship process.
Set-up and Configuration No set-up/configuration required


Customer Ref: INC33347016

OBS Log Number: 373102
Summary of Call CTMS Revenue Issue
Detail of Fix Amendment to standard invoice generation process to correctly populate the period from/to dates ahead of invoice validation.
Set-up and Configuration No set-up/configuration required


Customer Ref: ORS Report

OBS Log Number: 372062
Summary of Call SCHED_ORDS ORS report - start / stop
Detail of Fix The ORS master data has been changed for the 'MORT' database to include a DATETIME format for the SCHED_ORDS report for the Start Time and End Time for the trips.

The ORS master data has been changed for the 'MORT' database to include a range of values for the SCHED_ORDS and TRIPS reports for the Schedule for the trips.

The text 'SYSSCHED' has been introduced for the fields for the schedules for selection.

This text can include a number of offset days, for example, 'SYSSCHED-1' or 'SYSSCHED+1'.

If the report includes a range of schedules, the specified schedules will be assessed to ensure that they are sequential for the report to select any data.

For example, 'SYSSCHED-1' must be earlier than 'SYSSCHED' or 'SYSSCHED+1' or a specified schedule such as '200421' where 'SYSSCHED-1' translates as '200420'.

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


Customer Ref: Direct email

OBS Log Number: 372371
Summary of Call INVOICING Issue >20 SLB (following lines)
Detail of Fix Changes to file format to accomdate >20 SLBs
Set-up and Configuration No set-up/configuration required


Customer Ref: DU Type

OBS Log Number: 372455
Summary of Call DU Type for mandated carriers
Detail of Fix The schceduling engine will assess the orders with a mandated carrier with reference to the type of carrier and its DU types.

A carrier type of PARCEL requires its orders to be assigned to PCL trips to derive the carrier service level from the carrier route, then the label can be printed for the carrier.

The ordered DUs must be listed for the carrier shipment information for the order to be assigned to a trip for the carrier.

The order will not be assigned to another type of trip for the mandated carrier.

A carrier type not of PARCEL can assign its orders to other types of trips when it contains DUs that are not of the PARCEL category.

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


Customer Ref: No Ref

OBS Log Number: 372610
Summary of Call TMP files
Detail of Fix The POD_INFO files will be generated when an order on a delivery trip for a customer with system parameter OMS_CREATE_POD set to Y is debriefed with some stock being delivered.

If the order has been debriefed but its delivery trip stop has not yet been debriefed and the EDI parameter CHECK_STOP_TIMES is set to Y, the order will not be included in a file at that time.

An empty TMP file will not be generated on the server.

If the order has been debriefed but its delivery trip stop has been debriefed, the order will be included in a file.

The file will be archived and transferred as required.

A TMP file will not remain on the server.

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


Customer Ref: No Ref

OBS Log Number: 372612
Summary of Call C-TMS ORS tables
Detail of Fix Actual distance added to ORS, populated from microlise
Set-up and Configuration No set-up/configuration required


Customer Ref: INC32181522

OBS Log Number: 370887
Summary of Call CTMS won't give user an option to retain
Detail of Fix Changes to the order screen to prompt the user to save packing details before unscheduling an order
Set-up and Configuration No set-up/configuration required


Customer Ref: INC32202627

OBS Log Number: 370965
Summary of Call Has auto scheduled MSD/H61 orders
Detail of Fix Amendment to Scheduling engine to prevent orders being scheduled onto Van fleet trunk trips
Set-up and Configuration No set-up/configuration required


TID CHANGES

OBS Log Number:

Cust Ref: Reporter:
Summary of Call
Detail of Fix
Set-up and Configuration


OBSL 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
AT_ACC_INV_EXPORT_INV_370371.sql 1.1 AT Script 370371
AT_ACC_SERVICE_RATES_370371.sql 1.1 AT Script 370371
AT_ACC_SERVICES_370371.sql 1.1 AT Script 370371
AT_GEO_LOCATION_369101.sql 1.1 AT Script 369101
AT_INT_XML_ORD_HEADER_366572.sql 1.1 AT Script 366572
AT_SCH_ORD_ITEMS_370563.sql 1.1 AT Script 370563
AT_SCH_ORD_ITEMS_CONTENT_370563.sql 1.1 AT Script 370563
AT_SCH_ORD_SERVICES_370371.sql 1.1 AT Script 370371
CSV.sql 5.120 CSV extract package 372581
DATA_ADM_FUNCTION_372123.sql 1.1 Data Script 372123
DATA_ADM_MSEL_FORM_PARAM_372745.sql 1.1 Data Script 372745
DATA_ADM_SYSTEM_PARAM_366572.sql 1.1 Data Script 366572
DATA_ADM_SYSTEM_PARAM_370563.sql 1.1 Data Script 370563
DATA_ADM_SYSTEM_PARAM_370827.sql 1.1 Data Script 370827
DATA_ADM_SYSTEM_PARAM_372581.sql 1.2 Data Script 372581
DATA_ADM_SYSTEM_PARAM_CONFIG_370563.sql 1.1 Data Script 370563
DATA_ADM_SYSTEM_PARAM_CONFIG_366572.sql 1.1 Data Script 366572
DATA_ADM_SYSTEM_PARAM_CONFIG_370926.sql 1.1 Data Script 370926
DATA_IMP_DECODE_369101.sql 1.1 Data Script 369101
DATA_IMP_DECODE_ENTRY_369101.sql 1.1 Data Script 369101
DATA_MSG_SMS_VALUES_370562.sql 1.1 Data Script 370562
DATA_ORS_MASTER_DATA_372062.sql 1.2 Data Script 372062
DATA_REP_REPORT_370563.sql 1.1 Data Script 370563
DATA_REP_REPORT_PARAM_370563.sql 1.1 Data Script 370563
DELIVERY_DOCS.rep 1.1 Report 370563
DP_BNL_EDI_IN.sql 1.11 Inbound EDI Package 369921
DP_CSV_DUN.sql 5.55 Client specific CSV extracts 369482
DP_CSV_POD.sql 1.7 POD CSV Database Package 372610
DP_EPOD_WEB_SERVICE.sql 1.126 EPOD Web Service 370023
DP_INT_XML_CARPOD.sql 5.7 Inbound EDI Carrier POD Interface 366572
DP_INT_XML_MIC2.sql 1.33 CTMS to MIC Interface 372612
DP_MCS_SCANNING.sql 5.64 MCS Scanning Package 369552
DP_MCS_SCANNING.sql 5.65 MCS Scanning Package 371819
DP_MCS_SCANNING.sql 5.66 MCS Scanning Package 371993
DP_MIS.sql 5.5 MIS Interface Package 370371
DP_RDT_FAST_UNLOAD.sql 5.46 RF Unload Package 369482
DP_REPORTS.sql 5.61 Reports package 371513
DP_REPORTS.sql 5.62 Reports package 372062
DP_SCHEDULING_ENGINE.sql 5.160 Scheduling Package 370926
DP_SCHEDULING_ENGINE.sql 5.161 Scheduling Package 370965
DP_SCHEDULING_ENGINE.sql 5.162 Scheduling Package 371795
DP_SCHEDULING_ENGINE.sql 5.163 Scheduling Package 372455
DP_SHIPMENT.sql 5.30 Shipment Code package 373178
IMP.sql 5.199 CSV Imports Package 372770
IMPORTS_EXEC.fmx 10.21 Import executions 372770
INT_XML_IN.sql 5.199 Order Import Package 370019
INT_XML_IN.sql 5.200 Order Import Package 373178
INT_XML_MIC.sql 5.148 MIC interface 366572
INT_XML_OUT2.sql 5.302 Outbound XML Package 366572
INT_XML_OUT2.sql 5.303 Outbound XML Package 370545
INT_XML_OUT2.sql 5.304 Outbound XML Package 373784
INV.sql 5.50 Invoice Package 372123
INV.sql 5.51 Invoice Package 373102
INVOICES.fmx 2.63 Invoices Screen 372123
LOADING_LIST.rep 1.1 Report 370563
LOCATION.fmx 2.193 Location Maintenance 369101
MSG_PROCESSING.sql 5.71 Message Processing package 370562
OF_INT.sql 5.62 Oracle Financials interface 372371
ORDERS.fmx 2.430 Order Screen 370887
ORDERS_WIDE.fmx 1.29 Orders Screen 370887
ORS.fmx 1.30 Oracle Reporting suite 372062
PAR_INT.fmx 10.41 Paragon Interface form 372770
PLANNING.fmx 1.112 Planning Screen 370827
PLANNING.fmx 1.113 Planning Screen 370563
RTE.sql 5.25 Route Package 371105
SCH.sql 5.9 Scheduling package 372062
SHIPMENT_PALLETS.fmx 5.9 Shipment Pallets Form 369552
TIU_TRIP_STATUS.sql 5.55 Trigger on SCH_TRIP for status change 370562
TRG_ACC_INV_EXPORT_INV_BIU.sql 5.3 Trigger 370371
TRG_ACC_SERVICE_RATES_BIU.sql 5.3 Trigger 370371
TRG_ACC_SERVICES_BIU.sql 5.3 Trigger 370371
TRG_SCH_ORD_SERVICES_BIU.sql 5.3 Trigger 370371
TRG_SHA_LOAD_TRIPS.sql 1.10 Trigger 370562
TRG_SOI_XML.sql 5.20 Trigger 371378
TRIP_PLAN.fmx 1.274 Trip Planning Screen 370827
TRIP_PLAN.fmx 1.275 Trip Planning Screen 372966
TRIP_RES.fmx 1.25 Resource Allocation 364730
TRIP_RES_CRW.fmx 1.5 Trip Resource Crew screen 364730
TRIP_RES_DIARY.fmx 1.33 Resource Allocation 364730
TRIP_SHEET_DUNELM_DETAIL.rep 5.27 Driver Trip Sheet for Dunelm 370252
TRIPSUM.fmx 2.439 Trip Manipulation screen 370827
TRIPSUM.fmx 2.440 Trip Manipulation screen 372966
TRM.sql 5.198 Trip manipulation package 371105
UNSCHED_ORDERS.rep 1.5 Unscheduled Order Report 370827
V_MCS_SITE.sql 1.5 View 369101


ADDITIONAL CHANGES

WCS

There are no WCS changes required.


EPOD/T2A

There are no ePOD/T2A changes required.


MCS

A MCS change is required for the following logs:

  • Log 369101 (MCS v0.13)
  • Log 369552 (MCS v0.14)
  • Log 371819 (MCS v0.14)


PORTAL/TTM

There are no Portal changes required.


EDI

There are no EDI changes required.


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