Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


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
    Reply
    |
    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
    Reply
    |
    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.