Bea SWIFT Adapter Bedienungsanleitung

Stöbern Sie online oder laden Sie Bedienungsanleitung nach Hardware Bea SWIFT Adapter herunter. BEA SWIFT Adapter User Manual Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 113
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen

Inhaltsverzeichnis

Seite 1 - User’s Guide

SWIFT Adapter User’s Guide Version 3.5

Seite 2

Creating a SWIFT Format Based on an Existing SWIFT Message Format 1. Right-click the Cartridge node in the Designer. Select the New External Messa

Seite 3

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 i

Seite 4

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 f

Seite 5 - Terminology

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

Seite 6 - SWIFT Configuration

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

Seite 7 - Custom SWIFT messages

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 su

Seite 8

Right click the SWIFT External Format UI table and select ‘Expand’ menu item. You can select ‘Expand/Collapse’ menu items to expand/collapse SWIFT

Seite 9 - Creating a SWIFT Format

Select ‘Qualifiers’ sub menu item. All expanded qualifiers will be collapsed. See Also: SWIFT External Format UI Exporting a SWIFT Message Form

Seite 10 - SWIFT Message Format

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

Seite 11

SWIFT message format can also be saved using the usual export method, allowing to save the format in XML, HTML and TPLUS formats. 1. To save a SWIF

Seite 12

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

Seite 13

4. In the next dialog that appears you have various options to choose Header/Trailer, Validation and Edit options as shown in the following pictur

Seite 14

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 f

Seite 15

3. pre-advise the account servicer of a forthcoming deliver against payment instruction (the function of the message is PREA). The instruction may

Seite 16

Status Tag Qualifier Generic Field Name Detailed Field Name Content/Options No O 13A LINK Number Identification Linked Transaction :4!c//3!c

Seite 17

Mandatory QUALIFIER Order M/O Qualifier R/N CR Options Qualifier Description 1 M SEME N C Sender's Reference Field 23G: Function of the Me

Seite 18

5. As seen in the above picture, you have the option to include specific Header/Trailer (SWIFT Input/SWIFT Output/SWIFT Input Output/FICC Header(c

Seite 19

7. Note that the Design Element UI tool bar buttons in the figure are disabled thereby not allowing the user to modify the format as we have chose

Seite 20 - SWIFT Sequence

Similarly to pick the options for a qualifier, select the qualifier in the table and select or deselect the check box in the SWIFT Field Qualifier

Seite 21

To pick the options for a non-generic field, select the field in the table and select or deselect the check box in the Enabled column of the options

Seite 22

Creating a SWIFT Format from an empty message format 1. Right-click the Cartridge node in Designer and select the New External Message menu item f

Seite 23

4. In the next dialog box that appears see that the “Validation Options” and “Edit Options” pane are disabled as they are not applicable in this c

Seite 24 - Adding a SWIFT Sequence

5. After selecting the required Header/Trailer from the list box, click Finish button. 6. An empty message format is created as shown below.

Seite 25

See Also: Creating a SWIFT Format based on an existing SWIFT message format Entering the SWIFT Specification Exporting a SWIFT Message Format to Li

Seite 26

SWIFT ... 4 TERMINOLOGY ...

Seite 27

Removing validations from a sub field SWIFT Sequence A Sequence is a group of related information, delimited in most of SWIFT message formats. Howe

Seite 28

-----| 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 S

Seite 29 - Adding a SWIFT Field

-----| End of Subsequence A1 Linkages M 16S End of Block GENL End of Sequence A General Information Mandatory Sequence B Trade Details M 16R

Seite 30 - Adding a New Generic Field

Status Tag Field Name Content/Options O 21 Related Reference 16x …… …… …… Mandatory Sequence B Transaction Details M 15B New Sequence (CrLf)

Seite 31

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 b

Seite 32 - Adding Field Options

3. Select None in Sequence Delimiter. Select the Mandatory and Repeating properties of the sequence as required. 4. For this case, the last sec

Seite 33 - Entering an Option Format

See Also: Sequence Without Delimiters Adding a SWIFT Sequence with Start and End Delimiters Adding a SWIFT Sequence with Start Delimiter Adding a

Seite 34

3. Select Block Delimited in Sequence Delimiter. Select the Mandatory and Repeating properties of the sequence as per the specification. 4. The

Seite 35

See Also: Sequence With Start and End Delimiters Adding a SWIFT Sequence without Delimiters Adding a SWIFT Sequence with Start Delimiter Adding a

Seite 36 - Removing Field Options

3. Select New Sequence Indicator in Sequence Delimiter. Select the Mandatory and Repeating properties of the sequence as per the specification. 4

Seite 37

Adding Currency Code Validation ... 69 Adding Cou

Seite 38

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 F

Seite 39

3. Enter the description of the field in the Description text field. 4. For customizing a field, refer section Customize Field. 5. Add the Opt

Seite 40

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.

Seite 41 - Adding a Non-Generic Field

4. For a generic field, the checkbox in the Selected column is not enabled at this point, as qualifiers are not yet added. Only on adding the qualif

Seite 42

maximum length c h Alphabetic letters (upper case) and digits only Hexadecimal letters A through F (upper case) and digits only Nn! Fixed length

Seite 43

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!

Seite 44

Specification (Sub-Field1) (Sub-Field2) (Sub-Field2) In this format pattern, the specification for subfields B and C are the same. ie, Sub-Field2.

Seite 45

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

Seite 46

3. Select the required Qualifier from the drop-down list as shown above. The Description is automatically populated on selecting the Qualifier. 4

Seite 47

5. Map the options to the qualifier. To map, select the qualifier row. Select the options that apply to this qualifier by selecting the checkbox in

Seite 48

SWIFT S.W.I.F.T. SCRL is the abbreviation for Society for Worldwide Interbank Financial Telecommunication, Societé Coopérative à Responsibilité Lim

Seite 49

Specifying OR Option for a Qualifier The OR option, allows grouping of qualifiers. This is useful when one of the many possible qualifiers can appe

Seite 50

Adding a Non-Generic Field A Non-Generic field, unlike a generic field, is a discrete data item used for one purpose only. To add a non-generic fie

Seite 51

7. Select the required options by selecting the check box in the Selected column of the options table. Note that this column is enabled only on step

Seite 52

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 d

Seite 53 - Adding Copy of Fields

2. The selected row has a simple format and specification. Hence there is no ambiguity for Designer in mapping the format with the specification.

Seite 54

5. Note that there is no one-to-one correspondence between the Format and the Specification. In the above figure, all the formats that have no spe

Seite 55 - Updating a SWIFT Field

8. The format of option P in options table now looks like 9. Note the ( ) brackets added in the format after merging. These brackets can also

Seite 56

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 tre

Seite 57

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

Seite 58 - Customize Field

Field 35B Format ([ISIN1!e12!c])CRLF[4*35x] Specification (Identification Of Security)(Description Of Security) Format in Designer (ISIN1!e12!c)([CR

Seite 59

Export a SWIFT Message Format Terminology Sequence Each message type contains zero, one or more sequences. A sequence is a group of related inform

Seite 60 - Removing a SWIFT Field

Example Field 82a – OPTION A Format [/1!a][/34x]CRLF4!a2!a2!c[3!c] Specification (Party Identifier)(BIC) Format in Designer [/1!a[/34x]CRLF])(4!a2!

Seite 61

In this format pattern the separator does not belong to either of the two formats (A and B). In this case, format A is further divided into two parts

Seite 62

Number of lines that range between 1 and maximum number possible is present in format A along with format B. Maximum number of lines that is

Seite 63

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

Seite 64 - Specifying Null Field

From the above diagram it can be seen that the ‘Copy of Fields’ gets added as the last field in the message with the occurrence property. Note:

Seite 65 - Adding Code validation

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

Seite 66 - Removing Codes

3. The options available for the field are populated in the options table, with the apt options selected. Add any missing option if needed, refer

Seite 67 - Adding T14 Validation

6. Click the Remove button to remove the selected field from the Tag list, subsequently from the External Format - SWIFT UI. 7. To change the su

Seite 68 - Adding Date Validation

Customize Field Consider the message format MT101. Status Tag Field Name Content/Options No. Mandatory Sequence A General Information M 20 Se

Seite 69

2. In the Create Field/Modify Field dialog that appears, click the Customize button. 3. In the Customize Field dialog that appears enter the s

Seite 70 - Adding BIC validation

SWIFT Configuration SWIFT field dictionary and message library are stored under <installation dir>\config\swift folder. This folder contains

Seite 71

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

Seite 72 - Adding Decimal Validation

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

Seite 73

2. The Swift Field Validations dialog will be displayed. 3. In the top tool bar select the button to add a new validation. 4. The default t

Seite 74 - SWIFT External Message UI

Note: For the ‘Format Option’ sub field the validation button will not be enabled. If a sub-field has validations the text of the validat

Seite 75

Specifying Error Code Specify the error code in the ‘Error Code’ column. Specifying Field Options In the field options list only those options

Seite 76 - SWIFT External Format UI

Specifying Comment Comment for the validation can be specified in the comment text area. This is an optional property. See Also: Adding validat

Seite 77 - SWIFT Input Header/Trailer

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

Seite 78

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 cons

Seite 79 - SWIFT Output Header/Trailer

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 add

Seite 80

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. A

Seite 81

Custom SWIFT messages Depending on your requirement you may have to customize the SWIFT messages or make minor modifications to it. One such case

Seite 82 - FISC Header

See Also: Specifying properties common for all validations Adding validations for a sub-field Removing validations from a sub field Adding Time Off

Seite 83 - Swift Format Options

3. The error codes will be automatically set as ‘T27, T28, T29, T45’. You need not change it. 4. Specify the qualifiers, field options, null field

Seite 84

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 T

Seite 85 - Swift User Message (Data)

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

Seite 86

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

Seite 87 - SWIFT Sequence Info

See Also: SWIFT External Format UI Creating a SWIFT Format Entering the SWIFT Specification

Seite 89 - SWIFT Field Qualifier Info

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

Seite 90

The Section Properties panel in the Header panel shows the properties of the header block, such as whether it is Repeating and Optional. The Pr

Seite 91 - SWIFT Sub Field Info

The field and section properties displayed are not editable. See Also: SWIFT Output Header/Trailer SWIFT Input/Output Header/Trailer FISC Header F

Seite 92 - System/Service Message

3. The exported message will be saved under a directory by the same name as the version. Once you have exported all the customized mess

Seite 93

Swift User Message (Data) SWIFT Input/Output Header/Trailer When you choose this option, the Header and Trailer panel has similar fields as that o

Seite 94

The Section Properties panel in the Header panel shows the properties of the header block, such as whether it is Repeating and Optional. The P

Seite 95

The field and section properties displayed are not editable. See Also: FISC Header Format Options Swift User Message (Data) FISC Header When you

Seite 96 - Adding a System Field

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.

Seite 97

The same set of Header/Trailer options that were available during message creation is available here too. (Custom Header/Trailer corresponds to FIC

Seite 98

Swift User Message (Data) The External Format - SWIFT User message (Data) UI looks as below. The message format is shown in the table at the top, a

Seite 99 - Adding a Complex Field

The sub-fields displayed under the fields are a collection of sub-fields in the options selected while creating or modifying the field (using the C

Seite 100 - Fields Separated by OR/AND

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. Thi

Seite 101 - Adding a Group

See Also: SWIFT Field Info (Generic) SWIFT Field Qualifier Info SWIFT Field Info (Non-Generic) SWIFT Sub Field Info Adding a SWIFT Sequence SWIFT F

Seite 102 - System Field Dictionary

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

Seite 103

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 t

Seite 104

SWIFT Field Info (Non-Generic) When a non-generic field is selected in the External Format - SWIFT UI, the bottom panel shows the properties of the

Seite 105 - Collapsing Fields

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 show

Seite 106 - Library

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

Seite 107

4. Click ‘Next’. In the next dialog box select the header type required and the message type. The ‘Message Type’ combo box lists the message types

Seite 108

5. Click ‘Finish’ to create the System/Service message. See Also: Creating a SWIFT System/Service Format Based on an Existing SWIFT Message Forma

Seite 109

3. In the New Swift Message Format dialog that appears, select an existing format based on which the new format is to be created. Select Create base

Seite 110 - Sample Exported HTML File

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

Seite 111

3. You can specify the min/max occurs of the field in this dialog. If the field is non- repeating the field will be added as a simple field. In ca

Seite 112

5. You can change the optional property of the field in the ‘System Field Info’ panel. In some cases the same field may be present twice in the me

Seite 113

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 Add

Kommentare zu diesen Handbüchern

Keine Kommentare