How To Fix >3558 - You are not authorized to change account with authorization type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: >3 - Lock management messages

• Message number: 558

• Message text: You are not authorized to change account with authorization type &1

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 >3558 - You are not authorized to change account with authorization type &1 ?

  The SAP error message 3558 indicates that a user is attempting to change an account but does not have the necessary authorization for that action. The message specifies that the user lacks the required authorization type, which is indicated by &1.
  Cause:
  The error typically arises due to one of the following reasons:
  
  Insufficient Authorizations: The user does not have the necessary roles or authorizations assigned to perform the action on the specified account.
  Authorization Object Restrictions: The authorization object related to the account may have restrictions that prevent the user from making changes.
  User Role Configuration: The user’s role may not include the necessary permissions to change the account in question.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user’s roles and authorizations in transaction SU01 (User Maintenance) or PFCG (Role Maintenance).
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorization, you may need to assign the appropriate role that includes the required authorizations.
  If the user already has the role, check if the role needs to be modified to include the missing authorization.
  
  
  
  Review Authorization Objects:
  
  Identify the relevant authorization object that corresponds to the action being performed. Common authorization objects for account changes include F_BKPF_BLA (Accounting Document) or F_LFA1_APL (Vendor Master).
  Ensure that the user has the necessary values for the fields in the authorization object.
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes to user roles or authorizations, contact your SAP security team or administrator for assistance.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt the action again to verify that 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 govern access to account changes.
  Documentation: Review SAP documentation or internal guidelines regarding user roles and authorizations to ensure compliance with security policies.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message 3558.