How To Fix /SMB/FKCHK128 - You do not have authorization to use the functionality

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/FKCHK -

• Message number: 128

• Message text: You do not have authorization to use the functionality

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SMB/FKCHK128 - You do not have authorization to use the functionality ?

  The SAP error message /SMB/FKCHK128 You do not have authorization to use the functionality typically indicates that the user attempting to perform a certain action does not have the necessary authorizations assigned to their user profile. This can occur in various contexts, such as when trying to access specific transactions, reports, or functionalities within the SAP system.
  Cause:
  
  Missing Authorization Object: The user lacks the required authorization object that governs access to the specific functionality.
  Role Assignment: The user may not have been assigned the appropriate role that includes the necessary authorizations.
  Profile Issues: The user’s profile may not be correctly configured to allow access to the required transactions or functions.
  Authorization Changes: Recent changes in roles or authorizations may have inadvertently removed access.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the necessary roles that include the required authorizations are assigned.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after encountering the error to display the last authorization check. This will show which authorization object was missing.
  Identify the specific authorization object that is causing the issue.
  
  
  
  Modify Roles:
  
  If you have the necessary permissions, you can modify the roles using transaction PFCG (Role Maintenance) to include the missing authorization objects.
  If you do not have the necessary permissions, contact your SAP security administrator to request the required changes.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the functionality again to confirm that the issue is resolved.
  
  
  
  Documentation:
  
  Document any changes made to roles or authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  Authorization Concept: Understanding SAP's authorization concept is crucial. It involves roles, profiles, and authorization objects that control access to various functionalities.
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization errors.
  Security Audits: Regularly perform security audits to ensure that users have the appropriate access levels and that there are no unauthorized access issues.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.