Our regional sales teams are experiencing significant issues with lead management dashboard filters in SCX 2111. When users apply filters for specific regions (EMEA, APAC, Americas) combined with lead owner filters, the dashboards return inconsistent results. Sometimes all leads appear regardless of the filter settings, and other times the results are partially filtered but include leads from other regions.
We’ve verified that the region and owner fields contain correct data at the lead record level. The problem only manifests in the dashboard view. This is causing major issues with our regional performance tracking and territory management, as sales directors can’t trust the filtered reports they’re seeing. The filter logic worked correctly in our previous version before the SCX 2111 upgrade three weeks ago.
The region field is actually a custom picklist field we added about six months ago. The lead owner field is standard. Interestingly, when we filter by lead owner alone, it works perfectly. The problem only occurs when we combine region filters with owner filters, or when we use region filters by themselves.
I found SAP Note 3245891 and it does mention the filter logic change. However, I’m not entirely clear on how to implement the key-based mapping for our existing dashboards. Do we need to delete and recreate all affected dashboards, or is there a way to update the filter configuration in place?
This sounds like a filter mapping issue that sometimes occurs after version upgrades. Have you checked if the region field is a custom field or a standard field? Custom fields sometimes need remapping in Dashboard Designer after major version updates.
I’ve dealt with this exact scenario across multiple SCX 2111 implementations. Let me provide you with the complete solution addressing all the underlying issues:
Root Cause Analysis
The problem stems from three interconnected issues introduced in SCX 2111:
-
Dashboard Filter Mapping Changes: Custom picklist fields now require explicit key-to-value mapping in the filter definition. The automatic mapping that worked in previous versions no longer applies the same way.
-
Custom Field Logic in Analytical Queries: The query engine now treats custom fields differently when they’re combined with standard fields in filter expressions. This affects how the WHERE clause is constructed in the underlying SQL.
-
Regional Reporting Data Model: The lead entity’s relationship with custom regional fields needs proper join conditions defined in the dashboard’s data source configuration.
Step-by-Step Resolution
Phase 1: Fix Dashboard Filter Mapping
- Open each affected dashboard in Dashboard Designer
- For the region filter component, access Properties > Data Binding
- Change the binding mode from “Display Value” to “Technical Key”
- In the filter mapping section, explicitly map each region value:
- EMEA → technical key (usually the picklist option ID)
- APAC → technical key
- Americas → technical key
- Save and test the filter individually before proceeding
Phase 2: Update Custom Field Logic
- Navigate to Administration > Custom Fields > Lead Management
- Locate your region field definition
- Verify that “Enable for Analytical Reporting” is checked
- Add the field to the “Dashboard Filter Index” (new option in SCX 2111)
- This creates the necessary database indexes for efficient filter queries
- Rebuild the analytical indexes (takes 15-30 minutes depending on data volume)
Phase 3: Configure Regional Reporting Data Source
- In Dashboard Designer, edit the data source for your lead dashboards
- Access Advanced Settings > Custom Field Joins
- For the region field, configure the join condition:
- Join Type: INNER JOIN (not LEFT JOIN)
- Match Condition: Lead.RegionField_ID = RegionPicklist.OptionID
- This ensures proper filtering when combining custom and standard fields
Phase 4: Handle Combined Filters
For dashboards using both region and owner filters:
- Create a filter group that explicitly defines the logical relationship
- Set the group operator to AND (not the default OR)
- Define filter priority: Region (Priority 1), Owner (Priority 2)
- This controls the query execution order and prevents cross-contamination of filter results
Testing Protocol
- Test region filter alone with known data set
- Test owner filter alone with known data set
- Test combined filters with expected result count
- Verify with actual SQL query log if needed (transaction STAD)
Important Considerations
- Existing dashboards may need to be recreated rather than updated if they were created before SCX 2105. The data binding metadata structure changed significantly.
- User roles need S_RS_COMP1 authorization for custom field filter operations in SCX 2111
- Browser cache must be cleared after making these changes, as Dashboard Designer caches filter metadata locally
Alternative Approach for Quick Fix
If you need immediate resolution while implementing the full solution:
- Create a calculated field in the dashboard that concatenates region and owner
- Use this single field for filtering instead of separate filters
- This bypasses the join condition issues but is less user-friendly
The complete implementation should resolve your regional reporting issues and restore trust in the filtered dashboard results.
Adding to the previous comment - SCX 2111 changed the default behavior for custom field filters from value-based to key-based matching. This is documented in SAP Note 3245891. If your dashboards were created in the previous version, they’re probably still using value-based filter logic which doesn’t work correctly with the new query engine. You’ll need to recreate the filter components using the updated Dashboard Designer interface that supports key-based mapping for custom fields.
I suspect the issue is related to how custom picklist fields are indexed in the analytical query layer after the SCX 2111 upgrade. The version introduced changes to how custom field values are joined with the main entity tables in dashboard queries. Check if your region field has the proper value mapping configuration in the dashboard filter settings. You might need to explicitly map the picklist values to their internal keys rather than relying on the display values.