Friday, February 3, 2017

Routing Messages

Introduction

An operator only has access to the Route command if the operator's profile includes the "Route Message" entitlement. If you do not want an operator to route messages, then make sure that the "Route Message" entitlement is deselected in the operator's profile.
System messages are routed directly to _SI_to_SWIFT.
When you route a message, the message is sent from its current queue to the next logical queue. This queue depends on:
  • The routing rules defined for the current queue.
  • The format of the message.
  • For messages in SWIFT format only, the message type.
If you want messages to print automatically whenever they are routed, then select File/ Preferences/Enable Message Print.
The following description assumes that the default routing rules apply. You use the Routing application to change the routing rules. For more information, see message routing in the System Management Guide.

To route a message

  1. Select Route from the Message menu. The syntax and structure of a SWIFT message are validated to ensure that:
    • all mandatory fields, subfields, and sequences are complete
    • any optional fields selected are complete
    • all text loops have the minimum number of occurrences
    • all completed fields and subfields have the correct syntax.
  2. If a SWIFT message has no errors, then it is "valid" and is routed to the queue defined in the routing rules. The default routing for newly created SWIFT messages is:
    • All FIN messages except MT 999 messages are routed to the Message Verification queue (MP_verification).
    • MT 999 messages are routed from the Message Creation queue to the Message Authorisation queue (MP_authorisation).
  3. If a SWIFT message has errors then it is not valid and the message is not routed. An "Invalid Message" warning appears on the screen.
    Click OK to acknowledge any warnings.
  4. Correct any fields that are in error. All fields in error are identified in the error field colour. The cursor is automatically placed at the first error. In prompted mode, you can use these keys to move to fields that contain errors:
    • Ctrl + E moves the cursor to the next field which is in error
    • Ctrl + Shift + E moves the cursor back to the previous field which is in error.
    Remember that you can change between fast and prompted mode.
  5. Try to route the message again.
  6. If you cannot correct the errors in a message, or the message is incomplete, then take one of the following steps:
    • Select Move to Text Modification from the Message menu to move the message to the Text Modification queue for later editing.
    • Cancel the message.
Note
When a message is moved out of the creation queue, it is added to the Message File.
If you broadcast an MT 999 message to an alias for a group of correspondents, then Alliance Access creates a message for each correspondent. It also creates a copy of the message in the Message Creation queue, using XXXXXXXX as the BIC, and 999 as the branch. You can use the Message File application to inspect message instances. 

No comments:

Post a Comment