Warehouse scorecard KPI comparison not updating after scenario promotion in analytics workspace (si-2211)

SCM SAP IBP
, , , , , , , ,
1

We’re experiencing a persistent issue with our warehouse scorecard KPIs not refreshing after scenario promotion. Our planning team promoted a warehouse optimization scenario yesterday (scenario ID: WH_OPT_Q2_2025) through the standard workflow, but the scorecard comparison view still shows outdated metrics from the previous planning cycle.

The scenario promotion itself completed successfully without errors - we can see the new data in the planning area version, and individual KPI tiles show updated values when viewed directly. However, the scorecard comparison functionality that we use for executive reporting is stuck displaying KPIs from 3 days ago. We’ve tried refreshing the browser, clearing cache, and even logging in from different machines.

This is blocking our quarterly planning review meeting scheduled for tomorrow. The scorecard KPI comparison is critical for our stakeholders to evaluate warehouse performance improvements across different scenarios. Has anyone encountered similar behavior with scorecard refresh logic after scenario promotion in SI-2211? We need to understand if this is a versioning issue or if there’s a manual refresh step we’re missing in the promotion workflow.

2

I’ve seen this before. Check your planning area version assignments in the scorecard configuration. Sometimes the scorecard gets pinned to a specific version and doesn’t automatically follow the active scenario after promotion. Navigate to Analytics → Scorecard Settings and verify which planning area version is selected as the data source. It might still be pointing to the old version instead of the newly promoted one.

3

I need to add an important detail here about the scenario promotion workflow and scorecard versioning that wasn’t mentioned yet. In SI-2211, there’s a specific sequence that must be followed for scorecard KPIs to properly reflect promoted scenarios, especially when using comparison views.

First, regarding the scenario promotion workflow: When you promote a scenario, SAP IBP updates the planning area version, but scorecard KPIs that use aggregated metrics don’t automatically recalculate. This is by design to avoid performance issues with large datasets. The system expects either a scheduled refresh job or manual intervention.

For the scorecard KPI refresh logic, you need to understand the cache invalidation mechanism. Navigate to Analytics → Scorecard Configuration → Advanced Settings. Look for the ‘KPI Refresh Strategy’ parameter. If it’s set to ‘Scheduled’, your scorecard will only update during the configured refresh window (typically during off-peak hours). Change this to ‘On-Demand’ to enable immediate refresh after scenario changes. However, be aware this can impact system performance with complex KPIs.

Regarding planning area versioning, the ‘Auto (Follow Active)’ setting should work, but there’s a critical consideration: if your scorecard comparison view references multiple scenarios simultaneously (like comparing baseline vs. optimized), you need to ensure all referenced scenarios are using compatible planning area versions. Check your scorecard’s scenario selection filters - if one scenario points to version V1 and another to V2, but your promoted data is in V3, the comparison will show inconsistent data.

Here’s the step-by-step solution:

  1. Verify Planning Area Version Alignment:

    • Go to Master Data → Planning Areas → Versions
    • Confirm your promoted scenario (WH_OPT_Q2_2025) is assigned to the correct version
    • Check that this version is marked as ‘Active’ for your planning area

  2. Force Scorecard Cache Invalidation:

    • Navigate to Analytics → Scorecard Configuration
    • Select your warehouse scorecard
    • Go to Advanced Settings → KPI Refresh Strategy
    • Temporarily change from ‘Scheduled’ to ‘On-Demand’
    • Save the configuration

  3. Trigger Manual KPI Recalculation:

    • In the scorecard view, click the settings icon (gear)
    • Select ‘Recalculate All KPIs’ (requires IBP_SCORECARD_ADMIN role)
    • If you don’t have this role, use the workaround: change the planning area version to any other version, save, then change back to ‘Auto (Follow Active)’ and save again

  4. Verify Scenario Comparison Settings:

    • In your scorecard comparison view, check the ‘Scenario Filter’ settings
    • Ensure all scenarios being compared are pulling from the same planning area version or compatible versions
    • If comparing across versions, you may need to adjust the version compatibility settings

  5. Monitor Background Jobs:

    • Go to System Monitor → Background Jobs
    • Filter for ‘Scorecard_KPI_Aggregation’ jobs
    • Verify the last successful run was after your scenario promotion timestamp (2025-03-14)
    • If not, manually trigger this job or wait for the next scheduled run

  6. Clear Application Cache (if above steps don’t work):

    • Sometimes the issue is browser-side caching of aggregated data
    • Use Ctrl+Shift+R (hard refresh) or clear SAP Fiori launchpad cache
    • Log out completely and clear browser cookies for the IBP domain

For your immediate need (tomorrow’s meeting), I recommend using the workaround in step 3 to force an immediate refresh. For the long-term fix, change your KPI refresh strategy to ‘Hybrid’ mode, which allows both scheduled and on-demand refreshes. This gives you flexibility without constant performance overhead.

One more thing specific to SI-2211: there’s a known issue (documented in SAP Note 3245789) where scorecard comparison views don’t properly invalidate KPI cache when scenarios are promoted using the batch promotion API rather than the UI. If you’re using automated promotion workflows, this could be your root cause. The workaround is to add a post-promotion step that explicitly calls the scorecard refresh API or triggers the cache invalidation job.

4

Good point about the authorization. The manual refresh option requires the ‘IBP_SCORECARD_ADMIN’ role. If you don’t have that, you’ll need to ask someone with admin access to trigger it. Alternatively, you can force a refresh by temporarily changing the scorecard’s planning area version to a different one, saving it, then switching it back to ‘Auto (Follow Active)’ and saving again. This workaround tricks the system into invalidating the cache and recalculating all KPIs immediately.

5

We had exactly this problem last month. The issue was related to how our scorecard was configured to pull KPI data. The scorecard comparison view has its own refresh schedule that’s independent of the scenario promotion workflow. In our case, the scorecard was set to refresh only during the nightly batch job, so promoted scenarios wouldn’t appear until the next morning. You can trigger a manual refresh by going to the scorecard configuration and using the ‘Refresh KPI Data’ option in the actions menu. This forces an immediate recalculation against the current active planning area version.

6

The ‘Auto (Follow Active)’ setting should work, but there’s a known timing issue with scorecard KPI aggregation in SI-2211. When you promote a scenario, the planning area version updates immediately, but the scorecard’s aggregated KPI cache doesn’t invalidate automatically. This is especially problematic with comparison views that calculate deltas between scenarios. Check if your scorecard uses any custom KPI formulas that reference multiple planning area versions - these can cause stale data to persist. Also verify in the job log (System Monitor → Background Jobs) whether the ‘Scorecard_KPI_Aggregation’ job has run successfully after your promotion timestamp.