SWIFT Message Type OTDs

This section provides a general overview of the SWIFT message types and their OTDs.

SWIFT Message Structure

Messages used by the SWIFT network have a maximum of five components (see SWIFT Message Structure), as follows:

• Basic header block

• Application header block

• User header block (optional)

• Text block

• Trailer block

  

Each field component in the text block is preceded by a field tag. There are no field tags in the header and trailer blocks. The one exception to this format is MT 121, EDIFACT FINPAY, which has a single text field with no field tag identifier.

Information about a field common to all message types in which that field is used is found in the Standards - General Field Definitions volume of the SWIFT User Handbook. Information about a field specific to its use with a particular message type is found in the field specifications section of the Standards volume of the SWIFT User Handbook for that message type.

OTD and Collaboration Locations in Enterprise Designer

You can find the SWIFT OTDs, including the MT Fund OTDs and Generic OTD, in the Enterprise Designer’s Project Explorer tree. This figure also shows the location of the Java-based Validation Collaboration Definitions.

The Validation Collaborations directory contains the Collaboration Definitions that enable the validation features of the SWIFT OTD Library. See SWIFT Message Library JAR Files for details.

The Category 5 directory contains the SWIFT MT Funds message template OTDs in the library. See Parse Debug Level Message Example for details.

The bic.jar file allows you to update the BICDirService feature. See SWIFT Message Library JAR Files for details.