Moving to SAP S/4HANA? What You Need to Know About Access Control
Meet the Experts
Key Takeaways
⇨ Overcoming challenges in Access Control and Access Violation Management during the migration to SAP S/4HANA and cloud adoption.
⇨ Leveraging a previous SAP S/4HANA installation and global rule set to streamline Segregation of Duties (SoD) risk analysis.
⇨ The importance of collaboration with the implementation team and partners for a successful GRC upgrade and overall system migration.
Jabil went live on SAP S/4HANA 1909 and fully migrates to the cloud on our largest manufacturing instance (over 40,000 SAP users) in January 2022, and during the pandemic. That was quite a feat and added a different dimension to challenges that no one could have predicted. We had several challenges to Access Control and Access Violation Management during this transformation period. Fortunately for the GRC team, there was a small installation of SAP S/4HANA 1709 a few years earlier and most of the new tcodes that would affect the Segregation of Duties (SoD) risk analysis had already been introduced to our global rule set. We still needed to review all the object changes, while leaving any deprecated tcodes or objects untouched as we still have several other SAP instances that are still in ECC. Collaborating with the implementation team and their partners was key to the success of the GRC portion of the upgrade. We upgraded GRC to V12.0 SP14 later that year and upgraded our Access Violation Management tool while the manufacturing instance went live on SAP S/4HANA.
Read the presentation here.
