TPA Information | Description |
Sender | The name of the sending trading partner or “Unknown.” Select the sender from the profiles defined in Trading Networks, including your own profile. If you specify a partner for sender, you must also specify a partner for receiver. Likewise, if you specify Unknown for sender, you must specify Unknown for receiver. |
Receiver | The name of the trading partner that receives the message from SWIFT. Select the receiver from the profiles defined in Trading Networks, including your own profile. |
Agreement ID | Uniquely identifies the agreement between two partners, for example, MT541. This is a placeholder for the TN document type name (for example, “MT541”). |
IS Document Type | The IS document type
wm.fin.doc:UserParameters specifies the SWIFT TPA parameters. |
Agreement Status | Set to “Agreed.” To process messages according to a TPA, both sender and receiver TPAs must have the Agreement Status, “Agreed.” |
TPA Section | Parameter | Description |
FIN Process Info | Transport | The SWIFT interface used to send and receive SWIFT FIN messages. Valid values are: ![]() ![]() ![]() ![]() |
MessageType | The SWIFT FIN message type identifier, such as 541, Receive Against Payment. | |
ISDocumentName | IS document type for this message. IS document types for each message are located in the WmFINMessages package, for example, wm.fin.doc.nov10. cat5:MT541. | |
Version | Version of the SWIFT message, for example nov10. | |
Message Format | The format of the generated blocks and fields for the input FIN message. Valid values are: ![]() ![]() ![]() ![]() | |
SubfieldFlag | Indicates whether to parse SWIFT messages to the field or subfield level. Valid values are: ![]() ![]() Note: If you change this setting after creating message records, you must delete the message records pertaining to the TPA and recreate them. | |
InboundProcessingRuleService | Optional. Indicates whether to use a processing rule to manage message execution. To do so, type the service name to use. For more information, see
Receiving Messages from SWIFT. | |
ValidateContent | Optional. Indicates whether to validate the message. Valid values are Yes and No. | |
ValidateBICPlus | Optional. Indicates whether to validate BIC information in the message. Valid values are Yes and No. | |
ValidateNetworkRules | Optional. Indicates whether to validate the message against network rules. Valid values are Yes and No. | |
Network ValidationService | Optional. Name of the network validation service to use to validate network rules. | |
ValidateMarketPracticeRules | Optional. Indicates whether to validate the message against Market Practice rules. Valid values are Yes and No. | |
MarketPractice RulesService | Optional. Name of the Market Practice rules validation service to use. | |
ValidateUsage Rules | Optional. Indicates whether to validate this message against usage rules. Valid values are Yes and No. | |
UsageRulesService | Optional. Name of the usage validation service to validate the usage rules. | |
Message Header | This section contains information to be populated in blocks {B1}, {B2}, and {B3} of the outbound SWIFT message. | |
Logical Terminal | The logical terminal identifier defined in SAA. | |
ApplicationIdentifier | Identifies the application within which the message is sent or received. Valid values are: ![]() ![]() ![]() | |
ServiceIdentifier | Identifies the type of data being sent or received: ![]() ![]() | |
Priority | Indicates the priority with which to deliver the message to the receiver. Valid values are: ![]() ![]() ![]() | |
DeliveryMonitoring | Optional. Enables the sender to request delivery monitoring. Valid values are: ![]() ![]() ![]() ![]() | |
FINCopyServiceIdentifier | Optional. (Used with FINCopy messages only.) Three-character system ID used to support access to multiple services with the same CBT. | |
BankingPriority | Optional. Four-character field agreed upon by two or more parties to indicate priority. | |
ValidationFlag | Optional. Indicates whether special validation must be completed at SWIFT. For information about the MT message standards, see the SWIFT User Handbook/Standards. | |
AddresseeInformation | Optional. Information from the central institution to the receiver of the payment message. This information is used in the input of MT097, FIN Copy Message Authorization Refusal Notification. | |
Training | Indicates whether a message is sent to or received from a test and training logical terminal. | |
MQSeries Info | putMessage HandlerService | The name of the service generated when creating a message handler service for IS-to-WebSphere MQ transport. For more information, see
Using
WebSphere MQ Adapter to Communicate with SWIFT. |
AFT | folder | Fully qualified path of the folder you want the file polling listener to poll for this message, for example, c:\folder\bic.dat. Important: This folder must be accessible by both Integration Server and SAA. |
extension | Optional. File extension of the files to be received from the AFT folder. The default is inp. |