How To Fix /MOC/UI013 - No authorization to display change log for activity, contact admin

/MOC/UI013 - Overview

• Message type: E = Error

• Message class: /MOC/UI -

• Message number: 013

• Message text: No authorization to display change log for activity, contact admin

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 /MOC/UI013 - No authorization to display change log for activity, contact admin ?

  The SAP error message /MOC/UI013 No authorization to display change log for activity, contact admin indicates that the user does not have the necessary authorizations to view the change log for a specific activity in the SAP system. This is a common issue related to user roles and permissions.
  
  Cause:
  
  Missing Authorization Object: The user lacks the required authorization object that allows access to the change log functionality.
  Role Assignment: The user may not have been assigned the appropriate role that includes the necessary permissions.
  Profile Issues: The user’s profile may not be correctly configured to allow access to the change log.
  System Configuration: There may be system-wide settings that restrict access to certain functionalities based on user roles.
  
  
  Solution:
  
  
  Check User Roles:
  
  Verify the roles assigned to the user in transaction SU01 (User Maintenance).
  Ensure that the user has the necessary roles that include access to the change log.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after encountering the error