How To Fix /ACCGO/UIS_MSG363 - Authorization failed to make events obsolete

/ACCGO/UIS_MSG363 - Overview

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 363

• Message text: Authorization failed to make events obsolete

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 /ACCGO/UIS_MSG363 - Authorization failed to make events obsolete ?

  The SAP error message /ACCGO/UIS_MSG363 indicates that a user does not have the necessary authorization to make events obsolete in the system. This typically occurs in the context of the SAP General Ledger or the SAP Accounting system, where certain actions require specific authorizations.
  
  Cause:
  The error is caused by a lack of appropriate authorization in the user's role or profile. The specific authorization object that is usually involved in this scenario is S_TCODE (Transaction Codes) or other authorization objects related to the specific transaction or function being executed.
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs. This will show you the last authorization check and help identify which specific authorization is missing.
  
  
  
  Review Role Assignments:
  
  Check the roles assigned to the user in transaction SU01 (User Maintenance) or PFCG (Role Maintenance). Ensure that the user has the necessary roles that include the required