Editing a message

You can use the MER Facility to edit messages, for example to fix errors that are detected during validation or processing. Messages on an Edit queue can be opened to modify fields. The message is displayed in the same manner as during creation of the message. You can, for example, fix incorrect values and problems reported during authorization of the message, and then submit the message again.

Note: It can happen that, when you open a message that failed validation and click Validate, the edit function does not indicate a validation problem. The MER Facility performs the following automatic corrections when a message is opened for editing:
  • Uppercase conversion
  • Omission of empty fields
  • Automatic insertion of section markers (field 15 or field 16)
  • Other implicit modifications

If the MER Facility is to process a message for which the payload cannot be parsed, it assigns it the message type DNIUNPARSABLE. In the message list, this special type is abbreviated as Unpar., as shown in Figure 1. The full message type appears as hover help. For messages in domain DNIFIN, the local and remote addresses are also set to DNIUNPARSABLE. You can work with unparsable messages, but only if you have the access rights for that message type and the local address. Additionally, you need access rights for the message type and local address of the corrected message.

Figure 1. Message list with unparsable messages
Figure showing a message list with two unparsable and five other messages

If you edit an unparsable message in a domain other than DNIFINPLUS, the following page is displayed and you can correct the message:

Figure 2. Editing of an unparsable message
Figure showing editing of an unparsable message

If you edit an unparsable message in domain DNIFINPLUS, the following page is displayed and you can correct the message:

Figure 3. Editing of an unparsable DNIFINPLUS message
Figure showing editing of an unparsable DNIFINPLUS message

For a message in domain DNIFINPLUS, you can enter a value in the Message Option field if none is specified, and you must enter a value in the Date field if the message cannot be processed with the currently defined message definition set.

Correct the message content, then click Parse to check whether the message can now be parsed. If it can be parsed, use Proceed to display the Formatted view and continue editing. You need access rights for the new message type and local address for this step. After proceeding, you can no longer change the type or local address. The message type field can be left blank. The type is automatically determined when the message is parsed. If you enter a message type here, you can proceed only if the type determined from the message is identical to the one you specified. The date field can be left blank when you are editing a message that uses a current message standard. Message standards can get superseded by a SWIFT standards release change. If the message uses a superseded standard, enter the date on which the message was created or received, in ISO format.