S/4HANA introduces over 16,000 new transaction codes (t-codes) spanning across dozens of SAP components. These t-codes need to be evaluated for business process, security role, and segregation of duties (SoD) and sensitive access rule set impacts. Additionally, there are over 1,000 legacy ECC t-codes that have been decommissioned or have been partially or completely replaced by Fiori, Ariba, SuccessFactors, Global Trade Services, Hybris, etc. functionality.
When moving to S/4HANA you have opportunity to re-evaluate your security needs and your security model. Read this document to learn how KPMG can help you create a secure, scalable and sustainable security model for your SAP S/4 HANA environment, fulfilling leading practice objectives:
- more secure data and transactions
- future-proofed role design
- reduced costs
- better and more proactive ability to address compliance issues
- improved business ownership of application security.
Evaluate your existing security architecture and thoughtfully plan your security transition approach.
