When using the Message Monitor, unless looking for an overview, you will more than likely need to apply filters in order to achieve the view you require.
There are many different filters that can be used, depending on what view you require. The below image details how filters can be used;
Date Range and Time: These filters are used to show messages created/last updated over a particular time period. Dates will be the predominant filter being used here however, should your filter return too many results (maximum messages that can be displayed is 1000) you can filter further using the Time filters.
Organisations: These filters allow the user to find messages specific to certain Providers (instances) on the service. You can filter to show messages being sent to a provider, sent from a provider, or messages sent from a Provider to a specific other Provider. Selecting the same provider in both filters will show system generated messages.
Message Status: Every message shown within the message monitor will have a status. This filter is useful to get an overview of messages at certain statuses or to remove results to help isolate messages you are searching for. The statuses that messages can be at are:
- Awaiting Delivery – First status a message can be at. The system has generated the message and is awaiting the provider to request this message from their manifest.
- Requested – This is the second status a message will move to. This is when the provider has requested this message from the service.
- Acknowledged – Whether a message is coming into OTS from a provider or has been generated by OTS to be sent to a provider, the recipient will confirm back with an Acknowledgement that the message has been received.
- Not Acknowledged – This applies to inbound & outbound and will show when a message has been received that the system cannot process due to errors either in the message structure or the message content.
Message Direction: Inbound or Outbound. Is the message coming into the transfer service from an external source or has it been generated by the service to be sent to an external source.
Message Version: Depending on the service the message relates to (Pensions Cash, Re-Registration etc.), the integration version or Market Practice version each message will have a version label.
B2B Message Identifier: Each message generated on the service (inbound and outbound) will have it’s own unique identifier (example: 1ee8463a-e3ee-49dd-93b5-2dca2c84300b). This filter is particularly useful for searching for specific messages when provided with the ID from the end user or a member of the development team.
UK Funds Market Practice (Re-registrations) Message Identifiers: This is specific to Re-Registration (SWIFT) messages.
Inbound ISO ID: Not sure. Check
Comments
0 comments
Please sign in to leave a comment.