/ATL/GENERAL123 - No authorization to company &.

SAP Error Message - Details

• Message type: E = Error

• Message class: /ATL/GENERAL -

• Message number: 123

• Message text: No authorization to company &.

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.

AnswerBot

• What is the cause and solution for SAP error message /ATL/GENERAL123 - No authorization to company &. ?

  The SAP error message /ATL/GENERAL123 No authorization to company & typically indicates that the user does not have the necessary authorization to access or perform actions related to a specific company code in the SAP system. This is a common issue in environments where access control is strictly enforced.
  Cause:
  
  Missing Authorization Roles: The user may not have been assigned the appropriate roles or authorizations that allow access to the specified company code.
  Authorization Object Restrictions: The authorization objects related to company codes (e.g., F_BKPF_BES, F_BKPF_BUK, etc.) may not include the company code in question.
  User Profile Issues: The user profile may not be correctly configured, or the user may be using a different profile that lacks the necessary permissions.
  Organizational Structure Changes: Changes in the organizational structure or company code settings may have affected the user's access rights.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into what is missing.
  Review the user's roles and authorizations using transaction code SU01 (User Maintenance) or PFCG (Role Maintenance).
  
  
  
  Assign Missing Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include access to the required company code.
  
  
  
  Modify Authorization Objects:
  
  If the user has the roles but still encounters the error, check the authorization objects associated with those roles. Ensure that the company code is included in the relevant authorization objects.
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes, contact your SAP security team or administrator to review and adjust the user's authorizations as needed.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to company codes, such as F_BKPF_BES (Accounting Document) and F_BKPF_BUK (Company Code).
  Documentation: Review SAP documentation on authorization management for more detailed guidance on managing user roles and permissions.
  
  If the issue persists after following these steps, further investigation may be required, potentially involving SAP support or a deeper analysis of the authorization setup in your system.