How To Fix WGDS_ENH135 - Variant Class can be changed only after saving the converted variants

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_ENH -

• Message number: 135

• Message text: Variant Class can be changed only after saving the converted variants

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 WGDS_ENH135 - Variant Class can be changed only after saving the converted variants ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WGDS_ENH135 Variant Class can be changed only after saving the converted variants
  
  Cause:
  This error occurs in the context of SAP Variant Configuration (LO-VC), specifically when working with variant classes and converted variants in the Classification system.
  
  When you convert characteristics or classes (e.g., during migration or enhancement of variant configuration), the system creates converted variants.
  These converted variants must be saved before you can change the variant class assigned to them.
  If you attempt to change the variant class before saving the converted variants, the system throws this error to prevent inconsistencies or data loss.
  
  
  Explanation:
  
  The variant class is a classification object that groups characteristics and variants.
  During conversion or enhancement, the system temporarily holds the converted variants in an unsaved state.
  Changing the variant class while these variants are unsaved could lead to data integrity issues.
  Therefore, SAP enforces saving the converted variants first.
  
  
  Solution:
  
  
  Save the converted variants first:
  
  Go to the transaction or screen where the converted variants are displayed.
  Save all the converted variants.
  
  
  
  After saving, change the variant class:
  
  Once the variants are saved, you can proceed to change the variant class without encountering the error.
  
  
  
  If you are unsure where to save:
  
  Typically, this happens in transactions related to variant configuration or classification, such as:
  
  CL02 (Change Class)
  CT04 (Change Characteristic)
  Or during migration/conversion tools for variant configuration.
  
  
  Look for a "Save" button or menu option to commit the converted variants.
  
  
  
  Check for background jobs or batch processes:
  
  Sometimes, conversion is done via batch jobs or reports.
  Ensure these jobs have completed successfully and saved the variants.
  
  
  
  
  Additional Information:
  
  This message is part of the SAP Classification and Variant Configuration module.
  It ensures data consistency between variant classes and their associated variants.
  If you repeatedly encounter this error, review your process flow for variant conversion and saving.
  Consult SAP Notes or OSS messages if the problem persists after saving.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Attempting to change variant class before saving converted variants.
  
  
  Effect
  System blocks the change to prevent data inconsistency.
  
  
  Solution
  Save all converted variants first, then change the variant class.
  
  
  Related Areas
  Variant Configuration (LO-VC), Classification (CL02, CT04), Variant Conversion processes.
  
  
  
  
  If you need help with the exact transaction or step to save the converted variants, please provide more context about where and how you are performing the change.