The to-do-list before the transition to SAP S/4 HANA Cloud
We have already mentioned that the SAP S/4 HANA Cloud subscription model is subscription model consumption - based since FUEs align to four types of S/4 HANA Cloud users, the biggest difficulty is definitely mapping named users to FUEs
Permissions for ECC users such as Professional, Limited Professional, Employee, Worker, etc. must be mapped to the Use Type/Utilities provided by the FUE metrics. The aforementioned STAR is a valuable ally in determining appropriate FUE levels.
At WEGG we are experienced SAP licensing consultants and we have found from our experience that many customers simply convert the utilities already in the system into the total amount of FUEs to be counted under the contract, without making accurate prior analysis.
This is an activity that needs to be done because miscalculations could lead to a waste due to non-optimization (e.g., inactive users, duplicate users, etc.) and disputes with SAP in the future for non-compliant users accessing the system so we recommend paying special attention to this issue BEFORE signing the “Rise with SAP” contract.
We therefore suggest:
- Check how users are currently using the system
We first recommend getting a complete view of relativi ai user profile and usage activity data, as well as user access to self-reported modules, engines, and products: SAM analysis tools such as Snow Optmizer for SAP Flexera , which are natively integrated into SAP, make it easy to get this information into exportable reports.
Estimating the FUE count for SAP S/4 HANA Cloud based on data that includes inactive users, duplicate licenses on multiple systems, or users who are assigned a usage type that exceeds the activities recorded in the system risks being counterproductive. To this end, it is useful to have a dual view: from the perspective of licensing and actual usage.
Theoptimization of licenses according to actual system usage must be done BEFOREimplementation in SAP S/4 HANA where users will be assigned their respective roles. In fact, we know that in the SAP S/4 HANA system, the permissions and capabilities granted to a user are determined by the roles assigned to that business user's record : so we need to decide this upstream, not postimplementation, where more difficulties may arise in their review.
Having complete reports of both behavioral and authorization models allows us to verify that the roles and authorizations to be “fed” to the STAR simulation tool for FUE counting are set up correctly and also check or non-compliant users accessing the SAP system.