We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Automatic generation of field CreDtTm:Creation Date Time in MX MSGs during sending of MSG from MER
Manual entry of MX MSGs (T2 and CBPR+) has mandatory field CreDtTm:Creation Date Time We woud like this field filled automatically with a system date and time at the end of MSG processing in MER Facility that is when the MSGs is put in a MQ queue ...
Please document how to implement SWIFT security recommendations in WBIFN.
Requirement from my customer for information on how to implement SWIFT security recommendations in WBIFN. As a result of the recent security incident at another SWIFT customer institution, my customer is asking for documentation on how SWIFT recom...
Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN.
Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN. The business impact: A message which is successfully validated in MER may nevertheless fail to be send to SWIFT, because it fails the length check in DNF...
A utility to import MX messages into FTM is wanted.
Idea created : 02 FEB 2022.
Today it is possible to : Import FIN messages from an input file or data set and create,
for each FIN message, a corresponding IBM Financial Transaction Manager for SWIFT Services message in a target queue.
In MER add the possibility to search / filter the templates, saved in a queue, by field: "Description"
The user should be able to search the messages in a MER queue, by applying a filter on the column: description. This is useful if a user created a lot of templates and he inserted a particular description for every one.
Support longer passwords for standalone utilities using DB2
The standalone DB2 utilities of FTM SWIFT should allow using a password longer than 8 characters. This is required to use moden authentication means as pass phrases or pin/token. On z/OS, this implies support of JDBC type 4 connections. Relevant u...
FTM for SWIFT - Amount field with ',' formatting on the MER screen
PBB would like the following requirement implemented... Problem Description: By default MER Screen expecting to enter a ',' as a separator in the amount field. Is there any setting in FTM to change to amount format to include '.' instead of ',' e....
Block 3 field 121 (FIN MT199 and FIN MT103) in lower case despite DABADKKK DnqEROUOptions EditorAllFieldsUppercase FIN
Referring PMR 19041,010,678Also see item #36 in the attached doc. In order to comply with the SWIFT specifications and recommendations for the unique transaction reference (UETR - field 121 in GPI messages MT 103 and MT 199) we urgently need a pos...
Our bank performs regular housekeeping on our FTM DNI_A_MSG_PBOU1 table. However, after applying latest FTM 188.8.131.52 patches,Our housekeeping jobs don't work anymore. We opened PMR : 29110,000,778.L2 support suggested to refer to common solution gi...
Do not place IBM confidential, company confidential, or personal information into any field.