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
Generate UETRs for MX during MSIF sending, not in the MER Data Entry (DNIMX&DNIFINPLUS)
1. For T2 MSGs that we enter in DNIMX domain the field for UETR is not mandatory so we can leave it empty but when we send the MSG from MER to InterAct and to SWIFTNet the UETR is not calculated and field PmtId – UETR is empty even if we put CD code TGT. 2. For CBPR+ MSGs that we are entering in DNIFINPLUS domain the field PmtID is mandatory so we cannot complete the MSGs (Validate gets error DNIY7010E)
For person entering the MX MSG in MER Facility it is not easy to generate UETR outside MER and then to copy it into MSG manually. Not to mention the possibility of errors.
Today in MERVA for manualy entered FIN MSGs the UETR is generated during sending the MSG to SIPIN so the same should be done for MX MSGs when they are sent to InterAct.
Do not place IBM confidential, company confidential, or personal information into any field.