CTMS 11.0 ER025-044

EMERGENCY RELEASE - 11.0

RELNOTE ER025-044

Module	Program Name	Ver	Call/Iss	Client Ref	Pr'ty	Remarks	Reporter
INT_XML_OUT2.sql	Outbound EDI Package	5.256	344618	-	1	OPtional FTP log and amend copy for customer processing	Michelle

Module	Program Name	Ver	Call/Iss	Client Ref	Pr'ty	Remarks	Reporter
DATA_RES_LABEL_FORMATS_344921.sql	Data Script	1.1	344921	-	1	The UKMail labels and electronic manifests will be consistent: Weight has been rounded up to the next highest whole number. Collection date is the previous working day before the delivery date for the service level of the order. The account postcode is from the originating depot of the order and not the despatching depot should the order be cross-docked. The 2D barcode text does not mention UKMail. The 2D barcode will contain the same data that is printed on the label. The customer express tracking number for the shipment can be based on a 9 or 10 digit number: The tracking number will always be 9 digits left padded with zeroes and with the 10th digit as a check digit. The check digit will replace the 10th digit of the tracking number range should there be more than 9 digits. Note that the collection date for UKMail electronic manifests will be stored in the STOP_PLANNED_ARRIVAL_DATE and STOP_PLANNED_DEPARTURE_DATE tags in the file for mapping. The changes to the outbound EDI files will only present for electronic manifests for carriers that have a label format of UKMail. The other files for LOTS, LOAD, CITD, Microlise, etc. will not be changed. The WEIGHT in the electronic manifest files will not be rounded up at the DU type level because the weights will be subtotalled and rounded up to the next highest whole number by external mapping.	Denis Starodubov
DP_CARRIER.sql	Carrier Maintenance Database Package	1.64	"	"	"	"	"
INT_XML_OUT2.sql	Outbound EDI Package	5.259	"	"	"	"	"