How To Fix RQ427 - Grant &1 is not permitted for company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RQ - Messages for Cash Management and Forecast

• Message number: 427

• Message text: Grant &1 is not permitted for 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 RQ427 - Grant &1 is not permitted for company code &2 ?

  The SAP error message RQ427, which states "Grant &1 is not permitted for company code &2," typically occurs in the context of SAP's authorization management, particularly when dealing with roles and authorizations in the system. This error indicates that a user is trying to perform an action that requires a specific authorization grant, but that grant is not permitted for the specified company code.
  Cause:
  
  Missing Authorization: The user does not have the necessary authorization for the specified company code.
  Role Assignment: The user may not have been assigned the correct role that includes the required authorizations for the company code.
  Authorization Object: The authorization object related to the grant may not be configured correctly or may not include the necessary values for the company code.
  Profile Issues: The user profile may not be updated or may not include the necessary permissions.
  
  Solution:
  
  
  Check User Roles: Verify that the user has the appropriate roles assigned that include the necessary authorizations for the company code in question.
  
  Use transaction code SU01 to check the user’s roles.
  Use transaction code PFCG to review the roles and their associated authorizations.
  
  
  
  Review Authorization Objects: Check the relevant authorization objects (e.g., F_BKPF_BES, F_BKPF_BUK, etc.) to ensure that the user has the necessary permissions for the company code.
  
  You can use transaction code SU53 immediately after the error occurs to see what authorizations were checked and failed.
  
  
  
  Adjust Authorizations: If the user lacks the necessary authorizations, you may need to adjust the roles or create a new role that includes the required authorizations for the company code.
  
  This may involve working with your SAP security team or basis team to ensure that the roles are correctly configured.
  
  
  
  Testing: After making changes, 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 is resolved.
  
  
  Documentation: Document any changes made to roles or authorizations for future reference and compliance.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  SUIM: User Information System (to analyze user authorizations)
  
  
  
  Authorization Concepts: Understanding how authorizations work in SAP, including the use of authorization objects, profiles, and roles, is crucial for troubleshooting these types of errors.
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error message.
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.