290934 - Revision history

Middletong: /* Transmission */

2012-10-29T14:36:43Z

Transmission

← Older revision		Revision as of 16:36, 29 October 2012
Line 2,123:		Line 2,123:
	*CTMS_CITD_FTP_DESTINATION_USERNAME		*CTMS_CITD_FTP_DESTINATION_USERNAME
	*CTMS_CITD_FTP_DESTINATION_PORT		*CTMS_CITD_FTP_DESTINATION_PORT

			=REFERENCES=

			{\| Border="1"
			\| <center>'''Ref No'''</center>
			\| <center>'''Document Title & ID'''</center>
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>

			\|-
			\| <center>1</center>
			\| EST-290934 NW-8KEMRU Parcel Carrier Management v2.0.doc
			\| <center>2.0</center>
			\| <center>26/08/11</center>
			\|}


			=DOCUMENT HISTORY=

			{\| Border="1"
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>
			\| <center>'''Status'''</center>
			\| <center>'''Reason'''</center>
			\| <center>'''Initials'''</center>

			\|-
			\| <center>0.1</center>
			\| <center>30/09/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>PDR</center>

			\|-
			\| <center>1.0</center>
			\| <center>07/10/11</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>

			\|-
			\| <center>1.1</center>
			\| <center>24/10/11</center>
			\| <center>Draft</center>
			\| Updated after meetings on 11/10/11 and 20/10/11 with Nick Wilkins, Peter Greer and Colin Tye.
			\| <center>PDR</center>

			\|-
			\| <center>1.1</center>
			\| <center>04/11/11</center>
			\| <center>Draft</center>
			\| Review
			\| <center>PJH</center>

			\|-
			\| <center>2.0</center>
			\| <center>04/11/11</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>

			\|-
			\| <center>2.1</center>
			\| <center>17/11/11</center>
			\| <center>Draft</center>
			\| Updated to state labels will be produced per shipment, or unconsolidated transport order, DU quantity; a shipment ID will be generated per transport order/shipment; the sender/from location will be the ‘from’ location of the shipment. See section 3.13. Included a Carrier field in the Order Details screen. See section 3.14.1. Included manual packing and repacking. See section 3.15.
			\| <center>PDR</center>

			\|-
			\| <center>3.0</center>
			\| <center>18/11/11</center>
			\| <center>Issued</center>
			\| Issued to client
			\| <center>PJH</center>

			\|-
			\| <center>3.1</center>
			\| <center>28/11/11</center>
			\| <center>Draft</center>
			\| Updated CIPD and CITD information to store the carton numbers from Unison WMS. See sections 3.8.4, 3.15.1 and 3.16.
			\| <center>PJH</center>
			\|}


			=AUTHORISED BY=



			{\| Border="1"
			\| '''''Matt Crisford'''''
			\| Development Manager
			\|

			\|-
			\| '''''Peter Greer'''''
			\| TMSCC MTS Product Manager
			\|

			\|}

Middletong: /* Manual Pack Confirmation */

2012-10-29T14:08:47Z

Manual Pack Confirmation

← Older revision		Revision as of 16:08, 29 October 2012
Line 2,071:		Line 2,071:

	The ‘Pack Confirm’ and ‘Reprint Label’ buttons will need to check that the carrier of the order (or the trip if not mandated) has a label format setup and, if not, advise the user that the processing is not required for that carrier.		The ‘Pack Confirm’ and ‘Reprint Label’ buttons will need to check that the carrier of the order (or the trip if not mandated) has a label format setup and, if not, advise the user that the processing is not required for that carrier.

			====Repacking====

			If repacking is required (e.g. the carrier has advised that the scheduled collection will not be performed) then the user will have to follow the procedure to unscheduled the order, modify it and reschedule it.

			Afterwards, the labels can be produced via either the ‘Pack Confirm’ or ‘Reprint Label’ buttons as appropriate.

			==Despatch Confirmation==

			The despatch confirmation message will be generated by the update of the trip status to ‘EN-ROUTE’ and the transmission of this message will be dependent on the ‘hold’ flag set for the transport order on the trip stop.

			'''N.B. A despatch confirmation message will only be sent to the Unison WMS if the customer of the order has a ‘UNISON’ translation value setup (i.e. ‘UNISON_IF_VALUE’).'''

			A file will be sent to DHL Link for transfer to the appropriate WMS (i.e. ‘CITD’ for the Unison WMS).

			The despatch confirmation message will be contained in a file in the ‘TripOrder’ XML format with the name format ‘DESP_CONF_{TRIP_ID}_{SEQ}.XML’.

			The ‘CITD’ file has the following structure:

			[[Image:290934_126.png]]

			N.B. The ‘Shipment ID’ will be the shipment ID generated within C-TMS for each transport order/shipment created.

			The ‘Packing List Number’, ‘Shipment No’ and ‘Service Level’ will be obtained from the order sub-references for the shipment (i.e. ‘PACK_NO’, ‘SHIPMENT_NO’ and ‘CARRIER_SERVICE_TYPE’.)

			The ‘Carrier Code’ will be obtained from the trip and it will be included in ‘ORDER_HEADER_TMS/HAULIER’.

			The ‘Carton Number’ will contain the carton numbers used within Unison WMS, plus they will be unique within the transport order or the shipment with an associated ‘Tracking No’; ‘Carton Number’ will be included in the new ‘TRACKING_REF’ section as ‘UNIT_TRACKING_NO’ and ‘Tracking No’ as ‘UNIT_TRACKING_REF’.

			The ‘Tracking No’ data will be repeated for the despatch unit of the shipment in the ‘ORDER_DETAIL’ section.

			The ‘Order Number’ will be included in the new ‘ORDER_HEADER’ section as ‘SO_REF’ and will be obtained from the external reference (i.e. ‘Order Number’) associated with the carton number from the ‘CIPD’ message.

			The ‘Order Line Number’ will be ‘000’ by default because the ‘CD01’ record refers to what is contained in the ‘carton’ and this information will not be stored in C-TMS.

			===Production===

			The XML file will be produced via a database job using a new procedure ‘INT_XML_OUT2.PROCESS_XML_DESP_CONF’.

			===Transmission===

			The despatch confirmation messages will be sent to DHL Link via FTP.

			The directory structure and login details for DHL Link will be maintained in the new system parameters specifically for the electronic manifest.

			For example:

			*CTMS_CITD_FTP_DESTINATION_DIRECTORY
			*CTMS_CITD_FTP_DESTINATION_IP_ADDRESS
			*CTMS_CITD_FTP_DESTINATION_PASSWORD
			*CTMS_CITD_FTP_DESTINATION_USERNAME
			*CTMS_CITD_FTP_DESTINATION_PORT

Middletong: /* CIPD Message */

2012-10-29T14:05:38Z

CIPD Message

← Older revision		Revision as of 16:05, 29 October 2012
Line 2,054:		Line 2,054:

	'''N.B. If a ‘CIPD’ message is re-sent then the shipment will be updated with the new data and the labels will be re-printed automatically.'''		'''N.B. If a ‘CIPD’ message is re-sent then the shipment will be updated with the new data and the labels will be re-printed automatically.'''

			===Manual Pack Confirmation===

			Manual pack confirmation is required where the ‘CIPD’ message will not be received into C-TMS.

			The ‘Order Details’ screen will contain a ‘Pack Confirm’ button which perform the following functionality:

			#Enter an order with, or without, a mandated carrier in the new field in the ‘Order Details’ tab page.
			#Press the new ‘Pack Confirm’ button in the same tab page:
			#*If the order is not on a trip (i.e. it is not already scheduled) then it will be scheduled by running the scheduling engine for that OMS reference.
			#*The scheduling engine will only be run for the single order if it is not already running via the database job.
			#*A mandated carrier will be used if it exists for the order as per the standard scheduling functionality.
			#*Once the scheduling has been performed successfully (if required) then the labels will be printed to the default printer for the user for the trip and carrier assigned to the order.

			There will be another button called ‘Reprint Label’ in the tab page for the user to request reprinting for whatever reason and this button will not perform any scheduling.

			The ‘Pack Confirm’ and ‘Reprint Label’ buttons will need to check that the carrier of the order (or the trip if not mandated) has a label format setup and, if not, advise the user that the processing is not required for that carrier.

Middletong: /* Polarspeed */

2012-10-29T13:52:58Z

Polarspeed

← Older revision		Revision as of 15:52, 29 October 2012
Line 1,967:		Line 1,967:

	'''If it is printed for an unconsolidated transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed.'''		'''If it is printed for an unconsolidated transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed.'''

			==Parcel Label Trigger===

			The carrier labels will be produced upon receipt of the ‘Pack Confirmation’ message from the WMS or manually by the user via a ‘Pack Confirm’ button in the ‘Orders’ screen in C-TMS.

			The carrier labels may also be re-printed manually via a button in the new ‘Shipment Order Management’ form or via a button in the ’Orders’ form.

			There will be the ability to re-print labels by order or shipment and once selected a range, or a specific label number, can be requested. For example, if there are 11 orders for a shipment a user should be able to re-print all 11 labels, or labels 3/6 or labels 1, 7 and 11. It is accepted that the ‘Label Print Number’ will be out of sequence for re-prints.

			N.B. The ‘Reprint Label’ option will be available if the new ‘ORD_REPRINT_PACK_VISIBLE’ system parameter is set to ‘Y’.


			===Order Details===

			The ‘Pack Confirm’ and ‘Reprint Label’ buttons will be displayed if the new ‘ORD_REPRINT_PACK_VISIBLE’ system parameter is set to ‘Y’.

			The ‘Order Detail’ screen will be changed to enable the user to print labels for the individual orders in the shipment.

			This will be performed via a new ‘Reprint Label’ button:

			[[Image:290934_117.png]]

			New ‘Carrier’ and ‘Shipment ID’ fields will be added to the ‘Detail’ tab page of the ‘Order Details’ screen in the ‘ORDERS’ from, the ‘Carrier’ field will store a mandated carrier/haulier for manually entered transport orders (if a transport order is uploaded via a CSV import file or EDI file then the carrier will appear in this field); the ‘Shipment ID’ field will display the shipment ID generated for the transport order/shipment.

			==Pack Confirmation==

			===CIPD Message===

			The structure of the ‘CIPD’ file generated by Unison is shown below:

			[[Image:290934_118.png]]

			[[Image:290934_119.png]]

			[[Image:290934_120.png]]

			An example of a ‘CIPD’ file generated by Unison is show below:

			[[Image:290934_121.png]]

			[[Image:290934_122.png]]

			[[Image:290934_123.png]]

			[[Image:290934_124.png]]

			A new directory structure will be setup in the ‘EDI Maintenance’ screen.

			A new database job will be created when started without a time interval to process the files received.

			The ‘IMP’ package will be changed to import the file and generate the labels as required.

			N.B. The files processed will be placed in failed or processed directories as appropriate.

			The ‘SCH_ORD’ database table will be changed to include the packed date and will contain the system date and time when the packed quantity was updated:

			[[Image:290934_125.png]]

			The existing ‘T_SCH_ORD_AUDIT’ database trigger will be used for this purpose.

			The ‘CIPD’ output from Unison will be mapped into C-TMS. Initially orders will be packed at order level, but as part of Prospero orders will be packed at shipment level requiring a shipment label when the final order has been packed.

			Upon receipt of this file into C-TMS the transport order, or the shipment, DU type and quantity will be updated as per the values contained in the file. Changes and updates to the order line will be captured in the audit log for the order.

			'''N.B. The ‘Pack No’ and ‘Shipment No’ will be stored as order sub-references for the shipment (i.e. ‘PACK_NO’ and ‘SHIPMENT_NO’.)'''

			'''The ‘Carrier Code’ and ‘Service Level’ will not be stored in C-TMS because they are stored against the trip and carrier.'''

			'''The ‘Carton Type’ will be used to update the despatch unit type of the order line of the shipment.'''

			'''The ‘Carton Number’ will be used to update the despatch unit quantity (as a count of the carton numbers received) for the transport order or the shipment. It will contain the carton numbers used within Unison WMS and they will be unique within the transport order or the shipment; however, the carton numbers may not be sequential. (See section 3.8.4 for their storage.)'''

			'''The ‘Tracking No’ will be generated as a tracking reference within C-TMS when the label is printed for the despatch unit (i.e. carton for the CIPD).'''

			'''The carton’s dimensions will not be stored in C-TMS.'''

			'''The ‘Order Number’ will correspond to the customer reference of the transport order stored as ‘SCH_ORD.EXTERNAL_REF’ in C-TMS. It will be stored with the carton number in which it is contained.'''

			'''The ‘Order Line Number’ will be ‘000’ by default because the ‘CD01’ record refers to what is contained in the ‘carton’ and this information will not be stored in C-TMS.'''

			'''The ‘Quantity’ will be ‘00000000’ by default because the ‘CD01’ record refers to what is contained in the ‘carton’ and this information will not be stored in C-TMS.'''

			'''It is expected that one ‘CD01’ record will be received per ‘CC01’ record because the contents of the carton are not relevant at present.'''

			'''N.B. Pre-Prospero packing in Unison WMS will be performed by sales order reference (i.e. transport order) and not by shipment, therefore, the sales order information needs to be stored in C-TMS for the associated tracking reference for the despatch units packed in the shipment.'''

			'''N.B. If a ‘CIPD’ message is re-sent then the shipment will be updated with the new data and the labels will be re-printed automatically.'''

Middletong: /* Parcelforce */

2012-10-29T13:31:35Z

Parcelforce

← Older revision		Revision as of 15:31, 29 October 2012
Line 1,884:		Line 1,884:

	'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The reference for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''		'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The reference for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

			===Standard1===

			N.B. This label will be rotated 90 degrees clockwise when printed (i.e. the layout will be ‘Landscape’ and not ‘Portrait’ as for the other labels).

			[[Image:290934_110.png]]


			In this example, the sequence of the counts is shown below:

			[[Image:290934_111.png]]

			The ‘Standard1’ parcel label will contain the following information:

			[[Image:290934_112.png]]

			[[Image:290934_113.png]]

			Boxes will also be printed as shown in the example above.

			*‘Shipment ID’ will be the shipment ID generated for the OMS reference of the shipment for the transport order if it has been consolidated into a shipment, otherwise it will be for the OMS reference of the transport order.
			*‘Route’ is the name of the route code of the trip.
			*‘Package Number’ is the package number derived from the number of despatch units within a shipment (or transport order): e.g. 1/6 = DU 1 of 6 DUs.
			*‘Pal’ is the number of pallets in the shipment (or transport order) derived from the total number of pallets: e.g. 1/2 = pallet 1 of 2 pallets.
			*‘Par’ is the number of parcels in the shipment (or transport order) derived from the total number of parcels: e.g. 0/4 = there are a planned number of 4 parcels but this particular DU is not one of them because it is in the pallet category.
			*‘Tracking Number’ is the tracking reference for the shipment (or unconsolidated transport order).
			*The ‘Ship To’ address in rows 26-32 refers to the delivery address of the shipment.
			*The ‘Sender’ and ‘Return’ addresses in rows 36-41 and 50-55 refer to the from location (i.e. collection address) of the shipment (or unconsolidated transport order) (which may not be the same as the despatching location of the delivery trip).
			*The ‘Despatcher’ address in rows 43-48 refers to the despatching location of the delivery trip.
			*The counts refer to the number of despatch units in the shipment (or unconsoldiated transport order).
			*‘Date’ is the latest delivery date and time of the order.
			*‘BARCODE’ is based on the combination of ‘{C-TMS Trip ID}-{Temperature}-{Cust / WMS Ref}-{Label Print Number}’ to make it unique.

			N.B. ‘Pal’ and ‘Par’ will be defined by the new despatch unit category which will be ‘Pallet’ or ‘Parcel’.

			'''N.B. The label will be printed when it is packed and it will include the information for the loading trip in the depot the packing operation will be performed: if the shipment is being trunked to, and unloaded at, another depot for collection by the parcel carrier on another trip then the labels will contain the trunking trip.'''

			'''The ‘Sender’ will always be the ‘From Location’ of the shipment but the ‘Despatcher’ will be either the ‘From Location’ of the shipment (if it is not trunked) or the loading location of the shipment for the delivery trip.'''

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘Cust / WMS Ref’, ‘Del Point Ref’ and ‘Booking Ref’ references and ‘Special Instructions’ will be obtained from the first transport order in the shipment.'''

			'''If it is printed for an unconsolidated transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references and special instructions for the transport order can then be displayed.'''

			===Polarspeed===

			[[Image:290934_114.png]]

			<u>'''WMS (Unison) Ref / WMS Ref'''</u>

			Will show the Unison sales order number only on transport orders received via EDI in the customer reference.

			<u>'''Customer Ref / OUR'''</u>

			Will show the customer reference.

			<u>'''Consignee Ref'''</u>

			Will show the delivery point reference.


			The Polarspeed parcel label will contain the following information

			[[Image:290934_115.png]]

			[[Image:290934_116.png]]

			Boxes will also be printed as shown in the example above.

			*The ‘To’ address in rows 20-27 refers to the delivery address of the shipment (or unconsolidated transport order).
			*The ‘From’ and ‘Return’ addresses in rows 9-15 and 76-82 refer to the from location of the shipment.
			*The count refers to the number of despatch units in the shipment (or unconsolidated transport order).
			*‘Consignment No’ is the shipment tracking reference and will be prefixed with ‘TMS’ instead of ‘CIM’.
			*‘Tracking No’ is the despatch unit tracking reference and will be prefixed with ‘DHL’.
			*‘BARCODE1’ is the despatch unit tracking reference.
			*‘Ship Date’ will be the despatch date of the trip.
			*‘Deliver Before’ will be the late delivery time of the shipment (or transport order).
			*‘BARCODE2’ is the carrier and country reference.
			*‘LPN’ is the ‘Label Printing Number’ from the database sequence number.
			*Text ‘PointSpeed $ Revision: 1.0 $ by cbmc.co.uk’ will be replaced by ‘Calidus TMS by http://www.obs-logistics.com’.

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘WMS (Unison) Ref’, ‘Customer Ref’, ‘Consignee Ref’, ‘WMS Ref’ and ‘OUR’ references will be obtained from the first transport order in the shipment.'''

			'''If it is printed for an unconsolidated transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed.'''

Middletong: /* Vaccine Example */

2012-10-29T12:39:43Z

Vaccine Example

← Older revision		Revision as of 14:39, 29 October 2012
Line 1,829:		Line 1,829:

	'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''		'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

			===Parcelforce===

			[[Image:290934_105.png]]

			N.B. Parcelforce labels will only be produced in the domestic-label format.

			<u>'''Service Code'''</u>

			If a consignment is due to be delivered on a Saturday, then the word “SATURDAY” needs to be printed on the label, as shown in the example below. All other aspects of the label for deliveries on Saturday are identical to the standard domestic label:

			[[Image:290934_106.png]]

			The service code will contain the label content service indicator for the corresponding Parcelforce service that the consignment is being shipped on, as shown in the following table:

			[[Image:290934_107.png]]

			<u>'''Despatch Date'''</u>

			The despatch date will be the date on which Parcelforce will COLLECT the consignment for delivery.

			<u>'''Postcode Barcode'''</u>

			The postcode barcode (i.e. ‘BARCODE1’) should contain only the outward portion of the postcode. The postcode barcode value should be delimited by an asterisk on either side:

			[[Image:290934_108.png]]

			<u>'''Consignment Barcode'''</u>

			The format of the consignment barcode (i.e. ‘BARCODE2’ and ‘BARCODE3’) content is:

			*‘PB’ Prefix
			*Consignment Number (2 alpha, 7 digit)
			*Parcel Number; 001, 002, 003, etc.

			The Parcelforce label will contain the following information:

			[[Image:290934_109.png]]

			Boxes will also be printed as shown in the example above.

			*The tracking reference is for the despatch unit.
			*The ‘To’ address in rows 6-11 and 17-20 refers to the delivery address of the shipment (or transport order).
			*The ‘From’ address in rows 25-29 refers to the from location of the shipment.
			*The count refers to the number of despatch units in the shipment (or unconsolidated transport order).
			*The barcodes will be in ‘Code 128’ format.
			*‘BARCODE1’ will use the postcode prefix.
			*The ‘Saturday’ indicator will be printed for deliveries made on a Saturday only.
			*‘LPN’ is the licence plate number.
			*‘Sender’s Ref’ is the customer reference of the unconsolidated transport order or a transport order in the shipment
			*Text will be ‘Printed: {SYSTIME} by Calidus TMS by http://www.obs-logistics.com’.

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘Sender’s Ref’ reference will be blank because it pertains to the transport order. The shipment reference will then be the OMS reference of the shipment.'''

			'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The reference for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

Middletong: /* DHL EXpress */

2012-10-29T11:04:33Z

DHL EXpress

← Older revision		Revision as of 13:04, 29 October 2012
Line 1,746:		Line 1,746:

	The DHL TD parcel label will contain the following information:		The DHL TD parcel label will contain the following information:

			[[Image:290934_99.png]]

			[[Image:290934_100.png]]

			Boxes will also be printed as shown in the example above.

			*The ‘To’ address in rows 19-26 refers to the delivery address of the shipment.
			*The ‘From’ address in rows 6-11 refers to the from location of the shipment.
			*The counts refer to the number of despatch units in the shipment, or unconsolidated transport order.
			*‘ORIGIN’ is the collecting depot code for the ‘From’ address as maintained in the ‘Locations’ maintenance screen.
			*‘Sender’s Ref’ is the customer reference of the unconsolidated transport order or a transport order in the shipment
			*The ‘Handling’ code may be calculated from the label specification and included in the block in inverse video.
			*‘OXF’ is the sortation hub for the delivery location of the order.
			*‘AIRWAYBILL’ is the tracking reference number for the despatch-unit level.
			*‘Service’ is the customs duty for exports (i.e. ‘DDU’ for ‘Delivered Duty Unpaid’).
			*‘Weight’ is the shipment weight (or the unconsolidated transport order weight).
			*Text ‘CIM/DHL CAS 1.0 cbmc.co.uk’ will be replaced by ‘Calidus TMS by http://www.obs-logistics.com’.

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘Sender’s Ref’ reference will be blank because it pertains to the transport order. The shipment reference will then be the OMS reference of the shipment.'''

			'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The reference for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

			===Movianto===

			The label is produced using barcode39 fonts and has the following format:

			‘CCCC-XXXXXX-NNN-YYY’

			For a ‘Glaxo’ (GSK) consignment this could read as follows:

			GLAS-123456-001-PAL
			GLAS-123456-002-CTN
			(This would be a Scheduled order with both a Carton and a Pallet on it)

			GLAU-123457-001-CTN
			GLAU-123457-002-CTN
			(This would be an Urgent order with 2 Cartons on it)

			GLAV-123458-001-CTN
			(This would be a Vaccine order with 1 Carton on it)

			'''N.B. The same format will be used for the ‘Vaccine’, ‘Urgent’ and ‘Scheduled’ examples from the ‘Cherwell’ depot except that the ‘Vaccine’ will have a ‘NORTH’ or ‘SOUTH’ indicator. An example of the ‘Vaccine’ label is shown in the subsequent sections.'''

			N.B. The following ‘Movianto Spec’ example is the standard Movianto format and it will be used for deliveries not originating in the ‘Cherwell’ depot. These new formats will be used and the ‘Vaccine Example’ will follow these formats in the future.

			N.B. If the service level is not found then it will print ‘Service Level Not Supported’ in the place of the service level.

			====Technical Examples====

			[[Image:290934_101.png]]

			[[Image:290934_102.png]]

			====Vaccine Example====

			[[Image:290934_103.png]]

			The Movianto parcel label will contain the following information:

			[[Image:290934_104.png]]

			Boxes will also be printed as shown in the example above.

			*‘CTN’ is the despatch unit type.
			*The ‘To’ address in rows 4-8 refers to the delivery address of the shipment.
			*The ‘Return’ address in rows 31-37 refers to the from location of the shipment.
			*The counts refer to the number of despatch units in the shipment (or transport order).
			*The barcode includes the shipment tracking reference displayed beneath.
			*‘00019837’ is the tracking number of the despatch unit.
			*‘1403351’ will be the shipment ID genertated for the OMS reference of the shipment for the transport order if it has been consolidated into a shipment, otherwise it will be for the OMS reference of the transport order.
			*‘Primary Sender Ref’ is the customer reference of the unconsolidated transport order or a transport order in the shipment.
			*‘Primary Del Point Ref’ is the delivery point reference of the unconsolidated transport order or a transport order in the shipment.
			*‘Weight’ is the shipment weight (or the unconsolidated transport order weight).
			*The ‘BLOCK’ will contain text to indicate chilled items (e.g. ‘CHILLCARE 2-8o’ for vaccines).
			*‘Sender’ and ‘Return Address’ are the from location of the shipment.
			*Text ‘HCL v1.2a by cbmc.co.uk’ will be replaced by ‘Calidus TMS by http://www.obs-logistics.com’.

			'''N.B. The new Movianto format includes ‘SCAN’ in the ‘Return Address’ section; the direction only is only displayed for ‘Vaccine’ orders; the tracking reference has a new format.'''

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘Primary Sender Ref’ and ‘Primary Del Point Ref’ references will be blank because they pertain to the transport order. The shipment reference will then be the OMS reference of the shipment.'''

			'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

Middletong: /* DHL EXpress */

2012-10-29T10:28:11Z

DHL EXpress

← Older revision		Revision as of 12:28, 29 October 2012
Line 1,742:		Line 1,742:

	===DHL EXpress===		===DHL EXpress===

			[[Image:290934_98.png]]

			The DHL TD parcel label will contain the following information:

Middletong: /* Yodel */

2012-10-29T10:24:54Z

Yodel

← Older revision		Revision as of 12:24, 29 October 2012
Line 1,707:		Line 1,707:

	The qualifier J in brackets followed by the first 4 characters JD00, then a space, then the country code 022 (or 026 if shipped from Ireland), then a space, followed by the next three characters, then a space, followed by the remaining eight characters in two groups of four.		The qualifier J in brackets followed by the first 4 characters JD00, then a space, then the country code 022 (or 026 if shipped from Ireland), then a space, followed by the next three characters, then a space, followed by the remaining eight characters in two groups of four.

			[[Image:290934_95.png]]

			The Yodel parcel label will contain the following information:

			[[Image:290934_96.png]]

			[[Image:290934_97.png]]

			Boxes will also be printed as shown in the example above.

			*The ‘To’ address in rows 13-21 refers to the delivery address of the shipment.
			*The ‘From’ and ’Return’ addresses in rows 3-10 and 61-65 refers to the from location of the shipment.
			*The count refers to the number of despatch units in the shipment.
			*‘EXPRESS’ is the product service type of the carrier from the gazetteer.
			*‘Handling’ will be the handling/feature text from the gazetteer.
			*‘Shipment No’ and ‘Shipment ID’ will be the shipment ID generated for the OMS reference of the shipment for the transport order if it has been consolidated into a shipment, otherwise it will be for the OMS reference of the transport order.
			*‘Consignee Ref’ will be the delivery point reference of the unconsolidated transport order or a transport order in the shipment.
			*‘Sender Ref’ and ‘OUR’ will be the customer reference of the unconsolidated transport order or a transport order in the shipment
			*‘W COVENTRY’ is the name of the service centre of the delivery location.
			*‘HAMS HALL’ is the name of the sortation hub of the delivery location.
			*‘BARCODE1’ will be the routing barcode based on the service information in the gazetteer.
			*‘BARCODE2’ will be the licence plate barcode.
			*‘BARCODE3’ will be the carrier barcode.
			*Text ‘CIM/DHL CAS 1.0 cbmc.co.uk’ will be replaced by ‘Calidus TMS by http://www.obs-logistics.com’.
			*‘WMS Ref’ will be the customer reference.
			*‘LPN’ will be obtained from the licence plate number set for ‘BARCODE3’.
			*‘OUR’ will be the customer reference.
			*‘Return Address’ will be the same as the despatching depot.

			'''N.B. If a despatch-unit label is printed for a shipment then the despatch-unit quantities of the shipment will be used to decide how many labels will be printed. The ‘Consignee Ref’, ‘Sender Ref’, ‘WMS Ref’ and ‘OUR’ references will be blank because they pertain to the transport order. The shipment reference will then be the OMS reference of the shipment.'''

			'''If it is printed for a transport order then the despatch-unit quantities of the transport order will be used to decide how many labels will be printed. The references for the transport order can then be displayed. The shipment reference will then be the OMS reference of the transport order.'''

			===DHL EXpress===

Middletong: /* Yodel */

2012-10-29T10:09:17Z

Yodel

← Older revision		Revision as of 12:09, 29 October 2012
Line 1,645:		Line 1,645:

	The ANSI code list starts with a data identifier to show that it concerns a Licence plate code, followed by the IAC code and the sequence number. The sequence number contains a reference number (supplied by the issuing agency) followed by a sequence number, generated by the client. In this way uniqueness can be guaranteed, whilst allowing the CAS to generate numbers within a number range.		The ANSI code list starts with a data identifier to show that it concerns a Licence plate code, followed by the IAC code and the sequence number. The sequence number contains a reference number (supplied by the issuing agency) followed by a sequence number, generated by the client. In this way uniqueness can be guaranteed, whilst allowing the CAS to generate numbers within a number range.

			[[Image:290934_94.png]]

			N.B. The ANSI data identifier is NOT part of the Licence Plate! It does not have to be considered when determining the length of the Licence Plate.

			<U>'''Plausibility Checks:'''</U>

			The following plausibility checks will be applied to the item identification barcode (this means, we will not accept Licence Plates that do not meet the following requirements):

			*On any item, there is to be only one Licence plate
			*The Licence plate may not be identical to a Licence plate that has already been processed within one year.
			*The Licence plate must be the last barcode present on the label. On landscape type labels the positioning must be bottom right of the label.

			<U>'''ANSI Code List:'''</U>

			Any linear barcode using barcode symbology CODE 128 or Code 39 and starting with the ANSI Data Identifier J, 1J, 2J, 3J, 4J, 5J or 6J will be considered the (ANSI) Licence Plate of the item. The identifier is printed in parenthesis in the eye‐readable representation of the Licence plate. We will apply the following plausibility checks:
			*The Licence plate must not contain more than 35 characters
			*The Licence plate may only contain numeric and upper case alphabetic characters drawn from ISO/IEC 646 ‐ they must not include any lower case character or punctuation mark.
			*The Licence plate must start with a string of characters representing an issuing agency assigned by ISO. See the table below for the current issuing agency codes (IAC).

			<U>'''EAN Code List for Licence Plates:'''</U>

			Any linear barcode using barcode type EAN128 and starting with the special character FNC1 and EAN Application Identifier “JD” will be considered the (EAN) Licence Plate of the item. In this case we will apply the following plausibility checks:

			*The Licence plate must contain 16 characters (not counting the “JD” application identifier).
			*The Licence plate shall only contain numeric characters excluding 2 digit IAC identifier

			<U>'''Licence Plate Barcode:'''</U>

			In order to ensure that Item Number and Licence Plate identifiers are unique we will issue ranges of numbers to be used in generating these identifiers. The CAS Link system must not create numbers outside these ranges nor may it create duplicate numbers inside a reasonable time scale. When a range expires the numbers are re‐cycled but there must be NO repetition of Licence Plate identifier within one calendar year.

			Customers upgrading existing systems must create a method to create and record Licence Plate numbers and make sure the same Licence Plate number is not repeated within 12 months.

			Shipment reference numbers or Consignment numbers should also be kept unique ensuring the shipment or consignment can be effectively tracked using this number. Guidance is given here and a range of numbers will be allocated for the Select consignment numbers.

			For CAS Link installations the Licence Plates will always be an 18‐character code with a layout as shown below:

			(J) F IAC KKK A B C d e 1 2 3 4 5 6

			The leading “(J)” is ignored for identification purposes but must be included in the LP barcode and the parentheses only appear in the eye‐readable representation. The first significant set of characters (F IAC KKK) (as described above) will be for example “JD00 022” (or “JD00 026” for Eire). Next an identifier of 5 digits followed by a range of 6 digits. The size of the identifier and the number of digits in the range will depend on the size of range that has to be allocated to cope with the projected parcel volumes.

			When the upper limit of this range has been reached the system will have to start back at the lowest number in the range.

			DHL will supply an 11 digit pool number range so the CAS system can create the 18 digit (19 digits with leading identifier) Licence Plate Barcode identifier and the 18 digit eye‐readable number (19 digits with leading identifier).

			The Licence Plate Barcode identifier is made up from a static prefix of eight alphanumeric characters, for example: JJD00022 for UK followed by the pool number.

			Example Licence Plate Barcode for pool number 98765000001:

			JJD0002298765000001

			The eye‐readable number including spacing would be:

			(J)JD00 022 987 6500 0001

			Licence Plates identifiers are allocated in a straight numeric sequence start at the lower limit and increment by 1 every time you generate a shipping label.

			N.B. The eye‐readable Licence Plate number is prefixed with ‘(J)’ ‐ shown without the brackets in the barcode, the spacing required for the eye readable Licence Plate numbers is:

			(J)JD00 022 123 1234 1234

			The qualifier J in brackets followed by the first 4 characters JD00, then a space, then the country code 022 (or 026 if shipped from Ireland), then a space, followed by the next three characters, then a space, followed by the remaining eight characters in two groups of four.