How To Fix TRS0091 - No authorization to create security account in company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: TRS0 - Messages for Reconciliation

• Message number: 091

• Message text: No authorization to create security account in company code &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 TRS0091 - No authorization to create security account in company code &1 ?

  The SAP error message TRS0091 indicates that a user does not have the necessary authorization to create a security account in a specific company code. This error typically arises in the context of financial transactions or when trying to manage security accounts in the SAP system.
  Cause:
  The primary cause of this error is a lack of appropriate authorization in the user's role or profile. Specifically, the user may not have the required permissions to create or manage security accounts for the specified company code.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization object is missing.
  
  
  
  Review User Roles:
  
  Go to transaction code SU01 to review the user's roles and authorizations. Ensure that the user has the necessary roles assigned that include permissions for creating security accounts.
  
  
  
  Modify Authorizations:
  
  If the user lacks the necessary authorizations, you may need to modify their roles or create a new role that includes the required authorizations. This typically involves:
  
  Accessing transaction code PFCG to manage roles.
  Adding the necessary authorization objects related to security account creation (e.g., F_BKPF_BES, F_BKPF_BUK, etc.).
  
  
  
  
  
  Consult with Security Administrator:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security administrator or the person responsible for user management in your organization.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt the action that caused the error again.
  
  
  
  Related Information:
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to financial transactions and security account management. Common objects include:
  
  F_BKPF_BES (Authorization for Document Type)
  F_BKPF_BUK (Authorization for Company Code)
  
  
  
  Documentation: Refer to SAP documentation or your organization's internal guidelines for managing user roles and authorizations.
  
  
  Support: If the issue persists after checking authorizations, consider reaching out to SAP support or your internal IT support team for further assistance.
  
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the TRS0091 error.