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 Inflight
Created by Guest
Created on Jul 17, 2026

RELATED IDEAS

Enhanced reporting on 997 encoding error

When inbounds are successful and outbound 997 generates error encoding for 997 outbound envelope, we need more detail - exactly what search parameters is SPE using to locate outbound ST envelope. This at least should be logged in SPE logs, preferably a "translation report" just like other envelope lookup errors

What is your industry? Non-Industry Specific
How will this idea be used?

Expedite troubleshooting when 997 encoding error is encountered during processing
  • Admin
    Manoj Panda
    Jul 22, 2026

    Hi Michael,

    Thank you for submitting this idea — and for the clear, well-structured write-up. The problem you've described is a real pain point for teams dealing with 997 encoding failures: when SPE cannot locate the outbound ST envelope, the current experience leaves implementers and support engineers with almost no actionable signal, forcing costly manual investigation cycles.

    Your ask resonates with us on two levels:

    1. Observability during processing: Surfacing the exact search parameters SPE uses to resolve the outbound ST envelope in the SPE logs (partner profile, direction, ST control number, etc.) would immediately shorten time-to-diagnose without requiring any UI investment.
    2. A dedicated translation report: Bringing 997 envelope lookup failures into the same "translation report" workflow that already exists for other envelope lookup errors would give customers and support a consistent, self-service troubleshooting artefact — consistent with patterns already in the product.

    Both are achievable improvements and the business case you have articulated — reducing PER, implementation, and support team investigation time — aligns directly with our observability and operational efficiency goals for the platform.

    We will review this idea with the engineering team as part of our upcoming backlog prioritisation. I will keep you posted as it progresses. In the meantime, if you have a specific support case or a recent instance where this gap caused a measurable delay, please share the case ID — it will help us validate scope and priority.

    Thanks again for taking the time to contribute this idea.

    Best regards,
    Manoj Panda
    Product Manager, Sterling B2B Integration SaaS
    IBM

    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.