Custom MT type tree

On the Generic Envelope service MT example, the Generic Envelope service expects that the resulting file of the transformation map contains only SWIFT MT block 4 content, without any header or trailer information.

For example, blocks 1, 2, and ,3 are not populated by the map. This information is provided by the Generic Envelope service. The Transformation Extender Pack for Financial Payments ships type trees that represent SWIFT MT message syntax. That includes SWIFT MT headers and trailers, such as block 1, 2, 3, 4 and 5. This documentation provides the steps needed to build a custom type tree based from the provided type trees without any header or trailer information.

The type tree used in the examples, swift_mt103_plus_nohdrs.mtt, is a subset of the swift_iso7775_yyyy.mtt type tree that is included with the SWIFT component of the Transformation Extender Pack for Financial Payments . This type tree is shared between the Generic Deenvelope service and the Generic Envelope service examples.

In the above file name, yyyy indicates a four-digit year value; for example, 2012.