PATCH CTMS P038

From Calidus HUB
Revision as of 09:03, 16 December 2020 by StylesC (talk | contribs) (Created page with "<div class="noprint"> {{#vardefine:Client|OBS}} {{#vardefine:ClientName|OBS Logistics Ltd}} {{#vardefine:System|''CALIDUS'' TMS}} {{#vardefine:Doc_Title|Release Notes}} {{#vardef...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)





Aptean Logo.png







OBS Logistics Ltd

Release Notes

CALIDUS TMS

15th Dec 2020 - 1.0
Reference: P038











































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: PO-087071

OBS Log Number: 360569
Summary of Call Web service request for PWSCORE
Detail of Fix New Order Enquiry Webservice for PWSCORE
Set-up and Configuration No set-up/configuration required


Customer Ref: Order Integration

OBS Log Number: 370557
Summary of Call Order Integration
Detail of Fix Changes to the Inbound XML for integration
Set-up and Configuration No set-up/configuration required


Customer Ref: Booking Integration

OBS Log Number: 370558
Summary of Call Booking Integration - Update back to OR3
Detail of Fix New outbound flow from C-TMS to OR3
Set-up and Configuration No set-up/configuration required


Customer Ref: Email Order

OBS Log Number: 370560
Summary of Call Email output of order booking
Detail of Fix Changes for Customer Services screen.
Set-up and Configuration No set-up/configuration required


Customer Ref: Format File

OBS Log Number: 373655
Summary of Call Data Warehouse format file (tab)
Detail of Fix New system parameter MIS_TAB_DELIMITER exists to use a tab as a delimiter for the MIS extracts. When this parameter is Y, a tab will be used as a delimiter for the MIS extract files.

Assesses a new value for the MIS query to use:

Transactional will use created date and updated date within the date ranges for the MIS report values of 'P_from_date' and 'p_to_date' to select records.

The standard delimiter should be setup as '||'@'||' for conversion to a tab delimiter.

Reference (which is the default value) will use the existing queries.

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


Customer Ref: CSV Import

OBS Log Number: 375194
Summary of Call CSV import changes
Detail of Fix System parameter TRM_PROTECT_SHUNTS will be used to resequence the trips stops by planned arrival and departure times.

The trip stops will be created for the different types of trips for the orders.

These trips will include shunts between the same locations, collections from suppliers and deliveries to stores.

The collection stops from suppliers will be fixed to the planned available times of the orders on the stops.

These stops will contain orders for the same time windows for collection or delivery.

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


Customer Ref: CR-41

OBS Log Number: 370034
Summary of Call Asset to Asset Scanning
Detail of Fix The new T2A functionality for transport units will be available in the new Forward Items and Unload screens.

The latest version 4.0.0.0 of T2A will need to be released with this development.

The reason codes AP (Added to Primary Transport Unit), TU (Successfully Unloaded Contents from Primary Transport Unit) and UU (Unexpectedly Unloaded Contents from Primary Transport Unit) will need to be setup for type ITEM_NON_CON when Forward Items is active.

The new system parameter T2A_ASSET_ARRIVED_OFFSET_DAYS can be set with a number of days to select DELIVERED orders that have arrived at the depot.

The new system parameter T2A_ASSET_DUE_OFFSET_DAYS can be set with a number of days to select planned orders that are due to arrive at the depot.

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


Customer Ref: IM01-IM02

OBS Log Number: 373052
Summary of Call ARM: Mapping & Mods to Order Flow
Detail of Fix The inbound EDI process will have new parameters available to set the ordered quantity for orders based on the weight of the order lines when an ordered quantity cannot be provided.

An EDI parameter called CALC_ORD_DU_QTY can be set to Y to activate the new functionality.

An EDI parameter called WEIGHT_BASED_DU_QTY can be set to Y to enable a calculation to be performed for the WEIGHT provided and the Max Kg of the DU type.

The ordered quantity will then be based on the WEIGHT/Max Kg with the next whole number used.

If this calculation is not supported by the absence of a WEIGHT provided or the Max Kg for the DU type, an EDI parameter called DFLT_DU_QTY can be set to a number to specify that a default number of DUs will be ordered.

Note the EDI parameter VOLUME_BASED_DU_QTY_QTY overrides the weight calculation and default.

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


Customer Ref: IM03

OBS Log Number: 373053
Summary of Call ARM: Parcel Load Message
Detail of Fix Changes to prevent messages from being sent more than once when PREVENT_RESEND_ORDER is added to flow and set to Y
Set-up and Configuration No set-up/configuration required


Customer Ref: IM04

OBS Log Number: 373054
Summary of Call ARM: Core Fleet Parcels
Detail of Fix Exclude du categorys from Scheduling engine based on specific parameters
Set-up and Configuration No set-up/configuration required


Customer Ref: IM05

OBS Log Number: 373055
Summary of Call ARM: Pack message flow JDA - CTMS
Detail of Fix New functionality is available for the order packing processes for XML files, CIPD files and manual packing, unpacking and label printing in CTMS.

See functional specification 'FS-373055 - ARM - IM05 Pack Message Flow JDA - CTMS for Parcel Carrier Orders v3.0' for further advice about setup to activate the new functionality.

This development will enable unscheduled orders to be packed for the standard packing process.

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


Customer Ref: IM08

OBS Log Number: 373057
Summary of Call ARM: Core Fleet Labels
Detail of Fix Changes to allow labels to be printed for UNSCHEDULED and SCHED_COLL orders
Set-up and Configuration No set-up/configuration required


Customer Ref: IM09

OBS Log Number: 373058
Summary of Call ARM: Shunt / Trunk Planning
Detail of Fix The new system parameter called PAR_SHUNT_TRUNK can be set to Y to enable the Paragon interface to maintain shunt/trunk trips based on fixed routes instead of cross-dock paths.

A new button called Schedule to Depot will be displayed in the Order Export page of the Paragon Interface screen from which the UNSCHEDULED orders can be cross-docked before the Export button is used.

The Export button will validate first that an order exists that has been cross-docked before any orders are exported to Paragon.

The Schedule to Depot process is intended to cross-dock all available orders.

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


Customer Ref: IM10

OBS Log Number: 373088
Summary of Call ARM: Stage Planning- Schedule for parcel
Detail of Fix A Carrier Trunk flag has been introduced for the Fixed Routes to enable cross-docking of orders for collection by parcel carriers.

This flag will be effective for TRUNK route types in the scheduling engine for parcel carriers.

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


Customer Ref: IM12 (split IM13-14)

OBS Log Number: 373091
Summary of Call ARM: Load Message for JDA
Detail of Fix New functionality is available for the triggering and generaion of the LOAD files in CTMS.

See functional specification 'FS-373091 - ARM - IM12 Load Message for JDA v2.0' for further advice about setup to activate the new functionality.

This development will enable orders to be triggered only when they have not been sent previously for the same EDI process.

New references will be available in the output files based on new EDI parameters INC_TRIP_ACTION for a trip reference and INC_TRIP_TYPE for an order reference.

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


Customer Ref: IM15 (split IM16)

OBS Log Number: 373092
Summary of Call ARM: Despatch Messages from JDA
Detail of Fix Changes to the EDI processing to receive a Despatch message from JDA - New EDI parameters required on the flow.
Set-up and Configuration No set-up/configuration required


Customer Ref: IM17

OBS Log Number: 373093
Summary of Call ARM: Report re-label required
Detail of Fix A new export called 'Orders for Relabelling' is available to authorise to users to create an extract for a specified schedule of orders that have had labels printed before they were scheduled for delivery and then they have been scheduled for delivery to a carrier with a different label format.
Set-up and Configuration No set-up/configuration required


Customer Ref: Screening charge

OBS Log Number: 373170
Summary of Call Screening Fee
Detail of Fix Changes to the Finance function to allow Screening charges to be calculated and configured
Set-up and Configuration No set-up/configuration required


Customer Ref: IM13 - IM14 (split)

OBS Log Number: 373631
Summary of Call ARM: Load Message for JDA at a Hub
Detail of Fix UNLOAD and LOAD messages will be available for configuration at a hub location.

Trips for unloading and loading at a depot to cross-dock orders will be triggered by the usual methods for the EDI processes: updating the trip status to a specific status, updating the planned trip stop times, assigning an order to the trip whilst at the specified trip status.

The depot for the EDI process will apply to the location where the trip is being unloaded or loaded.

An UNLOAD message will require the new EDI parameter UNLOAD_ONLY to be set to Y otherwise the EDI process will apply to LOAD messages as standard.

New EDI parameters will apply to the orders to include in the UNLOAD and LOAD messages and if these messages need to be delayed until previous EDI messages have been received to provide the expected level of data to include in these messages.

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


Customer Ref: IM16 (split)

OBS Log Number: 373633
Summary of Call ARM: Receipt Messages from JDA
Detail of Fix RCVD messages will be available for receipt scans into a hub location.

EDI parameters may be configured to ensure that these scans are only used for auditing purposes or to update the scanned items as packed nd despatched as tracking references.

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


Customer Ref: PO 44010989681

OBS Log Number: 374133
Summary of Call SCR:Extract Suite changes
Detail of Fix The TRIP_TYPE reporting suite extract will include new columns for Start DateTime and End DateTime. These columns will select the same data as the existing Start Time and End Time columns and they can be used as alternative columns.

The new columns can be used as selection criteria with a range of dates and times.

The same columns will be available for the EX_TRIP reporting suite extract.

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


Customer Ref: IM12 - 2

OBS Log Number: 377157
Summary of Call ARM: LOAD Message with Child Addresses
Detail of Fix A new EDI parameter called INC_ORDER_CHILD_ADDR has been introduced to include any child addresses for the delivery location of the order in the ORDER_HEADER_ADDRESS section.

The ADDRESS_ID will further be decoded to the original location code for the child location using the CN_LOCATION_MAPPING.

This EDI parameter is intended to be made active for LOAD messages to specific WMS source systems.

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


Customer Ref: WREQ0049241

OBS Log Number: 378047
Summary of Call GSN:Add Customer Ref to UKMAIL Label
Detail of Fix Changes to the UKMAIL label to show external ref
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0049355

OBS Log Number: 378048
Summary of Call GSN:Change Import xml from CTMS to EFX
Detail of Fix The new system parameter EFX_INV_TRIP_VEH_TYPE controls the population of the VEHICLE_TYPE in the EFX files:

When N: TRIP level: NULL, ORDER level: TIPPER

When Y: TRIP/ORDER level: Trailer type for the trip stops

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


Customer Ref: WREQ0050167

OBS Log Number: 378203
Summary of Call GSN:Changes to DTS label
Detail of Fix Changes to the Label format for DTS
Set-up and Configuration No set-up/configuration required


Customer Ref: Customer Account

OBS Log Number: 378263
Summary of Call Customer Account - going on hold
Detail of Fix The customer and its available orders can be placed on hold via a new EDI process or via the Customer Maintenance screen using the new AccOn Hold tick box.

Orders may be updated to a status of ON-HOLD and released to their appropriate status of INVALID or UNSCHEDULED afterwards.

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


Customer Ref: WREQ0050313

OBS Log Number: 378264
Summary of Call GSN:Flow - Output IF007B and IF054
Detail of Fix New CFX interface , sending trips when status changed to Tendered
Set-up and Configuration No set-up/configuration required


Customer Ref: TID-Microlise

OBS Log Number: 378652
Summary of Call Prevent empty resource tags
Detail of Fix Prevent empty resource tags from being sent to Microlise set MIC_SEND_EMPTY to Y to use the functionality
Set-up and Configuration No set-up/configuration required


Customer Ref: WREQ0030373

OBS Log Number: 376771
Summary of Call CTMS & Microlise Improvements (2)
Detail of Fix Changed to Paragon and Microlise processing
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


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


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_CTMS_P038&oldid=9236’