8.4 Example for MM Confirmation Rule Maintenance

This topic describes about example for MM confirmation rule maintenance.

Let us assume that you have maintained a set of 4 confirmation rules for the MM module. The Characteristics of each of these rules are as follows:

Table 8-6 Characteristics table

Rules	Description
RULE_01	This is a full match type of a rule where you have indicated that the system should process the contract if the values in the MM contract match with the following details of an uploaded message: Counterparty Booking date Principal Amount Event Value Date Maturity Date Currency Interest Amount Currency Settlement for Receive Leg Product Type
RULE_02	Full Match – wherein you would like to have a corresponding match for the following field values: Counterparty Event Value Date Maturity Date Currency Principal Amount Notice Period Product Type
RULE_03	Partial Match, wherein you would like to have a corresponding match for the following fields: Currency Product Type Interest Amount Interest Amount Currency Principal Amount Counterparty
RULE_04	Partial Match – you would like to have a corresponding match for: Counterparty Value Date Maturity Date Currency Principal Amount

As a result, each time MM messages are uploaded into FLEXCUBE, the system tries to match the data available in the messages with existing MM contracts as per the sequence in which the rules have been maintained.

If the system is unsuccessful in finding a match, the message is marked with the status ‘Unmatched’. Such messages can be viewed from the Manual Matching screen where user will also be allowed to perform a manual matching of messages with existing contracts