After upgrading our SAP S/4HANA Cloud system from 1809 to 1909, several capacity planning Fiori apps have disappeared from our users’ launchpad. The apps were working fine before the upgrade, and users had proper access through their assigned roles. Specifically, the Capacity Planning Table and Capacity Leveling apps are no longer visible, even though the business catalogs appear to be assigned correctly in the role maintenance. Our production planners are unable to access these critical apps, significantly impacting their daily work. I’ve checked the role assignments and they seem unchanged from our pre-upgrade configuration. Has anyone experienced Fiori app availability issues after upgrading to 1909, particularly with capacity planning applications?
The disappearance of capacity planning Fiori apps after upgrading to S/4HANA Cloud 1909 is caused by business catalog restructuring and requires systematic resolution across three areas.
Business Catalog Assignment: SAP reorganized capacity planning catalogs in 1909. The previous catalog SAP_CA_BC_IC_LRD_PC has been deprecated and split into multiple new catalogs:
- SAP_PP_BC_CAPACITY_PLANNING_PC for capacity planning table apps
- SAP_PP_BC_CAPACITY_LEVELING_PC for capacity leveling functionality
- SAP_PP_BC_PRODUCTION_PLANNING_PC for general production planning apps
Access PFCG transaction and update your production planner roles by removing old catalog references and adding these new catalogs. Each catalog now has more granular authorization objects, so ensure your role includes all necessary catalogs for complete functionality.
Fiori App Availability: After catalog reassignment, verify app activation status. Navigate to /UI2/FLPCM_CONF (Fiori Launchpad Configuration) and check that the following apps are active:
- Capacity Planning Table (F2871)
- Capacity Leveling (F2872)
- Capacity Requirements (F2873)
If any apps show as inactive, use the activation button to enable them. In 1909, certain apps require explicit activation post-upgrade even if they were active in the previous version.
Role-Based Access: The 1909 release introduced stricter role-based access controls for capacity planning. Beyond catalog assignment, users need:
- Business role SAP_BR_PRODUCTION_PLANNER or equivalent assigned
- Authorization object P_TCODE with access to transaction CM01 (Capacity Planning)
- Authorization object C_ARBPL_BER for work center authorization
- OData service authorization for capacity planning services
Verify these authorizations in SU53 transaction after a user attempts to access the apps. Missing authorizations will prevent app visibility even with correct catalog assignments.
Implementation Steps:
- Update roles in PFCG by replacing old catalogs with new 1909 catalog IDs
- Generate authorization profiles after role modification
- Activate required Fiori apps in /UI2/FLPCM_CONF
- Run /UI2/FLPD_CUST to clear and refresh Fiori launchpad cache
- Execute PFUD transaction to synchronize user assignments
- Have users clear browser cache and re-login
For cloud deployments, also check that your communication arrangements include the capacity planning OData services. The upgrade may have reset some service configurations, requiring reactivation through the Communication Arrangements app.
Test with a single user first to confirm all three areas are properly configured before rolling out to all production planners.
Best practice is to create a new role or modify the existing role by removing old catalogs and adding new ones in a single change. This prevents any authorization conflicts. After saving the role changes, you must run PFCG transaction to generate the profile. Then refresh the Fiori cache as Mike mentioned. Users should clear their browser cache and log out/in to ensure they receive the updated launchpad configuration. The role-based access control in 1909 is more granular, so verify that users have the appropriate business role assignments beyond just the catalogs.
Don’t forget to check if the apps themselves are activated in the system. Sometimes after upgrades, certain Fiori apps need to be explicitly activated through the Fiori Apps Configuration transaction. The catalog assignment is only half the equation.
I’d also recommend checking the SAP Note for 1909 capacity planning changes. There were some prerequisite configurations that needed to be completed post-upgrade for certain PP-related Fiori apps to function correctly. The notes section usually lists the specific customizing activities required.
This is a known issue with the 1909 upgrade. SAP reorganized several business catalogs for capacity planning apps, and the old catalog assignments don’t automatically map to the new structure. You need to check the SAP Fiori Apps Reference Library for 1909 to identify the new catalog IDs. The capacity planning apps were moved to different catalogs with updated naming conventions.