This topic provides systematic instructions to perform an incoming message.

1. On Trade Finance Incoming Message Browser Summary screen, specify the following action:
   For more information on action and its operation, refer to Table 9-1:

   Table 9-1 Trade Finance Incoming Message Browser Summary - Action and Operation

   Action	Operation
   View Delete	Viewing and deleting the contents of a message: To view the contents of an incoming message Highlight the message you want to view and Click the ‘View Message’ button on the Browser The contents of the message will be displayed in a separate screen.
   Print	Printing a Message You can choose to print the details of an incoming message. To print the details of an incoming message, Highlight the message you want to print and Click the ‘Print button’ on the Browser. When you select the print option, you will be prompted to indicate whether you want to spool or directly print the message. You can also view the SWIFT tag description.
   Change Branch	Changing the Branch of the Message Select the message for which Branch has to be changed Click on 'Change Branch' button. The details of the message will be displayed with only the Branch field enabled. Choose the new branch from the list of values provided and save the message.
   TW Auth	Authorizing a Testword A telex message for which you entered a testword should be authorized before it can be routed to a user queue (if you have specified so in the Branch Preferences screen). To authorize a test word that was entered for a telex message, click the ‘TW Auth’ button from the Browser on this screen. During the authorization of a testword the authorizer will be required to re-enter the testword.
   Move To Queue	Routing a Message to a Queue After you have made the checks that are necessary for the media through which a message is transmitted you can route the message to a user queue. To change the queue in which an incoming message should be stored: Select the message Click the ‘Move to Queue’ button Select a queue from the adjoining option list. The message will be automatically moved to the queue that you specify. The final destination of an incoming message is the end-user queue. These queues represent departments or printers responsible for acting on the received messages. Once a message is lodged into an end user queue, it can be viewed on-screen or printed by the users who have access to the queue. You can move messages from one end user queue to another as well. For a message that was transmitted through Telex, you should enter the testword and have it authorized before you can route it to the relevant end user queue.
   Link Contract	Linking the Message to a Contract In the browser, select the message with which you want to associate a contract and click on the ‘Link Contract’ button. The Reference Number option-list is enabled for the selected message. You can select the appropriate contract from the list. The message will be subsequently associated with the contract selected here.
   Upload	Uploading Incoming Messages If the background process for incoming messages is not running you will have to upload the messages that have come into your bank from the incoming directory on the node to which your branch is connected. To upload messages from the incoming directory (specified in the MCS maintenance screen) click the ‘Upload’ button. All messages that were stored in the Incoming Directory will be uploaded to Oracle Banking Trade Finance and displayed in the Incoming Message Browser.
   Edit	Editing the Incoming Message Click 'Edit Message’ button if you wish to make changes to the SWIFT message, especially the messages marked for repair. This is explained in the next Section.
   Authorize	Authorizing the Incoming Message Use ‘Authorize’ button to authorize the message. All the amendments made to a SWIFT payment message have to be authorized by a user with appropriate authorization rights. At the time of authorizing, Oracle Banking Trade Finance will display the earlier version of the SWIFT payment message along with the amended version, in the same window. A list of all the errors due to which the message was marked for repair is also displayed. The authorizer can view all the errors and also verify the changes that were made to correct them. After verification, if all the details are found to be appropriate, the message is authorized. Oracle Banking Trade Finance maintains a detailed audit log of all amended SWIFT Payment Messages. The following details are captured for each authorized message: User ID of the person who authorized the amendments Date and time of authorization. At any point during the verification and authorization process, the authorizer can choose to cancel the entire operation without changing the status of the message.
   Force	Force Releasing Messages Use ‘Force Release’ button to forcibly release all Payment Message Transactions with ‘Funding Exception’ status and insufficient funds. In other words, the system will post the required accounting entries for such transactions regardless of insufficient funds in the accounts. However, an override will be displayed. The system will also maintain a detailed audit trail for such transactions. A user with appropriate rights can perform this function.
   Suppress	Suppressing the Incoming Message To suppress a message, click ‘Suppress’ button in the Incoming Browser and load the ‘Suppress Message’ screen. The following options are available to suppress a Payment Message: Suppress Message Generation Suppress Full No Suppress Specifying the ‘Suppress Message Generation’ Option If you select this option, Oracle Banking Trade Finance will stop the generation of the Payment Message. However, the system will post the necessary accounting entries for the messages being suppressed. Indicating the ‘Suppress Full’ Option If you select the full suppress option for a message, the system will not post the related accounting entries. Advice generation will also be stopped. In other words, the system will not pick up the Payment Message for any further processing. Specifying the ‘No Suppress’ Option A message marked with the ‘No Suppress’ option will be processed like any other normal Incoming SWIFT Payment Message. Specifying the Remarks for a Suppressed Message You can specify the reason for suppressing a Payment Message in the ‘Remarks’ field.
   Change Address	Receiver address details can be modified if logged in user has privileges.

2. Click ‘Exit’ or ‘Cancel’ to return to the Application Browser.