Add Filtering by GS ID

Hi Ethan,

I would like to discuss with you more details. Let me know your convenient time.

Thanks

/Manoj Panda

Product Manager

Hi Ethan,

Thank you for submitting this idea! This is a very practical request that addresses a real challenge when working with VAN providers like Ariba where multiple customers share the same ISA ID.

Understanding the Problem

I completely understand the issue you're facing. In X12 EDI, the structure is:

• ISA (Interchange) - The outer envelope, often shared across multiple customers when using a VAN like Ariba

• GS (Functional Group) - Contains the specific sender/receiver application identifiers

• ST (Transaction Set) - The individual transaction

Currently, if Document Tracking and Metrics only allow filtering by ISA ID, you're seeing aggregated data for all customers using the same Ariba ISA, which makes it impossible to analyze individual customer activity or troubleshoot customer-specific issues.

Business Impact

This limitation affects several important use cases:

Operational Challenges:

• ❌ Cannot isolate metrics for a specific customer using Ariba

• ❌ Difficult to troubleshoot customer-specific EDI issues

• ❌ Cannot provide accurate activity reports to individual customers

• ❌ Hard to identify which specific customer is having problems

• ❌ Cannot track SLA compliance per customer

What You Need:

• ✅ Filter by GS Sender/Receiver ID to see customer-specific data

• ✅ Drill down from ISA → GS → ST level in metrics

• ✅ Generate reports showing activity per GS ID

• ✅ Troubleshoot and analyze at the customer level

Clarification Questions

To ensure we design this correctly, I have a few questions:

1. Scope of Filtering:

• Do you need to filter by GS Sender ID, GS Receiver ID, or both?

• Should this be available in both Document Tracking and Metrics dashboards?

• Do you also need this in exported reports?

2. Current Workaround:

• How are you currently getting customer-specific data? (Manual queries, exports, support tickets?)

• How much time does this workaround take per customer inquiry?

3. Volume:

• Approximately how many customers do you have sharing the same Ariba ISA ID?

• How frequently do you need to filter by GS ID? (Daily, weekly, per customer request?)

4. Additional Identifiers:

• Besides GS ID, are there other identifiers you'd like to filter by? (e.g., ST Sender/Receiver ID, PO numbers, specific transaction types?)

5. Use Cases:

• What are your top 3 use cases for this filtering capability?

  • Customer-specific activity reports?

  • Troubleshooting failed transactions?

  • SLA monitoring?

  • Billing/chargeback validation?

Proposed Solution

Based on your description, here's what I'm envisioning:

Enhanced Filtering in Document Tracking:

Current: ISA ID → [All transactions]
Proposed: ISA ID → GS Sender ID → GS Receiver ID → [Filtered transactions]

Enhanced Metrics Dashboard:

• Add GS Sender/Receiver ID as filterable dimensions

• Show metrics broken down by GS ID when ISA is shared

• Allow drill-down: ISA → GS → Transaction details

Specific Features:

1. Multi-level Filtering: Filter by ISA, then further filter by GS Sender/Receiver

2. Search by GS ID: Direct search/filter input for GS identifiers

3. Saved Filters: Save commonly used GS ID filters (e.g., "Ariba - Customer A")

4. Export with GS Data: Include GS IDs in CSV/Excel exports

5. Metrics by GS: Show transaction counts, success rates, etc. per GS ID

Technical Considerations

Pros:

• ✅ Solves the VAN/shared ISA problem

• ✅ Provides customer-level visibility

• ✅ Improves troubleshooting efficiency

• ✅ Enables accurate customer reporting

• ✅ Data already exists in the system (GS IDs are captured)

Thank you for bringing this to our attention. This will benefit many customers who work with VANs and shared ISA scenarios.

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