How To Fix FR813 - Authorizations for account types are missing

FR813 - Overview

• Message type: E = Error

• Message class: FR - Messages for FI Reporting

• Message number: 813

• Message text: Authorizations for account types are missing

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.

FR813 - Details

• The SAP error message FR813 indicates that there are missing authorizations for specific account types in the financial module. This typically occurs when a user attempts to perform a transaction or access a report that requires permissions for certain account types, but their user profile does not have the necessary authorizations.
  
  Cause:
  
  Missing Authorizations: The user does not have the required authorizations for the account types involved in the transaction.
  Role Configuration: The roles assigned to the user may not include the necessary authorizations for the specific account types.
  Account Type Restrictions: Certain account types may be restricted based on company code, user group, or other criteria.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorizations are missing.
  Review the authorization logs to identify the specific account types that are causing the issue.
  
  
  
  Modify User Roles:
  
  If you have the necessary permissions, go to transaction code PFCG to modify the user roles.
  Add