ps: most likely your error is that you expect the person to confirm the change not to have the authorization to change the master data. So they are only an approver and the standard proposals suggest only the same. However it is a sensitive field confirmation where at least two users require both authorizations to change and confirm, but they must confirm each other's changes and then effectively create the record themselves and the checks are identical. Literally, the user names are hard-coded check values from the records.
Cheers,
Julius









