Catalogue of UPU Standards - Universal Postal Union
Catalogue of UPU Standards - Universal Postal Union
Catalogue of UPU Standards - Universal Postal Union
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
M17 EMSEVT Message specification, Version 1.0<br />
EMS EVENTS MESSAGE<br />
The EMSEVT message provides a mechanism for the reporting <strong>of</strong> events occurring to postal items<br />
which have individual item identifiers. The original specification was drawn up to support the<br />
reporting <strong>of</strong> events occurring to international EMS items but it can be applied to other classes <strong>of</strong><br />
item including parcels and special (identified) letter mail items such as registered, insured and<br />
Express letters.<br />
M18 CARDIT Message specification, Version 1.1<br />
CARRIER/DOCUMENTS INTERNATIONAL TRANSPORT<br />
The CARDIT message contains information about a consignment <strong>of</strong> mail which is handed over to a<br />
carrier.<br />
M19 TRAKIT Message specification, Version 2.0 WITHDRAWN<br />
Withdrawn – no longer in use.<br />
M20 CARDIT Message specification, Version 2.0<br />
CARRIER/DOCUMENTS INTERNATIONAL TRANSPORT<br />
The CARDIT message contains information about a consignment <strong>of</strong> mail which is handed over to a<br />
carrier. This version has the same functionality as version 1.1. The only difference is the EDIFACT<br />
Directory in which the message is implemented.<br />
M21 EXCEPT Message specification, Version 1.0<br />
ADMINISTRATION CONFIRMATION OF RECEIPT/CURRENT EXCEPTIONS<br />
The exception message contains information about the receipt and/or processing <strong>of</strong> receptacles for<br />
which no pre-advice message has been received.<br />
M22 RESDIT Message specification, Version 1.0<br />
CARRIER/CONFIRMATION OF RECEIPT OR CURRENT EXCEPTION<br />
The RESDIT message contains information about a consignment <strong>of</strong> mail as it is processed by a<br />
carrier. The sending <strong>of</strong> the CARDIT message is mandatory to receive a RESDIT message. The<br />
CARDIT/RESDIT messages are defined to work together. It is not possible to send a RESDIT<br />
message if a CARDIT has not been received.<br />
M23 MONORD Message specification, Version 1.0 WITHDRAWN<br />
Withdrawn – no longer in use. Please refer to M38.<br />
M24 RESORD Message specification, Version 1.0 WITHDRAWN<br />
Withdrawn – no longer in use. Please refer to M38.<br />
M25 TRAKIT Message specification, Version 3.0 WITHDRAWN<br />
M26<br />
Withdrawn – no longer in use.<br />
CAPREQ – Capacity request message specification<br />
The Capacity Request message is sent normally from a postal operator to a carrier upon discovery<br />
that the mail cannot be transported as scheduled or as agreed bilaterally. The trigger could come<br />
from the postal side (deviated volumes, delays in the domestic network, problems at destination<br />
operator, etc.) or from the carrier side (flight cancelled, cargo space insufficient, delays due to<br />
weather conditions, etc.). The Capacity Request message contains information about volumes <strong>of</strong><br />
mail for which the postal operator is looking for transport on a short term or for a certain period. This<br />
message covers the different scenarios defined within the FACTEUR MESSAGING subgroup.<br />
© <strong>UPU</strong> 2014 – All rights reserved 17