Integrating FinCopy and External Messages
This section describes the setup and integration of messages for transactions not present in the Calypso system:
| • | Messages received from FinCopy service: Integration of MT096 messages. |
| • | Integration of messages from another system that need to be matched to the MT096 messages. |
These messages have the subtype OUTGOINGEXTERNAL.
1. Setup Requirements
1.1 Domain Values
Add OutgoingExternalConfirm to domain workflowRuleMessage.
The OutgoingExternalConfirm message rule is similar to the IncomingConfirm message rule for OUTGOINGEXTERNAL messages. It applies the action set in the domain "OutgoingExternal.Action.Type Of Operation" when we receive a AMND/CANC/COPY message which is not out of sequence.
Add the following values to the domain "MsgAttributes":
Value = PORef
Value = IsFinCopy
Value = Subtype
Domain "messageType":
Value = OutgoingExternalConf
Add the following values to the domain "OutgoingExternal.Action.Type Of Operation":
Value = AMEND, Comment = CNTP_REPLACE
Value = CANCEL, Comment = CNTP_REPLACE
Value = COPY, Comment = CNTP_REPLACE
Add the following values to the domain "outgoingExternalType":
Value = MT300, Comment = OutgoingExternalConf
Value = MT305, Comment = OutgoingExternalConf
Value = MT306, Comment = OutgoingExternalConf
Value = MT320, Comment = OutgoingExternalConf
Value = MT330, Comment = OutgoingExternalConf
Value = MT340, Comment = OutgoingExternalConf
Value = MT341, Comment = OutgoingExternalConf
Value = MT360, Comment = OutgoingExternalConf
Value = MT361, Comment = OutgoingExternalConf
Value = MT362, Comment = OutgoingExternalConf
Value = MT392, Comment = OutgoingExternalConf
Value = MT395, Comment = OutgoingExternalConf
Value = MT396, Comment = OutgoingExternalConf
Value = MT399, Comment = OutgoingExternalConf
Value = MT600, Comment = OutgoingExternalConf
Value = MT601, Comment = OutgoingExternalConf
Value = MT692, Comment = OutgoingExternalConf
Value = MT699, Comment = OutgoingExternalConf
All outgoing external MT types are mapped to the same message type OutgoingExternalConf for which we define a global workflow.
1.2 Message Workflow for OutgoingExternalConf
On the transition PENDING - REMOVE - DISCARDED, the filter is:
On the transition PENDING - PROCESS - ACKED_UNMATCHED, add the rules OutgoingExternalConfirm, CheckIncomingFormat, SetChasing (if you want to use automatic chasing), and CheckIncomingProcess to set the message attribute Process Issue for any processing issue.
2. Integration
Outgoing External Confirmations follow the same integration logic as Incoming Confirmations in terms of AMND/CANC/DUPL logic, check on Duplicate and out of sequence messages.
Outgoing External Confirmations which represent PO confirmations follow the same matching process as a confirmation triggered by a Calypso transaction.
Outgoing External Confirmations are tagged with specific attributes as shown in the Message Report extract below to identify them into the system for audit purposes: Is External, SubType, IsFinCopy.
For FinCopy integration of MT096, we support both MT096 copy of PO confirmation, and MT096 copy of Counterparty confirmation.
| • | MT096, copy of PO’s confirmation: Message Type= OutgoingExternalConf, Is External=true, Subtype= OUTGOINGEXTERNAL, isFinCopy=true |
| • | MT096, copy of Counterparty’s confirmation: Message Type= IncomingConfirmation, Is External=true, Subtype=NONE, isFinCopy=true |
How are we doing?