CTMS 11.0 ER027-009

EMERGENCY RELEASE - CTMS 11.0

RELNOTE ER027-009

Module	Program Name	Ver	Call/Iss	Client Ref	Pr'ty	Remarks	Reporter
AT_INT_TMS_WMS_CONTROL_346772.sql	Alter Table Script	1.2	346772	WMS-TMS-IF/004	3	A database script will alter a database table to extend the length of the event type for the TMS-WMS interface control records.	Tony Walker

Module	Program Name	Ver	Call/Iss	Client Ref	Pr'ty	Remarks	Reporter
LOCATION.fmx	Location Maintenance	2.184	346777	WMS-TMS-IF/009	3	New message events for WMS_INT_FAIL for the WMS-TMS interface records. Message requests can be setup in TMS: Message type: WMS_INT_FAIL Medium: SMS or EMAIL Trigger: ORD, ORDA, ALC, PLIST, LOA, PACK or MAR Subject: Order Creation, Order Amendment, Allocation, Pick List, Pick Confirmation, Pack Confirmation or Despatch Confirmation Format: <ERR_MSAGE> (this will insert the error message in the EMAIL or SMS) Triggers can also be setup for DBAI (database connectivity problems between WMS and TMS) or DBAO (database connectivity problems between TMS and WMS). Each message trigger is optional. These message events can be reviewed in the Medium Audit page in the Messaging Maintenance screen where the message events will also be setup in TMS. The interface records themselves can be reviewed in the TMS-WMS and WMS-TMS pages in the Interface Errors screen as usual. The owner in WMS can be setup to have an email address per interface message type and these addresses will be used to send emails for failed processes in WMS should they exist. If they do not exist the equivalent message requests in TMS will be used (excepting database connectivity problems which must be generated out of the processing database). If email or SMS are not setup a user will not be informed of any problems with the processing of the interface records. Note that the database connectivity problems will require the message to be setup for MTS_OWNER user to control the message request and the recipients. For this reason the WMS Params page in the Location Maintenance screen can be used to store the contacts for new 199 (WMS to TMS) and 299 (TMS to WMS) message types.	Tony Walker
DATA_1_MSG_EVENT_TYPE_346777.sql	Data Script	1.1	"	"	"	"	"
DATA_2_MSG_TYPE_346777.sql	Data Script	1.1	"	"	"	"	"
DATA_3_MSG_REQ_346777.sql	Data Script	1.1	"	"	"	"	"
DATA_4_MSG_SMS_VALUES_346777.sql	Data Script	1.2	"	"	"	"	"
T_MSG_EVENT_IUD.sql	Trigger	1.2	"	"	"	"	"
DP_INT_TMS_WMS_IN_STUB.sql	TMS-WMS Interface Package	1.5	"	"	"	"	"
MSG_PROCESSING.sql	Message Processing Package	5.63	"	"	"	"	"

Module	Program Name	Ver	Call/Iss	Client Ref	Pr'ty	Remarks	Reporter
AT_INT_TMS_WMS_MAINT_346789.sql	Alter Table Script	1.1	346789	WMS-TMS-IF/015	3	Changes have been made to the TMS-WMS interface including: 1. Include parameter DEFAULT_PACKAGE_TYPE for PACK messages when the package type is not known. 2. Include parameter INC_MANDATED_CARRIER to orders to have a mandated carrier from the carrier of the sales order. Uses import decode WMS_CARRIER_MAPPING. 3. Set the actual weight not the planned weight an added item at pick/pack. 4. Set the actual despatched quantity of order lines for pick/pack to then calculate the actual despatched RPE quantity. 5. Only sets the order unpacked order lines to be zero packed if the order has been updated with actual pick containers. 6. An order line with zero planned quantity will be deleted for ORD/ORDA messages. 7. An order line with zero planned and packed quantity will be deleted for LOA messages.	Tony Walker
DP_INT_TMS_WMS_IN_STUB.sql	TMS-WMS Interface Package	1.3	"	"	"	"	"

Warning:

A manual change is required with this release - DP_INT_TMS_WMS_IN v1.5