Various Parameters
are used here to control when and with which product and transaction types
correspondence can be carried out. The settings that you make here are also
relevant for controlling SWIFT confirmations and IDocs.
Several correspondence types can be defined for identical parameter specifications. For example, in the case of a new fixed-term deposit, alongside a dealing slip, a confirmation letter can be seen as correspondence. Note that for identical parameter specifications, many internal user-defined correspondence types may be defined but only one external correspondence type. The external correspondence type is critical for the confirmation status of the transaction. In general, each activity/status (contract, contract settlement) of a transaction can be confirmed.
Alongside the form, you can also specify here whether the correspondence should be carried out automatically - for example, when the transaction changes over from the activity type, contract to settlement, or when a transaction is reversed. For SWIFT confirmations, there is no automatic correspondence function.
The "Counterconfirmation required" field controls whether a counterconfirmation should take place for the business partner. Additionally, the "Counterconfirmation" field must be set for the business partner-dependant standing instructions - provided that you carry out a confirmation match with the corresponding business partner.
You can also branch from here to the Form Editor to display the form data and/or change it.
There is no logging via a log form with automatic correspondence, only an entry in the financial transaction. In the menu, you find this via Goto -> Correspondence.
Check your entries after saving via the Check function.
You will find further information on SAPscript forms in TR Confirmations in the SAP Library via Back office -> Correspondence -> Outgoing correspondence.