How To Fix VCH_HL_CORE038 - Configuration not saved. Upward changes detected.

SAP Error Message - Details

• Message type: E = Error

• Message class: VCH_HL_CORE - Variant Configuration Core Function

• Message number: 038

• Message text: Configuration not saved. Upward changes detected.

What causes this issue?

In this configuration model, instances on lower BoM levels trigger the
assignment of characteristic values on higher-level instances.
Those calculated values would lead to a changed BoM explosion result for
the respective higher-level instances. This is not supported in
multi-level configuration.

System Response

The system detected this situation and therefore does not allow you to
save the configuration with a released status.

How to fix this error?

Please verify whether you configured your model in a top-down manner.
Make sure you assign values manually to characteristics on higher-level
instances. These would otherwise get calculated value assignments
propagated from lower-level instances.
Constraints in the configuration model cause such propagations of
calculated values between instances. Therefore, if configuring in a
top-down manner is not an option for you, contact your configuration
modeling expert.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VCH_HL_CORE038 - Configuration not saved. Upward changes detected. ?

  The SAP error message VCH_HL_CORE038: Configuration not saved. Upward changes detected typically occurs in the context of SAP Variant Configuration (VC). This error indicates that there are changes in the configuration that are not allowed because they would result in an upward change in the configuration hierarchy. This means that the system has detected that the configuration you are trying to save would lead to a situation where the characteristics or values are being changed in a way that is not permitted according to the configuration rules.
  Causes:
  
  Hierarchy Violation: The configuration you are trying to save may violate the hierarchy defined in the variant configuration. For example, if you are trying to change a characteristic value that is not allowed due to the existing configuration structure.
  Dependencies: There may be dependencies or constraints defined in the configuration that prevent certain changes from being made.
  Incorrect Configuration: The configuration might be set up incorrectly, leading to conflicts when trying to save changes.
  
  Solutions:
  
  Review Configuration Settings: Check the configuration settings and ensure that the changes you are trying to make do not violate any hierarchical rules or dependencies.
  Check Dependencies: Review the dependencies and constraints defined for the characteristics in the configuration. Make sure that the changes you are attempting to make are allowed.
  Use Lower-Level Changes: If you need to make changes, consider making them at a lower level in the configuration hierarchy, if applicable.
  Consult Documentation: Refer to the SAP documentation for Variant Configuration to understand the rules and constraints that apply to your specific scenario.
  Debugging: If you have access to debugging tools, you can trace the configuration process to identify where the upward change is being detected.
  Consult with SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CU01 (Create Configuration Profile), CU02 (Change Configuration Profile), and CU03 (Display Configuration Profile) to manage variant configurations.
  Training and Documentation: Consider training or reviewing documentation on Variant Configuration to better understand how to manage configurations and avoid such errors in the future.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.