3. Maintaining Messaging Branch Preferences
The messaging preferences that you indicate for your branch will govern the workflow aspects of the messaging system module. You can specify messaging preferences for your branch in the ‘Messaging Branch Preferences’ screen. In this screen you can indicate:
l The number of days for which outgoing messages should be kept in the browser
l Whether a test word is required for telex messages
l The activities on a message that require authorization
l The PDE Functional Validation / archive period
l The Text for hold mail and duplicate check
Note
You can specify preferences only for the branch from which you logged onto Oracle FLEXCUBE.
This chapter contains the following sections:
l Section 3.1, "Messaging Branch Parameters Maintenance"
l Section 3.2, "Message Type Maintenance"
l Section 3.3, "Swift Tag Maintenance"
l Section 3.4, "PDE Validations on SWIFT Messages"
l Section 3.4, "PDE Validations on SWIFT Messages"
3.1 Messaging Branch Parameters Maintenance
This section contains the following topic:
l Section 3.1.1, "Invoking Messaging Branch Parameters Maintenance screen"
3.1.1 Invoking Messaging Branch Parameters Maintenance screen
To invoke the ‘Treasury Messaging Branch Parameters Maintenance’ screen, type ’MSDTRPRF’ in the field at the top right corner of the Application tool bar and click the adjoining arrow button.
If you are maintaining preferences for a new branch of your bank, click the ‘New’ button on the Application toolbar. The ‘Messaging Branch Parameters Maintenance’ screen is displayed without any details.
If you are calling a branch preference record that has already been defined, double-click a record of your choice from the summary screen. In the ‘Summary’ screen, all the branch preference records that you have entered will be displayed in a tabular form.
The screen is shown below:
In the ‘Treasury Messaging Branch Parameters Maintenance’ screen you can only maintain (create or modify) the preferences for the current logged in branch. However, you can view the preferences maintained for other branches.
Following are the details captured here:
Branch
Specify the branch for which you are maintaining the preferences.
Message Archive Period
Archival is the process of storing old messages for future retrieval. You can 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 you specify. You can un-archive the details of outgoing message that has been archived by invoking the ‘Message History Retrieval’ screen. After you un-archive an outgoing message you can process it just as you would any other outgoing message.
Note
It is recommended that you indicate a value of ‘one’ in this field. In this case, only those messages that have been triggered for 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. 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 you have 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
You can indicate whether a testword needs to be entered before a telex message is generated from and received at your branch. You can state your preference from the Yes/No option that is available.
PDE Functional Validation
Check this box to indicate that system should identify an outgoing message as PDE (Possible Duplicate Emission) using 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 identifies duplicate messages by performing PDE functional validations also. Hash value based validation shall be done irrespective of this option being checked.
Indicating the activities that require authorization
You can perform several activities on a message that is to be generated from your branch and on those that have come in for your branch. For example, from the outgoing or incoming browser, you can change the address to which a message should be sent.
In the branch preferences screen, you can indicate the activities which when performed on an incoming or outgoing message, would require subsequent manual authorization for the message. Several activities have been listed in this screen. A message, on which an activity which has been selected in this screen is performed, would require subsequent manual authorization for the activity to take effect. A message, on which an activity not selected in this screen is performed, would be automatically authorized with the activity taking effect.
The activities that you can choose from are:
l Cancel
l Hold
l Change Node
l Testword
l Auth Repair Incoming
l Carry Forward
l Change Media
l Regenerate
l Change Address
l Reinstate
l Release
l Carry Forward
l Branch Move
l Change Media
l Change Priority
l Testword Check
l Auth Repair Incoming
A message on which you perform an activity that requires authorization will be available for further processing only after it is authorized.
SK Arrangement
You can choose the action to be performed on the message based on the Swift Key arrangement with the receiver. The options available for choosing are:
l Validate – If you choose this option, the system validates if a SK arrangement exists between your bank and the receiver. If Yes, then the original SWIFT message is generated otherwise, the message will go to repair.
l Generate FFT- If you choose this option, the system validates if a SK arrangement exists between your 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.
l No Validation- If you choose this option, you are instructing the system not to Validate but send the original SWIFT message always.
Processing SWIFT Messages if SK arrangement is ‘Validate’ in the static messaging table:
l Oracle FLEXCUBE checks for the value in the branch’s SK arrangement Field
l If the field value is ‘No validate’, Oracle FLEXCUBE will generate messages the normal way.
l If the SWIFT keys have been exchanged then the swift message will be generated
l 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 Tracker
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.
l Message header is changed from the original header to MT999
l That portion of the message after tag 21 will be prefixed with tag 79 followed by the original SWIFT message
l The message will be populated with the same contents as the original SWIFT message with the respective SWIFT tags
– The system will generate MT999 even if the SWIFT Key Arrangement does not exist with the receiver.
Saving the record
After you have made the mandatory entries, save the record. This record should be authorized before the End of Day process (EOD) is run.
Click ‘Exit’ or ‘Cancel’ button to return to the Application Browser.
This section contains the following topic:
l Section 3.2.1, "Maintaining Message Types"
3.2.1 Maintaining Message Types
You can maintain message types in Oracle FLEXCUBE through the ‘Treasury Message Type Maintenance’ screen. To invoke ‘Message Type Maintenance’ screen, type ’MSDTRMTM’ in the field at the top right corner of the Application tool bar and click the adjoining arrow button.
You will need to capture the following information in this screen:
Module
Specify the module for which you are maintaining message types. The adjoining option list displays all module codes available in Oracle FLEXCUBE. You can select the appropriate one.
Message Type
Specify the message type for which SWIFT codes can be maintained.
Description
Enter a brief description of the message type.
Priority
Specify the priority in which a message is to be sent is displayed. You have the option to change the priority. To change the priority specified for a message, click the button marked ‘Change Priority’. Thereafter, select an option from the option-list that is available for this field.
SWIFT Message Type
Indicate the SWIFT message type in which the free format message should expressed. For the following message types in BC module, you need to indicate the SWIFT message type as MT999:
l DISCREPANCY_REQ
l ACCEPT_REFUSAL
l DISCREPANCY_AUT
Maximum Message count
Maximum number of message send to the message types
Purge Message
Purging of message allowed based on the selection.
Acknowledgement Nak Processing
Acknowledgement Nak processing allowed based on the selection.
Generate at input
Check this box to indicate that this message is to be generated at the time of input of the contract, and not after authorization.
Show in product
Check this box to indicate that this message will be available in the product to be maintained against a particular event.
3.2.1.1 Viewing Message/Advice
Select a message/ advice and click ‘View’ button to view the complete message/advice. The system will display the following details in a new window..
You can view the following details:
l Reference number of the message/advice
l Document number generated for the message/advice
l Version number of the message/advice
l Receiver/sender of the message
l Type of the message
l Type of the SWIFT message
l Complete text of the message/advice
l Remarks, if any
l Reject reason, if any
l Message trailer
This section contains the following topic:
l Section 3.3.1, "Querying for SWIFT Message Tag Description"
3.3.1 Querying for SWIFT Message Tag Description
You can query for tag descriptions for SWIFT messages using the screen ‘Treasury Swift Tag Maintenance’ screen. You can invoke the screen by typing ’MSDTRSWT' in the field at the top right corner of the Application tool bar and click the adjoining arrow button.
The screen is as shown below:
Specify the following fields:
Swift Tag Maintenance
Swift Message/Sub Message Type
Specify the swift message/sub message type. The adjoining list displays a list of message types maintained in the system. Choose the appropriate one.
Description
The system displays the message description.
Envelope Message Type
The system displays envelope message type based on the message/sub-message type selected.
Tag Description
Tag Name
The system displays the tag name.
Description
The system displays the description.
Tag Option
Displays whether the tag is optional (O) or mandatory (M).
Lines
The system displays the number of lines required for the tag.
Sequence
The system displays the tag sequence number.
Repeatable
Indicates whether the tag is repeatable or not.
All Options
Indicates all options.
Sequence Name
Specify the sequence number.
Note
Swift message tag descriptions are factory shipped. However, it can also be maintained using this screen.
3.4 PDE Validations on SWIFT Messages
This section contains the following topics:
l Section 3.4.1, "Processing PDE Messages"
The system detects the messages (Incoming/Outgoing) as PDE messages by performing the validations discussed in the above section. The Incoming and Outgoing PDE messages are processed by the system in the following manner:
3.4.1.1 Incoming PDE Messages
In the case of incoming messages, EMS picks up the incoming messages and inserts it into a data store. If the incoming message has a PDE trailer (message contains the text ‘PDE:’} then the system will mark the process status as ‘Stopped due to PDE’. After due validations, you can release the message from the incoming PDE message queue. Once these messages are accepted it will continue to get uploaded as a normal message. If the PDE trailer is NOT present in the incoming message, then the message upload will continue as normal.
In the case of incoming messages with a PDE trailer, the ‘PDE Flag’ check box in the ‘Incoming Message Browser’ screen will be checked.
For more details on the PDE indication of an incoming message in the Incoming Message Browser, refer section ‘Viewing the details of an Incoming Message’ in ‘Processing Incoming Messages’ chapter of this User Manual.
3.4.1.2 Outgoing PDE Messages
In the case of outgoing messages you can decide to do any of the following if the system detects a message as a duplicate, based on the PDE validations:
l Auto release the message with the PDE trailer
l Release the message without the PDE trailer
l Reject the message
System displays an override when it finds a message to be a duplicate one. In this case the message is parked in the PDE queue and you can either opt to release the message without the PDE trailer or else release it with the PDE trailer. If you opt to release the message with the PDE trailer then the message is appended with PDE, else the message is released without PDE. You can also choose to reject the message. In this case the message status will be changed to ‘E’ (Exception) and this will not be picked up by EMS (Electronic Messaging System).
Due to message size restrictions in Oracle FLEXCUBE, sometimes a single message is physically split into multiple parts and each one is stored in a distinct record in the outgoing message data store. A message is marked as ‘PDE’ if ALL the split messages are found to be duplicates.
Note
All the messages in the PDE queue (Incoming and Outgoing) are completely processed by EMS prior to initiating EOD operations.
For more details on outgoing messages in PDE queue refer section ‘Processing Outgoing Messages with PDE Trailer’ in ‘Processing Outgoing Messages’ chapter of this User Manual.