5. SWIFT Messages Via Blockchain
Cross border Outbound transactions initiated from a particular Branch, with as specific Receiver BIC, Message Type,Transfer Currency and Source Code are processed using block chain network and not via SWIFT network. User can verify the details of transaction initiated in source environment are received in destination environment for the combination maintained.
5.1 SWIFT Message Routing Parameter Detailed
You can invoke ‘SWIFT Message Routing Parameter Detailed‘ screen by typing ‘PMDMSGRT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details by clicking on ‘New’ button to create a new record or verify the existing records by clicking on Enter Query button
Transaction Branch
Specify the Transaction branch in which the transaction is to be booked. Alternatively you can select a valid Transaction Branch from the list of values displayed.
Receiver BIC
Specify a valid Receiver BIC, which is the internal SWIFT routing receiver BIC. Alternatively you can select a valid Receiver BIC from the list of values displayed.
SWIFT Message Type
Specify the SWIFT message Type, for which the SWIFT Routing parameter is to be maintained. Alternatively you can select a valid Receiver BIC from the list of values displayed.
Transfer Currency
Specify the Transfer Currency. Alternatively, you can select a currency code from the list of values displayed.
Source Code
Specify the Source Code. Alternatively, you can select the Source Code from the list of values displayed
5.1.1 SWIFT Message Routing Parameter Summary
You can invoke ‘SWIFT Message Routing Parameter Summary‘ screen by typing ‘PMSMSGRT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Transaction Branch
l Receiver BIC
l SWIFT Message Type
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.You can also export the details of selected records to a file using ‘Export’ button.
5.2 DLT Message Browser Summary
You can invoke ‘DLT Message Browser Summary‘ screen by typing ‘PMSHYLTR’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Sender Branch
l Receiver Branch
l Reference Number
l Sender
l Receiver
l Status
l Generated Reference
l Source Type
l SWIFT Message Type
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
You can perform below action:
This action is allowed for all the outbound messages with Rejected/Failed status. You are required to have user/role level queue access rights, to take this action. Source Type needs to 'Out'.
You can use this action to resubmit the payment message for OFBA to pick up and process the message. This action is allowed for a configured number of times.
This sub screen have following fields as display fields
l DCN
l Generated Reference
l Receiver Branch
l Sender Branch
l Smart Contract ID
l Message Status
l Error Code
l Error Description
Status field is shown as the current status. Please select the option to 'Ready'.
On clicking of OK, the message is populated in the OFBA polling table for pick up by OFBA. The message status is then updated as 'Ready'.
On receiving the response from OFBA table, the ACK/NACK status is updated in the SWIFT Message Notification Browser (MSSNOTIB).
Retry of failed/rejected messages are allowed for the maximum number of retry count value maintained against the parameter 'MAX_OFBA_RETRY_COUNT' [PMDSYSPM]. The factory shipped value for maximum retry value is 10.
The system refers to the SWIFT Message Routing maintenance (PMDMSGRT) to decide whether to generate SWIFT CBPRPlus outbound message and send via OFBA or not.
The system checks transaction Source Code, Booking Branch, Instructed Agent BICFI as Receiver BIC, Transfer Currency, and MX Message Type as the SWIFT Message Type against the routing maintenance.
If the maintenance is satisfied, then the message is handed off via OFBA. The ‘Connectivity Option’ value is updated as ‘DLT’. The message is not handed off via the EMS OUT scheduler.