BEA SWIFT Adapter manual Conventions

Page 48

changing the format, the corresponding specification should also be changed to reflect the format as shown in the following cases.

Conventions

A, B refer to independent sub-fields.

(e.g.) in the format ([ISIN1!e12!c])CRLF[4*35x] A is [ISIN1!e12!c] and B is [4*35x]

A1, A2 refer to parts of a sub-field. (e.g.) if A is [/1!a][/34x] then A1 is [/1!a] and A2 is [/34x]

SEP means SEPERATOR.

Format Pattern	[A] SEP [B]
Representation	A [SEP B] B
in Designer
This format implies that,

1.Either A and B are present or only A is present.

2.Only B is present.

Here the separator does not belong to (cannot be associated with) either of the two formats (A and B). The separator appears only if both are present. In the grammar

[A]SEP [B] there is no way to represent such a requirement without ambiguity. Consider the formats [A SEP][B] and [A][SEP B] – they do not represent the fact that separator should appear only if both A and B are present.

Since the grammar cannot convey the meaning correctly, the SWIFT specification provides additional information as part of the description or clarifies it elsewhere in the document. Hence such information should be correctly correlated with the format in Designer, so that the application interprets the format, the way it should.

Note

The parser tries out the first format and if it fails, tries the second (and so on). Because of this, the order of the formats (that are ORed) is important and should always be maintained. In general, the one with more number of fields should appear first.

Example

Image 48

Contents Swift Adapter User’s Guide Entering the Swift Specification Exporting a Swift Message Format to Library Swift Terminology Swift Configuration Swift message libraryCustom Swift messages Standard-versionGSCC SRG 2008/standard-version Creating a Swift Format Page Page Page Page Page See Also Creating a Swift Format from an empty message format Page Page Entering the Swift Specification Swift Sequence Sequence Without DelimitersSequence With Start and End Delimiters Repetitive Optional Subsequence A1 LinkagesSequence With Start Delimiter Statu Tag Field Name Content/Options Adding a Swift Sequence Adding a Swift Sequence without DelimitersPage Adding a Swift Sequence with Start and End Delimiters Page Adding a Swift Sequence with Start Delimiter Adding a Swift Field Adding a New Generic Field Add the Options for the field Adding Field Options Entering an Option Format Restrictions on Length Types of Characters AllowedExamples Entering an Option Specification Specification Sub-Field1 Sub-Field2 Sub-Field2 Removing Field OptionsAdding Qualifiers and Associating them with Options Page See Also Specifying or Option for a Qualifier Adding a Non-Generic Field See Also Mapping Formats with Specification Sub-fields Specifying Field Definition and UsagePage Page Page Representing Complex Formats in Designer Conventions Field 35B Field 82a Option a Field 82a Option B Field 41a Option D Adding Copy of Fields See Also Updating a Swift Field Page See Also Customize Field Page Removing a Swift Field Adding validations for a sub-field DatePage Specifying properties common for all validations Specifying Error Code Adding Code validation Specifying CommentRemoving Codes Adding T26 Validation Adding T14 ValidationAdding Date Validation Specifying Date FormatAdding Currency Code Validation Adding Country Code ValidationAdding Time Offset Validation Adding BIC validationSee Also Adding C05 validation Adding Decimal ValidationAdding Party Identification Validation Specifying Party Identification CodesRemoving Validations from a Sub Field Removing CodesSee Also Swift External Format UI External Format Swift Header/TrailerSwift Input Header/Trailer Page Swift Output Header/Trailer Swift Input/Output Header/Trailer Page Fisc Header Swift Format Options See Also Swift User Message Data Page Swift Sequence Info Swift Field Info Generic Swift Field Qualifier Info Swift Field Info Non-Generic Swift Sub Field Info System/Service Message Creating an empty Service/System message formatPage Click ‘Finish’ to create the System/Service message Page Adding a System Field Adding a Simple FieldPage Page Adding a Complex Field Fields Separated by OR/AND Adding a Group Deleting a Field/Group System Field DictionarySpecifying Validations for a Field Specifying Validations for a Sub-fieldExpanding/Collapsing Swift Fields Expanding Fields Exporting a Swift Message Format to Library Exporting a Swift Message Format Page Importing a Swift Message Format Sample Exported Html File ScopeRepetitive Optional Sequence A1 Linkages End Of Sequence A1 Linkages Qualifier