How To Fix R7020 - Char.&1 has vers.&2 hierarchy; hierarchies must remain version-dependent

R7020 - Overview

• Message type: E = Error

• Message class: R7 - BW: Data basis

• Message number: 020

• Message text: Char.&1 has vers.&2 hierarchy; hierarchies must remain version-dependent

What causes this issue?

The hierarchy settings for characteristic &V1& have been changed from
'version-dependent' to 'not version-dependent'. Characteristic &V1&,
however, already has version &V2& hierarchies.

System Response

Characteristic &V1& cannot be activated.

How to fix this error?

Delete all the hierarchies from characteristic &V1& that have a version
that is not empty. You are now able to activate the characteristic.

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 R7020 - Char.&1 has vers.&2 hierarchy; hierarchies must remain version-dependent ?

  The SAP error message R7020 indicates that there is an issue with the hierarchy of a characteristic in a version-dependent context. This error typically arises when you are trying to use a characteristic that has been defined with a specific version, but the system is expecting a version-independent hierarchy.
  
  Cause:
  The error message "Char.&1 has vers.&2 hierarchy; hierarchies must remain version-dependent" usually occurs due to one of the following reasons:
  
  Version Dependency: The characteristic in question is defined with a version-dependent hierarchy, but the operation you are trying to perform requires a version-independent hierarchy.
  Incorrect Configuration: The configuration of the characteristic or the hierarchy might not align with the expected settings in the system.
  Data Inconsistency: There may be inconsistencies in the data or settings related to the characteristic or its hierarchy.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Hierarchy Settings:
  
  Go to the configuration settings for the characteristic in question and verify if