https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486629#M1931719 <HTML><HEAD></HEAD><BODY><P>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.</P><P></P><P>Cheers,</P><P>Julius</P></BODY></HTML> Mon, 15 Feb 2016 20:50:31 GMT Former Member 2016-02-15T20:50:31Z https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486627#M1931717 <HTML><HEAD></HEAD><BODY><P>I have a user trying to confirm Vendor changes using FK08. SU53 states that they are missing FDKUSER.</P><P>I am not sure that this is relevant, I cannot see why Internet User Maintenece would resolve this issue as we do not have Internet Users.</P><P>Is this message hiding what they really need? We are using ECC6.</P></BODY></HTML> Mon, 15 Feb 2016 17:27:27 GMT https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486627#M1931717 Former Member 2016-02-15T17:27:27Z https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486628#M1931718 <HTML><HEAD></HEAD><BODY><P>Yes, it is the 2nd most famous "noise" after S_CTS_ADMI 'TABL' and before S_DEVELOP 'DEBUG'.</P><P></P><P>See SAP Note 1671117 for the solution to "look behind the curtain" or eliminate the "single axis of evil"... <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span></P><P></P><P>Cheers,</P><P>Julius</P></BODY></HTML> Mon, 15 Feb 2016 20:45:12 GMT https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486628#M1931718 Former Member 2016-02-15T20:45:12Z https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486629#M1931719 <HTML><HEAD></HEAD><BODY><P>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.</P><P></P><P>Cheers,</P><P>Julius</P></BODY></HTML> Mon, 15 Feb 2016 20:50:31 GMT https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486629#M1931719 Former Member 2016-02-15T20:50:31Z https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486630#M1931720 <HTML><HEAD></HEAD><BODY><P>Thank you Julius - this makes sense, even if it is a pain. Thank you for your help</P></BODY></HTML> Tue, 16 Feb 2016 08:53:04 GMT https://community.sap.com/t5/application-development-and-automation-discussions/fdkuser-transaction/m-p/11486630#M1931720 Former Member 2016-02-16T08:53:04Z