Notice: The SAP S/4HANA Cloud Community migration to the SAP Community will begin on Thursday January 28th at 7:00 p.m. CET – Sunday January 31st 7:00 p.m. CET. During this time the S/4HANA Cloud Community will be set to “read only”. Partners and SAP employees can continue to access the Expertise Services Community at sap.com/s4hc-expertise. New content and questions will be directed to our new SAP Community S/4HANA Cloud page.
Please be aware that due to planned technical maintenance, the Expertise Services Community will be unavailable from 13:00 GMT on Friday January 29th. The community will be operational again on February 1st 2021. Please plan your activities accordingly.
with your approved SAP customer or partner ID (S-User) to get access to all content. Please go to the About page to find out how to get an S-User.
with your approved SAP partner ID (S-User) or SAP User ID to get access to all content. Please go to the About page to find out how to get an S-User.
In this post I share thoughts on factors common to success in the cloud.
All in on standardisation–from business case to project organisation, only standard S4HC capability is considered; a 'wandering eye' for customisation and bespoke scenarios is engineered out of the approach by design
Cloud mindset seen in everything that happens – from the use of adjacent cloud technology for example SAP Jam, JIRA and MS Teams for collaboration, cloud capability is exploited at every turn. Instead of bad practices managing by spreadsheets and email we see cloud productivity mastery
Rapid adoption of productivity practices – capability designed to drive down the operational burden including test automation tools and knowledge sharing with Customer Community is keenly embraced
Trust in SAP – instead of undertaking customer-specific cyber security testing, confidence is placed in SAP’s leadership in this area
Knowing what to let go of – success in the cloud means some concepts of old and no longer relevant. These include performance tests, exhaustive solutiondocumentation, the imperative of getting it right the first time and investing resources in bespoke capability. Instead, customers masterery means, for example, leaving performance testing to SAP, having faith in the system itself as documentation, embracing the sensibility of continuous improvement and smartlyparticipating in SAP Customer Influence forums to influence product capability