Phil Meeting 12.2 - Lessons Learned From Real World S4HANA Projects From 2019 To 2021
Phil Meeting 12.2 - Lessons Learned From Real World S4HANA Projects From 2019 To 2021
• Brownfield – is it a trend?
• The operation of S/4HANA Embedded Analytics should not interfere with the OLTP Production system
• SAP HANA 2.0 Active-Active (Read-Only) Architecture was designed for Disaster Recovery & Business
Continuance: this is an out-of-the-box solution from SAP for logs replication & for the secondary DB to be active
• This architecture can also be leveraged for “unlimited” analytics since OLAP activities will be read from Site B
• SAP S/4HANA analytics query can be built with hints to take advantage of this special architecture
While SAP continues to push its customers to move to SuccessFactors, SAP also recognizes that some
customers will not go immediately:
▪ SAP currently allows customers to run its current HR/HCM functionalities in a S/4HANA
Compatibility Pack mode – Fairfax Water is currently using it in Production!
▪ Q3 2022: SAP will release the Human Capital Management for S/4HANA on-premise edition –
it will be a license swap & additional costs
▪ The HCM for S/4HANA will only work on SAP HANA & will incorporate many functionalities
currently found on SuccessFactors
▪ SAP expects its customers to eventually move to SuccessFactors
7 © 2021 ASUG Confidential
SAP S/4HANA HCM On-Premise Edition
Solution for Now and for the Future
Any DB
Any DB
• A separate SAP S/4HANA instance used • SAP S/4HANA prototype for one or • A new consolidated SAP S/4HANA
Key for replicating data from existing ERP more business units including global Enterprise instance including
Characteristics: systems design and focus on data/reporting centralized database for Finance
• Harmonized reporting leveraging in- first transaction processing, data
memory computing • Phased roll-out for remaining structuring, and advanced reporting
• Gradually migrate legacy ERP to SAP business units
S/4HANA
• Customers looking to change operations • Customers looking to fully modernize • New or Existing SAP customers
Common gradually but leverage benefits of and integrate their SAP architecture • Customers looking to quickly retire
customer consolidated financials. while minimizing risk and impacts on legacy systems
attributes: • Customers with multiple ERP platforms business operations • Customers adopting new processes and
and want to slowly phase out financial systems design
• Customers with highly customized /
complex SAP installation
15 © 2021 ASUG Confidential
Adoption of S/4HANA Central Finance – Deliver Value to Enterprise
• Stay agile and innovative, with little disruption to business
• Gain a competitive advantage with an accelerated path to finance and digital
transformation
• Save time and cost with fewer resources required
Business • Shorten time to value compared to a full-scale upgrade
• Consolidate existing SAP and non-SAP ERP systems without needing to retire them
IT • Adopt new innovations and adapt to changing circumstances more quickly and flexibly
• Roll out new capabilities incrementally according to actual needs
• Avoid disruption to running systems thanks to real-time data replication
• Gain instant insight into all connected systems at any time
• Customer can use Central Finance as a steppingstone towards full SAP S/4HANA adoption.
• Central Finance will provide Customer a centralized platform, SAP S/4HANA capabilities, and selective
finance transformation.
• Customer can deploy Central Finance for central reporting & planning, central process orchestration and
central transactional progressively or in one roll out.
• Customer can build a business case by gathering current-state challenges from stakeholders and
identifying where value opportunities exist.
• The key drivers of cost are scope, timeline, cloud versus on-premise, and extended reliance on third
party support.
• Centralization of other non-Finance applications can increase the integration and value of Central
Finance and simplify the IT footprint.
• Stakeholder Buy-in: Business value proposition should include innovation with minimal disruption
and aligned with SAP Roadmap.
• Insufficient preparation of the legacy system: Success of conversion dependent on how carefully
the legacy systems is prepared and detailed planning.
• Complexity of data transfer: Moving data from SAP ERP (ECC) to S/4HANA is challenging if you
don’t properly prepare for conversion.
• Customization may be so extensive that it would be difficult or even impossible to migrate without
major undertaking and cost. S/4HANA CFIN and Cloud approach may also be a positive change that
can make customers rethink their overall strategic direction.