9.1.3.1 Features on Incoming Message Browser
This topic describes about features of incoming message browser.
- Upload incoming messages from the incoming directory on the node
- Check Testwords for Telex messages
- Authorize the Testword check for messages
- Link an incoming message to a contract
- Route the incoming messages to appropriate queues.
- Branch
- Document Number
- Reference No
- Sender
- Media
- Swift Message Type
- SWIFT Sub Message Type
- Testword
- Authorized
- Status
- Suppress Message
- Process Status
- Queue
- Branch
- Document Number (DCN) assigned to the incoming message -- the DCN is the delivery control number used to identify the message.
- Reference No
- Sender- the name address and location of the sender of the message
- Media - the media through which the message was transmitted
- SWIFT Message Type of the message
- SWIFT Sub Message Type
- Customer Name – the name of the sender of the message
- Address 1–4 – the location of the sender of the message
- Location – the location of the sender of the message
- Testword (in case of a Telex message)
- Entry By
- Release Time
- Running Number
- Authorized
- Checker Date Stamp
- Checker ID
- Status
- Suppress Message
- External Reference
- Process Status
- Modification Number
- Media Control System
- Message Status
- Once Auth
- Value Date
- Amount
- PDE Flag
- Queue
- Message Sequence Number
- Customer Reference Number
- SWIFT LAU
- LAU Validation
- RTGS Network
Checking the Testword for a Telex Message
Telex messages that come into your bank need to be checked for validity if you have specified so in the messaging branch preferences screen. This is done by entering a testword. The test word that you enter depends on the testword arrangement with the counterparty, the important aspects of the message like customer, date and currency.
If the testword you enter does not match the telex testword the message is registered as a defective message and put into the repair status.
Field | Description |
---|---|
External Reference Number | This is a unique message identification number that will be used to identify an
incoming message coming from an external system. This is defined as
the ICN number. On upload of an incoming message into Oracle Banking
Trade Finance, this number, given by the external system, will be
stored in Oracle Banking Trade Finance and passed on to the contract
generated as a result of the incoming message. If the incoming
message results in an outgoing message, the ICN number will be
linked to the outgoing message
also.
This number will help you in creating a relationship between the incoming message, the resultant contract in Oracle Banking Trade Finance, and the outgoing message, if any. If an Incoming message results in an outgoing contract (outgoing message), Oracle Banking Trade Finance will store the External reference number (ICN Number) at the following levels.
|
RTGS Network | The service identifier of the RTGS network will be picked up from field 113 of
block 3 header of the incoming message and displayed
here.
For TARGET 2 clearing network, the service identifier specified for the network in the ‘Clearing Networks’ screen will be defaulted and displayed here. |
Status | You can filter the records based on the status. The drop-down list displays the
following statuses:
You can list all the trade related MT202 which are failed during Bill Liquidation by filtering by ‘Status’ as ‘L’. On successful processing of Trade Related MT202, the ‘Generated Ref No’ is displayed with the Bill Contract Ref No in the ‘Incoming Message Browser’ screen. |
Parent topic: Load Incoming Message Browser Screen