BEA SWIFT Adapter - Manual

Custom SWIFT messages Depending on your requirement you may have to customize the SWIFT messages or make minor modifications to it. One such case is GSCC SWIFT messages. If these customized messages are used often or across the enterprise, you may want to make use of the SWIFT message library featur...

This detail is generally not important; but if you are manually editing the version (in say messages you already have) in XML’s remember to update the standard-version tag appropriately. The advantage of the above is that you have the same message library support for your customized SWIFT messages j...

See Also: Creating a SWIFT Format based on an existing SWIFT message format Entering the SWIFT Specification Exporting a SWIFT Message Format to Library Entering the SWIFT Specification A SWIFT message is composed of sequences and fields. A sequence is a group of related information made up of one o...

Removing validations from a sub field SWIFT Sequence A Sequence is a group of related information, delimited in most of SWIFT message formats. However, there are a few formats, which have sequences without delimiters. The Designer provides for creating sequences with or without delimiters. Furthermo...

-----| Note sequences A and B of this format. They have neither the start delimiter nor the end delimiter. To add such a sequence, see Add a SWIFT Sequence without Delimiters. See Also: Sequence With Start and End Delimiters Sequence With Start Delimiter Sequence With Start and End Delimiters Consid...

-----| End of Subsequence A1 Linkages M 16S End of Block GENL End of Sequence A General Information Mandatory Sequence B Trade Details M 16R Start of Block TRADDET O 94B TRAD Place Place of Trade :4!c/[8c]/4!c[/30x] -----> …… …… …… Note that in the above format, the sequences A and A1 have the ‘S...

Adding a SWIFT Sequence A sequence is a group of related information made up of one or more fields and/or sub-sequences. A sequence may or may not be delimited. Three types of SWIFT sequences can be added. They are Sequence Without Delimiters Sequence With Start and End Delimiters Sequence With Star...

See Also: Sequence Without Delimiters Adding a SWIFT Sequence with Start and End Delimiters Adding a SWIFT Sequence with Start Delimiter Adding a SWIFT Sequence with Start and End Delimiters 1. Click the Add New Sequence button in the toolbar of the External Format - SWIFT UI. 2. The SWIFT Sequence ...

3. Select New Sequence Indicator in Sequence Delimiter. Select the Mandatory and Repeating properties of the sequence as per the specification. 4. The Start Of Block text field is automatically populated with value 15A when the Sequence Delimiter is specified in the step above. This can be changed t...

Non Generic Field- Unlike a generic field, is used for one purpose only. See Also: Terminology Adding a new Generic Field Adding a Non-Generic Field Updating a SWIFT Field Removing a SWIFT Field Customize Field Adding validations for a sub-field Removing validations from a sub field Adding Copy of F...

See Also: Adding a Non-Generic Field Adding Field Options 1. Click the Add New Options button in the Create Field or Modify Field dialog. 2. A new row is added in the options table. Enter the Option, its format, specification and description in the respective columns. 3. When a row is added, the opt...

3. The formats within the brackets ( ) should be treated as a single unit. In the following figure, note option P. The format is :4!c(//4!a2!a2!c[3!c]). The ( ) brackets separates :4!c from the rest, thus implying only two sub-fields with formats 4!c and //4!a2!a2!c[3!c]. If the brackets were missed...

Specification (Sub-Field1) (Sub-Field2) (Sub-Field2) In this format pattern, the specification for subfields B and C are the same. ie, Sub-Field2. If this pattern is entered, only one instance of Sub-Field2 will be created, though the format indicates 3 subfields, which is not correct. In order to a...

The option is removed from the options table. If there is any qualifier associated with the removed option, in the case of a generic field, map it to the correct option or remove it. See Also: Adding a New Generic Field Adding Qualifiers and Associating them with Options 1. Click the Add New Qualifi...

Specifying OR Option for a Qualifier The OR option, allows grouping of qualifiers. This is useful when one of the many possible qualifiers can appear for a field option as per the specification. For example, field 95a allows one among a group of qualifiers BUYR, DEAG, DECU, etc. Follow the steps giv...

Specifying Field Definition and Usage A field’s definition and usage can be specified by clicking the button in the Create Field or Modify Field dialog. For example field definition and usage of field ‘23G’ in MT519 can be specified as shown below. See Also: Adding a new Generic Field Adding a Non-G...

13. The format now looks correct as below. Click OK. Use of brackets ( ) around a set of (two or more) formats indicates that they should be treated as a single unit. Consider the format:4!c(//4!a2!a2!c[3!c]). The ( ) brackets separates :4!c from the rest, thus implying only two sub-fields with form...

Adding Copy of Fields In some SWIFT messages a set of fields need to be treated as single entity. For e.g. in common group messages (MTnxx), a copy of the fields that occurred in the original message may occur at the end. The entire set should be treated as a single field. To support this we need to...

Updating a SWIFT Field 1. Select the field to be modified in the External Format - SWIFT UI and click the Modify SWIFT Field button in the toolbar. 2. The Modify Field dialog appears with the selected field in the Tag drop-down box.

Customize Field Consider the message format MT101. Status Tag Field Name Content/Options No. Mandatory Sequence A General Information M 20 Sender's Reference 16x 1 O 21R Customer Specified Reference 16x 2 M 28D Message Index/Total 5n/5n 3 O 50a Instructing Party C or L 4 O 50a Ordering Customer G or...

See Also: Adding a new Generic Field Adding a Non-Generic Field Removing a SWIFT Field Removing a SWIFT Field 1. Select the fields to be removed in the External Format - SWIFT UI and click the Remove Selected Fields button in the toolbar. The fields are removed from the format. 2. Sequences can also...

This removes the field from the Tag list. See Also: Adding a SWIFT Field Updating a SWIFT Field Adding a SWIFT Sequence Adding validations for a sub-field While adding a swift field you can also add validations for the sub-fields of the swift field. The validation types that are currently supported ...

Note: For the ‘Format Option’ sub field the validation button will not be enabled. If a sub-field has validations the text of the validations button will be ‘Red’ in color. If a sub-field does not have validation the text will be in normal color. You can click the ‘ ’, ‘ ’ to move validation(s) up/d...

Specifying Comment Comment for the validation can be specified in the comment text area. This is an optional property. See Also: Adding validations for a sub-field Adding Code validation Adding Code validation Code validation is applicable in cases where a field’s value should be one of a set of pre...

For example in MT519 sub-field ‘Function’ of field 23G must contain the following codes CANC and NEWM They can be added as shown below Pasting Codes From Clipboard You can also use the button to paste a set of codes from clipboard. Copy a set of codes along with their detail names and description fr...

Adding T26 Validation T26 validation is applicable in cases where a field’s value should not start or end with a slash ‘/’ and not contain two consecutive slashes ‘//’. 1. Add a new validation. 2. Select ‘Type’ as ‘T26’ in the ‘Type’ column. 3. The error code will be automatically set as ‘T26’. You ...

In MT514 sub-field ‘Rate’ in field 92A has a validation that when Sign is present, Rate must not be zero. For this field, T14 validation can be added as shown below. See Also: Specifying properties common for all validations Adding validations for a sub-field Removing validations from a sub field Ad...

Adding Currency Code Validation This validation is to verify that the currency code specified for a field is a valid ISO 4217 currency code. 1. Add a new validation. 2. Select ‘Type’ as ‘Currency Code’ in the ‘Type’ column. 3. The error code will be automatically set as ‘T52’. You need not change it...

See Also: Specifying properties common for all validations Adding validations for a sub-field Removing validations from a sub field Adding Time Offset Validation Time Offset validations are applicable for Time fields, whose value should be expressed, in a particular format HHMM and whose value shoul...

Adding C05 validation This validation is to verify that the BIC specified for a field is not a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO 1. Add a new validation. 2. Select ‘Type’ as ‘C05’ in the ‘Type’ column. 3. The error code will be automatically set as ‘C05’. You need not change it...

In MT567, sub-field ‘Amount’ in field 19A has a validation that the number of digits following the comma must not exceed the maximum allowed for the specified currency. For this field, Decimal validation can be added as shown below. See Also: Specifying properties common for all validations Adding v...

Removing Codes You can use the ‘ ’ button to remove an existing Party Identification code. Note that atleast one code should be present for a Party Identification Code validation. Note: You can use the ‘ ’ and ‘ ’ buttons to move code(s) up/down. See Also: Specifying properties common for all valida...

SWIFT External Format UI The External Format – SWIFT UI has 3 tabs – Header, Data and Trailer to represent the header block, text block and trailer block of the SWIFT message. The header and trailer types have to be specified while creating the external format. The header/trailer fields cannot be mo...

SWIFT Input Header/Trailer When you choose this option, the Header and Trailer panel has the following fields for a SWIFT external message format.

The field and section properties displayed are not editable. See Also: SWIFT Output Header/Trailer SWIFT Input/Output Header/Trailer FISC Header Format Options Swift User Message (Data) SWIFT Output Header/Trailer When you choose this option, the Header and Trailer panel has similar fields as that o...

The trailer has no fields and is blank in this case. Field properties Optional and Length are displayed in the Properties panel for the header. Note: When you choose the option ‘None’, the Header and Trailer sections will be empty. See Also: SWIFT Input Header/Trailer SWIFT Output Header/Trailer For...

Note that the sub-fields of a generic field are displayed under the qualifier in the External Format - SWIFT UI, similar to a sequence or field. This is because, though the qualifier is also a sub-field, it distinguishes the generic field. Hence the rest of the sub-fields are shown under it. See Als...

SWIFT Field Qualifier Info When a qualifier of a generic field is selected in the External Format - SWIFT UI, the bottom panel shows the properties of the qualifier. The check boxes Repeating and Optional show the qualifier properties. The Options that are associated with the qualifier are shown in ...

SWIFT Sub Field Info For a sub-field of a field (generic or non-generic) selected in the External Format - SWIFT UI, the bottom panel looks as shown below. Sub-field Info (Generic Field)

Sub-field Info (Non-Generic Field) The SWIFT Sub Field Info panel shows the sub-field’s Format, whether it is Optional and the Option in which it occurs. For each option (if the sub-field is specified in more than one option), the sub-field details are shown in separate rows. Validations can be adde...

See Also: Creating an empty Service/System message format Adding a System Field Adding a Group Adding a System Field A system field can be either A simple field. A field that does not have any sub-fields. For e.g. field ‘swift-address’ (tag 102). The format of the field is ‘4!a2!a2!c1!c3!c’. A compl...

7. The min/max Occurs, description and field name can be changed. See Also: Adding a Complex Field Fields Separated by OR/AND Adding a Group Adding a Complex Field A complex field consists of several sub-fields. For e.g. field ‘mir’ (tag 106) has the following format ‘(6!n)(4!a2!a2!c1!c)(3!c)(4!n)(6...

3. The field can be set as optional/repeating by specifying values for ‘min/max occurs’ in the ‘System Field Info Panel’. In case the same field is present twice in the message, the name of the field can be changed in the ‘Field Name’ column. Please note that the name of sub-fields cannot be changed...

3. If ‘AND’ is present between the fields and the first field is optional, enter the fields as optional. Additional validation for the presence of fields needs to be done separately. See Also: Adding a Simple Field Adding a Complex Field Adding a Group Adding a Group 1. In SWIFT external format UI, ...

Note: ‘Choice’ is not supported in case of groups. The groups added are treated as sequence. So while adding an OR group, make sure that it is added as an optional group. Validations to check the presence of the groups need to be done separately. See Also: Deleting a Field/Group Adding a Simple Fiel...

Adding a System Field Adding a Group Specifying Validations for a Field In case where validation needs to be done for the value of a field, it can be specified along with the field definition. The entry for field ‘msg-priority’ (tag 104) is shown below. <SwiftSystemFieldDef Name="msg-priority...

In some cases validation may need to be specified for a ‘sub-field’ of a field. For e.g. for field ‘mir’ (tag 106) validation needs to be done for sub-field ‘date’. It is specified as shown below <SwiftSystemFieldDef Name="mir" Tag="106"> <Format>(6!n)(4!a2!a2!c1!c)(3!c)(...

Right click the SWIFT External Format UI table and select ‘Expand’ menu item. You can select ‘Expand/Collapse’ menu items to expand/collapse SWIFT fields. Expanding Fields Select the ‘Expand’ menu item. Select ‘All’ sub menu item. All fields including sequences, fields and qualifiers will be expande...

3. The SWIFT message format is saved as XML file in the location <installation dir>\config\swift\format in the given Format Name. 4. SWIFT Formats saved this way are available for creating formats in future. Refer Creating a SWIFT Format based on an existing SWIFT message format . See Also: Cr...

4. The SWIFT format is saved in the location with the file name mentioned. See Also: Sample Exported HTML File Importing a SWIFT Message Format Importing a SWIFT Message Format SWIFT message format saved using the export method, can be imported. This is supported in XML and TPLUS formats. 1. To impo...

The message format in the file is imported. See Also: Exporting a SWIFT Message Format Sample Exported HTML File A sample of the SWIFT message format exported in HTML: MT543In SCOPE This message is sent by an account owner to an account servicer (account servicing institution). The account owner may...