Skip to Main Content
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.

Status Submitted
Categories Onboarding
Created by Guest
Created on Oct 8, 2025

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.

  • 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!