How To Fix SRM_VIEWGEN013 - Activity not supported

SRM_VIEWGEN013 - Overview

• Message type: E = Error

• Message class: SRM_VIEWGEN - No nodes were selected

• Message number: 013

• Message text: Activity not supported

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 SRM_VIEWGEN013 - Activity not supported ?

  The SAP error message SRM_VIEWGEN013: Activity not supported typically occurs in the context of SAP Supplier Relationship Management (SRM) when a user attempts to perform an action that is not allowed or supported in the current context or configuration. This error can arise from various scenarios, including issues with user authorizations, system configuration, or the specific transaction being executed.
  Possible Causes:
  
  Authorization Issues: The user may not have the necessary permissions to perform the action they are trying to execute.
  Configuration Settings: The system may not be configured to support the specific activity or transaction.
  Incorrect Transaction Code: The user might be using an incorrect or deprecated transaction code.
  Business Process Restrictions: Certain business processes may restrict specific activities based on the current status of documents or workflows.
  System Bugs or Limitations: There may be known bugs or limitations in the version of SAP SRM being used.
  
  Solutions:
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary roles