How To Fix GJ920 - No Authorization for Company Code &

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 920

• Message text: No Authorization for Company Code &

What causes this issue?

For the specified company code you are not allowed to post in FI.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Contact your system administrator for maintaining authorization object
F_BKPF_BUK

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GJ920 - No Authorization for Company Code & ?

  The SAP error message GJ920, which states "No Authorization for Company Code &," typically indicates that the user attempting to perform an action does not have the necessary authorization for the specified company code. This is a common issue in SAP systems where user roles and authorizations are strictly managed to ensure data security and integrity.
  Cause:
  
  Missing Authorization Role: The user does not have the appropriate authorization role assigned that includes access to the specified company code.
  Authorization Object: The authorization object related to company code access (e.g., F_BKPF_BES, F_BKPF_BUK) may not be properly configured for the user.
  User Profile Issues: The user profile may not be updated or may have been changed, leading to loss of access.
  Company Code Restrictions: The company code may have specific restrictions that limit access to certain users.
  
  Solution:
  
  Check User Roles: Verify the roles assigned to the user in transaction SU01 (User Maintenance). Ensure that the user has the necessary roles that include access to the required company code.
  Review Authorization Objects: Use transaction SU53 immediately after encountering the error to check which authorization objects are missing. This will provide insight into what specific authorizations are required.
  Modify Authorizations: If the user lacks the necessary authorizations, work with your SAP security team to modify the user's roles or create a new role that includes the required authorizations for the company code.
  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.
  Documentation: Ensure that any changes made to user roles and authorizations are documented for future reference and compliance.
  
  Related Information:
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  
  
  Authorization Objects: Familiarize yourself with relevant authorization objects that control access to company codes, such as F_BKPF_BES (Accounting Document) and F_BKPF_BUK (Company Code).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide guidance on authorization management.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.