User Guide > Map Connectors > Source and Target Map Connectors > SWIFT
Was this helpful?
SWIFT
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) operates a global financial messaging network that exchanges messages between banks and other financial institutions. Messages formatted to SWIFT standards can be read by, and processed by financial processing systems, whether or not the message traveled over the SWIFT network.
Schema File Required
You are provided a template file that contains the structure for your SWIFT file connections. If your SWIFT file structure is different, you may need to modify the template.
To make changes to a SWIFT template file
1. Import the file into Project Explorer.
2. Open the file in the Schema Editor.
3. Make your changes.
4. Save the file with a different name.
To obtain a template file, contact your sales representative. These template files are standard schemas.
Connector Parts
Connector parts are the fields you configure to connect with a data source or target.
The settings that are available depend on the connector you select.
For a list of all parts for source connectors, see Specifying Connector, Parts, and Properties.
For a list of all parts for target connectors, see Specifying Connector, Parts, and Properties.
Property Options
You can specify the following source (S) and target (T) properties:
Property
S/T
Description
SchemaFile
S/T
Used for parsing data and generating a new schema during design time. Select a schema file that contains the schema you want to use.
Validation
S/T
False is the default setting. When Validation is true, the adapter validates:
1. Field requirement
2. Field default value if this value is defined
3. Validates the CheckSum
4. Validation works differently on source and target files. Validation on the source side occurs when you apply the source property options. On the target side, validation occurs at run time. If validation is successful, this is indicated in the log file and if there are errors, error messages are logged to the log file. On source side validation, the first error is recorded in the log file and then the transformation stops before any other errors are recorded. On the target side, all errors are recorded to the log file, since validation occurs at run time.
Unicode
S/T
This property is important if your IDoc file is Unicode encoded. The default is false, therefore if your target IDoc file is Unicode encoded, change this setting to true.
Last modified date: 02/09/2024