Saturday, February 4, 2017

List of Exit Queues

AI_to_APPLI

All exit queues, except _SI_to_SWIFT and _SI_to_SWIFTNet are processed by a single Message Processing Function, identified as AI_to_APPLI. The processing results returned by this MPF are the same for all exit queues and are therefore described only once in this section. The two possible processing results are:
  • Success: The message has been delivered successfully to the message partner.
    By default, a message producing this processing result is completed.
  • Failure: The MPF is unable to reconstruct the message correctly. Such a problem may occur, for example, when the version number of the Message Syntax Table assigned to the LT through which a SWIFT message was received (and accepted because minimum validation was applied) is incorrect.
    By default, a message producing this processing result is routed to the follow-up queue (ToBeInvestigated).

BatchMXAcks

This is the queue of ACK notifications related to outgoing MX messages created by message partners and entered into Alliance Entry through the Application Interface. The AI input session uses the File Transfer connection method.
These notifications are created at the SWIFTNet outbound routing point and routed to this exit queue when the message is ACK'd. The reception of a positive acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFTNet) to return a processing result equal to "Success".

BatchSwiftAcks (Batch Ack Queue)

This is the queue of SWIFT ACK notifications related to outgoing messages created by message partners and entered into Alliance Entry through the Application Interface. The AI input session uses the File Transfer connection method, for example, batch transfer of messages using a DOS file.
These notifications are created at the SWIFT outbound routing point and routed to this exit queue when the message is ACK'd by APC/FIN. The reception of a positive acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFT) to return a processing result equal to "Success".

DeliveryNotifAcks

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • DeliveryNotifAcks. MT 011 notifications.
The MPF at this routing point is AI_to_APPLI.
From this exit point, you can send delivery notification instances to a message partner with Connection Method Print or to a message partner with Data Format CAS2 or XML version 2.
For more information about the configuration parameter that affects this queue, see Traffic Recon .
Note
As of Alliance Entry release 7.1.10, the Responder DN field is included in the delivery notification, allowing you to route a delivery notification instance based on the Responder DN.

DeliveryNotifNaks

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • DeliveryNotifNaks. MT 010, MT 015, and MT 019 notifications.
The MPF at this routing point is AI_to_APPLI.
From this exit point, you can send delivery notification instances to a message partner with Connection Method Print or to a message partner with Data Format CAS2 or XML version 2.
For more information about the configuration parameter that affects this queue, see Traffic Recon .
Note
As of Alliance Entry release 7.1.10, the Responder DN field is included in the delivery notification, allowing you to route a delivery notification instance based on the Responder DN.

FileActAcks

This is the queue of ACK notifications related to outgoing FileAct messages created by message partners and entered into Alliance Entry through the Application Interface. The AI input session uses the File Transfer connection method.
These notifications are created at the SWIFTNet outbound routing point and routed to this exit queue when the message is ACK'd. The reception of a positive acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFTNet) to return a processing result equal to "Success".

FileAct_***

This is the exit queue to which all incoming FileAct messages received from SWIFTNet are routed with success from the SWIFTNet inbound routing point.

FileActReject

This is the queue of NAK notifications related to outgoing FileAct messages created by message partners and entered into Alliance Entry through the Application Interface. The AI input session uses the File Transfer connection method.
These notifications are created at the SWIFT outbound routing point and routed to this exit queue when the message is NAK'd. The reception of a negative acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFTNet) to return a processing result equal to "Failure".

FileDeliveryNotifAck

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • FileDeliveryNotifAck. Positive FileAct delivery notifications.
The MPF at this routing point is AI_to_APPLI. From this exit point, you can send the delivery notification instances to a message partner with connection method printer or File Transfer XML.

FileDeliveryNotifNak

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • FileDeliveryNotifNak. Negative FileAct delivery notifications.
The MPF at this routing point is AI_to_APPLI. From this exit point, you can send the delivery notification instances to a message partner with connection method printer or File Transfer XML.

LocalMXAcks

This is the queue of ACK notifications related to outgoing MX messages generated by Alliance Entry or outgoing MX user-to-user messages created manually through Message Management (available on Alliance Web Platform).
The notifications are created at the SWIFTNet outbound routing point and routed to this exit queue when the message is ACK'd. The reception of a positive acknowledgement causes the MPF associated with the SWIFTNet outbound queue (_SI_to_SWIFTNet) to return a processing result equal to "Success".

LocalMXRejects

This is the queue of NAK notifications related to outgoing MX messages generated by Alliance Entry or outgoing MX user-to-user messages created manually through Message Management (available on Alliance Web Platform).
The notifications are created at the SWIFTNet outbound routing point and routed to this exit queue when the message is NAK'd. The reception of a negative acknowledgement causes the MPF associated with the SWIFTNet outbound queue (_SI_to_SWIFTNet) to return a processing result equal to "Failure".

LocalSwiftAcks (Local Ack Queue)

This is the queue of SWIFT ACK notifications related to outgoing messages generated by Alliance Entry or outgoing FIN user-to-user messages created manually through the Message Preparation component of Alliance Entry. The messages are:
  • MT 047: Delivery Instructions Redefinition Request
  • MT 090: User-to-SWIFT message
  • MT 0nn: All system messages
  • MT 101 through MT 999: FIN messages created manually through the Message Preparation component.
The notifications are created at the SWIFT outbound routing point and routed to this exit queue when the message is ACK'd by APC/FIN. The reception of a positive acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFT) to return a processing result equal to "Success".

LocalSwiftNaks (Local Nack Queue)

This is the queue of SWIFT NAK notifications related to outgoing messages generated by Alliance Entry or outgoing FIN user-to-user messages created manually through the Message Preparation component of Alliance Entry. These messages are described above.
The notifications are created at the SWIFT outbound routing point and routed to this exit queue when the message is NAK'd by APC/FIN. The reception of a negative acknowledgement causes the MPF associated with the SWIFT outbound queue (_SI_to_SWIFT) to return a processing result equal to "NAK'd".

MXDeliveryNotifAcks

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • MXDeliveryNotifAcks. MX notifications.
The MPF at this routing point is _AI_to_APPLI. From this exit point, you can send the delivery notification instances to a message partner with connection method printer or File Transfer XML.

MXDeliveryNotifNaks

The following traffic reconciliation notification instances are routed from the _TR_NOTIF routing point to this queue:
  • MXDeliveryNotifNaks. MX notifications.
The MPF at this routing point is _AI_to_APPLI. From this exit point, you can send the delivery notification instances to a message partner with connection method printer or File Transfer XML.

MX_***

This is the exit queue to which all incoming MX messages received from SWIFTNet are routed with success from the SWIFTNet inbound routing point.

MXSystem

This is the exit queue to which all incoming MX delivery notifications received from SWIFTNet are routed from the SWIFTNet inbound routing point. A copy is sent to _TR_REC for matching the notification with the original message instance.

MXToBeInvestigated (follow-up queue)

This is the default target queue specified for MX messages failing to match any of the conditional routing criteria specified in the sequence of routing rules at a routing point.

MT_*** (Message Inbound Queue)

All incoming messages received from APC/FIN are routed to this exit queue from the SWIFT inbound routing point, except:
  • system messages (MT 0nn)
  • statement messages (MT 940, MT 950, MT 970, and MT 996)

_SI_to_SWIFT (SWIFT Outbound Queue)

This is the queue of SWIFT messages ready to be sent to the SWIFT network. It is sometimes referred to as the SWIFT "ready" queue. The queue contains, most of the time, messages created at several processing points in the system:
  • FIN messages in CAS format received from the Application Interface when the disposition state requested by the CAS protocol specifies "Ready" or when routing point _SI_to_SWIFT is requested.
  • FIN messages received from the Application Interface, if the message partner has the permissions to bypass verification and authorisation.
  • FIN messages entered into the system by the Application Interface and routed from the AI inbound queue by internal default routing.
  • APC and FIN System Messages created using the Message Creation application.
  • MT 047 message created by the Redefine Delivery command available in the SWIFT Interface application. The message is routed from the system outbound queue (_SI_system_msg) as well.
  • Messages created using the Message Creation application. In general, these messages are routed to the SWIFT outbound queue from the authorisation queue (MP_authorisation).
    However, when the operator has the proper bypass permissions, messages may also be moved directly to the SWIFT outbound queue from any of the other queues involved in the preparation of messages, for example:
    • Message creation queue (MP_creation)
    • Verification queue (MP_ verification)
    • Modification queues (MP_mod_emi_secu, MP_mod_text, MP_mod_transmis).
Acceptance criteria: Message instance must be an original input SWIFT message.
Assigned MPF: _SI_to_SWIFT
With the default routing rules, the processing results returned by this MPF are:
  • Success: The outgoing message was positively acknowledged by APC/FIN.
    By default, a message producing this processing result is completed and a notification is routed to one of the four ACK queues.
  • Nacked: The outgoing message was negatively acknowledged by APC/FIN.
    By default, a message producing this processing result is completed and a notification is routed to one of the four NAK queues.
    When created using the Message Creation application, the message is routed to the modification queue (MP_mod_text) instead.
  • Inactive correspondent: By default, a message producing this processing result is routed to the _MP_mod_transmis queue.
Other processing results which can be returned by this MPF are:
  • Authorisation not present: No authorisation record was found. By default, an outgoing message producing this processing result is routed to the re-authentication queue (_MP_mod_emi_secu).
  • Not authorised by RMA: A valid enabled authorisation was found, but the message was not permitted. By default, an outgoing message producing this processing result is routed to the re-authentication queue (_MP_mod_emi_secu).
  • Failure: The processing of the outgoing message fails. By default, an outgoing message producing this processing result is routed to the follow-up queue (ToBeInvestigated).
An outgoing message whose processing fails for one of the reasons mentioned above is routed by default to the follow-up queue (ToBeInvestigated).
Note
FIN messages are sent in FIFO order with respect to the priority and position in the queue.

_SI_to_SWIFTNet (SWIFTNet Emission Queue)

This is the queue which provides a collection point for InterAct or FileAct messages ready for emission.
Acceptance criteria: Message instance must be a normal original input MX message.
Assigned MPF: _SI_to_SWIFTNet
With the default routing rules, the processing results returned by this MPF are:
  • "Success": The outgoing message was positively acknowledged.
    By default, a message producing this processing result is completed and a notification is routed to the MX delivery ACK queues.
  • "Nacked": The outgoing message was negatively acknowledged.
    By default, a message producing this processing result is completed and a notification is routed to the MX delivery NAK queues.
An outgoing message whose processing fails for one of the reasons mentioned above is routed by default to the follow-up queue (MXToBeInvestigated).
Note
Real-time messages are sent according to the message expiry date time. Store-and-forward messages are sent in FIFO order with respect to the priority and position in the queue.

Statement (Statement Queue)

Incoming statement messages are routed to this exit queue from the SWIFT inbound routing point. The messages are:
  • MT 940: Customer Statement Message
  • MT 950: Statement Message
  • MT 970: Netting Statement
  • MT 996: Answer to an MT 995 Query

System (System Inbound Queue)

All incoming system messages are routed to this exit queue from the SWIFT inbound routing point except:
  • MT 021: FIN Retrieval
However, a copy of each MT 021 FIN retrieval message is routed to the system inbound queue as well (System).

ToBeInvestigated (Follow-up Queue)

This is the default target queue specified for MT messages failing to match any of the conditional routing criteria specified in the sequence of routing rules at a routing point.
The follow-up queue is also invoked when MPFs fail to process messages which are insufficiently validated or improperly routed.

No comments:

Post a Comment