How To Fix GJ043 - No Authorization to & & in Company Code &

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 043

• Message text: No Authorization to & & in Company Code &

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 GJ043 - No Authorization to & & in Company Code & ?

  The SAP error message GJ043 ("No Authorization to & & in Company Code &") typically indicates that a user is attempting to perform an action in a specific company code for which they do not have the necessary authorizations. This error is common in financial transactions, especially in modules like SAP FI (Financial Accounting) or SAP CO (Controlling).
  Cause:
  
  Missing Authorization Roles: The user does not have the required authorization roles assigned to their user profile for the specific company code.
  Authorization Object Restrictions: The authorization objects related to the transaction being executed may not include the necessary company code or activity.
  User Profile Issues: The user profile may not be correctly set up, or the user may be using a different profile that lacks the necessary permissions.
  Changes in Authorization: Recent changes in the authorization roles or company code settings may have inadvertently removed access.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what is missing.
  Alternatively, use transaction code SU01 to check the user’s roles and authorizations.
  
  
  
  Review Authorization Roles:
  
  Ensure that the user has the appropriate roles assigned that include access to the specific company code and the required activities (e.g., create, change, display).
  If necessary, modify the roles or create new ones to include the required authorizations.
  
  
  
  Modify Authorization Objects:
  
  If the user needs access to a specific company code, ensure that the relevant authorization objects (e.g., F_BKPF_BLA, F_BKPF_BUK, etc.) are configured correctly in the user’s roles.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, contact your SAP security team or administrator to request the required access.
  
  
  
  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 issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to financial transactions in SAP.
  Transaction Codes: Common transaction codes related to user management and authorization include:
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  SU53 - Display Authorization Check
  
  
  Documentation: Review SAP documentation or internal guidelines on user roles and authorizations for your organization to ensure compliance with security policies.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the GJ043 error message.