User Tools
Add this page to your book 
Remove this page from your book 
Manage book (
Help Table of Contents
Common Messages
Transaction MCTFRE
This transaction is used to send common messages to the contract party/contract parties or to another address, which can be entered freely.
On the transaction panel the user needs to define the message type, the receiver of the message, and, if necessary, the receiver of copies.
Example: A bank erroneously receives an incorrect addressed SWIFT message from another bank. This bank can be informed of the misdirected message by sending a common message directly via this function.
At first, and as a basis for sending common messages, a “Manual Contract” has to be created. This manual contract is created using the transaction “Opening a Manual Contract” (MCTOPN). The contracts opened here serve as point of reference for common messages. The manual contracts enable the usage of all standard functions of the application in free format messages. It is also possible, for example, to implement the release workflow into the free format messages.
- This transaction is used to create confirmations of balances across multiple contracts. In doing so, the transaction takes into account all open liabilities across all business sectors available for the addressee entered. Normally, confirmations of balances are automatically created in the background. The transaction processes SPTs that were previously created by the “Creating SPTs” (MCBSPT) transaction.
- This transaction is also used to send “Payment Reminder” correspondence out to the Buyer for all the invoices that are not yet paid and is overdue. An attachment is generated with the list of past due invoices and its details such as open amount, supplier etc., and is sent to the Buyer. This is in relation to the business sector Receivable Finance.
Detailed information about common messages can be found under “Common Messages”.
Requirements
An existing Manual Contract which is not closed.
For incoming allNETT / RIVO messages see Overview of Incoming messages - allNETT / RIVO.
Transaction Control
Fees
None
Commissions
Results of this Transaction
Diaries
For more information see TRNDIA Diaries.
| Action | Description | Diary | Follow-up Transaction | Comment |
|---|---|---|---|---|
| Create | Reply to Query pending | Today + 5 Working Days | Common Messages | if “Message Type”='Request for Cancellation' or 'Query' |
Updating/Storing of Amounts (CBS)
Liability (LIA)
Outgoing Correspondence
Details on creation of messages can be found under DOCEOT Messages. For outgoing allNETT / RIVO messages see Overview of Outgoing messages - allNETT / RIVO.
The respective Common Messages will be created.
| Name of Message | Receiver | Message ID | SWIFT | TCO | DTA/DTE | Comment |
|---|---|---|---|---|---|---|
| Balance Confirmation | Adressee | MCTSAB1 | ||||
| Attachment Balance Confirmation | Adressee | MCTSAB2 |
Release
Signature required
Transaction Panels
Common Message
Settlement Details
Settlement
Bookings
Message Details
Camt.029 Answer Cancel.Request
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Free Format Message Details
Message Details MT741
DTAG Fields
Fee Conditions
Camt.056 Cancellation Request
Common Message
Datafields
| Datafield | Description |
|---|---|
| Own Reference | cf Appendix A, Table MCD field OWNREF |
| Name | cf Appendix A, Table MCD field NAM |
| Responsible User | cf Appendix A, Table MCD field OWNUSR |
| Opening Date | cf Appendix A, Table MCD field OPNDAT |
| Flag for Balance Statement | cf Appendix A, Table MCD field SALFLG |
| Flag for periodic settlement | cf Appendix A, Table MCD field STKGEBFLG |
| Address Block | cf Appendix A, Table PTS field ADRBLK |
| Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
| message to be created | This field selects the type of message to be created |
| Message Type to send | The type of message to be sent can be selected using this combobox. |
| Related Message Type | This field contains the message type of the incoming SWIFT message that has been received and may be refererred to in the outgoing message that is to be generated in this transaction. For example, if a SWIFT MT n96 (Answer) is generated, the field 'Related MT' can contain the message type of the incoming Query (e.g. MT795/ 495) that was received from the correspondent. In this example, the tag 11R of the outgoing SWIFT MT n96 contains the message type that the current message refers to, e.g. a MT 795. |
| from | This field contains the date of the related SWIFT message. |
| relevant message sent/received | This field allows the user to choose whether the related SWIFT message was RECEIVED or SENT. |
| Text of Common Message | Free text for the common message is to be entered in this field . |
| Role Message | This field selects the recipient of the message. |
| External Key | cf Appendix A, Table PTS field EXTKEY |
| Address Block | cf Appendix A, Table PTS field ADRBLK |
| Role Copy | This field selects the recipients of a cc copy of the message. |
| External Key | cf Appendix A, Table PTS field EXTKEY |
| Address Block | cf Appendix A, Table PTS field ADRBLK |
| Send Message Immediately | If this box is checked, the message in sent immediately - independent of the sequence of data captured. |
Message Details
Camt.029 Answer Cancel.Request
Datafields
Compliance
Free Format Message Details
Datafields
| Datafield | Description |
|---|---|
| External Key | cf Appendix A, Table PTS field EXTKEY |
| Address Block | cf Appendix A, Table PTS field ADRBLK |
Message Details MT741
DTAG Fields
Camt.056 Cancellation Request
