How To Fix /UI2/WD_CFG106 - Unable to save object &1 &2

/UI2/WD_CFG106 - Overview

• Message type: E = Error

• Message class: /UI2/WD_CFG -

• Message number: 106

• Message text: Unable to save object &1 &2

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 /UI2/WD_CFG106 - Unable to save object &1 &2 ?

  The SAP error message /UI2/WD_CFG106 Unable to save object &1 &2 typically occurs in the context of SAP Fiori or Web Dynpro applications when there is an issue with saving configuration objects. The placeholders &1 and &2 usually represent the type of object and its name, respectively.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to save the configuration object.
  Locking Issues: The object might be locked by another user or process, preventing changes from being saved.
  Data Consistency: There may be inconsistencies or errors in the data being saved, such as missing required fields or invalid values.
  Technical Errors: There could be underlying technical issues, such as database connectivity problems or system performance issues.
  Transport Issues: If the object is part of a transport request, there may be issues with the transport configuration or status.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to modify and save the object. This can