How To Fix FKCHK313 - You do not have authorization for &1 of checks in company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 313

• Message text: You do not have authorization for &1 of checks in company code &2

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 FKCHK313 - You do not have authorization for &1 of checks in company code &2 ?

  The SAP error message FKCHK313 indicates that a user does not have the necessary authorization to perform a specific action related to checks in a particular company code. This error typically arises in the context of financial transactions involving checks, such as payment processing or check management.
  Cause:
  The error is caused by a lack of authorization for the user to access or manage checks in the specified company code. This can happen due to:
  
  Missing Authorization Roles: The user may not have been assigned the appropriate roles or authorizations in their user profile.
  Company Code Restrictions: The user may have access to other company codes but not to the one specified in the error message.
  Authorization Object Issues: The relevant authorization objects (e.g., F_BKPF_BES, F_BKPF_BUK) may not be properly configured for the user.
  
  Solution:
  To resolve the FKCHK313 error, you can take the following steps:
  
  
  Check User Authorizations:
  
  Go to transaction code SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that they include the necessary authorizations for handling checks in the specified company code.
  
  
  
  Review Authorization Objects:
  
  Use transaction code SU53 to analyze the last authorization check failure. This will provide insights into which specific authorization object is missing.
  Common authorization objects related to financial transactions include:
  
  F_BKPF_BES (Authorization for Document Types)
  F_BKPF_BUK (Authorization for Company Codes)
  
  
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include the required authorizations for the company code in question.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the transaction again to confirm that the error has been resolved.
  
  
  
  Documentation:
  
  Document any changes made to user roles and authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  Authorization Management: Understanding how to manage user roles and authorizations is crucial for SAP security. Regular audits of user access can help prevent such issues.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization errors or provide additional guidance.
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.