Monday, November 2, 2026
Two Systems, One Role Concept: A Large Public Client’s Path to SAP S/4HANA
More Information
When a large public sector organization consolidated two legacy SAP landscapes, ECC and CRM, into a single S/4HANA environment, one of the hardest parts was the consolidation of authorizations. Two systems, two role philosophies, two sets of naming conventions, and years of independently accumulated role sprawl had to become one clean, audit-ready role concept, without slowing the program down or opening a compliance gap on go-live day.
This session tells that story. We walk through how the security team treated authorization redesign as a first-class migration workstream rather than a post-go-live cleanup project: mining real usage data from both legacy systems to define what access was actually needed, reconciling two fundamentally different authorization models (ECC’s transaction-driven structure vs. CRM’s business-role/BSP-driven structure) into a single harmonized S/4HANA role concept with Fiorization, and using automation to make role building, mass testing, and cutover fast enough that security stayed on the critical path instead of becoming the bottleneck everyone blames.
Because this was a public sector client, audit and compliance weren’t a final checkbox; they shaped the role design from day one. Attendees will leave with a practical blueprint for running authorization consolidation as a controlled, measurable, auditable engineering effort, not a scramble.