After a major organizational restructure where we merged three production plants into two regional hubs, our Fiori capacity planning app is displaying completely wrong KPI values. Available capacity shows 150% of actual, utilization percentages are negative in some cases, and the work center hierarchy doesn’t match our new org structure at all. The underlying data in tables CRHD and CRCA appears correct when we query directly, but the Fiori tiles and analytical charts are way off. We’ve tried refreshing the app and clearing cache, but the KPIs remain incorrect. The planning team has lost confidence in the system and is reverting to Excel spreadsheets. This is on S/4HANA 2020 with the standard Capacity Planning Fiori app. Has anyone dealt with KPI calculation issues after organizational changes? What needs to be rebuilt or recalculated to get accurate analytics again?
Your issue requires a three-phase approach to restore accurate KPI calculations after the organizational restructure:
Phase 1: Fiori App Cache Refresh
The Fiori launchpad caches tile configurations and KPI definitions at multiple levels. Standard browser cache clearing isn’t sufficient. Execute these steps in order:
- Transaction /UI2/FLP_SYS_CONF: Delete all cached configurations for the Capacity Planning app (search for ‘capacity’ in the app ID field)
- Transaction /UI2/CACHE_DELETE: Clear the Fiori launchpad cache completely, selecting both ‘Business Catalog’ and ‘Tile Configuration’ options
- Restart the SAP Gateway service using transaction SMICM → Administration → ICM → Restart (Hard)
- Have end users clear browser cache completely and log in using incognito/private mode for testing
This ensures the app loads fresh configurations without cached org structure references.
Phase 2: CDS View Join Update
Your capacity planning analytics rely on several interconnected CDS views that need updating. The key views to modify are:
-
I_WORKCENTERTP: This view contains associations to plant and organizational unit. After your merger, the plant codes changed but the view’s association logic still references the old three-plant structure. In Eclipse ADT, open this view and check the association to I_PLANT - it likely has a WHERE clause filtering specific plant codes.
-
I_CAPACITYREQUIREMENT: This view joins work center data with capacity requirements. The JOIN conditions need updating to reflect your new two-hub structure. Look for any INNER JOIN statements that reference plant or work center group hierarchies.
-
I_CAPACITYPLANNINGOVERVIEW: This is the primary analytical view consumed by the Fiori app. It aggregates data from the above views and calculates KPIs like utilization percentage and available capacity. The aggregation logic (GROUP BY clauses) needs to reflect your new organizational levels.
For each view, the modification process:
- Create a CDS view extension rather than modifying the standard view
- Update the association logic or add custom WHERE clauses to filter by your new regional hub codes
- Regenerate the OData service that exposes these views (transaction /IWFND/MAINT_SERVICE)
Phase 3: KPI Workspace Rebuild
This is the critical step that most organizations miss. KPI Workspace maintains its own calculation cache and historical values that don’t auto-refresh when underlying master data changes.
Execute in transaction STC01:
- App: SAP_KPI_WORKSPACE_REBUILD
- Select scope: ‘Capacity Planning’ KPI group
- Set recalculation period: Last 12 months (or your reporting horizon)
- Schedule as background job - this typically takes 4-8 hours for capacity data
After the rebuild completes, verify in transaction STC02 that all KPI calculations finished without errors.
Additional Configuration Checks:
Based on your description of negative utilization values, there are likely data consistency issues beyond just the org structure:
-
Work Center Capacity Verification: Transaction CR03 - verify that all work centers in your new hubs have positive available capacity values. During the merger, if capacity values weren’t properly migrated, you’ll get calculation errors.
-
Factory Calendar Alignment: Transaction OP4A - ensure your new regional hubs use consistent factory calendars. Mismatched calendars between merged plants cause capacity availability calculations to fail, resulting in negative or inflated utilization percentages.
-
Hierarchy Maintenance: Transaction PP01 - rebuild the organizational structure hierarchy for capacity planning. The Fiori app uses this hierarchy for drill-down analysis. If the hierarchy still shows three plants instead of two hubs, KPI aggregation will be incorrect at every level.
-
Data Source Refresh: If your Fiori app uses extracted data rather than real-time CDS views, execute transaction RSDS to refresh the analytical query data source. Force a full extraction rather than delta to ensure all org changes are captured.
Verification Steps:
- Query tables CRHD and CRCA directly - confirm work center assignments to new hubs are correct
- Test CDS view I_CAPACITYPLANNINGOVERVIEW in Eclipse ADT data preview - verify results match direct table queries
- Check KPI Workspace in transaction /UI2/KPI_WORKSPACE - confirm tiles show recent calculation timestamps
- Open Fiori app and compare one work center’s KPI values with transaction CM01 (Capacity Planning) - values should match exactly
After completing all three phases, your KPI calculations should accurately reflect the new two-hub structure with correct capacity utilization percentages and work center hierarchies. The key is addressing all three layers - app cache, analytical views, and KPI calculation engine - not just one or two.
This draft is based on general SAP S/4HANA knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
Sounds like the CDS views underlying your Fiori app are still using the old org structure joins. When org hierarchies change, CDS views with hardcoded plant or work center relationships don’t automatically update. You probably need to regenerate the analytical queries or update the view definitions to reflect the new structure.
That makes sense. We didn’t touch any CDS views during the restructure - just updated master data and org assignments in customizing. How do we identify which CDS views need updating? There are dozens of capacity-related views.
The Fiori Capacity Planning app uses several CDS views in a hierarchy, with I_WORKCENTERTP and I_CAPACITYREQUIREMENT as the core views. These views have associations that link to organizational units. After your restructure, the associations are probably pointing to obsolete relationships. You need to check the view definitions in Eclipse ADT and update any WHERE clauses or JOIN conditions that reference specific plant codes or work center hierarchies. Also verify that your new regional hub structure is properly maintained in customizing tables like T001W and CRHD before updating the views.
I suspect the KPI Workspace tiles are the real problem here, not just the CDS views. KPI Workspace caches calculation results and doesn’t automatically recalculate when master data changes. You need to go into transaction STC01 and run the app ‘SAP_KPI_WORKSPACE_REBUILD’ to force a complete recalculation of all KPI values. This can take several hours depending on data volume, but it’s necessary after major org changes. We had the same issue last year after a plant merger and the rebuild solved it completely.
Tested this on S/4HANA 2021 FPS02 — clearing /UI2/CACHE_DELETE with both Business Catalog and Tile Configuration selected immediately restored accurate capacity KPIs post-restructure.
Don’t forget that capacity planning KPIs also depend on the planning calendar and shift definitions. If you merged plants with different shift patterns, the capacity calculations will be off even if master data is correct. Check transaction OP4A to verify that your new regional hubs have proper factory calendars assigned and that all work centers reference the correct calendars.
We ran the KPI rebuild app overnight and it’s still processing. The shift calendar point is valid too - we did consolidate to a unified shift pattern. Will check that once the rebuild completes.
I suspect the KPI Workspace tiles are the real problem here, not just the CDS views.