How To Fix /PLMU/PPE_ENG_UI104 - Editing of the variant configuration data failed

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMU/PPE_ENG_UI -

• Message number: 104

• Message text: Editing of the variant configuration data failed

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 /PLMU/PPE_ENG_UI104 - Editing of the variant configuration data failed ?

  The SAP error message /PLMU/PPE_ENG_UI104 Editing of the variant configuration data failed typically occurs in the context of variant configuration in SAP, particularly when working with the Product Lifecycle Management (PLM) module. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to edit the variant configuration data.
  Data Inconsistencies: There may be inconsistencies or errors in the configuration data itself, such as missing or incorrect entries.
  Technical Issues: There could be technical problems, such as system performance issues, database locks, or temporary system errors.
  Configuration Settings: Incorrect settings in the variant configuration or the related master data can lead to this error.
  Missing Dependencies: If the configuration relies on certain dependencies that are not met, it can cause editing to fail.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to edit variant configuration data. This can be done by checking the user's roles and permissions in the SAP system.
  Review Configuration Data: Examine the variant configuration data for any inconsistencies or errors. This may involve checking the characteristics, values, and dependencies defined for the product.
  System Performance: If the error is due to system performance, consider checking for any ongoing background jobs or database locks that may be affecting the system. You may need to wait for these processes to complete.
  Configuration Settings: Verify the configuration settings in the variant configuration profile and ensure that all required settings are correctly defined.
  Check Dependencies: Ensure that all dependencies required for the configuration are correctly defined and available. This may involve checking the configuration model for any missing links or conditions.
  Consult Logs: Check the SAP application logs (transaction SLG1) for more detailed error messages that can provide additional context about the failure.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide patches and updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CU50 (Configuration Profile) and CU01 (Create Configuration Profile) for managing variant configurations.
  Documentation: Review SAP documentation related to variant configuration and PLM for best practices and troubleshooting steps.
  Support: If the issue persists, consider reaching out to SAP support for assistance, providing them with detailed information about the error and the context in which it occurred.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.