A move to S/4HANA changes a lot.
Processes change.
Transactions change.
Responsibilities change.
Roles change.
But one thing often survives longer than it should:
๐ข๐น๐ฑ ๐ฎ๐ฐ๐ฐ๐ฒ๐๐ ๐น๐ผ๐ด๐ถ๐ฐ.
There is a natural temptation during a large transformation to move existing roles forward because they already work.
Sometimes that makes sense.
Sometimes it carries years of:
โข Excessive access
โข Outdated assignments
โข Wildcards and broad ranges
โข Redundant roles
โข Old SoD conflicts
โข Historical exceptions into the new environment.
That means an S/4HANA program is not just a migration project.
It is also an opportunity to ask:
โ
What access should survive?
โ
What should be redesigned?
โ
What should be removed?
โ
Which controls need to change?
โ
What risk are we carrying into the new system?
The worst outcome is completing a major transformation and discovering that the access model underneath it still reflects the old organization.
