BEAメーカーSWIFT Adapterの使用説明書/サービス説明書
ページ先へ移動 of 113
SWIFT Adapter User’s Guide Version 3.5.
SWIFT .......................................................................................................... 4 TERMINOLOGY ............................................................................................. 5 SWIFT CONFIGURATION ........
Adding Currency Co de Validation ................................................................................................ ....... 69 Adding Country Co de Validation ..............................................................................
SWIFT S.W.I.F.T. SC RL is th e abbreviation for Society for Worldwide In terbank Financial Telecommunication, Societé Coopérative à Resp onsibilité Limitée.
Export a SWIFT Message Format Terminology Sequence Each message type contains zero, one or mo re sequences. A sequence is a group of related information made up of one or more fields and/or sub-se quences. A sequence may or may not be delimited. For delimiting a sequence use a start indicator and end indicator or start indicator alone.
SWIFT Configuration SWIFT field dictionary and message lib rary are stored under <installation dir>configswift fol der. This folder contains t he following files and fol ders. QualifierList . csv List SWIFT qualifiers with descript ion. SwiftField.
Custom SWIFT messages Depending on your requi rement you may ha ve to customize the SWIF T messages or make minor modifications to it. One such case is GSCC S WIFT messages. If these customized messages are used often or across the enterprise, you ma y want to make use of the SWIFT message library feature to store the customized SWIFT messages.
3. The exported message will be saved unde r a di rectory by the same name as the version. Once you have exported all the customiz ed messages to this directory, you can make of copy this directory to all D esign er installations as required. 4. Note that the version name wi ll also be i ncluded in the message definition (XML ) as shown below.
This detail is gen erally not important; but if y ou are manually editing the version (in say messages you already have) i n XML’s re member 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 just like standard SWIFT message s.
Creating a SWIFT Format Based on an Existing SWIFT Message Format 1. Right-click the Cartridge node in the Designer. Select the New External Message menu item from the context menu to create a SWIFT external format.
4. In the next dialog that appears you ha ve various options to choose Header/Trailer, Validation and Edit opti ons as shown in t he following picture:.
5. As seen in the above pi cture, you have the opti on to inclu de specific Header/Trailer (SWIFT Input/SWIFT Out put/SWIFT Input Outpu t/FICC Header(custom) or no Header/Trailer) from t he list box.
7. Note that the Design Element UI tool bar buttons in the figure are disabled thereby not allowing the user to modify th e format as we have chosen Read O nly mode in the Edit options. 8. The Enabled column of the format table all ows the user to pick from the optional fields, qualifiers and options for t he format .
Similarly to pick t h e options for a qualifier, sele ct the qualifier in the table and select or deselect the check box in the SWIFT Field Qualifier Info panel below.
To pick the options for a non- generic field, sele ct the field in the table and select or deselect the check box in the Enabled column of the options displayed in the SWIFT Field Info (Non-Generic ) panel below the table.
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 from the context menu to create a SWIFT external format. 2. In the New External Message dialog that appears, enter the Transf ormation Name and select SWIFT from the External M essage listbox.
4. In the next dialog box that appears see tha t the “Validation Options ” and “Edit Options” pane are disabled as they are no t applicable in this case. You h ave the option to include specific Header/Tra iler (SWIFT Input/SWIFT Output/SWIFt Input/Output/FIC C Header(custom) or no Header/Trailer as show n in the following picture.
5. After selecting the requ ired Header/Trail er f rom the list box, click Finish button. 6. An empty message format is created as shown below..
See Also: Creating a SWIFT Format based on an existing SWIFT message format Entering the SWIFT Speci fication Exporting a SWIFT Message Format to Library Entering the SWIFT Specification A SWIFT message is composed of sequence s and fields. A sequence is a group of related information made up of one or more fields and/or sub-se quences.
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 fo rmats, which have sequences without delimiters. The Designer prov ides for creating sequences with or with out delimiters.
-----| Note sequences A and B of this format. T hey 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 En d D elimiters Sequence With Start Delimiter Sequence With Start and End Delimiters Consider the message MT543.
-----| End of Subsequence A1 Linkages M 16S End of Block GENL End of Sequence A General Inform ati on Mandatory Sequence B Trade Details M 16R Start of Block TRADDET O 94B TRAD Place Place of Trade :4.
Statu s Tag Field Name Content/Options O 21 Related Reference 16x …… …… …… Mandatory Sequence B Transaction Details M 15B New Sequence (CrLf) M 30T Trade Date 8!n M 30V Value Date 8!n M 36.
Adding a SWIFT Sequence A sequence is a group of related informatio n made up of one or more fiel ds and/or sub-sequences. A sequence may or may no t b e delimited.
3. Select None in Sequence Delimiter . Select the Mandatory and Repeating properties of the sequence as required. 4. For this case, th e last sect ion about the delimiters and their f ormat is not required and hence disabled. Click OK. 5. The new sequence is added to the format as shown below.
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.
3. Select Block Delim ited in Sequence Delimite r . Select the Mandatory and Repeating properties of the sequ ence as per the specification. 4. The Start Of Block and End Of Block text fields are auto.
See Also: Sequence With Start and En d D elimiters Adding a SWIFT Sequence without Delimiters Adding a SWIFT Sequence with Start Delimiter Adding a SWIFT Sequence with Start Delimiter 1. Click the Add New Sequence button in the toolbar of the External For m at - SWIFT UI.
3. Select New Sequence Indicator in Sequence Delimiter . Select the Mandatory and Repeating properties of the se quence as p er th e specification. 4. The Start Of Block text field is automatically po pulated with value 15A when the Sequence Delimiter is specified in the step above.
Non Generic Field- Unlike a generic field, i s 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 Cust.
3. Enter the descripti on of the field in the Descri ption text fiel d. 4. For customizing a field, refer section Customize Field . 5. Add the Options for the field. 6. Make sure the Generic Field check box is selected. 7. Add the Qualifiers and ma p them to the Opti ons of the field.
See Also: Adding a Non-Generic Field Adding Field Options 1. Click the Add New Options butto n in th e Create Field or Modify Field dialog. 2. A new row is added in the opti ons table. Enter the Opti on, its format, specification and description in the respective columns.
4. For a generic field, the checkbox in the Sel ected column is not enabled at this point, as qualifiers are n o t yet added. Only on adding the qualif ie rs the column is enabled, so as to allo w the mapping of the qual ifier with the Option. S ee Adding Qualifiers and Associati n g them with Options.
maximum length c h Alphabetic letters (upp er case) and digits only Hexadecimal letters A through F (upper case) and digits only Nn! Fixed length x Any character of the permi tted character set upper .
3. The formats within the brackets ( ) should be t reated as a single unit. In the following fi gure, note option P. The format is :4!c(/ /4!a2!a2!c[3!c]). The ( ) brackets separates :4!c from the rest, th us implying onl y two sub-fields with formats 4!c and //4!a2!a2! c[3!c].
Spec ificat ion (Sub-Field1) (Sub-Field2) (Sub -Field2) In this format patt ern, the specification for su bfields B and C are the same. ie, Sub-Field2 . If this pattern is entered, only one in st ance of Sub-Field2 will be created, though the format indicates 3 subf ields, which is not correct.
The option is removed from the options table. If there is any qualifier associated with the removed option, in the case of a generi c field, map i t to the correct option or remove it. See Also: Adding a New Generic Field Adding Qualifiers and Associati ng them with Options 1.
3. Select the required Qualifier from the drop-down list as shown above. The Description is automatically populated on selectin g t he Qualifier . 4. Select the Presence of the Qualifier among O (Optional), M (Mandatory), OR (OR). See Specifying OR option for a Qu alifier to specify OR presence.
5. Map the options to the qualif ie r. To map, select the qualifier row . Select the options that apply to th is qu alifier by selecting the ch eck box in the Selected column of the required op tions, as shown below. 6. On selecting the options, they app ear in the Options column in the qualifier table.
Specifying OR Option for a Qualifier The OR option, allow s grouping of qualifiers. T his is useful when one of th e many possible qualifiers can appear for a fiel d option as per the specification. For example, field 95a allows one among a gro up of qualifiers BUYR, D EAG, DECU, etc.
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 field to a message format, follow the steps given below. 1. Click the Add New SWIFT Field button in the toolbar of the External Format - SWIFT UI.
7. Select the required opti on s by selecting the check box in the Selected column of the options table. Note that this column is ena bled only on step 5. 8. For a field existing already, the description and Options a re automatically populated when the field is selected from the Tag l ist.
Specifying Field Definition and Usage A field’s definiti on an d usage can be specified by clicking the button in the Create Fi eld or Modify Fiel d dialog. For example fi eld definition and usage of field ‘23G’ in MT519 can be specified as shown b elow.
2. The selected row has a simple format and specification . Hence there is no ambiguity for Designer in mapping the fo rmat with the specif ication. Designer shows the correct mapping in this case 3.
5. Note that there is no one-to -one correspondence between the Format and the Spec ificat ion . In the above figure, all the format s th at have no specification actually belong to BIC/BEI sub-field. Hence in order to correct the ma pping, those formats have to be merged for the specification BIC/BEI.
8. The format of option P in options table now looks like 9. Note the ( ) brackets added in the format afte r merging. These bracke ts can also be entered in the format dire ctly, w ithout going through t he Fields Forma t dialog. 10. The reverse is also possible in the Fields Format dialog.
13. The format now looks correct as below . Click OK. Use of brackets ( ) around a set of (t wo 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, th us implying onl y two sub-fields with formats 4!c and //4!a2!a2! c[3!c].
changing the format, the co rresponding specification sh ould also be changed to reflect the format as show n 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-fi eld.
Field 35B Format ([ISIN1!e12 !c])CRLF[4*35x] Spec ificat ion (Identification Of Secur ity)(Description Of Sec urity) Format in Designer (ISIN1!e12!c)([CRLF4*35x]) | 4*35x Spec ificat ion in Designer (.
Example Field 82a – OPTION A Format [/1!a][/34x ]CRLF4!a2!a2!c[3!c] Spec ificat ion (Party Identifier)(BIC) Format in Designer [/1!a[/34x]CRLF])(4!a 2!a2!c[3!c]) | ([/34xCRLF])(4!a2!a2! c[3!c]) Spec.
In this format pattern the separato r does not belong to ei ther of the two formats ( A and B ). In this case, format A is further divided into two parts A1 and A2 . The separator appears only if either one or both of A1 and A2 is/are present and format B is also present.
Number of lines that range between 1 and ma ximum number possible is present in format A along with format B . Maximum number of lines that is possible is present in format A along with format B . In this format pattern, format A can have multiple lines in its data, which are separated by CRLF.
Adding Copy of Fields In some SWIFT messages a set of fields need to be treated as single enti ty. For e.g. in common group messages (MTnxx), a copy of the fiel ds that occurred in the original message may occur at the end. The enti re set should be treated as a single field.
From the above diagram it can be seen that the ‘Copy of F ields’ gets added as the last field in the message with the occurrence property. Note: The ‘Copy of Fields’ of fields should be the last field in the message. It should be a top-level fi eld.
Updating a SWIFT Field 1. Select the field to be modifi ed in the External For mat - SWIFT UI and click the Modify SWIFT Field button in the toolbar. 2.
3. The options availabl e for the field are populated i n the options table, with the apt options selected. Add any missing option if needed, refer Adding Field Options .
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 suffix, refer the section Customize Field .
Customize Field Consider the message format MT101 . Status Tag Field Name Content/O ptions No. Mandatory Sequenc e A General Info rmation M 20 Sender's Reference 16x 1 O 21R Customer Specified Re.
2. In the Create Field/Modi fy Field dialog that appears, click the Customize button. 3. In the Customize Fiel d dialog tha t appears ente r the suffix and click OK. 4. Click OK in th e Create Field/Mo di fy Fiel d dialog. Now the External Format - SWIFT UI shows the fiel d with the suffix enter ed.
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 Field s button in the toolbar. The fi elds are removed from the format.
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- f ields of the swift field.
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 type will be ‘C ODE’. Click the ‘Ty p e’ column. The list of validat ion types will be displayed. Select th e appropriate validation type.
Note: For the ‘Format Option ’ su b field the validation bu tt on will not be enabled. If a sub-field has v alidations th e text of the validation s button will be ‘Red’ in color. If a sub-field does not have v alidation the text will be in normal color.
Specifying Error Code Specify the error code in the ‘Error Code’ column. Specifying Field Options In the field options li st only those options that are applicable to the se lected sub field will be displayed. By default all the displayed op t ions will be selected when you add a validation.
Specifying Comment Comment for the validation can be specified in the comment t ext 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 w here a field’s value should be one of a set of predefined values.
For example in MT519 sub-fi eld ‘Func tion’ of field 23G must con tain the following codes CANC and NEWM They can be added as shown below Pasting Codes From Clipboard You can also use t he button to paste a set o f codes from clipboard.
Adding T26 Validation T26 validation is applicable in cases where a f ield’s value should not start or end with a slash ‘/’ and not co ntain two consecuti ve slashes ‘//’. 1. Add a new validat ion. 2. Select ‘Type’ as ‘T26’ in the ‘Type’ column.
In MT514 sub-field ‘Rate’ in field 92A has a validation that when Sign is present, Rate must not be zero. For t his field, T 14 validation can be added as shown below.
Adding Currency Code Validation This validation is t o verify that the currency code specified for a field is a valid ISO 4217 currency code. 1. Add a new validat ion. 2. Select ‘Type’ as ‘Currency Code’ in the ‘Type’ col umn. 3. The error code will be au tomatically set as ‘T52’.
See Also: Specifying properties common for all validatio ns Adding validations for a sub-field Removing validations from a sub field Adding Time Offset Validation Time Offset validat ion s are applicable for Time fields, wh ose value should be expressed, in a particular format HH MM and whose value should be with in a particular range.
3. The error codes will be aut omatically set as ‘T27, T28, T29, T45’. You need not change it. 4. Specify the qualifie rs, field options, nu ll field and comment properties as specified earlier. The description and usage for this va lidat ion type will be displayed at t h e bottom.
Adding C05 validation This validation is to verify that the BIC specified fo r a field is n ot a BEI, ie must not be of subtype BEID, MC CO, TESP or TRCO 1. Add a new validat ion. 2. Select ‘Type’ as ‘C05’ in the ‘Type’ column. 3. The error code will be aut omatically set as ‘C05’.
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.
Removing Codes You can use the ‘ ’ button to remove an exi sting Party Identifi cation code. Note that atleast one code s hould be present for a Party Identi fication Code vali dation. Note: You can use the ‘ ’ and ‘ ’ buttons to move code(s) up/down.
See Also: SWIFT External Format UI Creating a SWIFT Format Entering the SWIFT Speci fication.
SWIFT External Format UI The External Format – SWIFT UI has 3 tabs – Header , Data and Trailer to represent the header block, text block an d trailer block of the SWIFT message. The header and trailer types have to be specif ied while creating the external format.
SWIFT Input Header/Trailer When you choose th is option, the Hea der and Trailer panel has the following fields for a SWIFT external message format..
The Section Properties panel in the Header panel shows the properties of the header block, such as whether it is Repeating and Optional. The Properties panel shows the properties of a field (shown when a field is selected). It shows whether the field is Optional and it’s Length.
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 H.
Swift User Message (Data) SWIFT Input/Output Header/Trailer When you choose th is option, the Hea der and Trailer panel has similar fields as that of a SWIFT Input Header/Trailer exce pt for the Application Header block in Header section which is divided as Applic ation Header Input and Application Header Output as shown below.
The Section Properties panel in the Header panel shows the properties of the header block, such as whether it is Repeating and Opti onal. The Properties panel shows the properties of a field (shown when a field is selected). It shows whether the field is Optional and i t’s Length.
The field and section properties displayed are not editable. See Also: FISC Header Format Options Swift User Message (Data) FISC Header When you choose th is option, the Hea der and Trailer panel has the following fields for a SWIFT input/output message format.
The trailer has no fields and is bl ank in t h is case. Field properties Optional and Length are displayed in the Properties pane l for the header. Note: When you choose the option ‘N one’, the Header and Trailer sections will be empty.
The same set of Header/Trailer options that were available during message creation is available here too. (C ustom Header/Trailer corresponds to FICC Header). You can set the maximum l ength for the message by enteri ng the length value in the ‘Max Length’ t ex t box.
Swift User Message (Data) The External Format - SWIFT User message (D ata) UI looks as below. The message format is shown in the ta ble at the t op, and a panel at the bottom s hows the properties of the row selected in th e table. The properties panel dynamically changes as the row selected in the table changes.
The sub-fields displayed under the fields are a collection of sub-fields in the op tions selected while creating or mo difying the field (using the C reate Field or Modify Field dialog).
Note that the sub-fiel ds of a generic fiel d are displayed under the qualifier in the External Format - SWIFT UI, similar to a se quence or field. This is because, though the qualif ie r is also a sub-field, it distinguishes the gene ric field. Hence the rest of the sub-fields are shown under it.
See Also: SWIFT Field Info (Generic) SWIFT Field Qualifier In f o SWIFT Field Info (Non-Generic) SWIFT Sub Field Info Adding a SWIFT Sequence SWIFT Field Info (Generic) When a generic field is selected in the Ext ernal Format - SWIFT UI, the bottom panel shows the properties of the field as below.
SWIFT Field Qualifier Info When a qualif ier of a generic field is selected in th e 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 qu alifier are shown in a table.
SWIFT Field Info (Non-Generic) When a non-generic fi el d is selected in the External Form at - SWIFT UI, the bottom panel shows the properties of the field as shown below.
SWIFT Sub Field Info For a sub-field of a field (generic o r non-generic) selected in the E xte rnal Format - SWIFT UI, the bottom panel looks as shown below.
Sub-fi el d Info (Non-Gen e ric Field) The SWIFT Sub Field Info panel shows the sub-field’s Format , wheth er it is Optional and the Optio n in which it occurs . For each option (if the s ub-field is specified in more than one option), the su b-field details are show n in separate rows.
4. Click ‘Next’. In the next dialog box se lect the header type required and the message type. The ‘Message Type’ combo box lists the message type s. The types of messages are ‘User’, ‘System’ and ‘S ervice’ . To create a System message select the type as ‘System’.
5. Click ‘Finish ’ to create th e System/Service message. See Also: Creating a SWIFT System/Service Format Based on an Existing SWIFT Message Format Adding a System Field Adding a Group Creating a SWIFT System/Service Format Based on an Existing SWIFT Message Format 1.
3. In the New Swift M essage F ormat dialog that appears, select an existing format based on which the new form at is to be created. Select Create based on selected format radio button. Click Next . 4. In the next dialog that appears you ha ve various options to choose Header/Trailer, Validation and Edit opti ons.
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 fi eld that does not ha ve any sub-fields. Fo r e.g. field ‘swift- address’ (tag 102).
3. You can specify the mi n/max occurs of the fi eld in this dialog. If the field is non- repeating the field wi ll be added as a simpl e field. In case a simpl e field is repeating select the max occu rs accordingly. In this case the field will be added as a section.
5. You can change the optional property of th e field in the ‘System Field Info’ panel. In some cases the same field may be pr esent twice in the message. The name of the field can be changed in such cases. The description of the field can also be changed.
7. The min/max Occurs, description an d 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-fiel ds.
3. The field can be set as optional/repeati ng by specifying va lues for ‘min/max occurs’ in the ‘System Fi eld Info Panel’. In case the same field is present twice in the message, the name of the field can be changed in the ‘Field N ame’ column.
3. If ‘AND’ is present between the fields and the first fi el d is optional, enter the fields as optional. Addi tional validation for the presence of fi elds needs to be done separately. See Also: Adding a Simple Field Adding a Complex Field Adding a Group Adding a Group 1.
Note: ‘Choice’ is not support ed 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 pr esence of the groups need to be done separately.
Adding a System Field Adding a Group Specifying Validations for a Field In case where validatio n needs to be done fo r the value of a field, it can be specified along with the fiel d definition. The entry for field ‘msg-priority’ (tag 104) is shown below.
In some cases validation may n eed t o be specified for a ‘sub-field’ of a field. F or e. g. for field ‘mir’ (tag 106) validation needs to be done for sub-field ‘d ate’.
Right click the SWIFT External Format UI table and select ‘Expand’ menu item. You can select ‘Expand /Collapse’ menu it ems to expand/colla pse SWIFT fields. Expanding Fields Select the ‘Ex p and’ menu item. Select ‘All’ su b menu item.
Select ‘Qualifiers’ sub menu item. All expanded qualifiers will be collapsed. See Also: SWIFT External Format UI Exporting a SWIFT Message Format to Library Exporting a SWIFT Message Format to Library A SWIFT message format once fully entered in Designer can be saved so that it is available for creat ing other formats dependin g on it.
3. The SWIFT message format is saved as XML file in t he location < installation dir >configswift format in the given Format Name . 4. SWIFT Formats saved this way ar e available for creating formats in future. Refer Creating a SWIFT Format based on an existing SWIFT message format .
SWIFT message format can also be saved us ing the usual export method, allowing to save the format i n XML, HTML and TPLUS formats. 1. To save a SWIFT format, select t he SWIFT format node in the Explor er and choose the context menu Export… . 2. In the Export dialog that appears, select the lo cation to sa ve the exported fil e.
4. The SWIFT format is saved in th e location with the file name men tioned. See Also: Sample Exported HTML File Importing a SWIFT Message Format Importing a SWIFT Message Format SWIFT message format saved using the expo rt method, can be imported. This is supported in XML and TPLUS form ats.
The message format in th e f ile is imported. See Also: Exporting a SWIFT Message Format Sample Exported HTML File A sample of the SWIFT message format exported i n HTML: MT543In SCOPE This message is sent by an account owner to an account se rvicer (account servicing institution ).
3. pre-advise the account servicer of a forthcoming deliver against payment instruction (th e fu nction of the message is PREA). The instruction may be linked to other settlemen t instructions , eg, for a turnaround or back-to-back, or other transactions, eg , foreign exchange deal, using the linkages sequence.
Status Tag Qualifier Generic Field Name Detailed Field Name Content/Optio ns No O 13A LINK Number Identification Linked Transaction :4!c//3!c 8 M 20C 4!c Reference (See Qualifier Description) :4!c//16.
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 Message FORMAT Option G 4!c[/ 4!c] (Function) (Subfunction).
デバイスBEA SWIFT Adapterの購入後に（又は購入する前であっても）重要なポイントは、説明書をよく読むことです。その単純な理由はいくつかあります：
BEA SWIFT Adapterをまだ購入していないなら、この製品の基本情報を理解する良い機会です。まずは上にある説明書の最初のページをご覧ください。そこにはBEA SWIFT Adapterの技術情報の概要が記載されているはずです。デバイスがあなたのニーズを満たすかどうかは、ここで確認しましょう。BEA SWIFT Adapterの取扱説明書の次のページをよく読むことにより、製品の全機能やその取り扱いに関する情報を知ることができます。BEA SWIFT Adapterで得られた情報は、きっとあなたの購入の決断を手助けしてくれることでしょう。
BEA SWIFT Adapterを既にお持ちだが、まだ読んでいない場合は、上記の理由によりそれを行うべきです。そうすることにより機能を適切に使用しているか、又はBEA SWIFT Adapterの不適切な取り扱いによりその寿命を短くする危険を犯していないかどうかを知ることができます。
ですが、ユーザガイドが果たす重要な役割の一つは、BEA SWIFT Adapterに関する問題の解決を支援することです。そこにはほとんどの場合、トラブルシューティング、すなわちBEA SWIFT Adapterデバイスで最もよく起こりうる故障・不良とそれらの対処法についてのアドバイスを見つけることができるはずです。たとえ問題を解決できなかった場合でも、説明書にはカスタマー・サービスセンター又は最寄りのサービスセンターへの問い合わせ先等、次の対処法についての指示があるはずです。
