This activity is used to connect one or several matching identifiers to a message code in external payment parameters. This can be defined for a specific payment method and applies for payment transactions created from an external file which is imported with this payment method.
This activity is relevant only for payment methods which are linked to a payment format with a file template that is used to identify the type for payment depending on the message code. Furthermore, this set up is considered only for payment transactions which are created from payment formats for which identifiers are used to search for information in IFS/Financials (invoices, issued checks or pseudo codes) and to match the payment with the information found.
By selecting the identifier for a message code, you restrict the identifiers to be used for the matching of the payment transaction, provided that the payment transaction is created with a message code. If you do not select an identifier for a message code, the payment transactions of this message code will not be matched. After the identifiers have been connected, you need to enable this matching setup in the general matching parameters in order to use identifiers per message code, instead of using all identifiers defined for the payment method. Note: The additional identifier search string of the connected identifier, is also considered if an identifier should be used for the matching.
To connect an identifier to a message code:
In order to perform this activity,
As a result of this activity, the identifiers that are connected to the message code will be used when the payment is matched in the external interface for payments.