How To Fix FSH_ARUN_MSG129 - User &1 is not authorized

FSH_ARUN_MSG129 - Overview

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 129

• Message text: User &1 is not authorized

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 FSH_ARUN_MSG129 - User &1 is not authorized ?

  The SAP error message FSH_ARUN_MSG129 indicates that a user is not authorized to perform a specific action or access certain data within the SAP system. This error typically arises in the context of financial or accounting transactions, where user roles and authorizations are strictly enforced.
  
  Cause:
  
  Insufficient Authorizations: The user does not have the necessary roles or authorizations assigned to their user profile to perform the action they are attempting.
  Role 
  Configuration Issues: The roles assigned to the user may not include the required permissions for the specific transaction or data access.
  User Status: The user account may be locked or inactive, preventing access to certain functionalities.
  Transaction Restrictions: Certain transactions may be restricted based on organizational policies or configurations.
  
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Review the roles assigned to the user and ensure that they include the necessary authorizations for the action being attempted.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53