How a retailer modernised their SAP landscape
summary
A large Australian retailer merges two brands’ finance backends — a 6 TB ECC system and a 1 TB S/4HANA — into a single S/4 under SAP Rise on AWS in eight months, hitting a five‑month technical go‑live and three more months to business go‑live. Key wins: zero data discrepancies, migration of 200+ interfaces, heavy optimization of document splitting, upfront sizing/connectivity and tooling planning, and now piloting Amazon Q for ABAP remediation and AWS SAP joint reference architecture for extensions.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker welcome
- 1:08Customer challenge and SAP Rise overview
- 3:37Why AWS for SAP Rise
- 6:49Customer journey and implementation
- 7:53Business goals and data cleanup
- 9:18Migration approaches and tooling
- 10:41Sizing and non-functional requirements
- 11:22Connectivity design and acceleration
- 12:25Trial migrations and dress rehearsals
- 13:49AWS support and advisory role
- 14:35Next steps and innovation plans
- 15:39AWS offerings for SAP Rise
- 16:41Closing remarks and call to action
related talks
12mModernize Manufacturing with SAP on
38mRise with SAP on AWS: Swarovski's technical journey(BIZ202)
46mReimagining Manufacturing: Clariant’s SAP RISE Journey with AWS
58mChoice and innovation for SAP customers
56mAccelerate your SAP S/4HANA transformation on
25mChoosing your SAP migration path
37mDecide and begin an SAP migration journey to AWS
08mEnabling successful MRO operations with the AWS Cloud