Skip to Main Content

Shape the future of IBM!

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

Start by posting 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 a 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.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace App Connect
Created by Guest
Created on Jun 14, 2021

SAP Adapter Discovery Agent Wizard should provide valid Message Model for Function Modules / BAPIs

BAPI "import" parameters and "export" parameters are separated from one another within SAP e.g. see SAP transaction SE37 (two tabs / separate views):

This allows import parameters to be defined as mandatory / optional independent of any export parameters.

...but import and export parameters are combined by the IBM SAP Adapter within a BAPI Message Model under a single parent / level:

This prevents SAP response messages (which contain output / export parameters, but not import / input parameters) from being validated against the Message Model generated using the Discovery Agent wizard.

Idea priority High
  • Guest
    Oct 29, 2021

    Thanks Ben - your suggestion (an option on how to group, enabling existing behaviour to be preserved) sounds good.

    If given the option on how to group where a split-grouping is opted for, I would say creating two separate global elements (one for import, one for export parameters) makes sense, as opposed to splitting the generated XSDs / namespaces etc.

    XML global elements are the starting point / anchor from which to match a message with it's definition - so this would work in terms of validation too.

  • Admin
    Ben Thompson
    Jul 2, 2021

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request, which we agree would improve the product... As the Idea raiser will be very well aware, this area of discovery capability within the Toolkit is notorious for its needs in the area of backward compatability, so we would need to be cautious in our implementation choices to ensure that existing users are not adversely impacted. That said, the suggestion sounds sensible (perhaps let the user choose to group the import and export together or not in order to preserve both behaviours?) and we will certainly monitor this idea for comments from other users to see if there is a wider market need. Status of the idea is updated to Future Consideration.