How To Fix NR813 - You are not authorized to change the status

SAP Error Message - Details

• Message type: E = Error

• Message class: NR - Number ranges

• Message number: 813

• Message text: You are not authorized to change the status

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 NR813 - You are not authorized to change the status ?

  The SAP error message NR813, which states "You are not authorized to change the status," typically occurs when a user attempts to change the status of a document or object in SAP but lacks the necessary authorizations to perform that action. This can happen in various contexts, such as changing the status of a purchase order, sales order, or any other document that has a defined status management process.
  Cause:
  
  Authorization Issues: The primary cause of this error is that the user does not have the required authorization roles or permissions to change the status of the specific document or object.
  Role Configuration: The roles assigned to the user may not include the necessary authorizations for the transaction or object type they are trying to modify.
  Document Status: The document may be in a status that is not allowed to be changed by the user based on the business rules configured in the system.
  
  Solution:
  
  
  Check User Authorizations:
  
  Verify the user's roles and authorizations using transaction code SU53 immediately after the error occurs. This transaction shows the last authorization check and can help identify which specific authorization is missing.
  Consult with your SAP security team or administrator to review and adjust the user's roles as necessary.
  
  
  
  Role Adjustment:
  
  If the user requires additional authorizations, the security team can modify the user's role or create a new role that includes the necessary permissions to change the status of the document.
  Ensure that the role includes the relevant authorization objects, such as F_BKPF_BES for accounting documents or other relevant objects based on the context of the error.
  
  
  
  Document Status Review:
  
  Check the current status of the document. If the document is in a status that is not allowed to be changed (e.g., completed, locked, etc.), the user may need to follow a different process to change the status or request assistance from someone with the appropriate permissions.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or internal guidelines related to the specific transaction or object type to understand the authorization requirements and status management rules.
  
  
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to authorization checks include SU01 (User Maintenance), PFCG (Role Maintenance), and SU53 (Authorization Check).
  Authorization Objects: Familiarize yourself with relevant authorization objects that may be required for the specific transaction or document type.
  SAP Notes: Check for any SAP Notes related to the specific error message or transaction for additional guidance or known issues.
  
  If the issue persists after checking authorizations and roles, it may be necessary to escalate the matter to your SAP support team for further investigation.