How To Fix WZ120 - Function deactivated

WZ120 - Overview

• Message type: E = Error

• Message class: WZ - Workflow: Model objects

• Message number: 120

• Message text: Function deactivated

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 WZ120 - Function deactivated ?

  SAP Error Message:
  WZ120 - Function deactivated
  
  
  Cause:
  The error message WZ120 - Function deactivated typically occurs when a user tries to execute a function or transaction that has been deliberately deactivated or restricted in the SAP system. This can happen due to:
  
  The function/module is not released for use in the current system/client.
  The function is disabled via system parameters or user authorizations.
  The function is part of a business process that is currently blocked or not allowed.
  Custom developments or SAP standard functions that are switched off via configuration or user exit.
  
  
  
  Solution:
  To resolve the WZ120 - Function deactivated error, consider the following steps:
  
  
  Check Authorization:
  
  Verify if the user has the necessary authorizations to execute the function.
  Use transaction SU53 immediately after the error to check missing authorizations.
  Adjust roles/authorizations accordingly.
  
  
  
  Check System Configuration:
  
  Some functions are controlled via IMG settings or system parameters.
  Consult the relevant IMG node or configuration to see if the function is deactivated.
  For example, in some modules,