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
Pain001V5 to ISF Mapper, request for Core Mapper with support for Post-Body Mapper to harvest ABN-specific Supplementary Data
In response to the requested Pain.001V5 to ISF mapper, please find attached the final specs (see file "FTM_Mapping_PAIN001.001.05 to ISF v0.3_Final for RFE.xlsx")
In short, we would require 1. a Core Mapper based on XSD Pain.001V5, 2. with support for a Post-Body Mapper for the mapping of the Supplementary Data to ISF Addenda. A sample Post-Body Mapper is requested for the below Supplementary Data mappings (see the attachement).
Re 1: Should be unambiguous, as the resp. XSD for Pain.001V5 is leading.
Re 2: This is a new feature, required to map Supplementary Data attributes which were introduced by the Pain.001V5 (ie Pain.001V3 does not cater for these). Supplementary Data is ABN (channel-) specific, hence why ABN requires a customer-specific solution like a Post-Body Mapper. This support for Post-Body Mapper must be maintainable and extendible, meaning that in case future channels require additional Pain.001V5 Supplementary Data fields to be mapped in ISF, ABN is capable of adding such new mapping requirements in the Post-Body Mapper themselves easily without requiring changes to the Core Mapper.
N.B. As response to PMR 40620,211,788 it became clear that the Pain.001V5 mapper in the SEPA pack is built with minimal mapping to ISF and does not support all the possible levels of repetition within the message and does not cover the full message content. Therefore we have been advised to raise this RFE.
Do not place IBM confidential, company confidential, or personal information into any field.