Name
Customer Case Study: Who Can Change What? Securing SAP Master Data at the Source
Description

Every SAP transaction relies on master data, yet significant risk can arise before a transaction is ever processed. Weak controls over who can request, approve and execute master data changes can expose an organisation to potential fraud, segregation-of-duties conflicts and gaps in accountability.

After identifying these risks, an internal Shared Services team redesigned the master data change process and introduced stronger governance, access controls and approval responsibilities. This practitioner case study explores how the team strengthened auditability and accountability while creating a more controlled approach to managing master data changes.

What You'll Learn:

  • Identify fraud and segregation-of-duties risks within the master data change process.
  • Separate request, approval and execution responsibilities through stronger controls.
  • Improve governance, auditability and accountability without creating unnecessary process barriers.
Norman Alimagno
Session Type
Customer Case Study