IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Under review
Workspace Sterling B2B Integration SaaS
Categories Onboarding
Created by Guest
Created on Oct 8, 2025

RELATED IDEAS

Enhancing ISA Envelope Handling to Support Transaction-Level Control Number Checks

At present, a single ISA envelope is shared across multiple transactions for a given partner/client/version combination. This setup limits our ability to implement transaction-specific ISA envelope configurations—particularly for enabling duplicate control number checks.
Because of this shared ISA usage, there is a risk of control number overlaps between newly added transactions and those that have been migrated. This overlap makes it hard to check for unique control numbers without accidentally affecting other unrelated transactions.
Example Scenario:
For a specific partner, the 850 transaction has been migrated to a new ERP system, where control number duplication must be strictly prevented. Simultaneously, a new 852 transaction is being introduced, which was not part of the migration and does not require control number uniqueness at the ISA level. Under the current model, both transactions share the same ISA envelope, making it impossible to apply different control number handling rules to each.

  • Admin
    Manoj Panda
    Dec 12, 2025

    Thank you for submitting this idea and explaining the business challenge clearly. The scenario you outlined highlights an important limitation in how ISA envelopes are currently shared across multiple transactions. As you noted, this shared structure makes it difficult to apply transaction-specific control-number rules—especially when some transactions require strict duplicate prevention (e.g., 850) while others do not (e.g., 852).

    This is a valid enhancement request, and we understand how it could help avoid control-number collisions, reprocessing effort, and potential partner disputes. Before we evaluate this further with engineering, I’d like to gather a few more details so we can size the impact and validate the design approach.


    1. How often do you encounter partners where different transactions require different control-number handling rules?

    2. Is the requirement specifically for duplicate control-number checking, or do you expect other ISA-level rules to also vary by transaction?

    3. Would creating separate ISA configurations per transaction be acceptable, or do you expect a more automated or dynamic approach?

    4. What are the current operational impacts when duplicates occur—for example, does it cause rejections, delays, or manual recovery efforts?

    5. Do you foresee this requirement growing as more transactions are migrated or new message types are onboarded?


    Thanks & Regards,

    Manoj Panda

    Senior Product Manager – IBM Sterling B2B Integration & VAN

    Reply
  • Guest
    Oct 8, 2025

    We need to be able to enable "duplicate control number check" at transaction level for an specific partner/client/version to avoid duplication/overlap risk due shared ISA. Thanks!

    Reply

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.