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 Needs more information
Workspace Sterling B2B Integration SaaS
Categories Other
Created by Guest
Created on Mar 24, 2026

RELATED IDEAS

Trading Partner Summary Report – Consolidated report across all BAs with additional fields such as GS Sender ID and GS Receiver ID

The current Trading Partner Summary report provides data only at the Business Agreement (BA) level, which results in fragmented reporting when multiple BAs exist for the same company. As a result, generating monthly operational statistics requires manual consolidation of five or more sheets, which is inefficient and error‑prone.

Additionally, the report lacks key identifiers that are necessary for business users to classify and analyze partner activity across multiple ERPs and partner types.

What is your industry? Automotive
How will this idea be used?

1. One Report Instead of Merging 5 Sheets

Today:
You get Trading Partner Summary report at BA level, so one company with multiple BAs produces multiple sheets → you manually merge them.

After Enhancement:
A single company-level report means:

  • No more combining multiple sheets

  • No manual Excel work

  • No risk of mistakes

2. Easy Identification of Customer vs Supplier

Today:

  • Same partner may be both customer & supplier

  • No way to distinguish them in the current report

After Enhancement:
Adding Inbound/Outbound direction helps:

  • Outbound = mostly customer workflows

  • Inbound = mostly supplier workflows

3. Clear ERP Segregation Using GS Sender/Receiver IDs

Since each ERP uses different GS IDs, adding these columns will allow you to see:

  • Which ERP generated the transaction

  • Which ERP the trading partner is communicating with

4. Business View Field Enables Better Categorization

With Business View included, you can:

  • Group partners by transaction type

  • Understand cross-functional business flows

  • Create targeted performance or volume reports
  • Admin
    Manoj Panda
    Apr 8, 2026

    Thank you for raising this — the pain point is very clear and well articulated.

    I understand that the current Trading Partner Summary report is scoped at the Business Agreement (BA) level only, which causes fragmentation when multiple BAs exist for the same company. This makes it difficult to generate monthly operational reporting, forcing manual consolidation across multiple sheets and increasing the risk of errors.

    I also noted the concern around the lack of key identifiers, which makes it challenging for business users to classify and analyze partner activity across multiple ERPs and partner types.

    To help us evaluate this effectively and determine the right scope, I have a few clarifying questions:

    1. Company-Level Aggregation

      • Are you looking for the report to aggregate and present data at a company / trading‑partner level, with the ability to drill down into individual BAs as needed?

    2. Key Identifiers

      • Which specific identifiers are currently missing and required for analysis?

        • For example: Partner ID, Company Code, ERP Identifier, Partner Type, or something else?

      • Are these identifiers already available in Sterling today but not surfaced in the report, or would they need to be newly introduced?

    3. Primary Use Cases

      • What are the top 2–3 operational metrics this report is used for each month (e.g., document volume, success/failure rate, SLA tracking)?

      • Is the primary consumer operations, business users, or analytics teams?

    4. Report Consumption

      • How is this report typically consumed today (downloaded CSV/Excel, dashboard view, scheduled export)?

      • Would a single consolidated view be sufficient, or is filtering/grouping by ERP, partner type, or region also required?

    This information will help us assess whether the need can be met through:

    • Enhancing the existing Trading Partner Summary report, or

    • Introducing a new, company‑level operational reporting view.

    Thanks again for bringing this forward — once we have the above details, we can evaluate prioritization and next steps.

    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.