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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Jun 26, 2018

RELATED IDEAS

Generated SAP Message Model Contention for multiple IDoc Versions

When creating two Message Models from the same IDoc for two IDoc versions (SAP Release Versions), the Message Model files are not tagged with the release version of the IDoc from which they are created from.

In contrast - the XSDs representing IDoc segments are versioned (using the segment version number) e.g. "xxxxxxx001.xsd" (001 representing the segment version number within SAP).

But the top-level IDoc XSDs e.g. SapIDocBO.xsd, Sap.xsd, SapDataRecord.xsd ... representing the Business Object wrapper, the IDoc type and the IDoc Data Record respectively, are not versioned.

This is fine (and always has been fine) when working with Message Sets, but when working with Message Models (within an Application project, or Static Library), this results in contention because Message Models will not allow two files with the same filename, but different contents, into the same scope.

Note: Also, even with versioning of IDoc segment XSDs, if one of the shared segments has changed between IDoc versions this would result in a clash in content between the 2 sets of xsds. This is because changes to a segment referenced by a shared segment do not trigger a segment version number change of the shared segment itself, thus contention is possible between two Message Models for different IDoc versions

Idea priority Medium
RFE ID 121724
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Sep 27, 2022

    This is a very critical need for my client, as they have many SAP adapters across hundreds of flows, so allowing the SAP adapter to become part of a shared library means they don't have to rebuild all those flows when a bapi or an idoc changes and then can re-use these shared libraries with the SAP adapter in them across many flows. The sooner we can get this the better.....

  • Guest
    Reply
    |     Oct 19, 2020

    RFE Review. Thank you for raising this RFE and apologies for the time period it has been in Submitted Status. Of course we have previously discussed this problem area both in person and over email, and it remains a concern for us. We think ultimate resolution of this would best be done via the provision of support for adapter models in shared libraries. Status of this RFE is update to Uncommitted Candidate.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.