Maintain Messaging Branch Parameters

On Homescreen screen, type MSDTRPREF in the text box, and click next.

Treasury Messaging Branch Parameters Maintenance screen displays.

Figure 2-1 Treasury Messaging Branch Parameters Maintenance

Description of "Figure 2-1 Treasury Messaging Branch Parameters Maintenance"

To maintain preferences for a new branch, click the New button on the application toolbar.

On Treasury Messaging Branch Parameters Maintenance screen, specify the details.

Table 2-1 Treasury Messaging Branch Parameters Maintenance - Field Description

Field	Description
Branch	Specify the branch for which the preferences are to be maintained.
Message Archive Period	Archival is the process of storing old messages for future retrieval. Specify the number of days for which an outgoing message should be kept in the Outgoing Message Browser. A message will be automatically archived after the number of days that are specified. The details of outgoing message that has been archived can be un-archive through the Message History Retrieval Summary screen. Then these un-archive messages can be processed as any other outgoing message. Note:It is recommended to enter a value of 1 in this field. In this case, only those messages that have been triggered for the generation today will be displayed in the Outgoing Message Browser.
PDE Archive Period	Specify the number of days for which messages should be kept in the queue for PDE Possible Duplicate Emission) identification. The system does not consider messages for PDE identification post the PDE archive period maintained here. Note: The PDE archive period should be less than or equal to message archival days.
Text for Duplicate	Every message is maintained in the Outgoing Browser as an un-generated copy of the original. When the copy is generated, it will contain along with the contents of the original message, any additional text that is maintained in the Text for Duplicate field.
Hold Mail Text	All the mail advices generated for a customer for whom Add Hold Mail Text is checked at the Customer Address Maintenance would have the hold mail text maintained in this field. This text will be displayed on top of the message.
Test Word check	Specify whether a testword needs to be entered before a telex message is generated from and received at the branch from the following options. Yes No
PDE Functional Validation	Check this box to indicate that system should identify an outgoing message as PDE (Possible Duplicate Emission) using the functional key or not. The PDE validation is done either using the hash value of the SWIFT message or using the tag/field value of the message. If this option is checked, Oracle FLEXCUBE Universal Banking identifies duplicate messages by performing PDE functional validations also. Hash value-based validation shall be done irrespective of this option being checked.
SK Arrangement	Select the action to be performed on the message based on the Swift Key arrangement with the receiver from the following options: Validate: On selecting this option, the system validates if an SK arrangement exists between the bank and the receiver. If yes, then the original SWIFT message is generated otherwise, the message will go to repair Generate: On selecting this option, the system validates if an SK arrangement exists between the bank and the receiver. If yes, then the original SWIFT message is generated otherwise, MT 999 (Free Format Messages) will be generated instead of the SWIFT message. FFT No Validation: On selecting this option, the system does not Validate but send the original SWIFT message always. Processing SWIFT Messages if an SK arrangement is Validate in the static messaging table: This system checks for the value in the branch’s SK Arrangement field. If the field value is No Validate, the system will generate messages the normal way. If the SWIFT keys have been exchanged then the swift message will be generated. If SWIFT keys have not been exchanged with the receiver and the value of SK Arrangement for the branch is Validate then the following messages will go to repair: MT420, MT754 and MT756. For all other messages, the original SWIFT message gets generated whether swift key exists or not. If SWIFT keys have not been exchanged with the receiver and the value of SK Arrangement for the branch is Generate FFT then the message MT999 would be generated instead of original SWIFT message.
Duplicate Advice Tracking	Check this box to track the duplicate advices. When an advice is duplicated or regenerated, the word Reprint appears over the advice. Generation of MT999: The message header is changed from the original header to MT999. That portion of the message after tag 21 will be prefixed with tag 79 followed by the original SWIFT message. The message will be populated with the same contents as the original SWIFT message with the respective SWIFT tags.
Authorization	Several activities can be performed on a message that is to be generated from the branch. For example, From the outgoing or incoming browser, The address to which a message should be sent can be changed. In the Messaging Branch Parameters Maintenance screen, specify the activities which are to be performed on an incoming or outgoing message and would require a subsequent manual authorization for the message. A message on which activity to be performed would require subsequent manual authorization for the activity to take effect. A message on which an activity not selected on this screen is performed, would be automatically authorized with the activity taking effect. Activities: Cancel Hold Change NodeTest Word Auth Repair Incoming Carry Forward Change Media Regenerate Change Address Reinstate Release Branch Move Test Word Check Change Priority

After entering the mandatory entries, save the record.

This record should be authorized before the End of Day process (EOD) is run.

Click the Exit button to end the transaction.